Might not be ideal for your situation but it will manage correct removal of accelerators before checking the spelling and does some other nice things like ignore words such as variables and words that you have defined shouldn’t be translated.

F Wolff: Fortunately our locale has plenty of localization, so we mostly translate the next GNOME GUI and then whatever we feel like, but I’m sure comment will be more than helpful for many translation teams. I made extensive use of pocount in GNOME 2.20 or maybe 2,22, to make our translation more homogeneous.

kelemeng, thank you for your suggestion. Personally I use Vim, which spell checker is very useful when coupled with the syntax highlight. But many translators use other tools, so using hunspell-po might make spell checking much easier. Poedit has orthographic verification too, but you must set the language and country for the spell checker to work. Poedit uses GtkSpell, which uses Aspell. Usually it’s patched to use Enchant, which uses Aspell by default too, but can be configured to use My/Hunspell instead.

Also, Wordforge looks cool, thanks for pointing to it . Why is it not part of the GNOME project?

There is now also infrastructure to program tests specific to a single language. This means we could even include some very specific tests specifically for pt-BR! In future, we hope to be able to mark the false positives as reviewed – this will allow pofilter and Pootle to skip those without complaining about them again. This should make it much easier to review translations again and again over the lifetime of several product versions. But of course, we should try to limit the false positives as well. Let us know if you find a pattern of false positives that we can eliminate.

Of course I use the translate toolkit in “special” ways. But something I often use is pocount – such a simple program, but it really helps me to prioritise my work and to plan. Together with pogrep and pomerge, it becomes easier to isolate important work, and to plan available time. When working on GNOME I often use these and a few other tools as well (I prefer pot2po over msgmerge, for example). If you like pofilter, you might also like poconflicts – a way of checking consistencies between different files.

I find the variable and accelerator tests the most useful as that is where our translators make the most errors. Once translators are familiar with these things you should see less errors. I made a change to the accelerators test which will now allow a language to have a list of valid accelerator characters, thus you can define them as the characters that appear on your keyboard (some language keyboards have precomposed diacritics on the keyboard).

Please do report any language specific entries that you want added. It will help you on pofilter but also help all the other users of the toolkit.