At 12:00am -0800 00-03-25, Palm Developer Forum digest wrote:
>Subject: Re: trademarkChr, etc., blues...
>From: Paul Nevai <[EMAIL PROTECTED]>
>Date: Fri, 24 Mar 2000 21:24:22 -0500 (EST)
>X-Message-Number: 48
>
># >Did you realize that if you want your program to be truly
>international then
># >you can't use chars like trademarkChr. In fact, you can't use
>anything above
># >127 [I think]. I wonder what can be done to keep trademarkChr,
>etc., and, at
># >the same time, to allow portability. Best regards, Paul
>#
># In the 3.5 SDK, the Chars.h header only contains characters that are
># safe to use with any character encoding. Characters that are specific
># to a given character encoding are contained in separate header files,
># for example CharLatin.h and CharShiftJIS.h. If you want to use one of
># these encoding-specific files, you'll want to define
># NON_INTERNATIONAL first, then include them.
>
>Hi Ken:
>
>Thanks. I knew this. I'd like international AND trademarkChr. Can't I have
>both? Best regards, Paul
Not sure what you mean by "I'd like international...". I assume you
mean "I want a program that will work properly no matter what
character encoding is being used on the device."
If you're talking about text found in static UI elements, then your
only two options are (a) always use "(tm)" for the trademark, or (b)
have multiple versions of the form/menu/whatever, and select the
appropriate one at run-time based on the device's character encoding.
If you're talking about dynamic text, then currently there's no API
which says "what's the character code for trademark on this device,
given its character encoding?".
When I had to deal with this in the past (on a Mac), I created my own
array of structs, which mapped from character encoding to trademark
string. For Latin (MacRoman) it mapped to the equivalent of
chrTradeMarkSign, and for most other encodings it mapped to "(tm)".
-- 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.palm.com/devzone/mailinglists.html
