1
Notabily something I have found is the length of time it takes to poll translation api's, my solution to this was to build :
https://translator.labs.coop/ - The Chronolabs Translation API.
This stores translations and can be passed a storage token which for a module would be something like for xtransam as a module as
md5('xoops-module-xtransam') - so that if someone else has ran for the translation your after; it will retrieve it from the cache for upto 24 months from the initial translations rather than having to wait to poll google, bing or mymemory.
This uses a file storage method not a database with similar classes to the cache class that comes with XOOPS - this is cause flat files are always much quicker than using a Database store and more manageable on mass.
In the next few weeks I will update xTransam, to this API for it provider methods this is so we eventually have fast and quick translations stored in the cache on this API. I will then after making a new Major Version of xTransam, looks too see if the language files have been finalised for XOOPS 2.6 and make a version for this as well.
I will post a thread here when both are complete!
Thanks
Simon - wishcraft/mynamesnot
