Thanks for letting me know.
Yes, I am aware that there are some strings without a text domain. I’ll fix that soon.
Make sure you’re using the right encoding throughout and declare UTF-8 in the header of your po/pot file.
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
Apologies, I have to correct myself:
If you are creating a po/mo file from source you have to tell PoEdit what encoding it has to expect.
Since WordPress uses UTF-8 throughout you can instruct PoEdit via Catalog -> Properties -> Source Code Charset to use UTF-8
Or you can add it manually to your po file:
"X-Poedit-SourceCharset: UTF-8\n"
In anyway, version 1.7.1 corrects the missing text domains.
Just out of curiosity: to what language are you translating? Maybe you like to add your translation to GlotPress?
Thread Starter
Hrohh
(@hrohh)
I have utf-8 in line “X-Poedit-SourceCharset: UTF-8\n”
screenshot from PoEdit

Yes, I already uploaded czech language via GlotPress, but I dont have capability to approve the strings.
Ok, I’ve changed those non-ASCII characters into HTML entities. That should make both of us happy.
I’ve commited an release candidate: version 1.7.2.
Give it a try and let me know whether it works for you, then I’ll release it.
Thread Starter
Hrohh
(@hrohh)
Sorry for delay. Yes, it works now in 1.7.2! 🙂 Thank you very much
No problem. Glad I could help.