Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of 3chaitanya@gmail.com
 designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
From: Chaitanya Sevak <3chaitanya@gmail.com>
Date: Thu, 12 Apr 2012 15:38:35 +0530
Message-ID: 
 <CAPvKu=zw3e4MGyYmm0vK=0Xd-bVZoTKHUHohEPT4h0c21S_-YA@mail.gmail.com>
Subject: Saved RTF has issue in encoding Latin1 characters
To: ooo-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d044304d03607a104bd788b62

--f46d044304d03607a104bd788b62
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 -- =C5=A1bke=C3=
=A2}sKeve
(Note - this is not garbage data but meaningful asian word if used with
monolingual font - APS-DV-PRAKASH)
Then save the file as RTF and check the RTF code using any notepad
application.

It saves the non english characters as unicode values and HEX code in
following fashion
For character =C5=A1 - RTF file code shows - \u353\'3f
For character =C3=A2 - RTF code shows - \u226\'3f
Like this for every special character the unicode value is correct but for
each such character HEX code is incorrect and that is - \'3f for every
special character.

Same string is stored in AbiWord shows proper HEX values-
For character =C5=A1 - RTF file code shows - \u353\'9a
For character =C3=A2 - RTF code shows - \u226\'e2
Which are correct as per wiki link.
http://en.wikipedia.org/wiki/Windows-1252

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

*Was reported on forum at -
http://www.oooforum.org/forum/viewtopic.phtml?t=3D153638*

--f46d044304d03607a104bd788b62--