roger.e.eller at sealedair.com
Mon Sep 30 11:24:50 EDT 2013
Loading a simple tab delimited text file in preOpenStack is one way.
Column 1 could contain object names or IDs, column 2 would be the labels in
the default language, column 3 would be those labels in another language,
and so on. Allow row 1 to be the language names with default language
abbreviations in parentheses (en) (ch) (fr) etc. You can use the first row
to populate a language choice menu. And the best part is that you (or the
end user) can easily add a language, even Klingon, outside of the
application using a simple text editor.
On Sep 30, 2013 6:17 AM, "Tiemo Hollmann TB" <toolbook at kestner.de> wrote:
> I don't know if somebody ever has made a "guide" for localization. I think
> the best approach depends on the quantity of objects of your stacks and
> languages you want to offer. From just copying the cards for each language
> and hard code the language to a sophisticated database with injection of
> propriate language on runtime into every object everything is possible.
> up to you. But perhaps somebody likes to shares his experience, like John,
> who was recently asking for a translation of button labels.
> Just my 2 cents, Tiemo
> > -----Ursprüngliche Nachricht-----
> > Von: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] Im
> > von Antti Ilola
> > Gesendet: Montag, 30. September 2013 11:56
> > An: How to use LiveCode
> > Betreff: Localization
> > Where do I find guide how to localize LiveCode stacks.
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
More information about the Use-livecode