Several extensions have indicated they would like translation to other languages.
Its not clear how this can be achieved. Any ideas on the proper approach - even if we can't do it now ? - current info - https://inkscape.org/en/contribute/translations/#translatable-content
Currently .po files are: - not dynamic and distributed with the main distributon - are per language They use a mechanism of direct translation of one phrase into a substitution phrase as outlined here: - http://wiki.inkscape.org/wiki/index.php/Translation_information#PO_translati...
So this mechanism cannot accommodate the extensions which probably need: - one file per language added to the current inx and code file. - perhaps a way of merging all these new po files when extensions are loaded.
Now: When we write an extension we can use the underscore variants (below) to get translations. My assumption is that this is looking in the translation database on the off-chance the word has been translated. However this will fail for all descriptions and currently untranslated names, options, gui-texts and items.
The complete set of translateable types for extensions is: - _gui-text, _name, _description, _filetypename, _filetypetooltip, _item, _option, _param - but its not clear any do get translated.
Can anyone confirm this is how it works now ? Any ideas on a plan for what might be done in the future so we can add it to the todo list ?