Laura Arjona: 10 short steps to contribute translations to free software for Android
This small guide assumes that you know how to create a public repository with git (or other version control system). Maybe some projects use other VCS, Subversion or whatever; the process would be similar although the commands will be different of course.
If you don t want to use any VCS, you can just download the corresponding file, translate it, and send it by email or to the BTS of the project, but the commands required are very easy and you ll see soon that using git (or any VCS) is quite comfortable and less scary than what it seems.
So, you were going to recommend a nice app that you use or found in F-Droid to your friend, but she does not understand English. Why not translating the app for her? And for everybody? It s a job that can be done in 15 minutes or so (Android apps have very short strings, few menus, and so). Let s go!
1.- Search the app in the F-Droid website
You can do it going to the URL: https://f-droid.org/repository/browse/?fdfilter=wordofappname
Example: https://f-droid.org/repository/browse/?fdfilter=pomodoro
Then, open the details of the app, and learn where s the source code.
2.- Clone the source code
If you have an account in that forge, fork/clone the project into your account, and then, clone your fork/clone in local.
If you haven t got an account in that forge, clone the project in local.
Filed under: Tools, Writings (translations) Tagged: Android, Contributing to libre software, English, Free Software, libre software, translations
git clone URLofTheProjectOrYourClone
3.- In local, create a new branch, and checkout to it.
cd nameofrepo
git checkout -b Spanish
4.- Then, copy the /res/values folder into res/values-XX folder (where XX is your language code)
cp ./res/values /res/values-es -R
5.- Translate
Edit the strings.xml file that is in the res/values-XX folder, and change the English strings to your language (respect the XML format).
6.- Translate other files, or delete them
If there are more files in that folder (e.g. arrays.xml ), review them to know if they have translatable strings. If yes, translate them. If not, delete the files.
7.- Commit
When you are finished, commit your changes:
git add res/values-es/*
git commit -a
(Message can be Spanish translation or so)
8.- Push your changes to your public repo
If you didn t create a public clone of the repo in your forge, create a public repo and push your local stuff into there.
git push --all
9.- Request a merge to the original repo
(Using the web interface of the forge, if it is the same for the original repo and your clone, or sending an email or creating an issue and providing the URL of your repo). For example, open a new issue in the project s BTS
Title: Spanish translation available for merging
Body: Hi everybody.
Thanks for your work in "nameofapp".
I have completed a Spanish translation, it's available for review/merge in the Spanish branch of my repo:
https://urlofyourclone
Best regards
10.- Congratulations!
Translations are new features, and having a new feature in your app for free is a great thing, so probably the app developer(s) will merge your translation soon.
Share your joy with your friends, so they begin to use the app you translated, and maybe become translators too!
Comments?
You can comment on this post in this pump.io thread.Filed under: Tools, Writings (translations) Tagged: Android, Contributing to libre software, English, Free Software, libre software, translations
I had dinner with a friend this evening and ended up discussing the FSF's
I (grudgingly) use the
Dear lazyweb,
I am tired of finding how to get my users to happily print again. Please help.
Details follow.
Several years ago, I configured our Institute's server to provide easy, nifty printing support for all of our users. Using Samba+CUPS, I automatically provided drivers to Windows client machines, integration with our network user scheme (allowing for groups authorization That means, you can only print in your designated printer), flexible printer management (i.e. I can change printers on the server side without the users even noticing Great when we get new hardware or printers get sent to repairs!)...
Then, this year the people in charge of client machines in the institute decided to finally ditch WinXP licenses and migrate to Windows 7. Sweet! How can it hurt?
Oh, it can hurt. Terribly.
Windows 7 uses a different driver model, and after quite a bit of hair loss, I was not able to convince Samba to deliver drivers to Win7 (FWIW, I think we are mostly using 64 bit versions). Not only that, it also barfs when we try to install drivers manually and print to a share. And of course, it barfs in the least useful way, so it took me quite a bit of debugging and Web reading to find out it was not only my fault.
So, many people have told me that Samba (or rather, Windows-type networking) is no longer regarded as a good idea for printing. The future is here, and it's called IPP. And it is simpler, because Windows can talk directly with CUPS! Not only that, CUPS allows me to set valid users+groups to each printer. So, what's there to lose?
Besides time, that is. It took me some more hair pulling to find out that Windows 7 is shipped by default (at least in the version I'm using) with the Internet Printing Server feature disabled. Duh. OK, enable it, and... Ta-da! It works with CUPS! Joy, happiness!
Only that... It works only when I use it with no authentication.
Windows has an open issue,
Continuing with his standard pace of approximately one new version per month, 


I have an office with a nice large window, but more often than not I have to close the shades to be able to see something on my screen. Even worse: There were so many nice and sunny days where I would have loved to take my laptop outside and work there, but it (a Thinkpad T430s) is simply not usable in bright sun. I have seen those nice eInk based eBook readers, who are clearer the brighter they are. That s what I want for my laptop, and I am willing to sacrifice color and a bit of usability due to latency for being able to work in the bright daylight!
So while I was in Portland for DebConf14 (where I guess I felt a bit more like tinkering than otherwise) I bought a
A Forest of X Server Changes
We've got about another month left in the X server merge window for
1.17 and I've written a small set of fixes which haven't been reviewed
yet for merging. I thought I'd advertise them a bit and see if I
couldn't encourage a few of you to take a look and see if they're
useful, correct and complete.
All of these are in my personal X server repository:
A lot of people read up on good Python practice, and there's plenty of
information about that on the Internet. Many tips are included in the book I
wrote this year,
I m not used to talking about my day job but here s an exception.
Over the past few years I worked in two startups (3 years each). It
was nice to spend time in different areas: one job was mostly about
research and development in a Linux cluster environment; the other one
was about maintaining a highly-customized, Linux-based operating
system, managing a small support team, and performing technological
surveillance in IT security.
In the meanwhile I ve reached a milestone: 10 years with Debian. I had
been wondering for a few months whether I could try my luck going
freelance, becoming a Debian consultant. I finally decided to go ahead
and started in August!
The idea is to lend a hand for various Debian-related things like
systems administration, development/debugging, packaging/repository
maintenance, or Debian Installer support, be it one-shot or on a
regular basis. I didn t think about trainings/workshops at first but
sharing knowledge is something I ve always liked, even if I didn t
become a teacher.
For those interested, details can be found on my website:
the perl 5.20 transition is over, debconf14 is over, so I should have more
time for RC bugs? yes & no: I fixed some, but only in "our"
(as in: pkg-perl) packages:
I previously forgot to mention that I was planning to attend 
When we setup