incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 119219] Saved RTF has issue in encoding Latin1 characters
Date Fri, 13 Apr 2012 16:13:32 GMT

--- Comment #6 from orcmid <> 2012-04-13 16:13:32 UTC ---
(In reply to comment #0)
> Hi,
> In Open Office 3.2 windows version, I observed issue in RTF file.
> You may open Open Office writer and copy -paste this string -- šbkeâ}sKeve
> (Note - this is not garbage data but meaningful Asian word if used with
> monolingual font - APS-DV-PRAKASH)
[ ... ]
> This does not give any issue in rendering the string in Open Office writer but
> if this file is used in other programs which strictly uses HEX values, we hit
> with issue. (Anyways incorrect HEX values is definitely an issue!)
> Thanks,
> Chaitanya

Here's my understanding of the situation.  I won't get too deep into it because
I'd like confirmation first:

The idea is to use OpenOffice-lineage software (i.e., 3.x,
Apache OpenOffice) in an out-of-band protocol trick for making documents using
a particular Asian character set encoding.  The use of the Asian character set
is accomplished by disguising it as single-byte Windows ANSI codes,
specifically Microsoft cp1252 (a variant of ISO 8859-1 in which the C1 controls
(codes 0x90 - 0xAF and perhaps others) are replaced by other graphic
characters.  The correct rendering is obtained in some single-byte applications
by using a font that renders the codes as quite different characters than those
specified for cp1252.

To accomplish the tunneling in 3.2 and later, the correct
Unicode characters for those Windows ANSI characters are used, although their
Unicode code points are not the same as the Windows ANSI code points.  I am not
sure how those are being entered in practice.  Apparently the correct Unicode
characters for the desired Asian characters are not being entered.

The disappointment is that the export from Unicode-centric OpenOffice ODF
1.2-supporting documents to RTF does not convert the Unicode characters used to
corresponding cp1252 code points so that they are successful disguises for
Asian characters in some non-Unicode applications.

An obvious way to move these characters through OpenOffice is by using the
correct Asian characters (if they exist in Unicode) in the first place, with
appropriate fonts and font mappings from Unicode.  This will work for
interchange among modern Unicode supporting applications, and it will work over
RTF.  Unfortunately, that does not do much for (legacy?) non-Unicode
applications and for those RTF documents created based on using the cp1252

Is that the essence of the situation?

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.
View raw message