To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3395
------- Additional comments from [email protected] Tue Sep 29 07:34:47 +0000 2009 ------- It seems possible to at least have a display of what formatting is used, but editing these would not work as WP's RC does. The difference between WP & OOo is that WP uses a form of nested and / or overlapping format codes, while OOo enforces absolutely no nesting and / or overlapping. Each bit of text could only have one single formatting style applied to it. The "bit" may range from a single character, to a paragraph, to the entire document - as long as the format stays consistent to the previous style's format the style is not closed. OOo uses only a sub-set of what I thought it did originally: instead of the formatting codes it only uses CSS-like styles (Cascading Style Sheets), but without the C part (cascading) - so that should probably read SS styles (Style Sheet). Whenever a hard-format change is done to anything, an entirely new auto-style is created. The previous style is stopped and a new style tag is started. The new style incorporates all the formatting codes of the previous style with the exception of the change. This sounds (to me at least) a bit wasted as a simple change to bold would duplicate every other format assignment (font, underline, font size, capitalization, italics, etc.) which is still as previous. However, I can see that it's much more efficient (program speed wise) than WP's nested / overlapping method: see below. WP (on the other hand) has no such thing as auto-generated-styles. It uses open and close tags for each format change. E.g. a bold start & end, an underline start & end, etc. It does have a style start & end tag as well, but this is considered similar to any other format tag pair. This method uses the least amount of space to actually save the formatting, seeing as any one single change is saved as only that change - the formatting which is not changed still continues and is not stopped & duplicated as with OOo. Programming speed wise this could have a detrimental effect though, seeing as displaying any piece of text all the previous text needs to be examined to find out what format is still applicable. With OOo only the latest style start tag needs to be found to display any one piece of text. The reason I can't see OOo using RC directly as WP does is this: OOo has no way of knowing to which style start tag a style stop tag refers. Thus it "assumes" it always refers to the latest style start. This does not create a problem in OOo due to the rule that only one style can be applied at any one time. WP's stop tags are always paired to a start tag (be that a style or other formatting code), thus the stop tag would stop its corresponding style / format and not become confused with something else (like OOo would). @mestech: It would certainly be possible to convert these "temporary" styles to full styles to be displayed in the stylist. It may be a bit difficult to group them into Paragraph, Character, Page, etc. ... but then again maybe not. It doesn't exactly serve the purpose of reveal codes though (only very partly). The real problem I can see with this is an entirely new style is created each time any one thing is changed. I've also not checked if duplicate formatting creates duplicate styles or if the existing (similar) auto style is re-used. This may create hundreds (if not thousands) of styles in the stylist. If you do need the hard-format to be saved as a Style in Stylist, this feature is already implemented (at least in 3.1, probably earlier). If you have the stylist open, select the hard-formatted text. Then click on the "New Style from Selection" button (top-right of stylist panel). Give the new style a name. The group would be the same as the currently displayed style group page (i.e. Paragraph, Character, Frame, Page / List). True this is not automatic, as you suggested for the macro, but at least it's not going to create hundreds of styles which are (nearly) the same to each other. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
