Scr1pts

During the L10n setup, a lot of Bash scripts were made to deal with different tasks, here are a few interesting ones:

Two first scripts were made to reorder strings in foreign locales, because langpacks came with mixed strings and so it was hard to track differences. One for .properties and another one for .dtd. Those scripts ends up used only for testing because Babelzilla was also able to reorder strings on langpacks

A script was made to fetch all langpacks from Songbird website and unzip everything

This wasn’t enough, some langpacks were missings (because they are not shipped with Songbird they doesn’t have not enough strings translated), another script was made to fetch from translate website

We even made a Python script to remove en-US strings from langpacks where strings were missing!

For previous Nightingale releases we made a script to take Songbird langpacks and repack them to be compatible with Nightingale

Now we have a full script to produce our own langpacks using files from Babelzilla

Last but not least we made a script to track changes done on Babelzilla and commit those on GitHub when a change is done

Some of those scripts are yet to be released or improved, but everything is working at this time.

The great thing is that once we release the new version of Nightingale, a simple script execution will be able to push langpacks from the latest translation version online 🙂

This cooperation could have not been possible without the help of : Tymofij, Goofy and Pascalc from Mozilla/Babelzilla who helped us providing support so thanks a lot to them!

What’s next?

We also plan on hosting Nightingale add-ons and their locales online so you can translate them, along with more tools to help you localize efficiently 🙂

Exciting news for those of you who want to help Nightingale development with a little bit of money: we are officially using Bountysource for bounties on bugs now. Bountysource is an open source project, which allows users to put money on a bug or feature request – wether it’s already in the issues tracker or not. And it makes it easy for developers to find bugs to work on to get a little bit of money. and it’s perfect for us: we don’t have to handle money in the whole process. To give a bounty on an existing issue, just go to https://www.bountysource.com/trackers/230233-nightingale-media-player-nightingale-hacking and select the issue you want to speed up from the list.

By putting a bounty on a bug, you make it more likely to get another developer, who is not currently wokring on Nightingale to fix a bug. We from the team will fix bugs with and without bounties equally, just dependent on our plans and personal preferences. So no worries if you don’t have the money to boost an issue.

We will add the “bounty” tag to all issues with bounties. If you start working on an issue with the tag, be sure to got to Bountysource and click the “Start Work” button.

For more information on how Bountysource works, visit their FAQ. Please hang on if you want to donate directly to the project. We are still looking into how to handle money the best.