README.l10n 2.6 KB

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