Template talk:Number

More adjustments
Thanks for adding another parameter nb for removing the brackets, as I requested elsewhere.

I have still some issues with the appearance at Ethics (Aristotle)/Book Eight. That would make the use of the template in the mentioned book perfect. --Dan Polansky 15:17, 13 June 2008 (UTC)
 * 1) The number appears at the very right border of the browser window, whereas I would like to see it next to the right border of the page. Is there a way, either using existing parameters, or by modifying the template code and adding new parameters, or by modifying the template's default behavior, how to achieve this?
 * 2) I would like to format the appearance independently of the anchor name, like "1984a", that is "1984a", while having 1984a as the anchor, for referring to using Page_name#1984a. Could you add an anchor parameter which defaults to the first parameter?


 * I've removed all formatting from the number template, and added a second (optional) parameter for the anchor. Now you can format the number however you want.  This is how I should have done it in the first place as I anticipated requests like yours.  The "nb" parameter is no longer required.  As far as getting the anchor to appear closer to the text, the easy answer is to replace ... with ... (or you can play with the 2 parameters to get it to appear as you wish).  This has the side effect of centering the text in the browser window, but I'm not sure how to get around that at the moment, if that even matters...most of my css knowledge is of the monkey see monkey do variety.--T. Mazzei 02:39, 14 June 2008 (UTC)

Positioning
I have added a parameter "class" to enable various options for positioning, including the option to position the number to the right of the text that is within a DIV of the "lefttext" class. However, the positioning for that class has only been finetuned for display; the finetuning for printing is currently missing. --Dan Polansky 12:42, 14 June 2008 (UTC)

Faulty positioning with ProofreadPage
This template doesn't work so well with ProofreadPage extension. Take a look at Page:Gesenius' Hebrew Grammar (1910 Kautzsch-Cowley edition).djvu/528, for example.

With the Monobook skin, the paragraph numbers on the margin appear with the scanned page behind them, on the right margin of the page.

With the Vector skin, the paragraph numbers on the margin appear with the typed text behind so that these numbers make the right-hand end of the line hard to read.

I don't know about other books, but in these books it is often important to use the side-by-side display of the digital text and the scanned page not just for editing and proofreading, but for reading, too, because Biblical Hebrew display in Windows XP is far from perfect and the reader has to verify the Hebrew passages with the scanned page. I received very heart-warming emails from professors of Hebrew: they really enjoyed the side-by-side display - except the positioning of the paragraph numbers.

A little CSS trick should probably fix it. Thanks in advance to the specialist who can do that. --Amir E. Aharoni (talk) 18:11, 2 May 2010 (UTC)


 * Placing sidenotes begin and sidenotes end in the header and footer allows the page numbers to display correctly, but may require scrolling left/right on smaller screens.--T. Mazzei (talk) 22:27, 2 May 2010 (UTC)


 * Thanks, but isn't it possible to enable it for all pages? Maybe i didn't make myself clear, but i am quite sure that it's needed not just in this book. --Amir E. Aharoni (talk) 06:40, 3 May 2010 (UTC)

Overlapping numbers
I use this template heavily for Gesenius' Hebrew Grammar through GHGmargin-letter.

Since the introduction of the "Layout"'s that the reader can choose the numbers overlap with the text no matter what layout i choose. See Gesenius' Hebrew Grammar/95. Paradigms of Feminine Nouns, for example. --Amir E. Aharoni (talk) 16:24, 2 November 2010 (UTC)
 * Prosody - thanks for your change. Now in Layouts 2 and 3 Gesenius' Hebrew Grammar looks better that it did before that big change and in Layout 1 it's reasonable, too. --Amir E. Aharoni (talk) 18:55, 2 November 2010 (UTC)