Skip to content

Commit

Permalink
Update po/README.md [skip ci]
Browse files Browse the repository at this point in the history
Instructions now use the new script, without reference to intltool.
The intltool scripts have been mostly obsolete for a number of years.
  • Loading branch information
jplloyd committed Mar 4, 2020
1 parent d8dcc0e commit 5e576ce
Showing 1 changed file with 7 additions and 13 deletions.
20 changes: 7 additions & 13 deletions po/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,24 +16,18 @@ We use [GNU gettext][gettext] for runtime translation of program text.
## After updating program strings

After changing any string in the source text which makes use of the
gettext macros, you will need to manually run

cd po/
intltool-update -g libmypaint --pot

for lang in `cat LINGUAS`; do
intltool-update -g libmypaint --dist $lang
done

gettext macros, you will need to run `./po/update_translation.sh`
and then commit the modified `po/libmypaint.pot` and `po/*.po`
files along with your changes.
Keeping this generated template file in the distribution
allows WebLate users to create new translations by themselves
without having to ask us.

The `.pot` file alone can be updated by running
just the first `intltool-update` command,
if all you want to do is compare diffs.
if all you want to do is compare diffs,
the `.pot` file alone can be updated by running:
```
./po/update_translations.sh --only-template
```

# Information for translators

Expand Down Expand Up @@ -69,7 +63,7 @@ Before working on a translation,
update the `.po` file for your language.
For example, for the French translation, run:

intltool-update -g libmypaint --dist fr
./po/update_translations.sh fr

## Use/Test the translation

Expand Down

0 comments on commit 5e576ce

Please sign in to comment.