View source for Localization/i18n Best Practices

= General tips =
Here are some general tips which will make your translators happy
== When in doubt, use translator-comments ==
When you are writing a string which may be confusing for the translators (contextual issues, or cultural issues), or if you want the string to be translated according to a particular convention, use translator-comments, which would show up alongside the message in the PO file translator get when they translate you software. Example (from Calculate activity)
<pre>
        # TRANS: multiplication symbol (default: '*')
        self.mul_sym = _('mul_sym')
</pre>
So as you can see from the above example, translator-comments are normal Python comments with the "TRANS" keyword.

== Use plural forms ==
Do not assume that all languages have a concept of singular and plural like English. Some languages might have a single form, and some have more than two form. Use [http://www.gnu.org/software/automake/manual/gettext/Plural-forms.html plural forms] via ''ngettext()'' in these cases. Example (from sugar-update-control):
<pre>
                header = gettext.ngettext("You can install %s update",
                                          "You can install %s updates", avail) \
                                          % avail
</pre>


== Use white-spaces and newlines only when you need to ==

The tool which converts the translated PO files into binary MO files, ''msgfmt'', can be quite picky about newlines and lines with only whitespaces. For example, the following string in sugar has a blank line at the end which is often overlooked by translators, causing msgfmt to choke.
<pre>
    print _('Usage: sugar-control-panel [ option ] key [ args ... ] \n\
    Control for the sugar environment. \n\
    Options: \n\
    -h           show this help message and exit \n\
    -l           list all the available options \n\
    -h key       show information about this key \n\
    -g key       get the current value of the key \n\
    -s key       set the current value for the key \n\
    -c key       clear the current value for the key \n\
    ')
</pre>


== Keep string formatting as less fancy as possible ==

In case of code like the following example, translators tend to translate the strings "error" and "file" into their own languages, causing msgfmt to choke.

<pre>
                notify.props.msg = _('%(error)s when deleting %(file)s') % \
                    { 'error': err.strerror, 'file': logfile }
</pre>

Avoid such strings if possible.

= Pootle specific tips =
These are some tips/guidelines which would keep [[User:Sayamindu|Sayamindu]] (who currently maintains the Pootle installation) happy ;-).

== Do not touch anything inside your po directory ==

If you change anything inside the po directory (including the POT file), and push it to Git, it will create a conflict which has to be updated in the Pootle side manually. Try avoid doing this, If you see any issues, please ping Sayamindu (sayamindu at laptop dot org) (you can also catch him on IRC, in channels like #sugar on Freenode with the nick unmadindu). If the changeset that yu have is large, send him a patch, and he will apply that from the Pootle side manually and commit.

== Try to keep the po directory in the top level directory of your repository ==

The various homebrew helper scripts which keep Pootle running properly make the assume that the po directory will be in the toplevel of the source repository. Try to avoid putting the po direcotry under a directory like i18n or such, as this will need yet another special casing in the helper scripts, making stuff more difficult to maintain.