Download
2011-03-16, 09:33:13
I was thinking also about a possibility to upload translation files directly into plugin's archives in extend.
(the backend would have to compress all plugin files along with translation files before it would be send to visitor who requested the file)
But there are 2 major problems with it:
1. what if plugin developer uploads a new version of his plugin ?
2. what if somebody creates own version of translation file for a plugin, and uploads it ?
As it goes about first point, traductors could be informed through a mail, that there's a new version of plugin which needs a translation update.
With second point, plugin dev would have to have a possibility to manage incoming translation files. It's a bit complex, as developer would have to have the ability to manage all actions in all possible circumstances.
But then we step into another problem: if developer stops development, and forgets about GS completely, but his plugins will be still working in new GS versions, who will handle uploaded translation files ?
(the backend would have to compress all plugin files along with translation files before it would be send to visitor who requested the file)
But there are 2 major problems with it:
1. what if plugin developer uploads a new version of his plugin ?
2. what if somebody creates own version of translation file for a plugin, and uploads it ?
As it goes about first point, traductors could be informed through a mail, that there's a new version of plugin which needs a translation update.
With second point, plugin dev would have to have a possibility to manage incoming translation files. It's a bit complex, as developer would have to have the ability to manage all actions in all possible circumstances.
But then we step into another problem: if developer stops development, and forgets about GS completely, but his plugins will be still working in new GS versions, who will handle uploaded translation files ?
Addons: blue business theme, Online Visitors, Notepad
