It seems that localization has gotten slightly more cumbersome with the introduction of Cocoa Bindings. Unfortunately, the names of the bindings show up in AppleGlot as localizable resources. This can lead to some problems when you ship off the glossary file to the translation folks. Things like NSNegateBoolean shouldn't be translated...

I've written a small XSL transformation to strip out the unnecessary xml elements. I've used it a couple of times and it seems to work pretty well.

GlossaryBindingsFilter.xsl

cd _WorkingGlossary
mv PithHelmet.bundle.wg PithHelmet.bundle.wg-original
xsltproc GlossaryBindingsFilter.xsl PithHelmet.bundle.wg-original > PithHelmet.bundle.wg

Once you get the translated file back from translation, you don't have to reinsert the values, you can just run the Incremental Update in AppleGlot. The conversion statistics will be wrong of course - so you won't be able to rely on them.

I would also make sure that the file is encoded properly. The files should always be UTF-8 - but sometimes editing in TextEdit screws up the encoding (usually to MacRoman). XCode is handy for fixing this.

If there are or you suspect xml syntax errors, the following gem should ferret out the problem:

xmllint PithHelmet.bundle.wg

Hope this helps a few people - it drove me batty for a while.