Michele,
If you don't mind I would like to re-work the hierarchical structure of the
styles since at present it is not very clean.
All excellent suggestions. Thank you! I've snipped most of your note
(the bits I agree with and don't need to answer).
4) Do we need OOoTextBodyNoIndent?
I have been using it in a few places where having an indent on the
first line causes layout problems, but perhaps when I redo things I'll
find I don't need it any more.
8) do we need the differentiation between OOoGuideName and OOoHeading0? I am
tempted to create a single style (OOoTitle).
Yes, we definitely need that differentiation.
1) The guide name should be in a smaller font than the chapter title
on the first pages of chapters.
2) OOoTitle is the style I use for the name of the book on the title
page of the book.
3) In the V2 template, the paragraph tagged with OOoGuideName was set
to be invisible when the chapter is included in the full book. (IIRC,
I used a style definition in the book template of "white" for that
paragraph, since I couldn't get hidden paragraphs to work. A kludge,
but it worked.)
4) Most importantly: If the guide name is in the same style as the
chapter title, then the guide name will show up in the book's table of
contents before every chapter name -- definitely unwanted!
BTW, I forgot to set up the conditional hidden section around the
copyright and ToC pages in my new template. You're welcome to do that,
or I'll add it after you fix the styles.
9) do we need OOoPageBreak and OOoDefinition?
OOoPage Break is what I have been using to ensure the chapters compile
into the master document correctly, with no page break or page style
hassles. It solved a problem with the conditional hidden section
around the copyright and ToC pages; without the OOoPage Break
paragraph (with an explicit page break after), the chapter text didn't
start on a new page. Every alternative I tested either didn't work or
had unwanted side-effects.
Regarding OOoDefinition: what para style do you foresee using for that
function? None of the other styles do what I want (an indented
paragraph without a further first-line indent), but what I had in mind
isn't essential and may waste too much space.
With the above structure we can change the font style for the whole guide
with very few clicks . An even better change would be to replace the font
size with percentage values so that by just changing the parent's style font
size all the other sizes change accordingly.
Yes, excellent. I agree. Thanks!
If you don't mind I am prepared to perform these changes both to the pdf
version template and to the "normal" template.
Thanks for offering! I accept, with enthusiasm. :-)
Do we need the "normal" (portrait, styled for printing) template for
the V3 docs? I use a template in a smaller page size (6x9 inches) for
the printed books. I suppose it would be useful as a starting point
for other purposes than the user guide.
Two more comments:
1) I would change the language to English USA (or even better to English UK)
Did it default to English (Australian)? If so, sorry! That was an
oversight, not intentional. Given that we are using computer-standard
spelling for some terms (color, dialog, and program, for example) I
think it would be easier for standard spell-checking to set the
language to English US.
2) I don't like BitstreamVera Serif and I don't like Deja Vu Serif either.
Both fonts work best in their sans version. What other fonts are shipped
with OOo?
I found the Serif version of Bitstream Vera easy to read on all my
monitors, as it is reasonably heavy (lightweight serif fonts are hard
for me to read online). For online reading, I am usually happier with
the sans version of fonts but Bitstream Vera Sans look "clunky" and
unattractive to me in large slabs of text -- and I find it harder to
read.
I don't like the DejaVu fonts as much as the BitstreamVera ones, but
obviously font choices are very much a matter of personal preference.
The fonts that a professional typographer friend of mine say are far
superior (for a whole range of reasons) are ones that I personally
find difficult to read. (No, I don't remember what those fonts were
and they were almost surely for print anyway.)
If you can find a different font that we both like (and no one else
has a problem with), I have no objection to changing it. Note: I'm
using the term "like" to mean "find comfortable to read".
I don't know what other fonts ship with OOo.
--Jean
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
