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


User mba changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'mba'                     |'er,mba'
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Thu Nov 27 14:09:04 +0000 
2008 -------

No, mn-TR is no valid ISO locale.

And this brings us to another problem that can make even "Plan C" impossible.

There is i18n-based functionality like our "break iterator" that is though to do
something with text, based on its "language" attribute, that we transport as UNO
struct com.sun.star.lang.Locale.

This struct does not allow to transport the script type and so e.g. the break
iterator is not able to distinguish between Mongolian text in cyrillic and
traditional layout. 

As the i18n code and even more the ICU that it uses for many purposes doesn't
know anything about configuration settings, I currently see no way to consider
additional information to make the wanted differentiation inside our i18n 
library.

So at the end we can have linguistic and other i18n support only for either the
cyrillic (Plan A) or the traditional (Plan B) variant.

cc'ing Eike, our expert for i18n stuff.

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