To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112350
                 Issue #|112350
                 Summary|extensions: SWP mishadles headers in tables
               Component|framework
                 Version|OOO320m18
                Platform|Unknown
                     URL|
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P4
            Subcomponent|ui
             Assigned to|mh
             Reported by|tjfrazier





------- Additional comments from tjfraz...@openoffice.org Sun Jun 13 22:10:31 
+0000 2010 -------
Within a Writer table, it is possible to format the text in a cell as a header
(of some outline level). This works well for text format, TOC, xrefs, &c. --
until SWP gets ahold of it.

SWP translates all headers into wiki "=" syntax; the text, "Header", formatted
in Writer as level 2, comes out, "==Header==", which is fine outside of wiki
tables. The MWF wiki code does not recognize this syntax inside wiki tables,
with the result that the text appears as "==Header==".

Given a header within a table, SWP should simply apply the character styling (or
some reasonable subset thereof) from the header style.

---------------------------------------------------------------------
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: issues-unsubscr...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to