# RE: New on list

From: Alfinito, Charles (AlfinitoC@cadmus.com)
Date: Tue Jan 12 1999 - 16:00:46 EST

"In
this
case, you have 8776 = U+2248 (ALMOST EQUAL TO), and the approximation
is the TILDE."

I'm not as deep into this info as you guys are. Forgive me. Where would I
get the conversions such as 8776 + U+2248.

Thanks,
Charles

-----Original Message-----
From: Brendan_Murray/DUB/Lotus@lotus.com
[mailto:Brendan_Murray/DUB/Lotus@lotus.com]
Sent: Tuesday, January 12, 1999 3:05 PM
To: Unicode List
Subject: Re: New on list

Charles Alfinito wrote:

> Unicode is presenting a problem. For example, a ~ may be the character in
a
> file. Normally in RTF this would be shown as \'98. Recently I had a file
> with the unicode, \u8776\'98. This character should have been an
> "infinity". Since my program can't handle the Unicode RTF (\u8776) it
> ignores it and changes the \'98 to a ~ which obviously is wrong.

Your RTF parser should accept the token pair \uxxxx\'yy as one: these refer
to
one
character, where the "xxxx" is the decimal value of the Unicode character,
and
the
"yy" is the fallback character (approximation) in your current code page. In
this
case, you have 8776 = U+2248 (ALMOST EQUAL TO), and the approximation
is the TILDE. If you want to be accurate, take the Unicode value; if you
only
want
a quick and dirty solution, use the fallback character.

This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:44 EDT