diff --git a/i2p2www/pages/site/get-involved/guides/new-translators.html b/i2p2www/pages/site/get-involved/guides/new-translators.html index 6fa94c57..82754f24 100644 --- a/i2p2www/pages/site/get-involved/guides/new-translators.html +++ b/i2p2www/pages/site/get-involved/guides/new-translators.html @@ -1,81 +1,112 @@ {% extends "global/layout.html" %} -{% block title %}New Translator's Guide{% endblock %} +{% block title %}{% trans %}New Translator's Guide{% endtrans %}{% endblock %} {% block content %} -Here's a very quick guide to getting started. +{% trans %}Here's a very quick guide to getting started.{% endtrans %} -

How to Translate the Website

+

{% trans %}How to Translate the Website{% endtrans %}

+ +

{% trans transifex='https://www.transifex.com/projects/p/I2P/' -%} +Translation of the website is done with .po files. The easiest way by far to +translate the website is to sign up for an account at +Transifex and request to join a translation team. +Alternatively it can be done "the old way" as outlined below. +{%- endtrans %}

  1. -Preparation +{% trans %}Preparation{% endtrans %}
      -
    1. - Come to #i2p-dev on irc and talk to people. - Claim the language - - To make sure other coworkers don't bump onto the files you are working on, - please update the translation status on this wiki page.
      2. -
    2. - Follow the new developer's guide, - Including the installation of monotone, - checking out i2p.www branch, and generate your own monotone keys. - It is not required that you sign a dev agreement.
      3. +
    3. {% trans url='http://ugha.i2p/i2pTranslation' -%} +Come to #i2p-dev on irc and talk to people. +Claim the language - +To make sure other coworkers don't bump onto the files you are working on, +please update the translation status on this wiki page. +{%- endtrans %}
      4. +
    4. {% trans newdevs=site_url('get-involved/guides/new-developers') -%} +Follow the new developer's guide, +Including the installation of monotone, +checking out i2p.www branch, and generate your own monotone keys. +It is not required that you sign a dev agreement. +{%- endtrans %}
    -
  2. -Create files: - If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language. - Then 'mtn add' the file. - Also add a _layout_xx.html for your language xx. - Add a flag image file for the menu (copy from the router).
    3. +
  3. {% trans -%} +Create files: +If the file for your language does not exist yet: +{%- endtrans %} +
      +
    1. {% trans -%} +Run "./extract-messages.sh" to generate a messages.pot in the base directory. +Edit the header of this file, then run "./init-new-po.sh locale" to generate the file +i2p2www/translations/locale/LC_MESSAGES/messages.po. "mtn add" this file. +{%- endtrans %}
      2. +
    2. {% trans -%} +Edit i2p2www/pages/global/lang.html and add a line for your language (copy an existing line). +{%- endtrans %}
      3. +
    3. {% trans -%} +Add a flag image file to i2p2www/static/images/flags/ for the menu (copy from the router). +{%- endtrans %}
      4. +
    +
    4. -
  4. -Edit files: - Edit _layout_xx.html, _menu.html, and other files with any text editor. - Be sure not to use an editor in HTML mode that reformats everything.
    5. +
  5. {% trans -%} +Edit files: +Edit i2p2www/translations/locale/LC_MESSAGES/messages.po. +To work with .po files efficiently, you may wish to use POEdit +{%- endtrans %}
    6. -
  6. -Check in: - mtn pull, mtn update. Then check in by "mtn ci -k yourname@mail.i2p file1 file2 ..." - This collects the diff info of your changed file into your local repo. Then "mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p". - This synchronizes your local repo with the repo on the target machine.
    7. - -
  7. -Repeat. Check in often. Don't wait until it is perfect.
    8. +
  8. {% trans -%} +Check in: +"mtn pull", "mtn update". Then check in by "mtn ci -k yourname@mail.i2p file1 file2 ..." +This collects the diff info of your changed file into your local repo. Then "mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p". +This synchronizes your local repo with the repo on the target machine. +{%- endtrans %}
    9. +
  9. {% trans -%} +Repeat. Check in often. Don't wait until it is perfect. +{%- endtrans %}
-

How to Translate the Router Console

+

{% trans %}How to Translate the Router Console{% endtrans %}

-

The easiest way by far to translate the router console is to sign up for an account at -Transifex and request to join a translation team. -Alternatively it can be done "the old way" as outlined below.

+

