Re: Awesome Books (in Markdown)
Please get me off of this email list. I have unsubscribed five times but I continue to receive Sent from my iPhone > On May 7, 2015, at 11:45 PM, Gerald Bauer wrote: > > Hello bowerbird, > > Wow. Thanks for highlight the gitenberg project and your great > comments and links. I had no clue. Have a great weekend. Cheers. > ___ > Markdown-Discuss mailing list > [email protected] > https://pairlist6.pair.net/mailman/listinfo/markdown-discuss ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Re: Awesome Books (in Markdown)
Hello bowerbird, Wow. Thanks for highlight the gitenberg project and your great comments and links. I had no clue. Have a great weekend. Cheers. ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
re: Awesome Books (in Markdown)
gerald said: > Again thanks for the great comments. sure thing. thanks for creating the resource. one thing i forgot. the most interesting thing about project gutenberg these days comes not from that project itself, but from an effort that calls itself "project gitenberg", which is putting the p.g. e-texts into github, or rather a customized iteration of github that had to be created when the number of repositories (one/book) overwhelmed the regular system. of course, the entire github infrastructure is ridiculously complicated overkill for a task as simple as managing the very small edits that are typical of a finished p.g. e-text, but someone had a hammer they wanted to use. and sure enough, someone else had money to fund grants for people to use hammers, so -- you know -- the effort now has some legs. the reason it's interesting, however, is that one of the first goals gitenberg set out was to transform the e-texts into .html and then e-book formats, which is the very thing that was my intent when i focused on p.g. in 1999. (what i've learned, over the last 35 years, is that i'm exactly 16 years "ahead of my time".) anyway... last i heard, gitenberg is leaning to asciidoc. that's a good plan, but they'll need to mod it. so, in the end, they'll have something that is exactly like z.m.l., light-markup for long-form. > https://github.com/GITenberg/gitenberg.github.com > https://groups.google.com/forum/#!forum/gitenberg-project > https://news.ycombinator.com/item?id=8214564 -bowerbird p.s. gitenberg could also be using "markua", which is scheduled to release an update on the alpha version of itself sometime _today._ markua is to be a markdown-inspired flavor that will be specially modified for long-form. so i guess you can say we have a trend now. for the record, asciidoc predated markdown, and it always had some focus on long-form. so did restructured-text, per its status as the light-markup used for python documentation. thus, once you start talking about _books_, markdown is lagging the field, considerably. but hey, it's never to late to muddy the waters! ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Re: Awesome Books (in Markdown)
Would it be helpful to think about digital image preservation? It seems to be a similar problem structure to what you are talking about. E.g. There is a https://en.wikipedia.org/wiki/Netpbm_format which aims to be the lowest common denominator imageformat. You convert images to a "Portable pixmap" and then reconvert to to another format. Maybe a commonly agreed upon Abstract Syntax Tree, between various lightweight markup format? -- # This is what a pbm file looks like (Easy to downconvert to, and easy to upconvert from): P1 # This is an example bitmap of the letter "J" 6 10 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 0 1 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 On Thu, May 7, 2015 at 4:48 PM, Gerald Bauer wrote: > Hello bowerbird, > >Again thanks for the great comments. > >Time to rediscover the classics and the Project Gutenberg! Will > try to get a Hemingway Challenge started in the next weeks. Stay > tuned. Cheers. > ___ > Markdown-Discuss mailing list > [email protected] > https://pairlist6.pair.net/mailman/listinfo/markdown-discuss ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Re: Awesome Books (in Markdown)
Hello bowerbird, Again thanks for the great comments. Time to rediscover the classics and the Project Gutenberg! Will try to get a Hemingway Challenge started in the next weeks. Stay tuned. Cheers. ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
re: Awesome Books (in Markdown)
gerald said: > the idea is to have the source > AND the rendered book in hypertext aha! great point. i see the utility now... > For Project Gutenberg you get the source > (but not a rendered book) which is where i entered this thread... :+) as, indeed, for some time, p.g. has offered .html versions of all its newly-done books, and even .epub and .mobi/kindle versions... once you understand the p.g. conventions, it's relatively easy to leverage them and generate .html at will. indeed, it was my effort to do that, at scale, for the whole library -- as it approached 10,000 books at the time -- which led me to first make z.m.l., during the period of 1998-2003... _however!_ the .html versions over at p.g. are usually _not_ auto-generated from their plain-text file... no, instead, the process by which the .html file is created is left to the individual in charge of the book, so that means each book is its own "snowflake", similar to each other, but "unique", in ways that are not apparent without close analysis. so inconsistencies in the e-text versions have been doubled in the .html versions! as you can imagine, this makes updating the library extremely difficult, virtually impossible. even the generation of the e-book formats has been fraught with problems due to that. back in 2003, i was unsuccessful in getting the p.g. powers-that-be to grok the power of z.m.l. to create and maintain a cyberlibrary. they constantly informed me a light-markup system "won't work" and mocked me for it. they wanted to use t.e.i. instead, while the minions who were doing the real work preferred to create their own snowflakes, and rolled their eyes at complex t.e.i. the conflict would've been comical, but their mistakes led to the decline and fall of the world's very first great cyberlibrary. 50,000 e-texts now, but a shadow of itself. > and for Leanpub you get the rendered book > but not the source. yeah, i've often thought that that's very ironic. you don't get the most useful version of the book. -bowerbird ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Re: Awesome Books (in Markdown)
Hello bowerbird, Thanks for the links. No worries about the name. Good point about Project Gutenberg. For the classics or any other books the idea is to have the source AND the rendered book in hypertext (HTML). For Project Gutenberg you get the source (but not a rendered book) and for Leanpub you get the rendered book but not the source. A good example in the awesome-books collection is the Pro Git book. >From the Markdown source you can generate the rendered book in different styles e.g. 1) -> http://git-scm.com/book/en/v1 or 2) -> http://gitbookio.gitbooks.io/progit/content/en/ Thanks again. Cheers. ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
re: Awesome Books (in Markdown)
gerald- gosh, i think that's the second time i've called you "gerard", instead of _gerald._ my apologies, again! -bowerbird ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
re: Awesome Books (in Markdown)
gerard said: > Might be great to get some classics > (in the public domain) > e.g. Shakespeare, Dickens and friends. your other page, gerard, gave a nod to other forms of light-markup, including restructured-text, asciidoc, textile, etc. so i'm unclear if this page now means "markdown" in the john-gruber sense, or a more-generic "light-markup" way. because project gutenberg was using light-markup -- i.e., a structured form of plain-text -- since its start in 1976... the "structure" was often a bit wobbly, as you would expect, given progress -- the earliest e-texts had no lower-case, originating on key-punch machines -- and it was only lightly "enforced" upon volunteers who comprise the project, and it was terribly inconsistent as well; _but_ it was solid enough, advanced enough, and consistent enough, that i used it as the foundation for my z.m.l., a light-markup that _targets_ long-form. so, you know... if you want examples, project gutenberg has 40,000-50,000. -bowerbird p.s. leanpub.com has a bunch as well. and the guys over there are, right now, developing "markua", their own flavor of markdown/light-markup for long-form... p.p.s. columbus didn't discover america. p.p.p.s. https://github.com/rhythmus/markdown-resources ___ Markdown-Discuss mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
