BodhiThis forum is for the discussion of Bodhi Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Namely that there is no vanilla .POT file in that folder....
Which means that if there's no .po file with your current language at the GitHub source of Moksha, you have no alternative but to pick a .po file of another foreign language and replace its foreign translations by translations in your own language. And then creating it with the proper name.
Of course it SHOULD have one. I had noticed it before but it is a minor issue. Would be great if someone did this work for us as it is not a priority to me and I am unlikely to do it unless pressed by someone to do it. Thanks tho for pointing it out and if you do send a pull request I will merge it if it looks ok to me
I think a compiling the moksha code with gettext stuff included should create pot file automatically. This would be my way to do it. I had some rough time with this topic in the past. I saved one link to help me:
I think a compiling the moksha code with gettext stuff included should create pot file automatically. This would be my way to do it. I had some rough time with this topic in the past. I saved onle link to help me:
Yes, a cleanly generated .pot file would be better, if only for the future.... But my "reverse engineered" .pot file appears to cover all translatable strings, so for the time being this looks like a good workaround.
Poedit, as far as I understand, can only be used for reverse engineering a .pot file (by removing translations from a .po file), and even that only in a limited way: you can scroll to a translated string and press "Ctrl k", which deletes its translation. That's a hell of a job for tackling all of Moksha's strings, so the online gettext tool that I found, was rather a lifesaver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.