Korea
Just an amateur hobbyist trying to learn more about programming and distributed workflows.
From mieum to ~mieum/booksin.space
Would you like me to wait on this until we decide about the gempub generation mechanism/syntax? ~mieum
From mieum to ~mieum/booksin.space
> I like this. Simple, and it automatically includes chapter titles to > the index/ToC. In that case then we'd either need to start numbering > headers in the gemtext itself or have the converter script auto-number > the chapters, because gemtext doesn't auto-number for us usually. Is the purpose of the numbering just to preserve the order of the chapters when generating the gempub? > I don't really like specifying the names of the chapters in the heading, > but I do like the automatic generation for when manual labelling isn't > needed. Like we could have a key where every h1 is a chapter, or every > h2, or every h1 and h2, etc. For my The King in Yellow (as an example), > you could split on every h2 and to split on chapters I think.
From mieum to ~mieum/booksin.space
> So is that a nack on possibly adding YAML (or something) throughout the > document to indicate where to break apart a file into separate files? Sorry, I didn't realize you were suggesting that. I think I have been dazed by the suddenly summery weather here @_@ > Thinking about it more it wouldn't add that much more for contributors > (just add markup every chapter break while you're converting to gemtext) > and it'd be pretty easy to convert from the one-page format to gempub if > you have actual markers on where to split it up (and also some > indication of what to title each chapter in the index file). So, for instance, headings preceeded by a '%' could indicate a chapter? The added bonus of doing something like this is being able to automatically generate a ToC or break up long texts by chapter for
From mieum to ~mieum/booksin.space
> > Should this file have a title heading + byline? Is it preferrable to > > programatically insert those using the metadata, or to have > > contributors format submissions with a title and byline themselves? > I think it should. In my opinion (I don't know what you envisioned), > you should be able to strip out all YAML and other such elements and get > a standalone gemtext document without having to make any modifications, > which means it should include all title, byline, and possibly copyright > info at the bottom. That's more or less how I had pictured it, although I think I had planned on appending the license/attribution postabmble to each item programatically. That way I can keep things consistent, and link the the appropriate license text when necessary etc. I had a good think about it today after reading your reply. It is less work to have the license and
From mieum to ~mieum/booksin.space
> > I think gempubs are a great idea! Is there a particular reason you > > suggest them to be optional? > It is a minor to major amount of extra work when making them by hand, > and I didn't want to burden extra contributors too much. ... > I'd say that properly splitting up an arbitrary book into a gempub > programatically (without manual intervention and reediting at least) > would be very difficult. ... > It'd probably be easy to to throw together a script to run down the > index.gmi line-by-line and concatenate like a real gempub reader would. > The reverse is hard, because how can you know whether a header is a > chapter or section that should be split up or a minor break that > shouldn't, and whether a section has stuff meant to come before it
From mieum to ~mieum/booksin.space
I accidentally responded direcrly to nytpu, so I'll re-reply to the list. I think gempubs are a great idea! Is there a particular reason you suggest them to be optional? It seems that gempub archives could be generated for each item easily enough at the time of cataloging. Either way, I will prepare to handle gempub submissions alongside a gemtext version, and I will at least devise a basic utility for generating them in the cataloging phase. Thanks nytpu! ~mieum
From mieum to ~mieum/booksin.space
> I've added the key "title" under "publication" in the YAML front- > matter to refer to the publication/magazine in which the story was > originally published. Ah, thanks, I'll update the template! And thanks for the patch tiis! It's been aplied and pushed. Lovecraft seems like a nice way to start populating these shelves :) ~mieum
From mieum to ~mieum/booksin.space
On Tue, Jun 08, 2021 at 07:11:17PM -0600, nytpu wrote: > To note: Like how the author metadata field is lastname, firstname for > sorting purposes, I made the title field have a suffix "the" to > facilitate sorting. Thank you! I'll add that to thr guidlines! > Also, if my proposal about including gempubs is accepted, there is a > gempub for The King in Yellow available here: > gemini://nytpu.com/gpubs/the-king-in-yellow.gpub > (I can send another patch adding it if necessary) I think I will just have the cataloguer build the gempubs from this gemtext file to keep things consistent. But I will reference that to
From mieum to ~mieum/booksin.space
Thanks for the patch tiis! I would love for Lovecraft to be the first book to get cataloged! I had a couple suggestions: > +author: H.P. Lovecraft I realized that author/editor fields should probably be formatted <Last name, First name> to facilitate sorting. I'll add that to the readme. > +--- > +(Found among the papers of the late Francis Wayland Thurston, of Boston.) > + > +> “Of such great powers or beings there may be conceivably a survival . . . a survival of a hugely remote period when . . . consciousness was manifested, perhaps, in shapes and forms long since withdrawn before the tide of advancing humanity ... forms of which poetry and legend alone have caught a flying memory and called them gods, monsters, mythical beings of all sorts and kinds. . . .”—Algernon Blackwood. > +
From mieum to ~adnano/gemini
Hey folks, I hope chiming in tangentially like this isn't a faux pas. I just wanted to say that I am grateful for all of you skilled and wise (and opinionated) people here on this list and Gemini at large. I consider myself among the most plebian of laymen, and have learned A LOT keeping an ear to the pavement about all things Gemini here. I am grateful that there are so many passionate and knowledgeable people caring about Gemini. In regard to the issue of this thread, I see many people whom I admire and respect expressing valid concerns about an important issue. I hope that all concerned parties here can hear each other, and that with this