Skip to content

Latest commit

 

History

History
52 lines (39 loc) · 1.92 KB

TRANSLATE.md

File metadata and controls

52 lines (39 loc) · 1.92 KB
Raw

Translating

Translators are encouraged to join the chat room. We will try to help and answer any questions you may have about the translation process.

There are some po editing utilities that can be helpful (but not required. .po files can be edited with any text editor).

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.

  • Fork the repo

  • After you clone your fork, go into the bric source po/ directory

  • run msginit -i bric.pot -o lc_CC.po -l lc_CC (Where lc is your iso-631-1 language code) and CC is your country code

  • At this point, you may open your new .po file and begin adding translations. You should also change ASCII to UTF-8 in the Content-Type line of your .po file if your language needs non-ASCII characters. Be sure to save the file in UTF-8 encoding.

  • Add the appropriate line for your language to the LINGUAS file

  • When done, make a pull request

  • Thank you!