🚀 go-pugleaf

Hello Sudesh,

If you want localize your software, there are two approaches:
1) Binary localization
2) Source localization

The idea in binary localization is that you read in original EXE that you've 
compiled and write out localized EXEs or language files (resourcedlls). This 
makes the localization process very simple. See for example 
http://www.multilizer.com/dev/vcl/ to see how this is done in practice.

Unlike binary localization, source localization might involve adding 
3rd-party code in your software before it can be localized. And the name 
also tells that you work on the source to produce language versions, after 
that you compile.

Both ways of doing the localization has they cons and pros. Anyway, binary 
localization has two big advantages:
1) No 3rd-party code needed
2) Localization process can't get easier ( EXE -> Translate -> Localized 
EXE)


Before localizing anything, however, you need to internationalize the code, 
i.e., ensure that all data that needs to be localized is separated from code 
so that localization tool can access it. In litterature this is called 
'internationalization'. For instance ModelMaker Code Explorer 
(http://www.modelmakertools.com/articles/hard-coded-strings.html) helps in 
automating this step.

Best regards,

Erik Lindberg
Multilizer

"Sudesh" <sudeshc@vfemail.net> kirjoitti 
viestiss�:4499917f$1@newsgroups.borland.com...
> Hello:
>
> How to Internationalize an existing BCB application?
> Any guidelines are appreciated.
>
> Thanks,
> Sudesh
>
>
>
>