To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105270
                 Issue #|105270
                 Summary|Writer saves text alignment not according to spec
               Component|Word processor
                 Version|OOo 3.1
                Platform|Unknown
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|save-export
             Assigned to|writerneedsconfirm
             Reported by|thzander





------- Additional comments from [email protected] Tue Sep 22 13:09:05 
+0000 2009 -------
This is an interoperability issue.

OOo writer seems to store and read text alignment not according to spec.
The fo:text-align tag gets the value 'end' for text that has a visual alignment
right and a text progression (style:writing-mode) of right-to-left.
If you look at the spec; http://www.w3.org/TR/xsl/#text-align then 'end' is
specified as;
 «Specifies that the content is to be aligned on the end-edge in the
inline-progression-direction.»

This means that for LTR paragraphs end equals right and for RTL paragraphs end
equals the visual alignment of left.
Yet OOo seems to equate 'end' with 'right' unconditionally.

Test documents and related materials can be found in the koffice bugtracker;
http://bugs.kde.org/207915

---------------------------------------------------------------------
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]

Reply via email to