On Thu, Jun 4, 2015 at 8:59 AM, Matjaž Godec <matjaz...@gmail.com
> If I see correctly, Your tools adds translations to project sources.
> How about external Language packs ?
Yes, that's correct - it's designed to work with the English and the
translation co-existing at the same path. The install and check
commands work like that, but the other commands should work against
any supplied path.
> Can You please explain, where in the extension structure we have to put
> translation files, to be picked in for example header menu.
As far as I know, the instructions contained on this page are still
In addition to that, translations are effectively extensions to the
properties files (with a specific locale), so can be placed in a
directory structure that matches the original, in a path that is
mapped in the extension module's XML file (e.g.
> I checked for Slovenian and all instances of Home, Shared Files, My Files,
> Sites, Tasks are translated but in header menu they still appear in English.
> In the same header People, Repository, Admin-tools get translated strings.
> Very strange and inconsistent.
That is very strange - the translations work for the bundled
languages. Have you tried comparing the Slovenian bundle against
another language? If that's the same, it's possible there's some bug
with loading external properties in some cases (it's not covered by
our test cases), so should be raised in JIRA (if you let me know the
JIRA number, I'll be able to take a look).