F1 Self-Evaluation Project Explanations/pages 381-390

From DPWiki
Jump to navigation Jump to search

381 382 383 384 385 386 387 388 389 390

381

The second paragraph (the first one's only 1 line long) is in a smaller font than the surrounding text, surrounded by extra whitespace, and is wrappable, so enclose it in block quotes.


382

The last paragraph is in a smaller font than the other text, preceded by extra whitespace, and is wrappable, so enclose it in block quotes.


383

Tag the illustrations and move them to paragraph breaks. The second one's already at such a break.

"Fig." is in mixed-case small-caps, and the figure's number is part of the identification of the illustration, so include it, and the ending period, in the same small-caps tag.

Most of the page is in a smaller font than the first few lines, and the text is wrappable, so a block quote is needed. On closer inspection, the last paragraph of the page ... whose indented first line is nicely concealed next to the illustration ... is in an even smaller font than what was used for the paragraph above it, so enclosing it in a separate pair of block quotes is appropriate.


384

Enclose the verse in no-wraps.

The first sentence after the verse is italicized; since it is a complete sentence, the exclamation mark goes INSIDE the italics tags.


385

Tag the illustrations and move them to paragraph breaks. "Fig." is in mixed-case small-caps, and the figure's number is part of the identification of the illustration, so include it, and the ending period, in the same small-caps tag.

The descriptive portion of the caption is not the same as its identification, even though both contain small-caps. Using semantic criteria, they should be tagged separately.

This is the first of a series of pages from the same project in which the original publication centered one- and two-line captions, and used hanging indented style on anything more than two lines. For consistency, the project manager asked that block markup not be used for hanging indents in captions.

The second sentence is a question, so the question mark belongs to the entire sentence and goes OUTSIDE the italics tags.

386

Similar to page 385, above.

The in-line headings are in boldface. The second one is a complete sentence, so the period goes INSIDE the tags.

387

Similar to page 385, above.

"gills" is boldface, and the size at which your computer displays the image may make that harder to notice.


388

Similar to 385 and 386, above. If you placed the [Illustration] tags at different paragraph breaks from the ones in the Model, that's fine.

389

Some italics and some boldface. The in-line heading is boldface and a complete sentence for formatting purposes, so the period goes INSIDE the tags.

Precede the Section heading with two blank lines. The heading is in mixed-case small-caps, so tag it.


390

Similar to page 385, above.

Tag the illustration; it's already at a paragraph break and doesn't need to be moved. "Fig." is in mixed-case small-caps, and the figure's number is part of the identification of the illustration, so include it, and the ending period, in the same small-caps tag.

Enclose the table in no-wraps; it's title is wrappable and goes outside those tags. Part of that title is boldface and part is normal weight, so tag the boldface portion. Draw the gridlines using hyphens (not underscores or macrons) and vertical bars, and plus signs at their intersections. The double border in this case was replicated using equals signs--note that the + sign between Fish and Tadpole is off by one in the sample document.

The headings in the table are in small-caps. Since small-caps are converted to all-caps in the Plain Text version of the eBook, they will take no extra space, so the easiest way to align this table is to do so before adding those tags. When a table contains italics and/or boldface, it's necessary to use placeholders for the tags before aligning the columns, and replacing them with actual tags afterwards.