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] Wed Mar 29 05:57:01 -0800 2006 ------- Having seen the discussion on the users list recently, I fear that this issue will never go away and will never be satisfactorily implemented for the WP die-hards. At each point in the text of a document, the appearance is defined by a _set_ of attributes (font, colour, language, margins, indentation, background colour etc.) As I understand it from the comments made, reveal codes indicate how this set is built up by applying them from some default by processing the text from the beginning of the document. In a style-oriented writer, the set of attributes is built up by following the definitions of a style along its parent derivation tree from some default at its root. In effect, each character is given the _whole_set_ of attributes at the _same_time_, and that set is called its style (simplifying wildly). These two approaches are so different, that just writing a translator from one form to the other must be a challenging exercise. Asking either to look like the other in the GUI seems inappropriate if not actually technically infeasible. I can see the way that people are using reveal codes, and that imported text can mess things up, and so there is a need to see where an attribute last appeared. The equivalent in OOo would be to discover where in the style tree a particular attribute was last given its value. The current values can be seen by looking at the current style definition, but it is not easy to check up the tree for a given attribute (say language, or italic, etc.) But the need would be for a tree description _per_attribute_; trying to show it for all attributes simultaneously would be an excessive amount of information. An alternative would be to have on all tabs in the style dialogs a button that jumped immediately to the parent so the differences can be seen. I am not an OOo developer so what I say should be taken with the appropriate grain of salt. But my guess is that trying to display anything resembling reveal codes is not worth the effort that would have to be put into it, and will be a drain on maintenance activity and testing forever. But an improvement in the dialogs showing how an attribute came to be applied by explicitly displaying the tree might be possible. Please correct any misconceptions I might have. --------------------------------------------------------------------- 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]
