Hacker News new | ask | show | jobs
by zatkin 3971 days ago
In my experience, localization is best done by referencing to indices in a key-value 'database'. So instead of saying "You have just purchased $x apples", you say $translate.instant('purchasedApples') (angular example), which references to en_US.json, which returns the English translation.
1 comments
MarkCole 3971 days ago
Oh I think you have misunderstood. On the code side for the website/software that is being translated that's what would happen.

This theoretical software is for gathering all of the translations, and having editors and translators (multiple) manage them with ease. Then generating all of the JSON/XML/XLIFF/Other_Format files for every language for use on the site/software. I have yet to find software that can do this well.

link
dawson 3971 days ago
https://www.localeapp.com/ does a pretty go job of this for Rails apps. We used it with 13 remote translators and I can't recommend it enough.
link
MarkCole 3971 days ago
Now this is a very interesting app, and is sort of almost what I would build with this theoretical 100k.

I feel like they are missing a trick with limiting themselves to just YAML/Rails though. I will keep an eye on this though, and hope they go language agnostic in the future. Seems to be a very well made product.

link