{% trans transifex='https://www.transifex.com/projects/p/I2P/' -%} +The easiest way by far to translate the router console is to sign up for an account at +Transifex and request to join a translation team. +Alternatively it can be done "the old way" as outlined below. +{%- endtrans %}

  1. -Preparation +{% trans %}Preparation{% endtrans %}
      -
    1. - Come to #i2p-dev on irc and talk to people. - Claim the language - - To make sure other coworkers don't bump onto the files you are working on, - please update the translation status on this wiki page.
      2. -
    2. - Follow the new developer's guide, - Including the installation of monotone and the gettext tools, - checking out i2p.i2p branch, and generate your own monotone keys.
      3. -
    3. - Generate your own gpg key and sign the dev agreement.
      4. -
    2. +
  2. {% trans url='http://ugha.i2p/i2pTranslation' -%} +Come to #i2p-dev on irc and talk to people. +Claim the language - +To make sure other coworkers don't bump onto the files you are working on, +please update the translation status on this wiki page. +{%- endtrans %}
    3. +
  3. {% trans newdevs=site_url('get-involved/guides/new-developers') -%} +Follow the new developer's guide, +including the installation of monotone and the gettext tools, +checking out i2p.i2p branch, and generate your own monotone keys. +{%- endtrans %}
    4. +
  4. {% trans -%} +Generate your own gpg key and sign the dev agreement. +{%- endtrans %}
    5. +
+ -
  • +
  • {% trans -%} Before starting a console translation, better help translate some i2p webpages first. -At least an i2p homepage in your language would be great. This will also help you learn monotone.
    • +At least an i2p homepage in your language would be great. +{%- endtrans %} -
  • -What to translate: - There are about 15 files in the i2p.i2p branch that needs translation: +
  • {% trans -%} +What to translate: +There are about 15 files in the i2p.i2p branch that needs translation: +{%- endtrans %} - Where xx is your language code like fr/de/ch/zh/... +{% trans -%} +Where xx is your language code like fr/de/ch/zh/... +There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code. +{%- endtrans %}
    • - There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code. - +
  • {% trans -%} +Create files: +If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language. +Then "mtn add" the file. +After creating a .po file, edit the headers. Then run "ant distclean poupdate". +{%- endtrans %}
    • -
  • -Create files: - If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language. - Then 'mtn add' the file. - After creating a .po file, edit the headers. Then run 'ant distclean poupdate'. -
    • -
  • -Start to work: - Edit the HTML files with any text editor. - Be sure not to use an editor in HTML mode that reformats everything. - To work with .po files efficiently, you may wish to use POEdit -
    • -
  • -Check in: - mtn pull, mtn update. Then check in by "mtn ci -k yourname@mail.i2p file1 file2 ..." - This collects the diff info of your changed file into your local repo. Then "mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p". - This synchronizes your local repo with the repo on the target machine. -
    • -
  • +
  • {% trans -%} +Start to work: +Edit the HTML files with any text editor. +Be sure not to use an editor in HTML mode that reformats everything. +To work with .po files efficiently, you may wish to use POEdit +{%- endtrans %}
    • + +
  • {% trans -%} +Check in: +"mtn pull", "mtn update". Then check in by "mtn ci -k yourname@mail.i2p file1 file2 ..." +This collects the diff info of your changed file into your local repo. Then "mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p". +This synchronizes your local repo with the repo on the target machine. +{%- endtrans %}
    • + +
  • {% trans -%} Repeat. Check in often. Don't wait until it is perfect. - -
    • +{%- endtrans %} -

    As you can see, it's not that difficult. -If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC. -

    +

    {% trans -%} +As you can see, it's not that difficult. +If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC. +{%- endtrans %}

    -

    FAQ

    +

    {% trans %}FAQ{% endtrans %}

    -Q: Why do I have to install monotone, Java, jsp, learn about .po files and html, etc.? Why can't I just do a translation and email it to you? +

    {% trans -%} +Q: Why do I have to install monotone, Java, jsp, learn about .po files and html, etc.? Why can't I just do a translation and email it to you? +{%- endtrans %}

    -Answer: Several reasons: +

    {% trans %}A: Several reasons:{% endtrans %}

    +

    {% trans -%} In summary: - Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard. +{%- endtrans %} -

    More Information

    -The #i2p-dev channel on IRC, or the translation forum on zzz.i2p. - - +

    {% trans %}More Information{% endtrans %}

    +

    {% trans zzz=i2pconv('zzz.i2p') -%} +The #i2p-dev channel on IRC, or the translation forum on {{ zzz }}. +{%- endtrans %}

    {% endblock %}