On 5/6/2012 2:22 AM, Jean-Francois Nifenecker wrote:
Le 06/05/2012 07:35, Gary Schnabl a écrit :

Your observation is what is typically used in practice--using serif
typefaces for body text in print docs and sans serif for onscreen
viewing. Some editors will switch typefaces used for headings, though:
sans serif for print docs and serif in an online doc.

Why not try creating your own "print" version by simply altering the
typeface for the body-text paragraph styles that were employed the
source docs--a very simple task. Then just port out your own PDF.

I do share the OP comments about printed matter vs screen display and your idea seems very interesting to me, Gary.

Perhaps we could keep that need in mind while re-designing the documentation templates? BTW, the styles cataloging is on my workbench for a few days now. I hope that, as a first step, I can get a styles dependencies map by to-morrow. (I'll open a new thread on due time)

What you might desire to do is going through a thorough listing of most (or all) of the factory-default styles and then work from there. The very start of such a listing of mine follows...

*Factory-default styles (Title)*

All of the formatting in this template contains the factory-default settings. No formatting changes are made whatsoever, so that the factory-default characteristics can be determined. The first instance (and possibly others) of any paragraph style will have a parenthetical notational at the end of that paragraph (possibly also preceded with a list style notation), such as in this paragraph. (Text body)

The factory-default template has the following styles (List Heading):

 *

   Applied Styles (List 4/List 1 Start)

 *

   Paragraph styles: Default (List 1/List 2 Start)

 *

   Page styles: Default (List 1/List 2 Cont.)

 *

   Conditional Styles (List 4/List 1 Cont.)

 *

   Text body (List 1/List 2 Start



Obviously, the formatting displayed in this post will have altered formatting from the OTT/ODT version; however, one could easily recreate the original formatting by applying the appropriate paragraph and list styles named above.

Doing an examination and study of the factory defaults like this can teach a template designer about what modifications should be needed, etc. in actual templates. It will also display that the original factory dfaults were never actually well-conceived and executed, even back in the OOo originals.

Gary




--
Unsubscribe instructions: E-mail to [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to