[wp-polyglots] Automatic update in 2.7 for local distributions

Jovan Kostovski chombium at gmail.com
Thu Aug 7 23:17:08 GMT 2008


Hi,

Here is my suggestion:

1. Read wp-config to get the locale settings and installed plugins to
get list of plugins

2. Connect to a remote server and collect the translations
2.1. Check for binary compiled translation files .mo exist
  If only .po version exists, compile it on the fly on the remote
server and send it to the user
  In case no translation can be found inform the user and use the
default language - English.
2.2 The script will replace all the files which will be found. I
wouldn't remove the old translations
 of the files which can not be found because the translations differ
only a little from version to version.
 This way the user will have a translation which will have few tens of
untranslated strings.

We should get a location where we should post the translations or the
update script should collect the files
from the translations SVN tree. As Milan said, it would be nice if
this location is configurable but this
would bring bigger complexity since every translation file can have
different location. Maybe you can add
one location that would be default (it will be considered that all
translations are there) and the user to be
able to add exceptions for every translation file separately.

The update would be problematic for those blogs which use multilingual
interfaces. This comes from the
variety of plugins for multilingual support and the number of
languages used. Basically this update will
be the same as described above but the script would have to check
which plugin for multilanguage
support is used and to read the appropriate config file. And once
again the things become really complex
since there are many plugins which enable multilanguage blogging and
each of them uses it's own way
for language configuration.


HTH, Jovan


More information about the wp-polyglots mailing list