Commit | Line | Data |
---|---|---|
1479465f GJ |
1 | Translators, when adding/updating your translation files, please follow |
2 | the following rules: | |
3 | ||
4 | * Update debian/changelog: | |
5 | ||
6 | - Beware that you should NOT update any of the legacy ChangeLog.old | |
7 | files for translation updates. | |
8 | ||
9 | * Format of entries in debian/changelog: | |
10 | ||
11 | Translation updates should go in a dedicated "[ Updated foo translations ]" | |
12 | section: | |
13 | ||
14 | ========================================================== | |
15 | dpkg (1.13.15) unstable; urgency=low | |
16 | ||
17 | .../... | |
18 | ||
19 | [ Updated programs translations ] | |
20 | * Catalan (Jordi Mallach). | |
21 | * Portuguese (Miguel Figueiredo). | |
22 | * Swedish (Daniel Nylander). | |
23 | ========================================================== | |
24 | ||
25 | New translations should go in a dedicated section named | |
26 | "[ New scripts translations ]": | |
27 | ||
28 | ========================================================== | |
29 | dpkg (1.13.15) unstable; urgency=low | |
30 | ||
31 | .../... | |
32 | ||
33 | [ New dselect translations ] | |
34 | * Vogon (Douglas Adams). | |
35 | ========================================================== | |
36 | ||
37 | This file contents MUST be encoded in UTF-8, and the entries inserted | |
38 | in language alphabetical order. | |
39 | ||
40 | * Format of commit message | |
41 | ||
42 | The formats above only apply to the debian/changelog file. | |
43 | They do not apply to the commit message. Following recommendations | |
44 | of <https://wiki.debian.org/Teams/Dpkg/GitUsage> you should start the | |
45 | commit message with a summary line, followed by an empty line and a | |
46 | a detailed/long description. For example: | |
47 | ||
48 | ========================================================== | |
49 | Update German translation of manual pages | |
50 | ||
51 | Update to 1354t. | |
52 | ========================================================== | |
53 | ||
54 | Note that the update should mention the file statistics as XXXtYYYfZZZu. | |
55 | ||
56 | "XXXt" means "XXX translated strings". | |
57 | "YYYf" means "YYY fuzzy strings strings". | |
58 | "ZZZu" means "ZZZ untranslated strings". | |
59 | YYY or ZZZ may be omitted if they are null. | |
60 | ||
61 | * Use of po/LINGUAS, dselect/po/LINGUAS or scripts/po/LINGUAS: | |
62 | ||
63 | When ADDING a new translation, don't forget adding the language to | |
64 | the LINGUAS file, otherwise it will not be used. | |
65 | ||
66 | * Always CHECK your translations: | |
67 | ||
68 | You MUST check your PO files for validity. | |
69 | ||
70 | The correct syntax for doing so is: | |
71 | ||
72 | $ msgmerge -U <file> dpkg.pot | |
73 | $ msgfmt -c -o /dev/null --statistics <file> | |
74 | $ msgcat <file> >/dev/null | |
75 | ||
76 | - msgmerge updates your file with the current POT file. | |
77 | - msgfmt checks it for validity. | |
78 | - msgcat may detect encoding problems. | |
79 | ||
80 | In addition to the above, the easiest way to check that the po4a | |
81 | translations have valid POD markup, is to try to build them (please | |
82 | see the Building sections in the README file for further details | |
83 | regarding the setup of the source tree): | |
84 | ||
85 | $ make -C man |