Many thanks for your answer, and your expertise !
I didn't know about that unused range, it will help me a lot since I just
have to focus my attention on it now.
Simon
Philip Semanchuk <[EMAIL PROTECTED]>
12/03/2003 15:53
Veuillez r�pondre � fop-user
Pour : "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
cc :
Objet : RE: Question about Word character encoding.
On Wed, 2003-03-12 at 09:16, [EMAIL PROTECTED] wrote:
> Here is the function I just coded to resolve my issue with the Word's
> specific characters (appearing as # in the resulting PDF). As I said, I
> did'nt find any complete table of the M$ Word's specific characters, so
> this function is not complete at all, but it is enought for my problem !
Simon,
I don't know what Word uses for internal character representation, but I
would not be surprised if it is the Windows-1252 character set. Win1252
is a superset of ISO8859-1. It defines the characters between 0x80 and
0x9f which ISO8859-1 specifically leaves undefined. It is in this range
that you find the curly quotes, em dash and TM symbol that often make
their way into documents and then don't display properly on non-Windows
platforms.
There is a great Web page about it here:
http://czyborra.com/charsets/iso8859.html
HTH
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
