Translating updates just got easier. You can now select to display only untranslated strings or only machine translated strings, which is especially important if you’re working with large markdown or json files. Just click on the filter icon in the top right part of the editor
and select the desired view:
If you want your community to see the translation progress of your project, feel free to add our badge to your Readme file, Wiki or Contributing Guidelines.
To generate the badge link, head to the Badge tab in Project Overview:
You can also generate badges for each of the project languages:
Check out how other GitHub projects are using our badge:
If you’re a language moderator or project owner, you may now find it easier to send multiple translated files (review requests) in a single pull request
Stay tuned for future updates!
Should you have any questions, feel free to join our community chat or send us an email.
]]>We are excited to announce that GitLocalize is now free for everyone!
Yes. All the features — the synchronization of repositories, the webhook to keep your projects up-to-date, manual and machine translation into all the supported languages, and teamwork — are available for free.
Practically. Whether you own OSS or private projects, you can sync them to GitLocalize and translate their documentation, guides and resource strings into all the languages. We intend to keep the platform free for every project, except really huge ones — in such cases we will have to discuss an Enterprise plan with additional technical support from our team.
Yes, we intend to keep it that way.
GitLocalize is still far from perfect, and what we need now is as much feedback as possible. Feel free to sign in or sign up with your GitHub account, add a new repo, and start translating right away. Our team will be more than happy to answer any questions — join the community chat or book a call to share your experience!
]]>We are excited to announce that GitLocalize is now part of Alconost!
Alconost Inc. is a U.S.-based Multi-Language Vendor that helps companies around the world with localization of their products and content into 80+ languages. Alconost will use its professional team and expertise in localization to support and improve GitLocalize, and to bring professional language services closer to developers.
Stay tuned for future updates!
Should you have any questions, feel free to join our community chat or book a call with us directly!
]]>We are excited to announce that Google is now experimenting with GitLocalize! We’re assisting the Web Fundamentals community with localizing their website.
So far, the Web Fundamentals community has been able to localize the site into 17 languages. But keeping the translations up-to-date has proven to be more than challenging. We believe that GitLocalize is the perfect solution to this problem!
Join the Web Fundamentals community to localize their vast knowledge of cutting-edge web technology into your language today. Innovation should never get lost in translation.
]]>If you haven’t signed up yet, register with GitLocalize for free and get ready to localize your Rails app with zero stress.
Read our blog article to learn more about how GitLocalize works and what it can do for you.
Navigate to the Add Repository
page from your profile. Here, you’ll see the form to register your GitHub repository with the GitLocalize platform.
In the middle of the page, specify where your source i18n files are located and where you want to generate translated files.
For example, let’s say that you have source English i18n YAML files at config/locales/en.yml
and want to have translated ones at config/locales/ja.yml
or config/locales/es.yml
. Set the drop-down menu on the left to File
, then type config/locales/en.yml
for Source Path
and config/locales/%lang%.yml
for Translation Path
.
This %lang%
is a placeholder for the two-character code of your translation target languages. For example, if you’re translating to Japanese and Spanish, ja.yml
and es.yml
will be generated, respectively.
If you have multiple i18n files, simply click the + Add Rule
button to register more rules.
Once you submit and add your repository, you can start continuous localization work with your Rails app on GitLocalize.
Simply go to your repository page from your profile, choose a language, navigate to the YAML file, and open the editor. You’re all set!
Check out the video below or our docs to see how the rest of the process works!
]]>GitLocalize is a one of the seven new apps that lauched on GitHub Marketplace on August 1st and our category localization is the new category on the marketplace!
GitHub introduces the new apps including GitLocalize in their official blog post, “Introducing seven new apps to GitHub Marketplace”. Check out the article to know more about other cool apps on the marketplace.
Go to our app page to find out more and sign up for a free account today!
]]>GitLocalize is a continuous localization platform for GitHub repositories and automates the process for developers. Because of the ever-changing nature of Internet-related product, keeping localizing them has been really challenging. GitLocalize solves this by connecting to your GitHub repository and naturally integrating with your development workflow in just a few clicks.
We started supporting from Markdown files. Try GitLocalize in a minute if you have a documentation project that you want to localize.
You can immediately get started with your GitHub account, choose your repository to integrate with GitLocalize and localize your files. Here are the key features of the platform:
Once you integrate your repo with GitLocalize, it starts pulling all the localization related files into its platform and watching the changes.
When you finish translating a file, you then make a review request and ask the team to review the changes, like what you do with a pull request.
After the review process, you can send a pull request back to your repo. It makes each contribution on GitLocalize each user’s commit on the repository.
With GitLocalize, your team no longer need to do anything extra to localize your project and developers only need to look at those pull request coming.
Since it automatically links a translation with its original sentence, it can show you which part needs to be translated when the original one is updated.
No need to manually check which parts are affected due to the original updated. You just need to look at GitLocalize editor and fill in the missing translations.
And of course, more features are lined up and will be shipped soon!
Check out the video below to see how it works in more depth!
We need your feedback to improve and bring the product to create the better future for localization. Please feel free to give us any feedbacks here. We will respond within a day.
Also, we have a Gitter channel to chat. Feel free to join and jump into the conversation.
And of course, this blog is localized into Japanese with GitLocalize, make a suggestion for the translation from here.
We hope to make your localization far easier and smoother and support your product’s global success! Happy localizing!
]]>