Validating and testing translations

aulo.aasmaa shared this question 9 years ago
Answered

Hello,


I am participating in the menion project in CrowdIn for translating Locus application to Estonian. Now that all available translations are done, I would like to ask if it is possible to actually download the XML files the translations concern to try the translations out in real application to see how they fit and match real situations etc. Any tips on taking the translated XML files into use on my Android phone (HTC WildFire) also useful. I mean if a simple overwriting would not do the trick.


Thank you,


Aulo Aasmaa

Replies (6)

photo
0

Hi Aulo,


first, many thanks for your translation!


It`s very helpful for us and mainly for ours users from Estonia.


You can see your translation in next version of the Locus. There isn`t in the Crowdin any way for your control of the translation, but if you want, we can prepare for you a test version of the Locus for your continously control.


Please, let me know, what you prefer.


Kind regards


Hana

photo
0

I have now managed to download all 4 XML files with Estonian translations from Crowdin site. How can I test them out in Locus Pro? Do I need some special testing edition of Locus for it or do I have to place them to some special location so Locus knows to read them?


Thank you already in advance!


Aulo Aasmaa

photo
0

Hi Aulo,


you`re too fast and very active :) There is unfortunately no way for you to simply test these texts just by putting them into some directory or something like this.


I created testing version with fresh texts from crowdin, so you may check what you need. Version is here for download https://dl.dropbox.com/u/8015949/Locu...

photo
0

Thank you! Maybe in some future version then.


My question is answered and happy with an answer and I only add an idea perhaps for future consideration:


Some applications have a functionality so that they monitor some folder for certain files and if found, then the external files take higher priority over same files of the actual application. This is often used approach in localization.


Say there was a /mnt/sdcard/Locus/Localization/{et|en|cz|...}/ folder and in that folder all the 4 XML files. Then when selecting a localization in Locus these files would be used instead of the ones in the application. Nothing will be overwritten anywhere, just during runtime these files would be used instead. Anybody could then make the language files suiting best for their needs.


No need for any new UI functionality - only the above mentioned principle would be documented in Locus Wiki and useful for developers and translators for easier testing.

photo
0

Thank you, the link can be removed now. Installing the application and checking out the translations as well as making necessary changes then in the Crowdin environment.


BTW - despite having being used Locus for quite a long time only now I am getting to realize how amazing application you have created. No other application I have tried offers so good customization, live tracking, online/offline maps selection and many many other features all in a neat single package. Well done indeed!

photo
0

this is interesting idea, unfortunately I think this is not possible in Android. All images and mainly translation files, are compiled during creating of APK package. So they`re hardcoded into this package and it`s not simply possible to use some external files.


Also settings of language in Locus is also little bit "hacking of Android" because by default, in Android is no functionality to simply change language in one single application. Usually, language in app is selected by language of your phone.

Leave a Comment
 
Attach a file