Lars,
On enWS if you have the preload headers gadget activated it does this for you, RIDER, for
the subpages for Chapters to work I believe that it needs for the Title page to have the
links and it identifies where it is on the list and does prev/next. If necessary I can
try and work it out from Remember the Dot's script.
At enWS, we started (though didn't complete) a naming convention discussion, though
from
that many of us are now defaulting to Chapter 1 .. 10 .. XX, rather than other variations
(abbreviations, no chapter names, roman numerals, etc.) I have utilised Pathoschild's
regex script to build a little function() to identify the current page, and then do the
subsequent pages. So it needs me to click on my function link, however, it is fairly
simply achieved.
Regards Andrew
On 10 May 2010 at 10:39, Lars Aronsson wrote:
Is it true that {{header|previous= |next= }} must be
filled
in manually for each chapter? Couldn't this be automated
in the same way as ProofreadPage links "<" and ">" in a
linear sequence, if you provide the table of contents in
a central place? If that TOC contained the page number
intervals and sections, everything in the chapter page
could be automated, right?
Is it true that full text search leads to to the Page:
and not to the main namespace page that transcludes it?
And that the former has no link to the latter?
If I search "the right understanding of the machine",
I find
http://en.wikisource.org/wiki/Page:The_Kinematics_of_Machinery.djvu/24
but I don't find
http://en.wikisource.org/wiki/The_Kinematics_of_Machinery/Introduction
How could that be improved? Is another Extension necessary?
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik -
http://aronsson.se