1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
## Packagers
**Packagers** should take the auto-generated
`org.hydrogenmusic.Hydrogen.metainfo.xml` files.
## Translators
**Translators** can edit the `*.po` files in [po](./po). In case your
language is not present yet, copy the `po/appstream.pot` file to a
file in the [po](./po) folder having your language code as basename
and `.po` as extension, like `es.po` or `pt_BR.po`. Please ensure no
other characters than the [language
code](https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry)
are contained in the basename as the toolchain is using it for the
`xml:lang` tag in the resulting document.
Applying new translations after editing or creating a `.po` file is
done using
``` bash
make
```
But it is also OK to just make a [pull
requests](https://github.com/hydrogen-music/hydrogen/pulls) with the
updated `.po` files or send it via our mailing list
hydrogen-devel[AT]lists.sourceforge.net and let the maintainers do all
the artifact generation for you.
## Maintainers and Developers
**Maintainers** and **Developers** must always edit
`org.hydrogenmusic.Hydrogen.metainfo.xml.in` when adding new releases
or updating meta information.
Translation of these metainfo files is separated from the main
translations in [data/i18n](../data/i18n) because it uses a different
toolchain and the main one should be as slim as necessary (`itstool`,
`msgfmt`, and `msgmerge` instead of Qt's `lupdate` and `lrelease`). In
addition, translation artifacts are not installed on the user's
system.
|
