First version of a python script which builds a Modulo:Dati page/... parsing Index and produces a running Lua script (first test using it:Indice:Georgiche.djvu producing Modulo:Dati/Georgiche.djvu). This means that Modulo:Dati/... pages could be built and updated both automagically (by an #irc bot) and manually (by javascript, or by a interactive bot).
Alex 2013/6/7 Alex Brollo <[email protected]> > Strategy 3 is extremely interesting, from the "if you are repeating > yourself, you are going wrong" point of view. Nevertheless such an approach > needs a well-designed and complete "chapters tree" as step one; the best > would be that titles of sections/subsections could be wrote one only to > avoid any possible mistake. > > A simple Excel page (or similar) would be probably the simplest way to > produce the template code to be seeded into pages containing the start of > chapters and ignoring other pages. > > With very few simple conventions, anything - but pagelist - could be > automatized, if a thorough seeding of such templates could be done as > proofreading step 1, since a script could add too needed section tags, then > build pages tags and fill chapter list into Index page, and all the needed > code for ns0 pages/subpages. > > > > 2013/6/7 Andrea Zanni <[email protected]> > >> >> ..... >> >> I wonder if there is a better way to define the logic structure of our >> book, maybe directly in the Index page. >> I don't know what would be easier for the user: >> * define the table of content once for all in the Index page >> * define the table of content once in the book Toc (there is often one, >> if not always, when needed) >> * define the table of content just putting templates thorough the book, >> as the reader goes through the book. >> >> What do you all think? >> >> Aubrey >> >> >> >
_______________________________________________ Wikisource-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikisource-l
