To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73103
------- Additional comments from [EMAIL PROTECTED] Fri Jan 5 20:40:13 -0800 2007 ------- pjanik: I set P2 because it's stopping people installing OpenOffice.org. They can't understand the first screens and just trash the app. :( sb: it's a possible workaround, but the problem is that decomposed Unicode is not uniformly supported. Different software (app or system) will handle it differently, resulting in displays which separate the base character and diacritic, and even, in one fascinating case, where diacritics became separated from the parent vowel and followed the cursor around the page. I spent several months once debugging a multiple and severe input/display problem that turned out to be caused by the use of decomposed Unicode, so I avoid it strictly since then. I'll consult on this. If we do decide decomposed Unicode is a worthwhile temporary option, how do we identify these strings in the overall GSI file? The last thing we want is the whole UI in decomposed characters. --------------------------------------------------------------------- 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]
