Contribute to the internationalization of Printoid

You can now contribute to the Printoid Project by translating the app by yourself to your native language!

You don’t have to be a developer, and you don’t need any development skills 🙂

But for convenient, easier integration and maintenance, and for tracking changes in the XML files, I have created a public repository on Github.

For your personal information, I have introduced a new Android Library called Printoid Languages. This library is now included in the Printoid project, and it contains all the resources for the internationalization of the application.

Don’t worry, the following informations looks hard to understand for a beginner with Git, but if you follow the steps in the right order, that’s very easy!

1. PREREQUISITES

First of all, you need to create your own Github account here ; or sign in to an existing account here.

You also need to install git on your computer. In a terminal, execute the following commands depending on your operating system.

2. FORK AND CLONE THE REPOSITORY

Creating a fork

Just head over to the GitHub page and click the “Fork” button. It’s just that simple. Once you’ve done that, you can use your favorite git client to clone your repository or just head straight to the command line:

Keeping your fork up to date

While this isn’t an absolutely necessary step, if you plan on doing anything more than just a tiny quick fix, you’ll want to make sure you keep your fork up to date by tracking the original “upstream” repo that you forked. To do this, you’ll need to add a remote:

If there are no unique commits on the local master branch, git will simply perform a fast-forward. However, if you have been making changes on master (in the vast majority of cases you probably shouldn’t be – see the next section, you may have to deal with conflicts. When doing so, be careful to respect the changes made upstream.

3. WORK ON YOUR TRANSLATIONS

Create a branch

Whenever you begin work, it’s important that you create a new branch. Not only is it proper git workflow, but it also keeps your changes organized and separated from the master branch so that you can easily submit and manage multiple pull requests for every task you complete.

<string name="connection_progress_dialog_message">The app is trying to communicates with your 3D printer.\nYou can drink a coffee for the next 2 seconds.</string>

4. SUBMIT YOUR CHANGES

Cleaning up your work

Prior to submitting your pull request, you might want to do a few things to clean up your branch and make it as simple as possible for the original repository’s maintainer to test, accept, and merge your work.

If any commits have been made to the upstream master branch, you should rebase your development branch so that merging it will be a simple fast-forward that won’t require any conflict resolution work.

This will open up a text editor where you can specify which commits to squash.

Submitting

Once you’ve committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes on your development branch and update.

Enjoy!

Then, as the developer of Printoid, I will perform some adjustments/corrections on your changes, then accept your pull request 🙂

Your changes will be integrated to Printoid Languages, and finally integrated to the Printoid main project during the next release generation!