Internationalization issues

For discussions about programming, and for programming questions and advice


Moderator: Forum moderators

Post Reply
HerrBert
Posts: 370
Joined: Mon Jul 13, 2020 6:14 pm
Location: Germany, NRW
Has thanked: 21 times
Been thanked: 136 times

Internationalization issues

Post by HerrBert »

Hello.

(I'm not sure if this is the right place to post this so feel free to move to according place...)

I have two questions about internationalization.

1. General problem: momanager creates .po files with #, fuzzy strings which are not compiled back to .mo files by momanager. I can compile #, fuzzy strings manually via commandline with the -f option of msgfmt. I've seen this in all puppies i used since ~2015. Why?

2. ATM i'm trying to translate recent version of petget (in recent slackware-based puppies) but translation fails, because petget calls /usr/lib/gtkdialog/box_ok and box_yesno which set TEXTDOMAIN to libstardust for themselves. Anything beyond these dialog calls is not translated by petget___*.mo

Is there a way to keep petget's TEXTDOMAIN?

Post Reply

Return to “Programming”