• Replies 1 reply
  • Subscribers 16 subscribers
  • Views 350 views
  • Users 0 members are here
Options
Related

Do you localise?

9635560
over 5 years ago

This is not a how to question - I know how. 

This is a “do you?” question, followed by “why?”.

Do you localise your apps / DF / widgets?

Why?

If so, have you noticed any benefits?

What languages do you use and why?

Et encores... Und so weite...

  • over 5 years ago

    Hi, good question.

    In practice, I use English and french.

    English, because it s international.

    French, because I am french and french people prefer have an app in french (benefit 1).

    Doing translations is many languages are not easy (finding the good words...with the good size) so it takes time to implement (disadvantage 1) , it takes time for the maintenance (disadvantage 2) and takes time for the tests (disadvantage 3).

    For one of my app, I dont have used  the internationalisation for ... memory reasons!

    1) each entry in .xml costs memory, so if you have 300 labels to translate it will use memory (about 8ko, I don t remember exactly)

    2) using Ui.loadResource(Rez.Strings.Calorie) in code costs more memory than using "Calorie", so you will earn memory again.

    If you don t have memory constraint, use internationalisation in english. Its very boring to implements internationalisation when the code is done.