To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=42171
------- Additional comments from [EMAIL PROTECTED] Tue Feb 15 09:14:24 -0800 2005 ------- Thanks for looking into this issue. So if I understand correctly, the situation is that: a) Uniscribe has a bug/limitation that it displays invalid combinining character sequences poorly b) OOo sometimes gives Uniscribe invalid combining character sequences to display I don't think it follows from this that nothing needs changing in OOo. For example, if the document contains 0e01+0e48+0e35, which Uniscribe cannot display properly, the OOo display engine might transform that to 0e01+0e48+25cc+0e35 before giving it to Uniscribe to display. Alternatively the Sequence Input Checking could be made more vigorous on Windows so that it is impossible for the user to enter such invalid sequences (which I believe is the case with some competitor products). The current situation may well be Uniscribe's fault, but it is not an acceptable situation for OOo Thai users on Windows, and I find it hard to believe that there is nothing OOo can do to improve the situation. --------------------------------------------------------------------- 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]
