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


User er changed the following:

                What    |Old value                 |New value
================================================================================
        Target milestone|OOo 3.1                   |OOo 3.x
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Thu Nov 27 15:32:27 +0000 
2008 -------
As the css::lang::Locale struct corresponds to the java.util.Locale this
essentially boils down to how Java will handle script codes in future.
The current Language/Country/Variant fields were modeled after IETF RFC
1766. That has been superseded by IETF BCP47 (RFC 4646 and 4646bis and
related) language tags. There was a "Java Locale Enhancement Project"
initiated at OpenJDK, see
http://mail.openjdk.java.net/pipermail/discuss/2008-October/001341.html
That mail in the quoted text at the bottom also includes valuable links.

Further references:
http://mail.openjdk.java.net/pipermail/announce/2008-November/000063.html
http://openjdk.java.net/projects/locale-enhancement/

I'm eagerly awaiting the outcome. However, we cannot support different
script types for the same language as long as that issue isn't solved.
After that, conversion between MS-LangID and lang::Locale will have to
be adapted, handling inside i18npool to pass it down to ICU, and quite
some effort will have to go into storage of fo:script elements in ODF
(v1.2 will have that) respectively a RFC4646 fall-back where the
combination of fo:language, fo:script and fo:country is not sufficient.

I think this issue here should be retargeted to OOo3.x, doing so.

Thank you for being patient ;)

  Eike


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