[SOLVED] Translation updates at GitHub: how quickly are they applied?
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.
Translation updates at GitHub: how quickly are they applied?
I'm a Dutch translator for various other projects, and I'm currently well under way with a complete revision of the Dutch translation for Moksha. Because the current Dutch translation is in bad shape.
I expect to be able to submit my new Dutch translation at GitHub in the next few days. How long will it approximately take before it'll be rolled out by means of the updates?
P.S.: I always like to do a live test of my translations, so from time to time I pump the relevant .mo file in my system for testing. It took me a while to find out that there was no moksha.mo, but that I had to replace the existing enlightenment.mo....
It would be fantastic in case you can contribute to translating job.
I can offer all info related to this work as I did this for slovak locales. Give me some time for preparing because I have some family plans during the weekend. I will you know
...
I expect to be able to submit my new Dutch translation at GitHub in the next few days. How long will it approximately take before it'll be rolled out by means of the updates?
...
Considering I am the one that usually packages moksha and adds the updated version to the repos, I can probably make it happen within a day or so of the change being added to Moksha's github page. Depends upon my work schedule more than anything.
Quote:
Originally Posted by Kiezel
...
It took me a while to find out that there was no moksha.mo, but that I had to replace the existing enlightenment.mo....
Ah yes, Moksha as an e17 fork still thinks it is e17. Perhaps in time I will deal with that and make everything from localization stuff to folder and bin names free of the enlightenment references. But for now we live with it.
Quote:
Originally Posted by the_waiter
...
I can offer all info related to this work as I did this for slovak locales. Give me some time for preparing because I have some family plans during the weekend. I will you know
Stefan
Unsure if you need Štefan's help. Either way, you or Štefan let me know when to redo the deb files and I will add it to the repos as promptly as I can.
The Dutch translation in the pull request is fully revised and very nearly complete. Not entirely complete, but that concerns only a couple of strings of minor importance, which I'll tackle once I find the time for it.
What? I spent 2 weeks with translation to slovak. You are ready within one day?
Two days.
I work fast when I have the time, and I had the time. Plus I've been translating for several projects since 2011 (Xfce, Linux Mint, Ubuntu, LXDE, and several more). So I've seen almost all strings before: no need to rack my brain for the right translation.
The Dutch translation in the pull request is fully revised and very nearly complete. Not entirely complete, but that concerns only a couple of strings of minor importance, which I'll tackle once I find the time for it.
Hope this helps!
OK I will see what i can get done this weekend on rebuilding the deb files to incorporate your changes. Much thanks.
Moksha has been updated. Perhaps I should have did more testing of some of the recent changes but hopefully there will be no problems.
There are no problems in a Dutch localized Bodhi because of my new translations. Even if I say so myself, it's a huge improvement compared with the old translations. Thanks for the Moksha update!
In the coming week, I intend to create a new pull request for the Dutch translations with some minor improvements and additions. After that, I'll consider the Dutch translating job as done for now.
Maybe one question: could Midori perhaps be uncoupled as "hard" dependency for the Bodhi app store? First thing I do is to install Firefox and Chromium, so I've no need for a poorly maintained and therefore probably insecure Midori.... I'd like to be able to uninstall Midori without losing the Bodhi app store as well.
There are no problems in a Dutch localized Bodhi because of my new translations. Even if I say so myself, it's a huge improvement compared with the old translations. Thanks for the Moksha update!...
Whatever problems arise wouldn't be from your translations it would be from some recent commits to Moksha. Should be no problems tho, at least no new problems.
Quote:
Originally Posted by Kiezel
... Maybe one question: could Midori perhaps be uncoupled as "hard" dependency for the Bodhi app store? First thing I do is to install Firefox and Chromium, so I've no need for a poorly maintained and therefore probably insecure Midori.... I'd like to be able to uninstall Midori without losing the Bodhi app store as well.
Yep, all that package does is install a menu item, but I agree there should be no hard dependency on Midori or any other web browser. That package has been around a long time and the deb file appears to have been created by an old no long active team member, Deepspeed. I went ahead and changed the menu item to launch x-www-browser and changed the Depends to a recommend field, recommending midori or firefox or chromium-browser. That should satisfy most people. Note x-www-browser has to properly set, but it appears to be set in a default install of BL 5.0, at least the 64 bit version ... I looked in a VM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.