Localize your translation files on the go with Beebox and Github
Nowadays localization gets more and more integrated into projects, and it’s crucial that development and localization members stay synchronized throughout the whole translation project. In this article we will see on how Git can be used with Wordbee Beebox.
If you don’t know how Git works, stay with me. Otherwise jump to next section of the article.
Git is a free, open-source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. It was designed by Linus Torvalds, the creators of Linux. Git tracks changes to source code for multiple users, allowing the sharing of the same codebase to other team members easily.
Let me break it down and explain some of the key wording:
Repositories: A repository is similar to a folder for projects. The project’s repository contains all of the project’s files and stores each file’s amendment history. Worked projects can be commented on and managed within the repository. Code repositories are only reliable if they are continually kept up to date with committing. Therefore, commits consist mostly of small changes rather than big, heavy fixes.
Commits and Pushes: Git commit puts your changes into your local repository, while Git push sends your changes to the remote location. Git push is used to add commits you have done on the local repository to a remote one — together with Git pull, it allows people to collaborate.
Git Branches: Let’s take a step back to understand how Git does branching and examine how Git stores its data in the first place.
Git does not store data as a series of changesets or differences, but rather as a series of snapshots. Git stores a commit object that contains a pointer to the snapshot of the content you staged. This object also contains the author’s name and email address, the message that you typed, and pointers to the commit or commits that directly came before this commit (its parent or parents).
Branching or branch out: In revision control and software configuration management, you can duplicate an object that’s under revision (such as a source code file or a directory tree) so that modifications can happen in parallel along both branches.
Follow this link if you want to know more about Git and learn about push and pull requests, staging, and tagging.
Git and translations
As we know by now, Git can track changes to any text file (not only source code), so it may be used also to maintain text-based documentation files and translation files.
But how does that work with Wordbee?
How to integrate Git and Beebox
As the integration with your source control system uses Beebox hot folder, it makes Beebox compatible with all source control systems including Git.
Take a look at this guide about file copy and hot folders to understand the settings and customize your setup.
Compatibility configuration with Beebox
As every integration is different depending of the operation of your software, you can integrate Beebox hot folders with your Git source control system. First, you will need to create a Beebox project and configure the parsers according to the source code you use and then enable the file to change detection for automation.
Pull your source code to Beebox hot folder. Once your Beebox project is ready, you need to decide the way you want to pull your source code into the Beebox input folder.
Commit and push your translation code, or use it immediately. Once processed, the translated files are generated into the Beebox output folder.
Commit and push
You can also register your Git repository in this folder to push your content back to another branch, for example by manually copying the files or automatically using a script triggered via Windows Scheduler.
Please visit this how-to guide to use Beebox with Git repositories.