https://issues.apache.org/ooo/show_bug.cgi?id=119219
--- Comment #10 from orcmid <[email protected]> 2012-04-13 18:02:56 UTC --- (In reply to comment #7) OFF TOPIC: Your immediate problem is resolved by upgrading the RTF export to use all of cp1252 as the alternative code set for non-Unicode consumers, as I discuss in Comment #9. That is not to see that this will happen, nor when. It requires someone to work over the RTF export code and implement a more-complicated support for the cp1252 mapping. (I suspect that there might be no mapping at all at the moment, with the code point for ASCII '?' used every time a Unicode escape is produced.) I have a separate question. When OpenOffice is used, how are the *desired* Asian characters entered by operators? Do you have keyboards for this? Do you select a particular font that causes the tunneled Asian characters to appear in displays and when printing? Finally, are you using a localized version of OpenOffice that supports that Asian language in your user interface? It would be good if OpenOffice were set up to use the Asian characters as they exist in Unicode, which would make full interoperability among Unicode uses, including in all of the ways I am asking about. Unfortunately, that would then conflict with the RTF case since Unicode codes that map to cp1252 would no longer be used. Is there any plan for working out of this bind and beginning to use Unicode correctly? -- Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
