tigefa4u projects Trac

l10n: forgot to extract one message, and corresponding french translation.

l10n/fr: javascript translations updated (100%)

#6353: extract messages from javascript code embedded in <script> tags in html files.

Mark some more messages for translation in *.js files.

Makefile: updated L10N tasks to take into account the catalogs dedicated to the messages in Javascript files (#6353).

Also, added an `init-xy` target for creating the catalogs for a given locale `xy` (only create the missing catalogs, e.g. the new messages-js.po one).

setup: move all l10n related commands in `trac.util.dist`.

This way, plugins can easily re-use the Trac operating mode (compile before install). If they need to localize .js files, they should do something like:

{{{#!python
from trac.util.dist import get_l10n_js_cmdclass
extra['cmdclass'] = get_l10n_js_cmdclass()
}}}

If they don't need the new `*_js` related commands, they should do:

{{{#!python
from trac.util.dist import get_l10n_cmdclass
extra['cmdclass'] = get_l10n_cmdclass()
}}}

Also, don't modify the standard `build` command in place, but rather subclass it (http://www.mail-archive.com/distutils-sig@.../msg11760.html).

setup: in `generate_messages_js` command, use binary mode to open the catalog file

l10n/fr: fill in translation for Javascript messages

l10n/fr: `python setup.py init_catalog_js -l fr`

#6353: tweak `trac.web.chrome` changes, in fact we always need babel.js in order to have `_` and `babel.format` defined and working.

Adding some fallback methods instead would have worked for `_` and `ngettext`, but for `babel.format` this needed too much copying from babel.js, so just include it.

Also fixed unit-tests in trac.web.tests.chrome.