To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92325


User hdu changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'hdu,hennerdrewes,tl'
--------------------------------------------------------------------------------
              OS/Version|Linux                     |All
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Tue Feb  3 15:18:06 +0000 
2009 -------
OOo uses ICU's implementation of the BiDi algorithm 
(http://www.unicode.org/reports/tr9) for text 
ordering. The attached samples shows that everything works indeed as intended 
by the unicode 
consortium. There are well known problems with this algorithm where formatting 
marks are needed to 
resolve ambiguities (e.g. the "once again, together" chapter in
http://people.w3.org/rishida/scripts/bidi/#where).

On the other hand a well known legacy application doesn't seem to use the BiDi 
algorithm for text 
reordering. Since we aim for excellent compatibility this can be considered a 
bug. Not following the BiDi 
algorithm might be considered a bug too. Maybe the application layer should 
just insert formatting 
markers automatically to resolve all ambiguities.

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