Hi! I think I might have lost some part of this email thread, but couldn't locate them in the archive.
I saw the Gnome Glossary website: http://developer.gnome.org/projects/gtp/glossary/ and noticed an old colleague of mine who used to work in our group as the contact person. I'm not sure how this project originated back then. I'd like to pass on the glossary tool that we use at Sun Globalization: https://g11nportal.sun.com/sungloss It requires user account which you can get immediately. You can find terms (English and translated into about 9-10 languages) for Gnome there and export glossary for your language into a spreadsheet. I'd be happy to get your feedback on them and find a way to collaborate to refine the glossaries. regards, Young Clytie Siddall wrote On 08/10/06 01:44,: >On 05/08/2006, at 5:59 AM, F Wolff wrote: > > >>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 still think it's useful, and I can't understand why it's no longer >current. I know we create a de facto compendium from the available >files for each language, but a glossary is a more specific terminogy >file, which can be useful in many situations. > > >>I saw a few issues that looked like encoding problems, which I thought >>people might want to know about. >> >> ><snip> > > >>* 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.) >> >> > >;) > > >>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. >> >> > >Most likely, the glossary files are not utf8 simply because they are >so old. UTF8 is the standard now: I don't think any teams are >accepting files in legacy encodings. > > >>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 >> >> > >As a gnome-glossary translator, I would also be interested to know if >we can add to the glossary, maintain it actively. > >from Clytie (vi-VN, Vietnamese free-software translation team / nhóm >Việt hóa phần mềm tự do) >http://groups-beta.google.com/group/vi-VN > > >_______________________________________________ >gnome-i18n mailing list >gnome-i18n@gnome.org >http://mail.gnome.org/mailman/listinfo/gnome-i18n > > > _______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
