rust/comprehensive-rust
1
0
Fork 0
mirror of https://github.com/google/comprehensive-rust.git synced 2025-04-25 08:53:01 +02:00
Code Issues Releases Activity

Mention POT-Creation-Date in instructions (#1314)

Browse Source 
I don’t know if this is enough on its own? In principle, the new
publication system should work smoothly without people having to know
much about this header, so that’s why I only describe it briefly.

Followup to #1243.
This commit is contained in:
Martin Geisler 2023-10-07 18:32:10 +02:00 committed by GitHub
parent 1f022e318a
commit ac8e3ed14f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
TRANSLATIONS.md
View File

@ -100,18 +100,25 @@ Next, please update the file `.github/labeler.yml` to include the new language:
### Refreshing an Existing Translation ### Refreshing an Existing Translation
As the English text changes, translations gradually become outdated. To update As the English text changes, translations gradually become outdated. The
the `po/xx.po` file with new messages, first extract the English text into a translations contain a POT-Creation-Date header which tells you when they were
`po/messages.pot` template file. Then run last updated with new English messages.
To update the `po/xx.po` file with new messages, first extract the English text
into a `po/messages.pot` template file. Then run
```shell ```shell
msgmerge --update po/xx.po po/messages.pot msgmerge --update po/xx.po po/messages.pot
``` ```
Unchanged messages will stay intact, deleted messages are marked as old, and Notice that the POT-Creation-Date field is updated to the current time and date.
updated messages are marked "fuzzy". A fuzzy entry will reuse the previous This becomes the new baseline for the translation: new English text added
translation: you should then go over it and update it as necessary before you afterwards will not show up in your translation, including completely new pages.
remove the fuzzy marker.
When running `msgmerge`, unchanged messages stay intact, deleted messages are
marked as old, and updated messages are marked "fuzzy". A fuzzy entry is not
used when we publish a translation! You have to go over the fuzzy entries by
hand and verify that the translation is correct the fuzzy marker.
> **Note:** Your PRs should either be the result of running `msgmerge` or the > **Note:** Your PRs should either be the result of running `msgmerge` or the
> result of new translation work on the PO file for your language. Avoid mixing > result of new translation work on the PO file for your language. Avoid mixing