Hold Open The Glass Door...Please

Shaun McCance has sent in an announcement about the Terminology revamping project that is being undertaken for Gnome Documentation styleguide. Everyday a term (or a group of related terms) would be sent to the gnome-docs list for discussion. Once a consesus is reached on the terms, the Completed List would be created. Eventually, the list would also contain language recommendations for both Gnome Documentation and User Interfaces.

A rough list of the terms is can be found here. This list has been collated from various documents.

<quote from Shaun's mail>

For the curious, my plan is to change the GNOME Documentation Style Guide to something more like the GNOME Manual of Style. That is, it will contain language recommendations for both documentation and user interfaces. There may be sections that deal specifically with documentation, if needed, but the core of the document will not be documentation-specific.

</quote>

Sounds like a great idea, towards standardizing the terminology base.

Claude Paroz reported on the gnome-i18n mailing list today about the msgfmt errors that were showing up on the damned lies page against some files in a few languages. Bengali_India also has a few red medallions and the problem was baffling me since msgfmt checks on the files locally were not showing any errors. It was only after submitting them to the Gnome svn that the msgfmt error messages were showing up. After discussions on the gnome-i18n mailing list and irc conversations, the following seems the correct solution for plural form related errors for languages that do not have any plural forms.

Open .po file in a text editor (like gedit) and insert the following line in the header section:

"Plural-Forms: nplurals=1; plural=0;\n"

should look like this:


Once you encounter a string with a plural form there are two ways to go about it.

1. If both the strings contain a variable (like %d) indicating a number, then the translation can be done as per the language requirements for handling single and plural numbers. e.g.

msgid "%d file has been modified"
msgstr_plural "%d files have been modified"
msgstr [0] ""
msgstr [1] ""

In this case, after translation the string should look like the following in a text editor:

msgid "%d file has been modified"
msgid_plural "%d files have been modified"
msgstr [0] "%d-টি ফাইল পরিবর্তন করা হয়েছ "

Note: The %d has been retained in the msgstr.

2. The second way is the more important of the two and requires caution. If the singular version string does not have a variable, but the plural string contains a variable, then the translation of only the plural string has to be done. e.g.

msgid "one file has been modified"
msgstr_plural "%d files have been modified"
msgstr [0] ""
msgstr [1] ""

In this case, after translation the string should look like the following in a text editor:

msgid "one file has been modified"
msgstr_plural "%d files have been modified"
msgstr [0] "%d-টি ফাইল পরিবর্তন করা হয়েছ "

Note: The %d has to be present in the msgstr and will take the relevant number of "files modified" when the program encounters such a situation.

Also note, in both cases above the msgstr [1] "" has to be manually removed from the strings.

As a final check, please do ensure that the following command does not throw any errors:

msgfmt -vc -o /dev/null (filename.po)

For more information about plural-forms this document is extremely helpful.