luisgulo/photoprism
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Translations: Update frontend README.md

Browse source 
Signed-off-by: Michael Mayer <michael@liquidbytes.net>
This commit is contained in:
Michael Mayer 2020-07-16 10:29:03 +02:00
parent 73e7911b5e
commit a4c68fb34a
1 changed files with 7 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
frontend/src/locales/README.md
View file

@ -19,9 +19,8 @@ identified by their [two-letter locale](https://www.gnu.org/software/gettext/man
like `de.po` for German.
You can open, edit and save them with Poedit to update existing translations.
!!! info
As it doesn't seem necessary for now, and to reduce the amount of work,
we don't maintain translations for dialects like `de_AT` or `pt_BR`.
As it doesn't seem necessary for now, and to reduce the amount of work,
we don't maintain translations for dialects like `de_AT` or `pt_BR`.
To add a new translation, open `translations.pot`, click on "Create New Translation" at the bottom, select
the language, and start translating.
@ -29,6 +28,11 @@ When done, save your translation as `*.po` file using the two-letter language lo
In addition, the new language needs to be added to the `Languages` function
in `/frontend/src/options/options.js`.
A binary `*.mo` (machine object) file will be automatically saved along with every `*.po` file.
You won't be able to open those in a text editor, but please include them in git commits or when sending
translations via email. The compiled `translations.json` file is not required for pull requests
and often causes merge conflicts.
If you have a working development environment in place:
Running `npm run gettext-compile` in the `frontend` directory compiles existing translations into
@ -55,8 +59,3 @@ in the `frontend` directory. This updates the POT file `translations.pot`.
Apply changes to existing translations by clicking on "Catalogue" > "Update from POT File..."
in the Poedit app menu.
!!! note
A binary `*.mo` (machine object) file will be automatically saved along with every `*.po` file.
You won't be able to open those in a text editor, but please include them in git commits or when sending
translations via email. The compiled `translations.json` file is not required for pull requests
and often causes merge conflicts.