VladPolskiy/dpkg
1
0
Fork 0
mirror of https://github.com/yaobinwen/dpkg.git synced 2026-01-12 08:20:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: Update l10n commit documentation

Browse Source 
Changelog: silent
This commit is contained in:
Guillem Jover
2020-11-08 03:36:45 +01:00
parent c4d7c906e6
commit 511f7183df
1 changed files with 21 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

67
README.l10n
View File

@ -1,63 +1,38 @@
Translators, when adding/updating your translation files, please follow
the following rules:
* Update debian/changelog:
* Do not update debian/changelog:
- The file will get generated out of the commit messages at release time.
- Beware that you should NOT update any of the legacy ChangeLog.old
files for translation updates.
* Format of entries in debian/changelog:
Translation updates should go in a dedicated "[ Updated foo translations ]"
section:
==========================================================
dpkg (1.13.15) unstable; urgency=low
.../...
[ Updated programs translations ]
* Catalan (Jordi Mallach).
* Portuguese (Miguel Figueiredo).
* Swedish (Daniel Nylander).
==========================================================
New translations should go in a dedicated section named
"[ New scripts translations ]":
==========================================================
dpkg (1.13.15) unstable; urgency=low
.../...
[ New dselect translations ]
* Vogon (Douglas Adams).
==========================================================
This file contents MUST be encoded in UTF-8, and the entries inserted
in language alphabetical order.
* Format of commit message
The formats above only apply to the debian/changelog file.
They do not apply to the commit message. Following recommendations
of <https://wiki.debian.org/Teams/Dpkg/GitUsage> you should start the
commit message with a summary line, followed by an empty line and a
a detailed/long description. For example:
Following guidelines in <https://wiki.debian.org/Teams/Dpkg/GitUsage>
you should start the commit message with a summary line, followed by an
empty line and optional pseudo-headers.
The summary line should use the following format:
«po: <Action> <Language> <part> translation»
Where:
- <Action> is one of “Update” or “Add”,
- <Language> should be capitalized (such as “English”),
- <part> should be one of «programs» (for lib, src/, dpkg-deb/, dpkg-split/
and utils/), «dselect», «scripts» and «man pages» (man/).
For example:
==========================================================
Update German translation of manual pages
po: Update German programs translation
Update to 1354t.
Closes: #123456
Reviewed-by: Full Name <email@example.org>
==========================================================
Note that the update should mention the file statistics as XXXtYYYfZZZu.
"XXXt" means "XXX translated strings".
"YYYf" means "YYY fuzzy strings strings".
"ZZZu" means "ZZZ untranslated strings".
YYY or ZZZ may be omitted if they are null.
* Use of po/LINGUAS, dselect/po/LINGUAS or scripts/po/LINGUAS:
When ADDING a new translation, don't forget adding the language to