View Single Post
Old 01-08-2012, 08:25 AM   #84
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
Quote:
Originally Posted by ixtab View Post
One more addition -- just thinking aloud about what would happen if we switched to UTF-8 properties:
- the advantage would be that editing files locally becomes easier.
- the tool would need to be rewritten to initially produce UTF-8 files, and to cope with UTF-8 in translated files. (rewriting into ISO-8859-1 if necessary)
- most importantly though: What would happen to *already existing* translations at transifex? We have steady progress for quite a few languages there, and I guess translators will be pissed off in case everything suddenly goes back to zero. This is the worst-case scenario, and I hope it wouldn't happen, but I'm not sure how to properly test this.
It could be possible to pull all translations from Transifex, commit current state, replace in localized .properties \uXXXX with UTF-8 characters (with some script) and push updated translations back. Even in a case of error in work of script noone translation wouldn't be lost as they will be stored in Git repo, so we could retry or even rollback

But, of course, there will be some roughnesses in transition from PROPERTIES to MOZILLAPROPERTIES (where values are stored in UTF-8), so your point is completely valid here. Though, I think these roughnesses are manageable.

Last edited by eureka; 01-08-2012 at 08:27 AM. Reason: clarify choices for recovery from script error
eureka is offline   Reply With Quote