gaim/www

Luke asks, and he receives, translator howto for third party plugins.

2006-03-06, Gary Kramlich
4b81482fb9a9
Parents 0d66b253bffb
Children d92d09c162ef
Luke asks, and he receives, translator howto for third party plugins.
Developer howto coming shortly...
1 files changed, 72 insertions(+), 0 deletions(-)
  • +72 -0
    htdocs/translations.php
    • --- a/htdocs/translations.php Tue Feb 28 22:43:08 2006 -0500
    +++ b/htdocs/translations.php Mon Mar 06 11:22:34 2006 -0500
    @@ -40,3 +40,75 @@
    </ol>
    <li>String freezes are announced on gaim-i18n</li>
    </ul>
    +
    +<h1>Third Party Plugin Translation HowTo</h1>
    +<p>So you've Gaim is 100% translated in your language and there are still
    +untranslated strings. These strings are most likely owned by a third party
    +plugin you have installed. Following the below steps should help you to get
    +those strings translated. However, each third party plugin may be run
    +differently, so some of these suggestions may not apply.
    +</p>
    +
    +<ul>
    + <li>Determine if the plugin has translation support. The easiest way to
    + determine this is to check the plugin's website if it has one. If it
    + doesn't, try contacting the developers. If they are unsure of how to
    + implement translations support, point them
    + <a href="/api/plugin-i18n.html">here</a>.
    + </li>
    + <li>Determine if a translation already exists. If it does contact the
    + original author and see if they could use your help. In the event
    + that they are no longer maintaining it, contact the developers of the
    + plugin, and let them know that you would like to take over maintaining
    + the translation.
    + </li>
    + <li>If a translation does not already exist, follow the below steps:
    + <ol>
    + <li>Acquire the po template (.pot) for the plugin (note that this
    + file and it's location will vary for each plugin).
    + </li>
    + <li>Find the two letter language code for your language. If
    + translating to a regional dialect, append the two letter region
    + or country code. Rename the file to match this. For example,
    + Protuguese is pt.po, and Brazilian Portuguese is pt_BR.po.
    + </li>
    + <li>If the plugin has a translation mailing list, or possibly even
    + a developers list, subscribe to it.
    + </li>
    + <li>Open the translation file in a text editor.</li>
    + <li>Translate the strings.
    + <ul>
    + <li>Translated .po files may be submitted in whatever native
    + encoding is most convenient (and hopefully canonical).
    + Please ensure that the Content-type: line reflects the
    + proper character set.
    + </li>
    + <li>Please check your translations carefully. Make sure
    + you have the same number of newlines and %s or other
    + formatting codes in the translation as you have in the
    + original. The po/check_po.pl script can help with this.
    + </li>
    + <li>Before submitting updated or new translations, please
    + run the following command to ensure the file does not
    + contain errors: <code>msgfmt -c --statistics xx.po</code>
    + </li>
    + <li>The comments at the top of each .po file should appear as
    + follows:<br/>
    +<pre># PLUGIN_NAME Xxxxx translation
    +# Copyright (C) 2002, Another Name &lt;email@something.com&gt;
    +# Copyright (C) 2003, Your Name &lt;email@whatever.com&gt;
    +#
    +# This file is distributed under the same license as the PLUGIN_NAME package.
    +#</pre>
    + </li>
    + </ul>
    + </li>
    + <li>Submit the translation to the developers. This again will vary
    + from plugin to plugin.
    + </li>
    + </ol>
    + </li>
    + <li>Listen for string freezes. Again, this will vary from plugin to plugin,
    + and may even been non-existant.
    + </li>
    +</ul>