diff options
| author | Patrick Storz <eduard.braun2@gmx.de> | 2019-10-17 00:16:32 +0000 |
|---|---|---|
| committer | Patrick Storz <eduard.braun2@gmx.de> | 2019-10-19 12:33:34 +0000 |
| commit | 76ce73061550ff42e97c1fec9836c35cc0e24d64 (patch) | |
| tree | 9ea6f017e13bc4f5cc63eb17f8a23e1e58ccee3a /src/selection-describer.cpp | |
| parent | Add export/import PDF blend modes and add isolation modifier (diff) | |
| download | inkscape-76ce73061550ff42e97c1fec9836c35cc0e24d64.tar.gz inkscape-76ce73061550ff42e97c1fec9836c35cc0e24d64.zip | |
Extensions: Implement translationdomain functionality
Inkscape will read the "translationdomain" attribute from the
<inkscape-extension> root element in the .inx file.
It will then attempt to lookup a message catalog that matches
this domain, register it with gettext, and use it for translations.
Message catalogs may be located in either
- the .inx file's location
- the root of the "extensions" directory containing the .inx
- the system location Inkscape's own catalog is loaded from
To make this functionality available to script extensions, Inkscape
will set the environment variables
INKEX_GETTEXT_DOMAIN
and
INKEX_GETTEXT_DIRECTORY
so extension scripts can then use something like
bindtextdomain(INKEX_GETTEXT_DOMAIN, INKEX_GETTEXT_DIRECTORY)
textdomain(INKEX_GETTEXT_DOMAIN)
to enable the feature.
See also
https://gitlab.com/inkscape/inkscape/issues/333
https://gitlab.com/inkscape/extensions/issues/117
Diffstat (limited to 'src/selection-describer.cpp')
0 files changed, 0 insertions, 0 deletions