incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 119219] Saved RTF has issue in encoding Latin1 characters
Date Mon, 16 Apr 2012 19:39:17 GMT
https://issues.apache.org/ooo/show_bug.cgi?id=119219

--- Comment #21 from orcmid <orcmid@apache.org> 2012-04-16 19:39:17 UTC ---
(In reply to comment #20)
> Hi orcmid,
> Thanks for your cooperation. Could you please guide us how to find charset of a
> font ? How does Open Office detects fcharset ?
> Thanks

The character code that a font is based on is determined by TTF information. 
That appears to be how the same font can be used with software that works with
single-byte code-page characters and other software that has a different
"native" character set, such as a Unicode representaitn.

It is clear that \fcharset0 is determined correctly some of the time during the
export as RTF and it is not determined correctly at other times.  The
\fcharset128 seems to be inappropriate at all times unless there is something
like the Indic extension that can happen with the font you are using.  I doubt
that.

Since this is specific to RTF, the first place to look is in the code of the
RTF export.  There may also be interactions with the different ways characters
are introduced and the APS-DV-Stardust font applied to them.  But somehow,
there is a determination that has either \fcharset0 or \fcharset128 used at the
front of the file and then the occurences of characters with that font are
converted appropriately (as \' cp1252 codes) or not (as \u Unicodes with "?"
single-byte representations).

I am not familiar with the RTF export code and cannot offer any further
information.

-- 
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.

Mime
View raw message