Stay updated with Crowdin by signing up for our newsletter
Localization used to be a part of the app scaling strategy. But not anymore. Today, when users download a mobile application, they already expect it to match their language preferences. So no matter what stage of the app development you’re in, localization should be part of it. The good news, localization is no longer a process that slows down everything. If done with the right technology, it is smoothly integrated into the development process and becomes an integral part of the app life cycle.
Let’s discuss automation in the app localization, sharing translations between Android and iOS projects, and providing context for translators. You’ll also learn how to localize strings without resource files and export Android XML and Strings files if the sources were uploaded in other formats.
Here’s our traditional roundup of all the new features and improvements released in the last month. They include newly launched integration with Marketo, a new app for seamless glossary translation, new features for UI localization with Crowdin plugin for Figma, improved navigation for the Resources in Crowdin, exclusive Crowdin Enterprise updates, and more.
Read on to learn details and check out all the new features the first month of 2021 brought us.
Until recently, UI design and localization were two independent processes. Moreover, usually, localization was initiated after the product succeeded and was about to scale. The growing customer demand to use products in their native languages, though, makes teams release multilingual products right from the start. Localization becomes an ongoing process for most companies.
To empower design teams to participate in the company’s localization initiatives more actively, we’ve launched plugins for Adobe XD, Figma, and Sketch. This post will embrace user interface localization best practices and showcase how you can use the plugins to adapt them to your localization workflows.
For a non-tech-savvy person, creating an SRX file with the segmentation rules might become a time-consuming task. You need to go through the list of specifications and compose the rules using the XML vocabulary. On the other hand, merging and splitting the strings manually might take an even longer time. Luckily, there’s now an intuitive way to add custom segmentation rules, test, and apply them to similar strings automatically.
In this post, we’ll take a closer look at content segmentation, discuss why it is important in localization, and give you step-by-step instructions on how you can quickly add custom segmentation with the Segmentation Rules Generator app.
As much as 60% of consumers worldwide ‘rarely or never’ buy from English-only websites. This proves that if you’re looking to enter foreign markets, your content has to be localized. But before that, consider writing for translation and localization from the very beginning.
Read on to discover some writing for translation tips and how you can accelerate the localization process to improve its cost and time efficiency.
Let’s review the last month of the previous year for the updates and new features that will help you automate localization, provide context, and launch multilingual products in 2021 faster.
The key updates released in December include: updates to Source files, Strings, and Tasks API, new versions of CLI, Android Studio plugin, plugins for Adobe XD and Sketch, new and updated Crowdin Apps, improvements to task and user management in both Crowdin and Crowdin Enterprise, and more.
2020 has been a year of turbulent changes. Sometimes it felt like the events were unfolding with a speed you can hardly follow. Still, we’ve learned a lot and re-evaluated how we approach many things, from global problems to the routine daily workflows. What remained unchanged is the role of technology in everything we do. It has helped us collaborate on our projects wherever we are, stay flexible with our planning, and move towards our goals, no matter what.
We’d like to take a moment and look back at what our team has been onto this year. For us, it was the highest time to give you even more automation possibilities and more functionality for cross-department collaboration so that you could keep launching multilingual products in the new demanding environment with less effort.
At the end of the year, when achievements are evaluated, and the big goals ahead are all set, we start to look for ways to optimize the usual processes. It’s a great time to rethink how we are doing things daily, and localization processes are not an exception. There’s always a place for improvement.
In localization, we believe productivity depends on how many routine tasks you can automate and the technology you use to do the rest of them. We’ve assembled a collection of Crowdin Apps to help you with the full-scale management of your localization workflow. All of them are free to use and can be installed for your Crowdin and Crowdin Enterprise projects.
A multilingual website is a great way to appeal to millions of potential customers around the world. What if we say that website translation does not require busy engineers’ involvement and a tedious preparation process?
Crowdin introduces JS Proxy – technology aimed at helping teams localize websites effortlessly. No manual source content export or translation copy-pasting.
They say you can’t improve what you can’t measure. A pretty obvious statement that gets trickier if applied to the translation quality control. Localization quality assurance is a complex task that includes linguistic QA, visual QA, functionality QA, and more. You can now cope with the first one easier and get more insights into the contributors’ performance with the Linguistic Quality Assurance app.
Read on to learn how you can configure the app for your Crowdin and Crowdin Enterprise projects and track the quality, productivity, and efficiency of translation with the industry-standard metrics.