Gnome glossary project

[F Wolff <friedel translate org za>]

Hi list

(moderators: sorry, I emailed with a non-subscribed address first)

I have a few questions and comments about the gnome glossary project. I
recently checked out the files and had a look, but there are a few
issues.

Many files have not been updated recently. This is not necessarily a
problem, but I just wondered if the project was still considered
"active", or is it simply at a point where most people just use it?

I saw a few issues that looked like encoding problems, which I thought
people might want to know about. Many seemed related to the comment at
the message with msgid "Base", but not all:
* de.po: encoding of comment at msgid "Base"
* el.po: encoding of comment at msgid "Actor", "Antialiasing", "Base"
and many others
* ko.po: UTF-8 encoded comment at msgid "Base" (rest of file is
"euc_kr")
* lv.po: encoding of comment at msgid "Base"
* sr Latn po: encoding of comment at msgid "Base"
* sr.po: encoding of comment at msgid "Base"
* te.po: encoding of comment at msgid "Base"
* tr.po: encoding of comment at msgid "Base"
* vi.po: The plural equation (not really an issue, and already discussed
with Clytie. The header line can be removed since there are no plurals.)
* zh_CN.po: UTF-8 encoded comment at msgid "Base" (rest of file is
"gb2312")
* zh_TW.po: UTF-8 encoded comment at msgid "Base" (rest of file is
"big5")

Perhaps the problematic comment at "Base" is due to tools not working
correctly with the encodings. Perhaps this can be avoided by not using
the fancy "times" character in the cvs file, and to update the
translations from a newly generated .pot file.

Furthermore, perhaps a conversion to UTF-8 for all files should be
considered. I guess some of the encodings like big5 simply don't have
that character, although I didn't confirm this.

I hope that the maintainers will be interested to fix these issues and
to review the files to get them up to date. We are interested in reusing
en integrating these files in the Pootle project. The ones with the
encoding problems are unfortunately not usuable as they are now, since
our tools are a bit more stringent than msgfmt, and we actually would
like to have usuable comments. Anyone might be able to fix some of
these, but I would like to hear if it is something one can merely post a
patch for here, or what procedure is recommended. 

Lastly, what is the procedure to have new languages and updates
commited? I think there might be some new interest in this project from
Pootle users, starting with me for the inclusion of af.po :-). 

Regards,
Friedel