Professional Documents
Culture Documents
1 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
ID:
Password:
Register Help
(Revision History)
7/6/2010 9:41 PM
2 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Common Problems:
Formatting
Common OCR Problems
OCR Problems: Scannos
OCR Problems: Is that really a degree sign?
Handwritten Notes in Book
Bad Image
Wrong Image for Text
Previous Proofreader Mistakes
Printer Errors/Misspellings
Factual Errors in Texts
Inserting Special Characters
Alphabetical Index to the Guidelines
7/6/2010 9:41 PM
3 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
We do change minor typographical conventions that don't affect the sense of what the author wrote. For
example, we rejoin words that were broken at the end of a line (End-of-line Hyphenation). Changes
such as these help us produce a consistently formed version of the book. The proofreading rules we
follow are designed to achieve this result. Please carefully read the rest of the Proofreading Guidelines
with this concept in mind. These guidelines are intended for proofreading only. As a proofreader you are
matching the image's content while later the formatters will match the image's look.
To assist the next proofreader, the formatters, and the post-processor, we also preserve line breaks. This
allows them to easily compare the lines in the text to the lines in the image.
Back to top
Summary Guidelines
The Proofreading Summary is a short, 2-page printer-friendly (.pdf) document that summarizes the main
points of these Guidelines and gives examples of how to proofread. Beginning proofreaders are
encouraged to print out this document and keep it handy while proofreading.
You may need to download and install a .pdf reader. You can get one free from Adobe here.
Back to top
Project Comments
When you select a project for proofreading, the Project Page is loaded. On this page there is a section
called "Project Comments" containing information specific to that project (book). Read these before
you start proofreading pages! If the Project Manager wants you to do something in this book
differently from the way specified in these Guidelines, that will be noted here. Instructions in the Project
Comments override the rules in these Guidelines, so follow them. There may also be instructions in the
project comments that apply to the formatting phase, which do not apply during proofreading. Finally,
7/6/2010 9:41 PM
4 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
this is also where the Project Manager may give you interesting tidbits of information about the author
or the project.
Please also read the Project Thread (discussion): The Project Manager may clarify project-specific
guidelines here, and it is often used by proofreaders to alert other proofreaders to recurring issues within
the project and how they can best be addressed. (See below.)
On the Project Page, the link 'Images, Pages Proofread, & Differences' allows you to see how other
proofreaders have made changes. This forum thread discusses different ways to use this information.
Back to top
Double Quotes
Proofread double quotes as plain ASCII " double quotes. Do not change double quotes to single
quotes. Leave them as the author wrote them. See Chapter Headings if a double quote is missing at the
start of a chapter.
For quotation marks other than ", use the same marks that appear in the image if they are available. The
French equivalent, guillemets like this, are available from the pulldown menus in the proofreading
7/6/2010 9:41 PM
5 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
interface, since they are part of Latin-1. Remember to remove space between the quotation marks and
the quoted text; if needed, it will be added in post-processing. The same applies to languages which use
reversed guillemets, like this.
The quotation marks used in some texts (in German or other languages) like this are not available
in the pulldown menus, as they are not in Latin-1. They are often converted into guillemets like
this (or like this for languages that use the quotes this way), but be sure to check the
Project Comments in case the Project Manager has given different instructions.
The Project Manager may instruct you in the Project Comments to proofread non-English language
quotation marks differently for a particular book. Please be sure not to apply those directions to other
projects.
Back to top
Single Quotes
Proofread these as the plain ASCII ' single quote (apostrophe). Do not change single quotes to double
quotes. Leave them as the author wrote them.
Back to top
7/6/2010 9:41 PM
6 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
End-of-sentence Periods
Proofread periods that end sentences with a single space after them.
You do not need to remove extra spaces after periods if they're already in the OCR'd textwe can do
that automatically during post-processing.
Back to top
Punctuation Spacing
Spaces before punctuation sometimes appear because books typeset in the 1700's & 1800's often used
partial spaces before punctuation such as a semicolon or colon.
In general, a punctuation mark should have a space after it but no space before it. If the OCR'd text has
no space after a punctuation mark, add one; if there is a space before punctuation, remove it. This
applies even to languages such as French that normally use spaces before punctuation characters.
However, punctuation marks that normally appear in pairs, such as "quotation marks", (parentheses),
[brackets], and {braces} normally have a space before the opening mark, which should be retained.
Original Image:
and so it goes ; ever and ever.
Correctly Proofread Text:
and so it goes; ever and ever.
Back to top
7/6/2010 9:41 PM
7 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
For example, in A horse ; my kingdom for a horse. the space between the word "horse" and the
semicolon should be removed. But the 2 spaces after the semicolon are fineyou don't have to delete
one of them.
In addition, if you find any tab characters in the text you should remove them.
Back to top
Type
semi-detached
semi-detached
Hyphen
Hyphens
Hyphen
7/6/2010 9:41 PM
8 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Hyphen &
Em-dash
En-dash
En-dash
XY=Z
X - Y = Z
En-dash
21/2
2-1/2
En-dash
A plague on both
your houses!I am dead.
Em-dashes
sensations--sweet, bitter,
salt, and sour--if
even all of these are simple
tastes. What
Em-dashes
senses--touch, smell,
hearing, and sight--with
which we are here concerned,
Em-dashes
Em-dashes,
Hyphen,
& Long Dash
Long Dash
Long Dash
Long Dash
Long Dash
Em-dash
Back to top
7/6/2010 9:41 PM
9 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
to-*day. The asterisk will bring it to the attention of the post-processor, who has access to all the pages
and can determine how the author typically wrote this word.
Similarly, if an em-dash appears at the start or end of a line of your OCR'd text, join it with the other line
so that there are no spaces or line breaks around it. However, if the author used an em-dash to start or
end a paragraph or a line of poetry, you should leave it as it is, without joining it to the next line. See
Dashes, Hyphens, and Minus Signs for examples.
Back to top
On pages that start with part of a word from the previous page or an em-dash, place a * before the
partial word or em-dash. To continue the above example:
Original Image:
tomed to from having to do his own family
Correctly Proofread Text:
*tomed to from having to do his own family
These markings indicate to the post-processor that the word must be rejoined when the pages are
combined to produce the final e-book. Please do not join the fragments across the pages yourself.
Back to top
7/6/2010 9:41 PM
10 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
same number of periods as appear in the image. Sometimes the printed page is unclear; in that case,
insert a [**unclear] to draw the attention of the post-processor. (Note: Post-processors should replace
those regular spaces with non-breaking spaces.)
English examples:
Original Image:
Contractions
In English, remove any extra space in contractions. For example, would n't should be proofread as
wouldn't and 't is as 'tis.
This was a 19th century printers' convention in which the space was retained to indicate that 'would' and
'not' were originally separate words. It is also sometimes an artifact of the OCR. Remove the extra space
in either case.
Some Project Managers may specify in the Project Comments not to remove extra spaces in
contractions, particularly in the case of books that contain slang, dialect, or poetry.
Back to top
Fractions
Proofread fractions as follows: becomes 1/4, and 2 becomes 2-1/2. The hyphen prevents the whole
and fractional part from becoming separated when the lines are rewrapped during post-processing.
Unless specifically requested in the Project Comments, please do not use the actual fraction symbols.
Back to top
Accented/Non-ASCII Characters
Please proofread these using the proper symbols or accented characters to match the image, where
possible, including the use or non-use of accents. We can only use Latin-1 characters during
proofreading; if you aren't sure if a character is in the Latin-1 character set, check the tables below. If
they are not on your keyboard, see Inserting Special Characters for information on how to input these
characters during proofreading.
7/6/2010 9:41 PM
11 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
The character (oe ligature) is not in Latin-1, so we mark it with brackets like in man[oe]uvre, or
[OE]dipus for the capital . Note that the character (ae ligature, as in encyclopdia) is in Latin-1,
so that character should be inserted directly.
For other characters outside of Latin-1, see Diacritical marks for how to proofread accents or other
marks above or below Latin letters. For characters that are not addressed in these guidelines, see the
Project Manager's instructions in the Project Comments.
Back to top
[=x]
[x=]
[:x]
[x:]
1 dot
[.x]
[x.]
grave accent
[`x]
[x`]
['x]
[x']
circumflex
[^x]
[x^]
[vx]
[xv]
[)x]
[x)]
tilde
[~x]
[x~]
cedilla
[,x]
[x,]
Back to top
Non-Latin Characters
7/6/2010 9:41 PM
12 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Some projects contain text printed in non-Latin characters; that is, characters other than the Latin
A...Zfor example, Greek, Cyrillic (used in Russian, Slavic, and other languages), Hebrew, or Arabic
characters.
For Greek, you should attempt a transliteration. Transliteration involves converting each character of
the foreign text into the equivalent Latin letter(s). A Greek transliteration tool is provided in the
proofreading interface to make this task much easier.
Press the "Greek Transliterator" button near the bottom of the proofreading interface to open the tool.
In the tool, click on the Greek characters that match the word or phrase you are transliterating, and the
appropriate Latin-1 characters will appear in the text box. When you are done, simply cut and paste this
transliterated text into the page you are proofreading. Surround the transliterated text with the Greek
markers [Greek: and ]. For example, would become [Greek: Biblos]. ("Book"so
appropriate for DP!)
If you are uncertain about your transliteration, mark it with ** to bring it to the attention of the next
proofreader or the post-processor.
For other alphabets that cannot be so easily transliterated, such as Cyrillic, Hebrew, or Arabic, replace
the non-Latin characters or OCR garbage with the appropriate mark: [Cyrillic: **], [Hebrew: **],
or [Arabic: **]. Include the ** so the post-processor can address it later.
Greek: See the Transliterating Greek wiki page, Greek HOWTO from Project Gutenberg, or the
"Greek Transliterator" pop-up tool in the proofreading interface.
Cyrillic: While a standard transliteration scheme exists for Cyrillic, we only recommend you
attempt a transliteration if you are fluent in a language that uses it. Otherwise, just mark it as
indicated above.
Hebrew and Arabic: Not recommended unless you are fluent. There are significant difficulties
transliterating these languages and neither Distributed Proofreaders nor Project Gutenberg have
yet chosen a standard method.
Back to top
Superscripts
Older books often abbreviated words as contractions, and printed them as superscripts. Proofread these
by inserting a single caret (^) followed by the superscripted text. If the superscript continues for more
than one character, then surround the text with curly braces { and } as well. For example:
Original Image:
Genrl Washington defeated Ld Cornwall's army.
Correctly Proofread Text:
Gen^{rl} Washington defeated L^d Cornwall's army.
If the superscript represents a footnote marker, then see the Footnotes section instead.
The Project Manager may specify in the Project Comments that superscripted text be marked
differently.
Back to top
7/6/2010 9:41 PM
13 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Subscripts
Subscripted text is often found in scientific works, but is not common in other material. Proofread
subscripted text by inserting an underline character _ and surrounding the text with curly braces { and }.
For example:
Original Image:
H2O.
Correctly Proofread Text:
H_{2}O.
Back to top
Line Breaks
Leave all line breaks in so that later in the process other volunteers can easily compare the lines in the
text to the lines in the image. Be especially careful about this when rejoining hyphenated words or
moving words around em-dashes. If the previous proofreader removed the line breaks, please replace
them so that they once again match the image.
Back to top
Chapter Headings
Proofread chapter headings as they appear in the image.
A chapter heading may start a bit farther down the page than the page header and won't have a page
number on the same line. Chapter Headings are often printed all caps; if so, keep them as all caps.
Watch out for a missing double quote at the start of the first paragraph, which some publishers did not
include or which the OCR missed due to a large capital in the image. If the author started the paragraph
with dialog, insert the double quote.
7/6/2010 9:41 PM
14 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Back to top
Paragraph Spacing/Indenting
Put a blank line before the start of a paragraph, even if it starts at the top of a page. You should not
indent the start of the paragraph, but if it is already indented don't bother removing those spacesthat
can be done automatically during post-processing.
See the Sidenotes image/text for an example.
Back to top
7/6/2010 9:41 PM
15 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
7/6/2010 9:41 PM
16 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Illustrations
Ignore illustrations, but proofread any caption text as it is printed, preserving the line breaks. If the
caption falls in the middle of a paragraph, use blank lines to set it apart from the rest of the text. Text
that could be (part of) a caption should be included, such as "See page 66" or a title within the bounds of
the illustration.
Most pages with an illustration but no text will already be marked with [Blank Page]. Leave this
marking as is.
Original Image:
7/6/2010 9:41 PM
17 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
7/6/2010 9:41 PM
18 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Footnotes/Endnotes
Proofread footnotes by leaving the text of the footnote at the bottom of the page and placing a tag
where it is referenced in the text.
In the main text, the character that marks a footnote location should be surrounded with square brackets
([ and ]) and placed right next to the word being footnoted[1] or its punctuation mark,[2] as shown in
the image and the two examples in this sentence. Footnote markers may be numbers, letters, or symbols.
When footnotes are marked with a symbol or a series of symbols (*, , , , etc.) we replace them all
with [*] in the text, and * next to the footnote itself.
7/6/2010 9:41 PM
19 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
At the bottom of the page, proofread the footnote text as it is printed, preserving the line breaks. Be sure
to use the same tag before the footnote as you used in the text where the footnote was referenced. Use
just the character itself for the tag, without any brackets or other punctuation.
Place each footnote on a separate line in order of appearance, with a blank line before each one.
Do not include any horizontal lines separating the footnotes from the main text.
Endnotes are just footnotes that have been located together at the end of a chapter or at the end of the
book, instead of on the bottom of each page. These are proofread in the same manner as footnotes.
Where you find an endnote reference in the text, just surround it with [ and ]. If you are proofreading
one of the pages with endnotes, put a blank line before each endnote so that it is clear where each
begins and ends.
Footnotes in Tables should remain where they are in the original image.
Original Image:
The principal persons involved in this argument were Caesar*, former military
leader and Imperator, and the orator Cicero. Both were of the aristocratic
(Patrician) class, and were quite wealthy.
* Gaius Julius Caesar.
Marcus Tullius Cicero.
7/6/2010 9:41 PM
20 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
7/6/2010 9:41 PM
21 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
7/6/2010 9:41 PM
22 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
7/6/2010 9:41 PM
23 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Multiple Columns
Proofread ordinary text that has been printed in multiple columns as a single column. Place the text from
the left-most column first, the text from the next column below that, and so on. Do not mark where the
columns were split, just join them together. See the very bottom of the Sidenotes example for an
example of multiple columns.
See also the Index and Table sections of the Proofreading Guidelines.
Back to top
Tables
A proofreader's job is to be sure that all the information in a table is correctly proofread. Separate items
with spaces as needed, but do not worry about precise alignment. Retain line breaks (while handling
end-of-line hyphenation and dashes normally). Ignore any periods or other punctuation (leaders) used to
align the items.
Footnotes in tables should remain where they are in the image. See footnotes for details.
Original Image:
7/6/2010 9:41 PM
24 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
TABLE II.
Flat strips compared
with round wire 30 cm.
in length.
Wire 1 mm. diameter
Copper.
Iron.
20
100
Copper.
Parallel wires 30 cm. in
Iron.
length.
20
100
STRIPS.
SINGLE WIRE.
0.25 mm. thick, 2 mm.
wide
...... 15 35
0.25 mm. diameter .... 16
48
Same, 5 mm. wide ....
13 20 Two similar wires ...... 12 30
"
10 "
"
11
15
Four
"
"
9
18
"
20
"
"
10 14
Eight "
"
8
10
"
40 "
"
9
13
Sixteen "
"
7
6
Same strip rolled up in
Same, 16 wires bound
the form of wire .. 17
15
close together ..... 18
12
Original Image:
Objects.
1st person, I,
me,
{ 2d
"
thou,
thee,
Singular {
" mas. { he,
him,
{ 3d " fem. { she,
her,
{
it,
it.
{
{
Plural
Poetry/Epigrams
Insert a blank line at the start of the poetry or epigram and another blank line at the end, so that the
formatters can clearly see the beginning and end. Leave each line left justified and maintain the line
breaks. Insert a blank line between stanzas, when there is one in the image.
Line Numbers in poetry should be kept.
7/6/2010 9:41 PM
25 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Check the Project Comments for the specific project you are proofreading.
Original Image:
Line Numbers
Line numbers are common in books of poetry, and usually appear near the margin every fifth or tenth
line. Keep line numbers, using a few spaces to separate them from the other text on the line so that the
formatters can easily find them. Since poetry will not be rewrapped in the e-book version, the line
numbers will be useful to readers.
Back to top
7/6/2010 9:41 PM
26 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Proofread this by deleting the word, even if it's the second half of a hyphenated word.
In some older books, the single word at the bottom of the page (called a "catchword", usually printed
near the right margin) indicates the first word on the next page of the book (called an "incipit"). It was
used to alert the printer to print the correct reverse (called "verso"), to make it easier for printers'
helpers to make up the pages prior to binding, and to help the reader avoid turning over more than one
page.
Back to top
Blank Page
Most blank pages, or pages with an illustration but no text, will already be marked with [Blank Page].
Leave this marking as is. If the page is blank, and [Blank Page] does not appear, there is no need to add
it.
If there is text in the proofreading text area and a blank image, or if there is text in the image but none in
the text box, follow the directions for a Bad Image or Bad Text.
Back to top
7/6/2010 9:41 PM
27 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Table of Contents
Proofread the Table of Contents just as it is printed in the book, whether all capitals, upper and lower
case, etc. If there are SMALL CAPITALS, see the guidelines for Small Capitals.
Ignore any periods or other punctuation (leaders) used to align the page numbers. These will be removed
7/6/2010 9:41 PM
28 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
PAGE
7/6/2010 9:41 PM
29 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
...
103
Indexes
You don't need to align the page numbers in index pages as they appear in the image; just make sure that
the numbers and punctuation match the image and retain the line breaks.
Specific formatting of indexes will occur later in the process. The proofreader's job is to make sure that
all the text and numbers are correct.
See also Multiple Columns.
Back to top
7/6/2010 9:41 PM
30 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
7/6/2010 9:41 PM
31 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Original Image:
7/6/2010 9:41 PM
32 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Formatting
You may sometimes find formatting already present in the text. Do not add or correct this formatting
information; the formatters will do that later in the process. However, you can remove it if it interferes
with your proofreading. The <x> button in the proofreading interface will remove markup such as <i>
and <b> from highlighted text. Some examples of formatting tasks include:
<i>italics</i>, <b>bold</b>, <sc>Small Caps</sc>
Spaced-out text
Font size changes
Spacing of chapter and section headings
Extra spaces, stars, or lines between paragraphs
Footnotes that continue for more than one page
Footnotes marked with symbols
Illustrations
Sidenote locations
Arrangement of data in tables
Indentation (in poetry or elsewhere)
Rejoining long lines in poetry and indexes
If the previous proofreader inserted formatting, please take a moment and provide feedback to them by
clicking on their name in the proofreading interface and posting a private message to them explaining
how to handle the situation in the future. Remember to leave the formatting to the Formatting
rounds.
Back to top
7/6/2010 9:41 PM
33 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Bad Image
If an image is bad (not loading, mostly illegible, etc.), please post about this bad image in the project
discussion and click on the "Report Bad Page" button so this page is 'quarantined', rather than returning
the page to the round. If only a small portion of the image is bad, leave a note as described above, and
please post in the project discussion without marking the whole page bad. The "Bad Page" button is only
available during the first round of proofreading, so it is important that these issues be resolved early.
Note that some page images are quite large, and it is common for your browser to have difficulty
displaying them, especially if you have several windows open or are using an older computer. Before
reporting this as a bad page, try zooming in on the image, closing some of your windows and programs,
or posting in the project discussion to see if anyone else has the same problem.
7/6/2010 9:41 PM
34 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Back to top
Printer Errors/Misspellings
Correct all of the words that the OCR has misread (scannos), but do not correct what may appear to you
to be misspellings or printer errors that occur on the page image. Many of the older texts have words
spelled differently from modern usage and we retain these older spellings, including any accented
characters.
Place a note in the text next to a printer's erorr[**typo for error?]. If you are unsure whether it is
actually an error, please also ask in the project discussion. If you do make a change, include a note
describing what you changed: [**typo "erorr" fixed]. Include the two asterisks ** so the
post-processor will notice it.
Back to top
7/6/2010 9:41 PM
35 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Back to top
` grave
Alt-0224
Alt-0192
Alt-0232
Alt-0200
Alt-0236
7/6/2010 9:41 PM
36 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Alt-0204
Alt-0242
Alt-0210
Alt-0249
Alt-0217
Alt-0205
Alt-0243
Alt-0211
Alt-0250
Alt-0218
Alt-0253
Alt-0221
edilla
Icelandic
Alt-0231 Alt-0222
Alt-0199 Alt-0254
superscripts Alt-0208
Alt-0185 * Alt-0240
Alt-0178 * sz ligature
Alt-0179 * Alt-0223
Alt-0206
Alt-0207
/ slash
Alt-0244 Alt-0245 Alt-0246 Alt-0248
Alt-0212 Alt-0213 Alt-0214 Alt-0216
Alt-0251
Alt-0252
Alt-0219
Alt-0220 currency mathematics
Alt-0241 Alt-0255 Alt-0162 Alt-0177
Alt-0209
Alt-0163 Alt-0215
marks
accents punctuation Alt-0165 Alt-0247
Alt-0169 Alt-0180 Alt-0191 Alt-0164 Alt-0172
Alt-0174 Alt-0168 Alt-0161
Alt-0176
Alt-0182 Alt-0175 Alt-0171
Alt-0181
Alt-0167 Alt-0184 Alt-0187
ordinals Alt-0188
Alt-0166
Alt-0183 Alt-0186 * Alt-0189
Alt-0170 * Alt-0190
* Unless specifically requested by the Project Comments, please do not use the ordinal or superscript
symbols, but instead use the guidelines for Superscripts. (x^2, f^o, etc.)
Unless specifically requested by the Project Comments, please do not use the fraction symbols, but
instead use the guidelines for Fractions. (1/2, 1/4, 3/4, etc.)
For Apple Macintosh:
You can use the "Key Caps" program as a reference.
In OS 9 & earlier, this is located in the Apple Menu; in OS X through 10.2, it is located in
Applications, Utilities folder.
This brings up a picture of the keyboard, and pressing shift, opt, command, or combinations of
those keys shows how to produce each character. Use this reference to see how to type that
character, or you can cut & paste it from here into the text in the proofreading interface.
In OS X 10.3 and higher, the same function is now a palette available from the Input menu (the
drop-down menu attached to your locale's flag icon in the menu bar). It's labeled "Show Keyboard
Viewer." If this isn't in your Input menu, or if you don't have that menu, you can activate it by
opening System Preferences, the "International" panel, and selecting the "Input Menu" pane.
Ensure that "Show input menu in menu bar" is checked. In the spreadsheet view, check the box
for "Keyboard Viewer" in addition to any input locales you use.
The dropdown menus in the proofreading interface.
Or you can type the Apple Opt- shortcut codes list below for these characters.
This is a lot faster than using cut & paste, once you get used to the codes.
Hold the Opt key and type the accent symbol, then type the letter to be accented (or, for some
codes, only hold the Opt key and type the symbol).
These instructions are for the US-English keyboard layout. It may not work for other keyboard
layouts.
(Print-friendly version of this table)
` grave
Opt-`, a
ligature
Opt-'
7/6/2010 9:41 PM
37 of 39
Opt-`, A
Opt-`, e
Opt-`, E
Opt-`, i
Opt-`, I
Opt-`, o
Opt-`, O
Opt-`, u
Opt-`, U
Opt-e, A
Opt-e, e
Opt-e, E
Opt-e, i
Opt-e, I
Opt-e, o
Opt-e, O
Opt-e, u
Opt-e, U
Opt-e, y
Opt-e, Y
edilla
Icelandic
Opt-c
(none)
Opt-C
(none)
superscripts (none)
(none) * (none)
(none) * sz ligature
(none) * Opt-s
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Opt-i, A
Opt-i, e
Opt-i, E
Opt-i, i
Opt-i, I
Opt-i, o
Opt-i, O
Opt-i, u
Opt-i, U
marks
Opt-g
Opt-r
Opt-7
Opt-6
(none)
* Unless specifically requested by the Project Comments, please do not use the ordinal or superscript
symbols, but instead use the guidelines for Superscripts. (x^2, f^o, etc.)
Unless specifically requested by the Project Comments, please do not use the fraction symbols, but
instead use the guidelines for Fractions. (1/2, 1/4, 3/4, etc.)
Note: No equivalent shortcut; use drop-down menus if needed.
Back to top
7/6/2010 9:41 PM
38 of 39
Columns, Multiple
Comments, Previous Proofreaders'
Common OCR Problems
Contents, Table of
Contractions
Dashes
Dashes, End-of-line
Dashes, End-of-page
Degree Signs
Diacritical Marks
Double Quotes
Double Quotes, missing at start of chapter
Drama
Drop Cap
Drop-down Menus
Ellipsis
Em-dashes
Endnotes
End-of-line Hyphenation and Dashes
End-of-line Space
End-of-page Hyphenation and Dashes
End-of-sentence Periods
Epigrams
Extra Spaces Between Words
Errors, Factual
Errors, Printer
Factual Errors in Texts
Fixing Errors on Previous Pages
Footers, Page
Footnotes
Formatting
Forum
Fractions
Front/Back Title Page
Full Stops, End-of-sentence
Greek Text
Handwritten Notes in Book
Handy Proofreading Guide
Headers, Page
Headings, Chapter
Hebrew Text
Hyphenation, End-of-line
Hyphenation, End-of-page
Hyphens
Illustrations
Image, Bad
Indenting, Paragraph
Indexes
Inserting Special Characters
Italics
Keyboard Shortcuts for Latin-1 Characters
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Numbers, Line
OCR Problems, Common
OCR Problems: Is that really a degree sign?
OCR Problems: Scannos
oe Ligatures
Ordinal Symbol
Ornate Capital Letter (Drop Cap)
Other things that you're unsure of
Page, Blank
Page Headers/Page Footers
Page, Title
Paragraph Side-Descriptions (Sidenotes)
Paragraph Spacing/Indenting
Period Pause "..." (Ellipsis)
Periods, End-of-sentence
Plays: Actor Names/Stage Directions
Poetry
Preexisting Formatting
Previous Proofreader Mistakes
Previous Proofreaders' Notes/Comments
Previous Pages, Fixing Errors on
Primary Rule
Project Comments
Project Discussion
Punctuation Spacing
Printer Errors/Misspellings
Quote Marks on Each Line
Quotes, Double
Quotes, Missing at start of chapter
Quotes, Single
Raised Text (Superscripts)
Scannos
Shortcuts for Latin-1 Characters
Sidenotes
Single Quotes
Single Word at Bottom of Page
SMALL CAPITALS
Space at End-of-line
Spaces, Extra
Spacing, Paragraph
Spacing, Punctuation
Special Characters, Inserting
Stage Directions (Plays)
Subscripts
Summary Guidelines
Superscripts
Table of Contents
Tables
Tabs
Text, Wrong Image for
Title Page
7/6/2010 9:41 PM
39 of 39
http://www.pgdp.net/c/faq/proofreading_guidelines.php
Titles, Chapter
Trailing Space at End-of-line
Word at Bottom of Page
WordCheck
WORDS IN SMALL CAPITALS
Wrong Image for Text
7/6/2010 9:41 PM