When a string has already been translated in your app, Localazy can automatically find all the same untranslated strings and translate them for you.
Smarter translation memory 🔗
As your app becomes bigger, the number of phrases inevitably grows, and soon, you may not be able to keep all of them in your mind, and you may tend to add the same phrases multiple times.
For this reason, there is a translation memory in translation platforms, that serves as an additional source of information for the translators. However, when using professional translation services , some platforms charge you for the translation again. Not nice, well?
Localazy InTM behaves differently. It’s a pro-active translation memory that scans your app and looks for the same phrases in the source language with missing translations in other languages. If there is a missing translation that could be completed from another source, it’s offered through our unique review.
Localazy InTM offering a translated phrase:
Okay, a bit smarter translation memory is all the magic around InTM? Of course not! There are two more critical features that InTM provides.
Reuse of previous translations 🔗
Localazy is tightly integrated with your app and understand its structure. However, you may decide to rename your dynamic app module or library. Unfortunately, there is no way how we can detect that you did so. Old phrases are deprecated in favour of new ones being uploaded because their namespace has changed. And those new ones are left untranslated.
Yes, they are, but only for a short period of time before Localazy InTM processes all of them and reuses translations from deprecated ones. Thanks to its advanced heuristic, it can skip the review process and approve new translations for you automatically.
From your point of view, it seems like translations are smoothly moved to another namespace, but now you know that it’s not that simple at all .
Localazy InTM translated the phrase automatically:
Reuse between connected apps 🔗
Supporting different platforms is not easy. For example, there is a big difference between how Android and iOS apps are translated, and the situation becomes more complicated with support for hybrid/browser-based apps (React Native, Ionic, etc.). There are differences in how strings are referenced, and so different platforms can’t share one repository. It would break deprecating phrases and other essential features for version control.
The InTM mechanism is currently much smarter as it can work across many so-called Connected Apps. Connected Apps are a feature add-on, which you need to enable first, but it can save you tremendous amounts of time and money in the long run, esp. with this specific use case.
InTM can replicate translations between connected apps seamlessly. It’s very similar to our ShareTM that works on a global level, but InTM has a kind of higher authority and different approach. For example, ShareTM is designed to filter out certain phrases to protect private data, while InTM doesn’t have these limitations as it only operates on YOUR projects.
What is best about that? If you translate for example, your iOS app to a completely new language, all your effort is seamlessly replicated to the Android app and other connected projects too! You and all your users can instantly benefit from it. It’s in line of the very nature of our vision.
InTM vs. ShareTM 🔗
I’ve already mentioned that there is a difference between InTM and ShareTM. InTM operates only inside your project/projects and can afford to handle all translations without filtering out those containing app-specific data.
Also, InTM can bypass the review process based on an algorithmic set of rules and approve phrases automatically for you. That’s extremely useful for particular situations like namespace changes.
The last big difference is that InTM is bound to your projects and thus doesn’t need to use language detection mechanisms and better fit to your projects’ existing structure.
Also, there is another subtle reason for using InTM - during the review process, if InTM offers the translation, you can be sure about its quality as only approved phrases from your own projects are suggested. That easier your decision-making and speed up the review.
InTM is also a bit faster as ShareTM needs to perform many more operations. InTM goes through all your projects in a single loop, whereas ShareTM uses a distributed approach to be able to handle thousands of connections. From our point of view, there are also considerable differences in how data are stored and processed over time.
As can see, InTM and ShareTM are here to perform very similar operations, but each has pros and cons. And each of them is here for a reason; a good reason.