jimberry
10-16-2002, 09:34 AM
So what are the chances of getting the resource editor/compiler to use a text resource script as its storage medium instead of the current binary .bri files?
Currently, if I have an app with a hundred text strings, I have to use the windows gadget thingies to type in each string and its ID. Worse yet, if I need an Italian version of the resource file, I have to then type in all of the Italian strings, along with the IDs again. And for German...
It'd be an awful lot easier if there were just text resource scripts (like Windows and PalmOS resource scripts) into which I could just type the strings using a text editor. Then I can just email the relevent sections of the script to anyone who wants to edit or translate them and when they email 'em back I can just paste in the changes in one fell swoop.
Any thoughts?
I guess alternatively it would work to have an "import from text file" option when you create string resources, but it's not as elegant, flexible or simple as just using a text script to start with.
-jim
Currently, if I have an app with a hundred text strings, I have to use the windows gadget thingies to type in each string and its ID. Worse yet, if I need an Italian version of the resource file, I have to then type in all of the Italian strings, along with the IDs again. And for German...
It'd be an awful lot easier if there were just text resource scripts (like Windows and PalmOS resource scripts) into which I could just type the strings using a text editor. Then I can just email the relevent sections of the script to anyone who wants to edit or translate them and when they email 'em back I can just paste in the changes in one fell swoop.
Any thoughts?
I guess alternatively it would work to have an "import from text file" option when you create string resources, but it's not as elegant, flexible or simple as just using a text script to start with.
-jim