Uli,

>Date: 28 Feb 1999 17:01:18 -0800
>From: [EMAIL PROTECTED] (Uli Foerster)
>Subject: Re: Char of the poptrigger down arrow
>
>
>- -----Original Message-----
>From: David Fedor <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Saturday, February 20, 1999 12:31 AM
>Subject: Re: Char of the poptrigger down arrow
>
>
>>...
>>By the way: to properly support other character sets (e.g. Japanese Palm
>>OS), we moved the PalmOS-specific characters that were improperly defined
>>as high ascii characters, meaning between 0x80 and 0xff.
>>
>>So in Palm OS versions greater than 3.0x, the command stroke character is
>>0x16 not 0x9d, the shortcut character is 0x17 not 0x9e, the ellipsis is
>>0x18 not 0x85, and numeric space is now 0x19 not 0x80.  The diamond, heart,
>>club and spade characters are in the symbol font now, not in the standard
>>fonts except as a temporary measure in English fonts for compatibility.
>
>So every app using one of these chars is broken past 3.0?
>Oh, no...

1. If you're running on a device which uses the Latin (code page 1252)
character encoding, currently all of the glyphs in the high ascii range are
the same as before, other than the shortcut and command stroke characters.

2. This situation will soon be changing, however. For example, location
0x80 will soon sport the sexy new Euro glyph, thus if you have to use a
numeric space character, you need to check the OS version and select either
0x80 (pre 3.1) or 0x19.

3. Which also means that if, for some reason, you must use the numeric
space character in resource data, you better have two sets, one for use
with pre 3.1 roms, and the other for 3.1 and later roms.

4. The character code positions used for the four playing card glyphs were
also undefined in older versions of the 1252 code page, but Microsoft is
gradually filling in the blanks...for example, 0x8E was the club playing
card character, but that code position has been assigned by Microsoft to
"Capital Z with Caron". Which means that if you read the tea leaves, you
want to use the new playing card glyphs located in the symbol font.

5. The horizontal ellipsis will continue to exist at location 0x85 in Latin
fonts, as that's part of the 1252 code page. It doesn't existin that
location for other character encodings, such as Shift JIS (Japanese). Which
means that if you absolutely have to use a horizontal ellipsis versus three
periods, you need to programmatically determine the correct character code
to use at run time, or have two sets of resources.

-- Ken

Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 650-947-9222 (direct) +1 408-261-7550 (main)


Reply via email to