EbookFoundation
/
gutenbergsite
mirror of https://github.com/EbookFoundation/gutenbergsite.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Adding word_processor_faq

bookshelf
Gutenberg back end service account 2019-12-10 13:42:15 -05:00
parent 0dedcfea7c
commit ff77a02aba
2 changed files with 109 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
site/how_to/volunteers_voices.md
View File

@ -11,20 +11,20 @@ Some people chose an interview format for their responses, with pre-set question
<div class="contents">
<ol>
<li><a href="#">Amy Zelmer</a></li>
<li><a href="#">Ben Crowder</a></li>
<li><a href="#">Col Choat</a></li>
<li><a href="#">Dagny</a></li>
<li><a href="#">Gardner Buchanan</a></li>
<li><a href="#">Jim Tinsley</a></li>
<li><a href="#">John Mamoun</a></li>
<li><a href="#">Ken Reeder</a></li>
<li><a href="#">Lynn Hill</a></li>
<li><a href="#">Sandra Laythorpe</a></li>
<li><a href="#">Suzanne Shell</a></li>
<li><a href="#">Tony Adam</a></li>
<li><a href="#">Tonya Allen</a></li>
<li><a href="#">Walter Debeuf</a></li>
<li><a href="#amy-zelmer">Amy Zelmer</a></li>
<li><a href="#ben-crowder">Ben Crowder</a></li>
<li><a href="#col-choat">Col Choat</a></li>
<li><a href="#dagny">Dagny</a></li>
<li><a href="#gardner-buchanan">Gardner Buchanan</a></li>
<li><a href="#jim-tinsley">Jim Tinsley</a></li>
<li><a href="#john-mamoun">John Mamoun</a></li>
<li><a href="#ken-reeder">Ken Reeder</a></li>
<li><a href="#lynn-hill">Lynn Hill</a></li>
<li><a href="#sandra-laythorpe">Sandra Laythorpe</a></li>
<li><a href="#suzanne-shell">Suzanne Shell</a></li>
<li><a href="#tony-adam">Tony Adam</a></li>
<li><a href="#tonya-allen">Tonya Allen</a></li>
<li><a href="#walter-debeuf">Walter Debeuf</a></li>
</ol>
</div>
@ -78,7 +78,7 @@ I tried to apply the editing rules outlined on the PG site, though they weren't
When I submitted the title pages of the book to PG for copyright clearance it was rejected because the book was published in 1926. I don't know what I was thinking about when I chose it. It must have just LOOKED old enough. I had scanned and proofed about half of it, so I just abandoned it and looked for something else. Interestingly, Australians and residents in other countries with similar copyright laws, can now read it as it is in the public domain in Australia and is now on the Project Gutenberg of Australia site. I was able to finish it and post it at PG, after all.
###How did you develop your PG experience from there?
### How did you develop your PG experience from there?
I think that one of the most valuable things I did was to join the volunteer discussion group. I found that I didn't need to take part, but could just take note of all the different issues raised by other volunteers. Some days there was no activity by the group, but then a hot topic would be raised (e.g. whether some books, such as Mein Kampf by Adolf Hitler, should not be accepted by PG, even if eligible) and there would be plenty of comments. I realised also that I could ask for help on specific questions regarding preparation of texts and receive prompt informative answers. Once, when I thought that I was sending to ONE of the members of the group an e-mail with a large attachment, I was quickly made aware that EVERYONE had received it. Some weren't amused, but I am a quick learner--I didn't do it again.
Subscribing to the weekly newsletter is also worthwhile. There is a link on the main page of the PG web site to allow people to subscribe to the mailing list and discussion group. I also found a few people who I began to e-mail privately, outside the discussion group. That helped a lot, too. Perhaps there is merit in instigating a mentor scheme, whereby a new volunteer can refer to another more experienced one for help, guidance and encouragement. I would be interested in taking part in that.
@ -434,7 +434,7 @@ For a book with nice clear, good-sized print, I figure that it averages out to a
I feel that I've got my process pretty well set by now. I've put together several little home-made utility programs, written in FoxPro, which assist me. (I've put in some effort to try to adapt some of these for possible use by others, but the problems are that it takes a lot more work to polish software to the point that I feel comfortable letting somebody else pound on it, and the scope of what I think the software ought to do gets bigger every time I work on it, and it's not nearly as enjoyable - for somebody who develops software at work every day - as producing etexts.)
*My complete production process, with rough time breakdown, is as follows: *
**My complete production process, with rough time breakdown, is as follows:**
1. Scan the book, 2 pages at a time, about 1 minute per scan (30 seconds per page). (I do not cut the pages out of the book, I just lay it flat on the scanner and press down on the spine.)
2. Run the BMP file through TextBridge Pro, about 30 seconds per page. (Again, when working with clear, good-sized print.) I save the output as text with no line breaks.
3. Run a little FoxPro utility that I wrote that massages and formats the file a little bit.

