Skip to content

Translations

R4zorax edited this page Jul 14, 2018 · 17 revisions

uSkyblock-Revived

The uSkyBlock uses gettext for generating translations for different languages.

This tool helps us to keep track of strings within the source-code, and extracts them for translation.

Translating to another language

  • Copy the keys.pot file, and rename it to <language-code>.po
  • Open the newly created .po file in a text-editor or a po-editor
  • Edit the headers, to reflect the language and other state of the translation
msgid ""
msgstr ""
"Project-Id-Version: v2.3-HF3\n"
"Report-Msgid-Bugs-To: https://github.com/rlf/uSkyBlock/issues\n"
"POT-Creation-Date: 2015-04-17 08:45+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Mikey Mouse <[email protected]>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
"Language: nl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

Of special concern is the Language:.

Now you can use your favourite po-editor to translate all the msgstr entries in the .po file.

Good Suggestions:

  • POEdit - Windows/Mac/Linux client
  • Loco - Free online po-editor
  • Gted - Eclipse Plugin

Note: Never touch or translate the msgids.

Once the .po file has been translated, post the .po file back to uSkyBlock, by either:

  • create a pull-request to get it added to the official-release.
  • paste it to pastebin, and create an issue on GitHub linking to it.
  • paste it to pastebin, and create a forum post on DevBukkit linking to it.
  • paste it to pastebin, and create a forum post on Spigot linking to it.
  • create an issue on GitHub, and attach the .po file to it.

Once the .po file has been approved and merged to the uSkyBlock master, the translations will be available in the next release.

Testing the translation

Either place the newly created .po file in the i18n.zip file within the jar-file, or copy it to the plugins/uSkyBlock/i18n folder, once the plugin has been reloaded, the new translation should be available from the /usb lang command.

Disclaimer

We can not be held responsible for translations not made by us. If in any case a translation is not correct you can contact us and we will deal with the matter as soon we can. In case of an translation on purpose being rude or inappropriate we will remove the translation.