Hi,

Frank and Scott asked me to look into the style guide at http://documentation.openoffice.org/servlets/ProjectDocumentList and to make some recommendations. Here is what I found:

For the title page the style guide requests the version information to be named twice: in the title line and at the bottom of the page. This is not necessary in my opinion. As the How To's do not state the version number in the title anyway I would suggest to name it only at the bottom of the page.

The specifications for the "Contents" section are not sufficient. To have a less monotonous layout of the TOC I would suggest to create more visible chapter groups by well distinguished font sizes and paragraph distances. I would enlarge the level 1 font, for example up to 18p, and give it a larger spacing above paragraph (for ex. 0.5"). The spacing above level 2 paragraphs could then be 0.1".

In the "Chapters" section the style guide allows for chapter numbering of all levels. As no one remembers a third level chapter number like 1.1.3 and the OOO User Guide does not make use of these specification anyway I would suggest for large documentations to number only the chapters. Chapter 1 in the User Guide would then be "1 Using OpenOffice.org Help" (and not "Chapter 1: Using..." as it is now).

In the section "Bulleted and numbered lists" I would leave the default indent of 0 because bullets and numbers already indicate a list. So, on the first level of a list there is no indent necessary.

In the "Icons in text" section I would limit the icon size to 0.16 cm square (now 0.64 cm square). If this is not legible I would recommend to use icons only in the first line of a paragraph to avoid irregular line distances when icons are inserted within text.

Martina

--
 [EMAIL PROTECTED]  -  Technical Writer
 StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
 http://www.sun.com/staroffice

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to