On locale maintenance. February 15, 2007
Posted by andy in : coding, screengrab , trackbackI just had a thought.
The whole point of locales is to externalise the language from the extension code into translatable blocks that reside in a separate area. Currently this resides inside the extension, but why not have it reside on a remote server and cache it locally?
Obviously your extension could ship with whatever translations it has, but if the person using it was French and you didn’t include an fr-FR version then it could connect to a server (let’s say Babelzilla) and request it from their servers (Babelzilla hold all of the translations anyway). If it was there, it would be downloaded and incorporated into your extension somehow (this bit is where the magic happens).
Translations would be tied to a particular version, so when a developer releases a new version, you could log in to their system and roll forward all translations or deprecate them. Then any new translations could be easily made and added to your extension without you actually having to do anything.
If people wanted a particular translation, then they could request it through the extension that managed all of this dynamic locale stuff, or they could just write a translation and submit it.
I think this is a great idea. I must ask Goofy what he thinks.
Comments»
Do you want to buy a prom dress?
hi i want to help you in the developing of this add-on but in other way, i want to develop a version of this for my own with a few more specification please reply this message please