Index talk:Illustrated Bible Dictionary (1893).djvu

Proofreading Guidelines

• Sample page is page 2.
• Do not break page text into columns in the Page body. (The page header and footer have {{Div col}} for Page space display only.)
• Include first and last page entry in header in ALL CAPS. Header format is {{c|FIRST{{gap|8em}}page#{{gap|8em}}LAST}}.
• Bold the name and following comma for each entry, as in A′aron,.
• Use the symbol prime (′), not quote (') in the entry name, as in A′aron,.
• Use caps for B.C. and A.D.

Illustrations

• Use commons:Category:Illustrated Bible Dictionary (1893) for storing and linking illustrations.
• When linking to images, use

[[File:Example.jpg|frameless|400px|center]] for images as wide as the page

[[File:Example.jpg|frameless|200px|center]] for images one column width

[[File:Example.jpg|frameless|100px|left/right]] for images half a column width

[[File:Example.jpg|frameless|66px|left/right]] for images one-third a column width

Proofreading Guidelines Discussion

@Billinghurst:

1. Can this book go forward with a problematic image with no known solution? If so, can you help me with this layout? See Page 2. My questions are:
2. Does it make sense to use {{c|AARON{{gap|8em}}2{{gap|8em}}ABANA}} as a header, or should {{running header}} be used?
3. Does it make sense to put {{Div col}} in the header and footer so that Page view shows columns? I thought this might be easier for validation, but I don't know how or if it impacts ebooks.

Help appreciated! Outlier59 (talk) 15:47, 21 June 2016 (UTC)

1. Sure, the work won't be WS:FT-level, however, the work remains credible and usable. (Would the library throw the book away if a page was ripped out?)
2. If you truly want the header to look "woopee", you go for it. I don't bother, to me the header is of low value in our (transcluded) presentation for the web, so I set up an approximation (in the Index: page) and move on.
3. Columns can just ugly when trying to represent a book with a fixed page width, onto the web with a variable page width (and even more uncertainty with different mediums like ebooks and mobiles). IMNSHO too much work, no valuable return. We ditched that approach long ago with the DNB as it is a presentation form used to get most text possible onto a page as undertaken by the publisher. AND a readability issue well recognised even then is that when you use small font, you cannot have long long lines. Our presentation issues are different on the web, so we are not beholden to the means of 19thC typographers which are of little value, or problematic for us.

These are my opinions, though #3 is also guidance on our practice. — billinghurst sDrewth 23:44, 21 June 2016 (UTC)