Skip to content

Latest commit

 

History

History
47 lines (38 loc) · 1.87 KB

TRANSLATING.md

File metadata and controls

47 lines (38 loc) · 1.87 KB
Raw

Translators are encouraged to join the chat room #hldig on Libera (ircs://irc.libera.chat/hldig). We will try to help and answer any questions you may have about the translation process.

output messages

There are some po editing utilities that can be helpful.

If you have experience translating files in a po format, then you will be able to skip most of the instructions.

A sample po file (from the GNU coreutils cp command)

msgid "write error"
msgstr "Schreibfehler"

#: lib/copy-acl.c:54 src/copy.c:1387 src/copy.c:2863
#, c-format
msgid "preserving permissions for %s"
msgstr "Erhalten der Zugriffsrechte für %s"

#: lib/error.c:191
msgid "Unknown system error"
msgstr "Unbekannter Systemfehler"

#: lib/file-type.c:40
msgid "regular empty file"
msgstr "reguläre leere Datei"

#: lib/file-type.c:40
msgid "regular file"
msgstr "reguläre Datei"
  • You will need the gettext package from your OS distribution. (Most likely it is already installed by default)
  • Follow the steps for pull requests to begin working on your translation addition.
  • After you clone your fork, go into the hldig source po/ directory
  • run msginit -l ?? (Where ?? is your iso-631-1 language code) Example: To create a french .po file, run msginit -l fr.
  • At this point, you may open your new .po file and begin adding translations. The Translation Project have a list of editors that is specifically designed for working with po-files.
  • When done, make a pull request
  • Thank you!