At 12:00am -0700 00-09-20, Palm Developer Forum digest wrote:
>Subject: RE: strings and string lists
>From: Rick Gadbois <[EMAIL PROTECTED]>
>Date: Tue, 19 Sep 2000 14:10:48 -0400
>X-Message-Number: 62
>
>I am curious about this conversation. I write apps that run in several
>languages...10,12,15 languages.
>To date I have used indexed arrays.
So these are PC-relative strings, or resources? And does it have to
support dynamic language configuration (by the user, at run-time), or
can that be at install time?
>At times memory boundaries have been an
>issue, but I have always been able to solve these issues with segmenting.
>For each form I create in constructor, I dynamically fill it at run time
>with the appropriate language array. This way one prc supports several
>languages dynamically.
>I am not sure the way I am doing it is the most efficient.
>But, I wouldn't want to use constructor for 10 languages X 100 screens.
Wow, 100 forms? That's a big UI. I'm assuming this is the Esendant
Patient LogPad�, right? One option is to use .r files with #if
statements to control which data is used for resources (based on the
target locale), which would simulate what I think you're doing with
hard-coded strings, but still keep it localizable.
>Do you need to use constructor for overlays?
No. Well, yes, but not yet. Unfortunately the tool situation with
respect to overlays isn't great. The best solution currently is to
use the PRC2OVL tool that comes with the 3.5 SDK. This can create an
overlay from a full PRC - but that means you have to build the
localized PRC first, and then extract the localized resources into an
overlay.
-- 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/
