On or about 3/17/2006 12:19 PM, Robin Laing penned the following: > Jallan wrote: >> Robin Laing wrote: >> > >> > >> If want to change the "Default" style, just select modify in the >> Stylelist for the "Default" character style, and then change the >> "Default" style and all the paragraphs in the "Default" style will >> change, except ... and this is important, when you have applied direct >> formatting on top of the underlying styles. >> >> What else. You don't want special effects like bolding and italics or >> font changes *within* a paragraph to vanish because you have changed >> the underlying font. To put it in Word Perfect terms, when you change >> a paragraph style the paragraph display as though you inserted a bunch >> new codes at the beginning of each paragraph in place of the old ones, >> but any following control codes within that paragraph are left alone. >> Accordingly what you see may be far more determined by these following >> codes. >> >>> I still have to find the font and spacing issue that was changed in a >>> style but after setting the default style, the font issue is still >>> present. But what I did confirm that one of may major issues with >>> importing documents has been related to a style that the default >>> style doesn't fix. >> >> >> Possibly this is overlying direct formatting or an overlying character >> style. If you set the Stylelist to show character styles, then the >> character style at the current cursor position will be highlighted in >> the list. You can then edit that style. If the style doesn't change in >> the list when visually you see a change within a paragraph, such as a >> font change or a change from non-bold to bold, then direct formatting >> has been applied. >> >> To see the underlying paragraph formatting in a paragraph just do >> CTRL-SHIFT-SPACE to remove all but the basic paragraph style >> formatting in that paragraph. After you've seen what this shows, you >> can press CTRL-Z to put the character style formatting and direct >> formatting back again. >> >> Jallan >> > > Your long description is a good example to me on why Reveal codes is > better. > > Look here or if that isn't it, look there. I guess this is why I feel > reveal codes is nicer. A single keystroke and all my codes are > displayed. No opening this tool box or changing this setting and > opening that dialog. > > I will learn styles when I can but it took me minutes to learn how to > use reveal codes. Styles are not that easy. > > BTW, thanks for the description on how the coding works in OOo. I wish > there was something to make it easier to find these errors as it is my > major headache as I have to import and convert many documents to ODF and > they have to look the same as the MS or WP version's of the document. > > Importing a document or series of documents is not perfect, no matter > what program you use. I have had these issues with all of the Word > processors I have used. I just found WP the was the quickest to clean > the coding problems that occurred. >
I, too, also thank all those that have responded to my original query. I'm glad to see that I'm not the only one who prefers a 'reveal code'. I also find styles harder to deal with. They seem to be OK for business type letters or standard book writing, but for us non-professionals the WP style is easier and, IMHO better. I have learned and gotten slightly confused at times with some of the information here - but I'll stick it out. I'm glad I posted my question. -- Ed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
