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 17:50:37 GMT

--- Comment #9 from orcmid <> 2012-04-13 17:50:37 UTC ---
Yes, the RTF specification allows, but does not require the use of
code-page-specific controls.

I assume it is not being specified beyond the use of the \ansi control because
the single-byte codepage does not appear to be used for anything but ASCII
(7-bit) codes and anything else in Unicode that does not fit in ASCII is coded
as '?' (but the Unicode character offering is correct).


It would seem that your particular problem would be solved were the RTF export
in OpenOffice updated to emit the \ansi\ansicpg1252 control sequence and
present the correct hex for cp1252 along with the Unicode code point when there
is a correspondence.  When there is no corresponding cp1252 code, the hex for
'?' would still be provided.  (cp1252 is more than Latin1 and your tunneling
usage depends on that).

Since the Unicode code points are also being provided, the RTF will still
interchange successfully among all Unicode-supporting RTF producers and
consumers (OpenOffice-lineage and Microsoft Office products, for exampe).


The only possible downside is for RTF consumers that use the code-page-relative
encodings instead of the Unicode information and do not recognize the
\ansicpg1252 control or simply fail to accept the full range of cp1256
printable codes.  This is probably low risk, especially with regard to the
defacto prevalence of cp1252 in the context of RTF (although Apple users might

I think that would allow your particular usage.  I have a separate question
about the use of OpenOffice as intended, though.

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

View raw message