Robin Laing wrote:
r.
No one just has to look at the attributes that are changed. I look at
the above Normal (Web) and I have 12 major options that can be changed
within it. I see a problem on the page I have but I am not sure what
option is the problem. Of course, if is is a font option that changed,
now it isn't the style at all that changed the formatting, though it
could have.
Be reasonable. If you see the wrong color, it isn't the paragraph
spacing. Normally you know almost exactly what is wrong. And, yes, as
you've been told again and again, direct formatting overwrites basic
style formatting.
And to use this as an example. In this document, "Header 1" is being
used. It is defined as Times New Roman, 14pt Bold for the font. Yet it
is also on a second line that looks totally different. Same font and
size but not Bold but underlined. I select the line and the Heading 1
style is what is highlited. This is a great example of how the
formatting of the style does not represent what is on the screen. Now
if I am correct, the second header would be closer to "Header 2".
You've been told again and again that styles get overwritten by direct
formatting by users who don't use styles. Remove the direct formatting
from the header with Ctrl-Shift-Space and you should see the underlying
paragraph style formatting. Then put it back with CTRL-Z.
Whether you want to use the direct formatting or the style formatting,
or some other formatting in your final document. Just make a choice and
implement it.
Not to confuse things but there are other formatting changes that occur
on the blank line between the two headers that is still indicated at
being "Header 1"
This is in three lines of text on an imported document.
Yes, all quite as one might expect. Really, what is the problem? Change
what you import to the formatting you want.
I don't know as I didn't create it. It is something that was imported
or pasted from another source.
It doesn't matter how undesired formatting got there. Just change it to
what you want.
We won't agree on the power of each. I agree that there are times
styles are much better than RC's but there are times that RC is much
better than styles.
Again, there are no formatting code tags in OpenOffice.org, other than
what you can see with View -> NonPrinting characters.
Again, whether a text processing application supports styles has nothing
whatsoever to do with whether it uses formatting code tokens internally.
And an application that does not use formatting code tokens internally
will not have the numerous problems that using formatting code tokens
involves: no orphaned "begin this attribute" and orphaned "end this
attribute" tokens, because there are no tokens. Formatting is applied
directly, not by the user applying tokens that apply formatting,
formatting the messes up when a begin attribute or end attribute token
gets deleted, or through nesting of tokens.
All that mess is gone.
Using styles, where used with WordPerfect, MS Word, OOoWriter, Quark
Express, Adobe InDesign, in HTML is a method of avoiding a lot of
problems on any text processing system, not an alternative to reveal codes.
The alternative to revealing codes is to not use code tokens at all, to
get rid of that way of setting formatting and to set formatting directly.
Stop mixing this up with using or not using styles.
Jallan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
