Ummm ... I think it is. It's a standard feature of guiprep. It's *almost* a required activity for the Content Provider. But one that the guidelines suggest that the proofer (who doesn't know this has probably happened) will nullify. Here is the applicable Proofing Guideline: Words like to-day and to-morrow that we don't commonly hyphenate now were often hyphenated in the old books we are working on. Leave them hyphenated the way the author did. If you're not sure if the author hyphenated it or not, leave the hyphen, put an * after it, and join the word together like this: 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. Now an only mildly conservative reading of that suggests that just about any word that could possibly be hyphenated should be "-*"ed unless there's another example showing the "right way" on the very same page. There's certainly no moderating language encouraging the proofer to do anything else. Especially considering the possible calumny if they should do the wrong thing. And it says right there to leave it for the PPer if it's not obvious to you in the context of the one page available to you at the time. In fact, if the CPer has done what most CPers do, and left provably hyphenated words hyphenated and closed up the rest, the Guideline actually would lead the proofer to undo it all. On Fri, Apr 16, 2010 at 8:49 PM, Karen Lofstrom <klofstrom@gmail.com> wrote:
On Fri, Apr 16, 2010 at 5:26 PM, don kretz <dakretz@gmail.com> wrote:
The first easiest way is to do this before posting the project in the first place.
That sounds like a good idea. Why don't we add it as a step in the preparation process?
-- Karen Lofstrom _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d