I agree, line numbers would be OK, since usually invisible. BUT! Those who reflow would get different line numbers. . . . On Tue, 23 Feb 2010, Joshua Hutchinson wrote:

I'd suggest a different direction. If you have a situation like that, don't bother with page numbers (since they do disturb the "flow" of reading).  Rather, in the index, use line numbers.  Most modern editors will happily tell you what line number you are currently on and even jump to a specific line number.  The line number in a text file is fixed, so it will be a consistent number to jump to and yet doesn't disturb the flow of reading in the text itself.

Now, before you say it, I realize this would require someone to write up a quick and dirty script/program to convert page numbers to line numbers in an index ... but it's doable.

Josh

On Feb 23, 2010, christine <lostpaces.dp@googlemail.com> wrote:

I have been following this conversation, and would like it to lead to a slight change in the PG pagination rule.

As post-processor at DP-Int, I often have the feeling of uploading unfinished works because I have to remove the pagination from the text files. I don't mind in novels, but for books with index, it is another matter.

Some time ago, I received a mail asking me why I format my page numbers as invisible in the html files. One of my reason is that I can not see the point of showing them, since most of everything is linked (TOC, LOI, Index, etc...)

When I started post-processing, I included the page numbers in the text files, and often had to remove them to have the project posted. When I asked about the reason, I received the answers "it disturbs", "there is no need for it, the reader can do a search", etc.

Now, it does not seem very logical to show them in a linked file (html) and leave them out in the text file. Doing a search is not a very good solution either, in most of the case, it is like searching for a Smith in a british telephon book, more finds than you care for.

As example: I am currently working on "The Life of Napoleon", one of the index entries says "N. returns to Paris". Well, searching for "Napoleon" or "Paris" in that project would brings too many finds, as for "returns" this would not bring you to the proper page either, because, there, you find "is driven back".

So, would it be possible to just relax that rule and let the volunteer decides *if* the pagination in the text file of a project is needed or not.

Christine (aka Lostpaces)

___________________________________________________________________________________________

_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d

I've seen paragraph numbers used as anchors in a few contexts. Line numbers also work if you use hidden anchors in the HTML. Webscriptions uses something along these lines, IIRC, with a small javascript box in the navigation frame displaying the current paragraph number. Won't work in epub or other derivative formats, though. -Bob On Tue, Feb 23, 2010 at 12:41 PM, Joshua Hutchinson <joshua@hutchinson.net> wrote:

True, but the text files usually aren't reflowed (we've all talked ad-naseum about how easy/hard that is to do, so I won't go back into that). Eventually, you run into limitations.  If you chose path X, the path Y people will not get what they want. Josh

On Feb 23, 2010, Michael S. Hart <hart@pglaf.org> wrote:

I agree, line numbers would be OK, since usually invisible.

BUT!

Those who reflow would get different line numbers. . . .