1deb13e1aa
We have initTranslations() for binding an extension's
gettext domain, but nothing to help with using gettext
from an extension.
Such help would be useful though, as an extension that
calls textdomain() like a normal application would
inadvertently changes the default domain for the whole
gnome-shell process.
Instead, extensions have to use domain-specific versions
of the gettext functions:
```js
const Gettext = imports.gettext.domain('my-extension');
const _ = Gettext.gettext;
```
Make this a bit easier by adding those functions directly
to the extensions object when initTranslations() is called,
then expose helper functions for calling them.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2594
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1941>
|
||
|---|---|---|
| .. | ||
| completion/bash | ||
| man | ||
| po | ||
| src | ||
| COPYING | ||
| generate-translations.sh | ||
| meson_options.txt | ||
| meson.build | ||
| README.md | ||
gnome-extensions-tool
gnome-extensions-tool is a command line utility for managing GNOME Shell extensions. It is usually built as part of gnome-shell, but can be used as a stand-alone project as well (for example to create an extension bundle as part of continuous integration).
Bugs should be reported to the GNOME bug tracking system.
Building
Before the project can be built stand-alone, the po directory has to be populated with translations (from gnome-shell).
To do that, simply run the included script:
$ ./generate-translations.sh
License
gnome-extensions-tool is distributed under the terms of the GNU General Public License, version 3 or later. See the COPYING file for details.