93
site/how_to/word_processor_faq.md Normal file
View File

@ -0,0 +1,93 @@
---
layout: default
title: PG-Word Processor FAQ
permalink: /how_to/word_processor_faq.html
---
# Word Processor FAQ
This page is no longer actively maintained. Some content may be inaccurate or outdated, including software names and external links. Please visit [Distributed Proofreaders](https://www.pgdp.net/c/) to view forums where best practices are actively discussed and maintained.
<div class="contents">
<ol>
<li><a href="#editors-and-word-processors">Editors and Word Processors</a>
<ol class="inner_1">
<li><a href="#whats-the-difference-between-an-editor-and-a-word-processor">What's the difference between an editor and a word processor?</a></li>
<li><a href="#should-i-use-an-editor-or-a-word-processor">Should I use an editor or a word processor?</a></li>
<li><a href="#which-editor-or-word-processor-should-i-use">Which editor or word processor should I use?</a></li>
<li><a href="#how-can-i-make-my-word-processor-easier-to-work-with-for-plain-text">How can I make my word processor easier to work with for plain text?</a></li>
<li><a href="#what-is-the-difference-between-proportional-and-non-proportional-fonts">What is the difference between proportional and non-proportional fonts?</a></li>
<li><a href="#i-cant-get-words-in-a-table-or-poem-to-line-up-under-each-other">I can't get words in a table or poem to line up under each other.</a></li>
</ol>
</li>
<li><a href="#about-using-microsoft-word">About using Microsoft Word</a>
<ol class="inner_1">
<li><a href="#ive-edited-my-book-in-word--how-do-i-save-it-as-plain-text">I've edited my book in Word &#8212; how do I save it as plain text?</a></li>
<li><a href="#quotes-look-wrong-when-i-save-a-word-document-as-plain-text">Quotes look wrong when I save a Word document as plain text.</a></li>
<li><a href="#dashes-look-wrong-when-i-save-a-word-document-as-plain-text">Dashes look wrong when I save a Word document as plain text.</a></li>
<li><a href="#i-saved-my-word-document-as-html-but-the-html-looks-terrible">I saved my Word document as HTML, but the HTML looks terrible.</a></li>
</ol>
</li>
</ol>
</div>
## Editors and Word Processors
### What's the difference between an editor and a word processor?
An editor shows you the characters you type, exactly as you type them. It puts new-line characters in when you hit the Enter key, and only when you hit the Enter key. Its ultimate aim is to give you exact control of plain text. EDIT in DOS, Notepad in Windows, vi and emacs in *nix, Tex-Edit Plus and BBEdit Lite in Mac, are all editors.
A word processor, in addition to entering the characters, also lets you change the font, the size of individual words, and whether they are italic or bold. It doesn't generally want individual line-ends put in on each line; it just rewraps the text as you change it. Its ultimate aim is to print your document on paper with full formatting facilities. WordPerfect for MS-DOS and Windows, MS-Word for Windows and Mac, AbiWord for Windows and Linux, and Nisus Writer for Mac are all word processors.
### Should I use an editor or a word processor?
For dealing with plain text, which is what PG is about, you might expect a text editor to have the edge, since the formatting features of word processors can get in the way of making a clean text.
However, if you use a word processor, and you ignore all of the layout and formatting that have to do with fonts and paper, it will work equally well. There are a few common problems associated with Word Processors mentioned below.
### Which editor or word processor should I use?
The one you like best!
Any of them will do the job. Even the most primitive editors of 1971 will do the job. The most feature-bloated word processor of tomorrow will do the job. No editor or word processor affects in the slightest the "quality" of the text produced.
For PG purposes, therefore, the only difference between them all is how easy you find them to use, and what facilities they have for helping you — and those are decisions that only you can make.
If you already have a favorite editor or word processor, stick to it. If you don't, there's a huge selection available for you to consider, on any type of computer.
Sometimes, using a word processor, you may encounter some problems in saving your book as plain text. You have to figure out how to get it right just once, and then use that same method thereafter. If you have problems with this, ask other volunteers or one of the Posting Team for help.
### How can I make my word processor easier to work with for plain text?
First, switch off everything called "Smart ——" or "Automatic ——". Modern word processors commonly offer lots of typical typing support features — "Smart Quotes", "Auto Correct", automatically capitalizing the first word in each sentence, anything like that. By all means, leave on any informative highlighting of misspelled words or other errors that it offers, but switch off any feature that changes what you type without asking you. Older books contain text that doesn't sit comfortably with modern rules, and we don't want your word processor deciding what Chaucer really wrote!
Now, choose a non-proportional font, and apply it to the whole document. It's important to work in a non-proportional font, because you may have to line words up underneath each other and it is not possible to do this consistently in non-proportional fonts like Times or Arial.
If you work in Courier, size 10, 11 or 12, and your word processor is set for a normal page size, about 7 inches across excluding margins, then what you see in your WP is a pretty good approximation to how the text will look in PG plain text format. One formula, suggested by John Mamoun in the Volunteers' Voices section, is to Select All the text, choose Courier New font, 10 point size, and set the margins at 5.5 inches, then Save As "Text with layout".
### What is the difference between proportional and non-proportional fonts?
A non-proportional, or "monospaced", or "typewriter" font, is one where all of the letters take up exactly the same amount of space on screen: a capital "W", a lower-case "i" and a space are all equally wide. The Courier family of fonts is commonly used for this.
A proportional font is one where each letter takes up just the amount of space it needs, so that a capital "W" is much wider than a small "i".
Unfortunately, the different sizes of the letters in different proportional fonts means that it's not possible to line up letters consistently: a "W" may be equivalent to three "i"s in one proportional font, and to four "i"s in another. This means, for example, that it is not possible to use a proportional font to format plain text tables or poetry correctly — lining up the spaces and words using one proportional font will cause it to look skewed using another.
You should always look at PG texts in a non-proportional font, even if you prefer to work mostly using a proportional font, because readers and automatic converter programs will assume that you meant to your text to be viewed using a non-proportional font.
### I can't get words in a table or poem to line up under each other.
You are using a proportional font. You should always use a non-proportional font like Courier for PG work. Change the font of the entire document to Courier and try again.
## About using Microsoft Word
PG volunteers use many different word-processors, but Microsoft Word is the one we hear most queries and problems about.
### I've edited my book in Word — how do I save it as plain text?
First, make sure that all text is using Courier or Courier New and is at the same point size (usually 10-12). Move your right margin so that you see roughly the right number of characters per line (usually 65-70). Then choose File / Save As and then choose the format "Text Only with Line Breaks". Save your file with the extension ".txt" to distinguish it from your Word format file.
After saving, open your text file using Notepad or some other simple text editor and look at the results. You should see a typical PG layout of the text — lines up to 70 characters long, a blank line between paragraphs and no indentation at the start of each paragraph. If so, you're done.
### Quotes look wrong when I save a Word document as plain text.
You may have left "Smart Quotes" on in Word options. This tells Word to use left- and right-slanted quote marks at the beginning and end of a quote instead of the plain ASCII straight quotes. When you save a document that contains these angled quotes as plain text, they come out as non-ASCII characters that look wrong on most editors and viewers. The solution is to turn off Smart Quotes in Word and/or replace the ones it has already created.
### Dashes look wrong when I save a Word document as plain text.
When Word recognizes an em-dash as such, it may try to use a special character for it. This may appear as a black square, an empty box, or a funny accented letter when you Save As text and look at it in a different editor.
You can usually do a Find and Replace on this character either in Word or in another editor after Saving As text to change it to two dashes.
For those interested, the "funny character" is character 151 (97H), and is specific to Codepage 1252 [V.76].
### I saved my Word document as HTML, but the HTML looks terrible.
Yes. Word is not unique in having this problem, but HTML saved from Word is the case we hear most about. Microsoft themselves offer a free plug-in to Word that saves the file in "Compact HTML", which is a bit better. You can fix it by hand, or you can use [HTML Tidy](http://tidy.sourceforge.net/), a handy utility, which will do some clean-up on the HTML. If you're working with HTML, you really need a copy of Tidy anyway, because it's such a great way to do a check on the correctness of your HTML.
Tidy is also embedded in some Windows GUI tools, like Tidy-GUI, HTML-Kit and NoteTab.