Email list hosting service & mailing list manager

Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 09:46 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 16:10 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 16:44 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 16:54 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 17:10 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 18:58 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 21:15 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 17:28 UTC)
Re: Cookbook is now scraped and ready to browse Arthur A. Gleckler (08 May 2019 21:18 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 21:28 UTC)
Re: Cookbook is now scraped and ready to browse Lassi Kortela (08 May 2019 21:35 UTC)

Re: Cookbook is now scraped and ready to browse Lassi Kortela 08 May 2019 17:10 UTC

> Okay, I've downloaded a copy.

Thanks! Wayback Machine downloader was invaluable (there are well over
1000 HTML files).

> I agree.  I love Org mode, but Markdown is nice, too.  The only drawback
> of not using HTML directly is that it limits what we can express.  For
> my own blog, I write in S-expressions that map directly to HTML for this
> reason.

The HTML-as-S-expressions format actually sounds very reasonable. Maybe
we should first investigate what has the best tooling (or is easiest to
write new tools for). Would something Scribble-like work? That would be
close to HTML-as-Sexprs. Even Texinfo could be a contender - tons of
other Scheme documentation is using it so we'll have to write some tools
to index and render it at some point anyway.

> IANAL, as they say.  But I'm happy to follow their intent.

Agreed, that's the wise and polite way to go.

But if we don't get permission we'd probably have to start a new
cookbook from scratch at some point in order to give up-to-date advice
and cover more implementations. It'd be a shame if users had to keep
switching between two different cookbooks for the same job.

I just realized that we should keep authorship information for each
original wiki page in the scraped versions. I'll see if it's easy to
extract from the tar file. The nice thing with Wiki engines is they
produce very regular HTML markup.