> I think you would be better off managing the resource file so you can have
> seperate builds. Very few software developers like to have their binaries
> from a make altered by "branding" software. Also, there are times when you
> localize, dialogs need to be re-laid our due to size of text and there are
> also social and political issues where you don't want the same functionality
> per localization.
thats what Makefiles are for *grin*
---
# compile requirements
all:
LANG=en PROTECTION=ON make dkjr
LANG=en PROTECTION=OFF make dkjr_unprotected
LANG=de PROTECTION=OFF make dkjr_unprotected
LANG=it PROTECTION=OFF make dkjr_unprotected
LANG=sv PROTECTION=OFF make dkjr_unprotected
---
*grin* - also, if you put all your "internationalized" resources into
a resource file (.rcp), you can parse the resource files using the
following syntax:
dkjr_$(LANG).rcp
:) thats the trick i have been using for a *long* time :) each .rcp
file has its own unique layout/setup for each language - which, normally
only needs to be done once.
btw: i have never released the localized versions :) i did it for fun.
// 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/
