[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libreoffice-documentation] LibreOffice Branding and Documentation
- Subject: Re: [libreoffice-documentation] LibreOffice Branding and Documentation
- From: Gary Schnabl <gSchnabl@SWDetroit.com>
- Date: Mon, 08 Nov 2010 21:24:41 -0500
- To: firstname.lastname@example.org
On 11/7/2010 6:23 PM, Ron Faile wrote:
On 11/7/2010 5:09 PM, Gary Schnabl wrote:
On 11/7/2010 5:41 PM, Ron Faile wrote:It's how it was created. That's a good point for the final docs, but I just meant this as a mockup for the overall feel of it.
I've made a few changes based on Michael's mockup and would like to know what you think. The file is Document template 0.3 and is posted here:
You will need the Liberation Sans Regular, Linux Libertine G Regular, Linux Biolinum G Regular and Linux Biolinum G Italic fonts to view it correctly. I've also added some proposals for the information boxes and would like to know your thoughts on those as well.
I noticed that the template used dozens? of empty paragraphs (Default or Text body paragraph style) for interparagraph spacing instead of using the vertical (before and after) spacing that the paragraph styles themselves afford. Was that done intentionally or was that how my copy reads, as I originally experienced some difficulty in downloading the template?
One means would be to introduce specialized paragraph styles (as needed...) with the desired interparagraph spacings already preinstalled.
Roger that... However, it only takes a minute or so to create a custom paragraph or character style, so it is a good practice to always include them in any template and not employ a series of empty paragraphs for spacing purposes. The custom styles do not need to set up with their parameters initially--just give the styles appropriate, useful names to serve as arrows in your quiver to use when needed.
If you intend to use subdocuments in a master document, you might want to take care not to use a generic term for a paragraph style, say Title, in all the docs because an automatic generation of a ToC would treat all such styles with that term the same--usually not what you want. To get around that, you might want to include custom styles named Book title, Chapter title, Front-matter title, etc.
Anyway, it is a good habit to start with some custom styles (as needed) right from the start when designing any template.
For practice, every so often I might take an OOo template, make some changes to it, then save it as a DOC file and import that DOC file into Adobe FrameMaker and see how that goes--usually (hopefully) pretty straightforward and flawless. FrameMaker is a much better medium for bookmaking in that crossrefs between external subdocuments are much easier to effect and thus are more reliable. Besides, FrameMaker is a hybrid word processor/DTP app that has better typesetting algorithms than a fancy word processor. (Adobe InDesign is even better yet). But that is my personal preference as to building books (master docs) for PDFs or print.
Also, MS Word makes beautiful tables with ease. So converting them afterward to another medium like OOo or FrameMaker can take advantage of that Word feature. You could create a series of custom tables in Word and collect them and convert them for later use in OOo or FrameMaker--provided that you do not mind using packages developed by private companies. Some people have hangups about using a proprietary software package or O/S.
Southwest Detroit, two miles NORTH! of Canada--Windsor, that is...
E-mail to email@example.com for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/documentation/
All messages you send to this list will be publicly archived and cannot be deleted
- Prev by Date: Re: [libreoffice-documentation] Installation instructions?
- Next by Date: [libreoffice-documentation] State of a document on Drupal site
- Previous by thread: Re: [libreoffice-documentation] LibreOffice Branding and Documentation
- Next by thread: Re: [libreoffice-documentation] LibreOffice Branding and Documentation