Error in Calibre Version 3.45 64bit

[Leonatus]

3.45.2 works! Thank you! You are the greatest, Kovid!

[kovidgoyal]

You're welcome

[JimmXinu]

Kovid,

I wonder if these two plugin issues might also be related?

Encoding error on convert after epubmerge:
https://www.mobileread.com/forums/sh...63#post3867663

.mo translation files converted .po by v3.45.2 are flawed, but v.3.44 work:
https://www.mobileread.com/forums/sh...94#post3867694

[kovidgoyal]

See https://github.com/kovidgoyal/calibr...43e070897b6583 for the first issue.

for the second the msgfmt calibre budles was changed to the oe for python3 with some backports so it works in python 2 as well. What is the issue with it?

[JimmXinu]

Accented characters and the like aren't correctly encoded in .mo files when using 3.45.

Attached is a zip with a German .po file for FanFicFare and the .mo files as generated by 3.44 and 3.45.2.

One example: Search for 'ber FanFicFare' (for Über FanFicFare) in the .mo files.
Ü becomes \303\234 in 3.44 but \303\203\302\234 in 3.45.2.

[kovidgoyal]

This should take care of it https://github.com/kovidgoyal/calibr...45159d86c59bd1

[BetterRed]

Is this intentional: strings in Tweak values must now be prefixed with a 'u', viz:



Seems a bit arcane, maybe it's been like that for a while and I hadn't noticed.

BR

[kovidgoyal]

It's a temporary thing, once calibre moves to python 3 the u prefix will be gone again. And you dont have to enter the u it will work without it as well.

[JimmXinu]

Originally Posted by kovidgoyal

This should take care of it https://github.com/kovidgoyal/calibr...45159d86c59bd1

Thanks!

[thiago.eec]

Originally Posted by JimmXinu

.mo translation files converted .po by v3.45.2 are flawed, but v.3.44 work:
https://www.mobileread.com/forums/sh...94#post3867694

Windows 10 x64 1903
calibre 3.46
system locale: pt_BR
calibre language: pt_BR

I'm having a weird problem with that command too:

calibre-debug.exe -c "from calibre.translations.msgfmt import main; main()" pt_BR.po
Failed to compile translations file: pt_BR.po, ignoring

The weird part is that the 'pt_BR.mo' file is still being generated, and seems to work fine. I tried it with several po files (with non ASCII characters), and none raised that error. Then, just to check, I tried changing the file name to 'pt-BR' and got no error message. Any other name would do, including names with underscore.

Now it gets weirder: supose I have 02 files ('fr.po' and 'pt_BR.po') on a folder. When I tried to generate the mo file for the french translation, then I got this:

calibre-debug.exe -c "from calibre.translations.msgfmt import main; main()" fr.po
Failed to compile translations file: pt_BR.po, ignoring

It complains about the 'pt_BR.po' file just for being in the same folder, since it is not being converted right now.

At last, I tried changing calibre language to English. Now everything works fine! No errors at all. No complaints about 'pt_BR.po' file.

P.S.: I never had that error before 3.45.

[kovidgoyal]

If you set your calibre language to pt_BR and have a pt_BR.po file in the current directory, calibre will try to use it as the language file -- this is to help translators who are translating calibre itself to debug their trnaslations files easily. See https://calibre-ebook.com/get-involved for details.

You can use the following to prevent that error message (which is harmless)

set CALIBRE_OVERRIDE_LANG=en

[thiago.eec]

Originally Posted by kovidgoyal

If you set your calibre language to pt_BR and have a pt_BR.po file in the current directory, calibre will try to use it as the language file -- this is to help translators who are translating calibre itself to debug their trnaslations files easily. See https://calibre-ebook.com/get-involved for details.

You can use the following to prevent that error message (which is harmless)

set CALIBRE_OVERRIDE_LANG=en

Thanks for the reply, @kovidgoyal.

I thought I needed to set the environment variable CALIBRE_TEST_TRANSLATION to test calibre translations.

Was this changed on 3.46? Before that, this message never showed up.

[kovidgoyal]

No that is still the case, I assumed you had that variable set.

[thiago.eec]

Originally Posted by kovidgoyal

No that is still the case, I assumed you had that variable set.

No, I don't have this variable set. And, like I said, I never got this message on previous versions.

EDIT: Just to clarify, I'm using this command on a random directory, not related to calibre at all. I'm using it to bundle translations files to a plugin.

[kovidgoyal]

Well it's harmless in any case, so just ignore it.