>Ok, using CW7.0....but I am NOT using the Palm Constuctor....I HATE THAT >THING....I'm using VFDIDE and have the PilRC plugin for CW7.0 working >just fine. >Now the question....I want to put multiple languages on my palm app. How >did I do this before...well, I couldn't get the multi-language .prc >working,
What was the problem? >so I used cw to create the .r file and had some folks create >.r's with all the different languages. Then created different targets >with the appropriate .r's. > >Yeah, yeah...stupid...I know...but I was in a hurry and the prc plugin >for CW wasn't yet working correctly with multi language support (I THINK >that may be fixed now, not sure, haven't tried). What do you mean by "prc plugin" and "multi language support"? >Now, my problem, I have totally changed the prc for the next release of >our app. And, I don't want to do the same thing with the .r's again. So, >I need some advice on the best approach to managing multiple languages >in prc files with CW. > >One of the biggest problems is that when using multiple languages, >sometimes the text string size differences require slight field >displacement. In my experience dynamic form layout, even on desktop computers with big forms and lots of white-space, never really works as well as you would like. On the smaller Palm screen, this is even more of an issue. So this typically means that you have to have different form layouts for each language, and you wind up with (hopefully equivalent) sets of resource data, one for each target language. >Option 1: Create multiple prc's....but VFDIDE doesn't support multiple >languages (I'm talking kanji here folks, not roman languages). >Option 2: Use the multi-language support for PilRC. But the problem here >is with string lengths, especially in labels that are prompting for >field entry on the same "line" >Option 3: Dunno...any suggestiongs... I don't know how you'd best handle these with VFDIDE, but there are several CW-based approaches that have been discussed on this list previously - I think Scott Johnson describe one technique that he used, which was based on .r files. Typically the biggest challenge is keeping all of the data in sync (you add a button to the English form, and forget to update the Japanese version). -- 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/support/forums/
