Michael Jörgens wrote: Exactly! The ProofreadPage extension has solved half of the problem, so we no longer need to manually link to the previous/next scanned page. But we still have to deal with the other half of the problem: previous/next chapter. This should also be possible to solve with an extension, shouldn't it? -- Lars Aronsson (lars(a)aronsson.se) Aronsson Datateknik - http://aronsson.se

2010/5/11 Michael Jörgens <joergens.mic(a)googlemail.com> I'm facing with the same problem, but I think I'll use a different way: a bot job, to create chapters by the summary of chapters into main ns0 page or - better - from the summary into Index page. If such a summary is built once with sufficient care, adding too the relevant elements for pages index tag as a parameter (from, to, fromsection, tosection), I suppose that a bot could get all what it needs to build running chapters with prev and next parameters too. Alex_brollo

2010/5/11 John Vandenberg &lt;jayvdb(a)gmail.com&gt; Hi John, thanks, it's really excing! Can be,I'll upload a en.source text again just to see it at work. :-) Nevertheless, I'm working about something deeply different. Our bot browse recent changes, and reads content new/edited pages of "interesting" namespaces. By now, it does banal jobs; but I guess, we'll add more and harder works, both "automatic" (t.i. something the bot "decides by himself" browsing the content of the page) or "requested" (I imagine into html comment: the first I'll implement will be something like this: <!-- Alebot, please keep away from this page --> ;-) to block Alebot without blocking other bots). I used some html comment "bot directives" into the last work I uploaded, they run but they aren't addressed to the Recent Changes script. So, the mechanism will be browser-indipendent, since it will produce plain wiki code, just as a human diligent user; and it will be js-free too. I'll post news into my user WIP page if I'll got something decent (I'm not sure at all about!). But the en: pre-load idea is great, I'll try to study it, to customize it to it:source project! Alex_brollo

This may work on chapters, but I dislike replacing the true name by a number. And it wo't work on Books with poems were this two pointers got to the name of the previous and next poem. And it won't work on magazines, with lot of articles in. 2010/5/11 Billinghurst &lt;billinghurst(a)gmail.com&gt;

Michael, The mean reasons that we were looking to standardise chapter names is that we are now getting to the stage where we are putting in references to future books that we are planning to work upon. Ahead of time we don't know chapter names, or even if they have names, plus the references themselves usually refer to something like Ch.2, so they are already in that format. Some of that conversation is at http://en.wikisource.org/wiki/Wikisource_talk:Naming_conventions in all its glory. That is not to say that we don't use the chapter name in the header, as we do, it is just not in the subpage name. Poems? Poetry? Don't even know what that is! ;-) Regards Andrew <- poetry free zone On 12 May 2010 at 7:17, Michael Jörgens wrote: