Hi Chris, > In other words, simply forcing the *build* to do the right thing > can mean we are hiding issues that should be fixed elsewhere
Indeed, but in this case it was simply a .mo file based on a latin1 encoding instead of UTF8, while the main program was loading/running the files/translations always in utf8. It is fixed already, there was a bug in the source tar ball that was fixed a few hours after the initial release, but I got the bad one :-( Upload of new calibre done. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13