> Multilizer supports binary localization method in Palm software
> localization. Multilizer derives for example the following benefits from
> binary localization. Many features affect, besides developers, also
> translators and the QA. ( To see both Pros and Cons of binary localization,
> check "Localization Types":
> http://www.multilizer.com/dev/localizationtypes.htm )
>
> Reduced complexity.
so, its not for us hard core programmers then.. i'll stick to my
makefiles - i have never had problems sending someone a .rcp file
(100% text) and then getting them to translate it.. they normally
only translate text anyhow - maybe a few small fixes here and there
for alignment, but, thats no biggie.
> - No compiling required. Since the binary is being edited directly, there's
> no need to recompile language versions.
what happens when the new language makes a control bigger than it
was in its native language? to be perfect, someone is going to have to
move the resource..
> - Your engineers can achieve faster debug-fix cycles, since translation bugs
> can be fixed immediately within Multilizer.
vim project_$LANG.rcp
pilrcedit project_$LANG.rcp
dont see anything that would speed that up *grin* - also, not touching
the *sources* :)
> - Sensitive source files do not need to be dispatched to translation
> agencies, ensuring that you protect you IP and investment in your code. All
> you need to send is a *.PRC along with Multilizer Project file.
this is not required if you have seperated your resources from your
sources (as, most programmers should have done)..
> Erik Lindberg
> http://www.multilizer.com
i am sure some people will find it useful, i'd actually prefer to
see a real localization solution on the palm - overlays just dont
cut it either... what the hack, a new project for me.
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
