> >> I tried changing the 'Transliteration' option in the PalmRez
> >> The 'None' option looks promising, but it just turns every character
> >> in every resource into a zero byte. THAT can't be right.
>
> > That sounds like a bug in PalmRez. Let's see...yup, it's a bug
>
>What is that option is actually supposed to do? When fixed, will it cause
>no transliteration at all (which is what I want) or will it still assume the
>input is Mac Roman and convert it to something else?
It will do no transliteration at all.
>Also, just what is the difference between the '3.0 and earlier' and '3.1 and
>later' options? The names suggest it has something to do with those few
>characters that got relocated in the 3.1 fonts, but I don't know what gets
>converted to what.
3.1 and later assumes that certain glyphs exist in the control range
of the four regular (non-symbol) fonts. Specifically:
Character MacRoman <= Palm 3.0 >= Palm 3.1
--------- -------- ----------- -----------
chrCommandStroke 0xC3 0x9D 0x16
chrShortcutStroke 0xC5 0x9E 0x17
chrEllipsis 0xC9 0x85 0x18
In pre-3.1 fonts, the command and shortcut characters were in the
high-ASCII range, at slots that were (at that time) undefined by
Microsoft's code page 1252. Since these undefined slots are filling
up, these characters were moved down into the control range. Since
app shouldn't typically need to have either of these characters in
resource-based text, it's unlikely that the change will impact
anybody.
The ellipsis was replicated to the 0x18 location so that every
regular font, no matter what the character encoding, would contain
this truncation character.
So 99% of all apps can just use the '3.0 and earlier' setting and be fine.
> Better documentation would be helpful.
I'll pass along the request.
-- Ken
Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 530-470-9200
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
