F1 Self-Evaluation Project Explanations/pages 001-010

001 002 003 004 005 006 007 008 009 010

001

This page appears to begin a new Section, so leave two blank lines above the heading at the top.

Enclose each of the tables in no-wraps and right-align the numbers. The column-position of those numbers may vary, so a 'diff' due to that is not an error in any sense. The Guidelines request that we try to keep line length under 75 characters when possible, as it was on this page. Using the same alignment for all three groups of numbers will win you favor with the Post-Processor. We remove the "guide dots" in accordance with the Guidelines, and use dashes, not underscores, to draw the horizontal lines.

002

All of the comments for 001 apply here; they were consecutive pages in the original book.

003

The proofers did a reasonably good job in aligning the columns, which gives us a good headstart.

Some rules about tables:

1. if possible, they should be less than 75 characters wide.

2. it is not always possible to do that; just do your best.

3. in-line tags have to be handled according to how they will look in Plain Text, not how they look with our angle-tags.

4. tables are enclosed in no-wraps to protect all of your hard work from being rewrapped in post-processing.

5. column headings are parts of the table and go inside those no-wraps; table headings are not parts of the table and go outside the no-wraps.

6. draw horizontal lines with hyphens, not underscores or macrons; draw vertical lines with the vertical bar; draw their intersections with plus signs.

7. we have considerable creative latitude in rearranging the data to meet as many of these criteria as possible.

With those in mind, here's one way to approach this particular table:

There are some italics entries in the first column, and we want to allow for that before doing the rest of the alignment.

First of all, tables are constructed from cells, so the third phrase in italics ("ash from insoluble matter included on weights given") will be enclosed in one set of tags, not three. Do that, and tag the other two phrases as well.

Next, we must account for the fact that, in Plain Text, italics will look like _italics_ (one underscore on each side, not three characters on one side and four on the other). You can temporarily replace all of the opening tags with a symbol that does not appear in the text, and replace all of the closing ones with a different unique symbol. (If there also was boldface, their tags would be temporarily replaced by two other unique symbols; same for <g> and <f>, but not for <sc>, as it takes no extra space in Plain Text.)

Once these preparations are complete, begin the alignment. Doing all of the rows (cells) in the first column, then the second, etc., is one way to keep track of what's been done and what remains, and at the same time being able to keep track of how wide the table is becoming.

You can leave extra spaces between the columns and rows as you progress, and add the separator lines at the end; or draw those horizontal and vertical lines as you go; whichever you find easier to do is fine.

After the first pass, the formatter found that the table, including the vertical lines and the temporary symbols used for the italics, was considerably wider than 80 characters. Re-arranging the first column brought the width down to 80. Further re-arrangement, and hyphenating "Mirabelle" in the second column heading, could do the rest, but might not be what the Post-Processor would want, so formatting ended at this width.

Finally, after making sure everything does line up and the horizontal / vertical lines are in place, straight, and with plus signs at their intersections, we have to remember to replace the temporary symbols with the actual <> in-line tags. Once that's done, the table won't appear to be aligned, but when you see it published, it'll look beautiful.

004

This page is good practice for people not used to reading languages like German: our eyes are not trained to spot gesperrt, so we must be especially careful to find it (4 occurrences on this page).

The extra whitespace between the paragraphs is how the entire book was printed, so it's not a thought break. However, you can't know that just by looking at one page.

005

Easy-to-find boldface and lots of not-so-easy-to-find small caps. All of the small-caps on this page are all-caps small-caps; they are abbreviations, so the periods, which stand for omitted letters, go INSIDE the small-caps tags.

006

A classic, simple Index. Just follow the Guidelines for Indexes: dp:faq/document.php#bk_index Note that the extra horizontal space in "thickness" is not gesperrt but a means the typesetter has used to even the spacing across the line to avoid large clumps of white space. Gesperrt is not usually a technique used in English language projects.

007

Same as 006.

008

The first sub-entry is a continuation of the last sub-entry on the previous page, so it is not indented.

The rest is the same as 006.

009

Same as 006. This page actually shows sub-entries on separate lines, rather than using semi-colons, so the line-splitting has been done for you. Remember B is not bold because it is a heading. "Babes-Ernst" is in small capitals though because names are small capped throughout this index, for example, "Appert" and "Aristotle".

010

The period after the italics phrase belongs to the sentence, not to the phrase, so it goes OUTSIDE the tags.

And the main reason for including this page is the hard-to-find italicized "h" near the bottom.

Greek never is italicized, even though it often looks that way in the original books. But, it can be bold or in small-caps (although not on this page).