Q: Who can upload screenshots to project?

There are several user permission levels in Localazy . You can manage who has access to which feature by appointing them to a certain role in the project. To upload screenshots, users must have a Reviewer role. This prevents unwanted clutter or potential spam in the case of public projects.

Question 1

How to configure Connected Projects?

Accepted Answer

Activate the Professional plan to unlock the Connected Projects feature for your projects. Then select the projects you want to connect and you are done!

The connection is bi-directional and transitive. Meaning that connected projects mutually receive translations from each other. Also, if project A is connected to B, and B is connected to project C, then A might also receive translations from C and vice versa.

Question 2

Which localizable file format conversions do you support?

Accepted Answer

Localazy supports all major format conversions from Android XML and iOS .strings through multilingual JSON to XLIFF, qt-ts, and many more formats. You can learn more about supported file format conversions in the documentation.

Question 3

How can I convert different localization file formats?

Accepted Answer

In the File Management section of Localazy, when downloading your files, you can select the desired format and download your strings in any of the available file formats.

Format Conversions feature is also an integral part of the Localazy CLI tool, so if you want to automate format conversions, you will need to install Localazy CLI on your preferred platform.

Read the article: How to convert localization files into different formats?

Note: Format Conversions are available only as a part of the Professional plan

Question 4

How can the Continuous Localization Team improve my workflow?

Accepted Answer

Continuous Localization Team (CLT) acts as your own outsourced team for translation and reviews.

Depending on your configuration, CLT can help you get more languages ready by conducting human-assisted machine translations, translate your project by professional translators, or help you review your crowdsourced translations.

It is a real set it & forget it solution for automatic translation. Cut your time to market and translation costs, set up CLT now, enjoy localization on autopilot, and focus on what’s important: your product.

Question 5

What is the price of Continuous Localization services?

Accepted Answer

The price of services provided by the Continuous Localization Team depends on the chosen language pair and the selected level of service.

You can choose between:

Professional Translations
Professional Proofreading
Human Translation Validation
Human-Assisted Machine Translations

You can see the estimated costs before you order.

To start, sign up, click on the Order translations tab in the left menu and top up some translation credits to your balance.

Learn how to order translations for your project.

Question 6

What is a continuous translation, and how can Human-Assisted Machine Translations help?

Accepted Answer

Have you ever needed to order translations multiple times? Then you already know that there is quite a managerial overhead in handling the translation contract and translation delivery on its own.

Not your problem anymore, with continuous translations by our Continuous Localization Team (CLT).

Human-Assisted Machine Translations is one of the continuous translation services provided by CLT and can help you get more languages faster with zero hassle. Select this service to quickly test new markets or languages and get the best machine translation result for every string verified by a human. On top of that, the human preserves context, punctuation, and placeholders.

Translations made by the Human-Assisted Machine Translation are automatically approved and ready to be used in your project. With enough credits, you can get your project translated completely. We advise you to follow up with thorough localization testing to correct possible mistakes.

Set up the Human-Assisted Machine Translation now, top up your translation credits and forget it. Our systems will work towards improving the multilingual support of your project while you sleep or focus on more important things.

Question 7

How to create and manage Releases?

Accepted Answer

Once you subscribe to one of our paid plans and activate the Releases feature, you can start using new commands in the Localazy CLI tool to create and manage tags for your translations or navigate to the Releases page under the Tools section in the menu to manage your releases inside the Localazy platform.

Learn more about Release Tags management with Localazy CLI Learn more about manging Releases with Localazy

Question 8

Can I use the Localazy Pre-translate feature for free?

Accepted Answer

Every account comes with a 14-day trial period with the Business Plan active to try all the features before committing to a paid subscription.

The pre-translate feature trial is limited to a maximum of 1000 source keys translated, but once you ugrade to a full subscription of the Professional or higher plan, you can enjoy unlimited use of MT pre-translate!

Learn more about the Professional plan

Question 9

Is the Context Screenshots feature free to use?

Accepted Answer

The Context Screenshots feature with OCR linking is available in the Professional plan and higher tiers.

Figma Screenshots become available once your organization upgrades to the Autopilot plan.

Learn more about Localazy Pricing

Question 10

Who can upload screenshots to project?

Accepted Answer

There are several user permission levels in Localazy. You can manage who has access to which feature by appointing them to a certain role in the project.

To upload screenshots, users must have a Reviewer role. This prevents unwanted clutter or potential spam in the case of public projects.

Question 11

How can Localazy help me solve duplicities in the project?

Accepted Answer

Your projects can often contain multiple keys with the same content. Be it button labels across a large-scale information system, including keys on the backend and frontend or Android vs. iOS versions of your app. There are two ways to approach duplicate keys with Localazy.

The first option to consider when you have two or more projects that contain duplicities is to use the Connected Projects feature, which is available with the Professional plan. Connected Projects can help you by translating identical keys across multiple projects. This feature is great for a portfolio of projects sharing duplicate keys or Android and iOS versions of the same app. When enabled, Localazy distributes existing translations between connected projects and automatically decides whether the translation can be used right away or needs to go through review first.

For a robust duplicity management that can work with duplicities inside one project and across multiple projects as well, we recommend the Duplicity Linking feature, available with the Business plan. With duplicity linking, you can define one key as the source for all other keys with the same or similar content. The other keys are then marked as hidden and get their translation from the linked key.

Question 12

Can I merge two duplicate source keys so they can share the same translation?

Accepted Answer

Sure! If you can’t or don’t want to rename the keys to use the same name in the source integration, you can use the Duplicity Linking feature when you don’t want to alter the source, so the keys will share their translations.

Localizing a large project can result in creating duplicated keys, which becomes hard to manage, especially when multiple teams work on the same project. Localazy offers a solution called Duplicity Linking that allows you to reuse translations across linked keys in all languages and even across several projects.

Duplicity Linking is available in the Business plan

The feature links multiple different keys with the same content, with one source key acting as the content source and the others as the linked keys. The linked keys retain their own values and translations, but when the link is active, and their translation value is retrieved, the content source key value is used instead for all languages. Removing the link restores the linked key to its original behavior.

You can learn more in the article: Keep your duplicate strings under control with the Duplicity Linking feature

Question 13

How can I mark and merge duplicates?

Accepted Answer

If your project has duplicate keys, you can easily resolve them by linking them together. When a key is linked to another, it automatically inherits the content of the linked key during publishing. Linked keys are automatically marked as hidden and do not require separate translations. While a linked key can still have its own content, that content won’t be used during publishing and will be replaced by the content of the linked key as long as the link is active.

You can manage duplicity links using public API, automating their creation or deletion.

Learn more in the Duplicity Linking API documentation.

Question 14

How to save on translations of duplicate content?

Accepted Answer

When translating content, it’s common to encounter duplicate phrases or sentences. Translating these duplicates multiple times not only consumes valuable time and resources but also risks inconsistencies in translations. Here are some strategies to save on translations of duplicate content:

Use Key Clustering: Key Clustering automatically identifies and groups keys with identical values, eliminating the need to translate the same content multiple times. This not only saves time and resources but also ensures consistency across translations.

Leverage Duplicity Linking: Duplicity Linking allows you to link multiple keys with the same content. When one key is translated, all linked keys are automatically updated with the new translation. This reduces the time spent on translating duplicate content.

Utilize Machine Translations (MT): Machine Translations can provide initial translations for your content, which can then be reviewed and refined by human translators. This can speed up the translation process and reduce costs.

Remember, the key to saving on translations of duplicate content is to leverage the right tools to streamline the translation process and ensure consistency across all translations.

Question 15

What should be included in a translation glossary?

Accepted Answer

A translation glossary should include a list of terms used in the Localazy project, related to the particular domain of knowledge and their definitions. It should also contain industry-specific terms and provide their clarification. The glossary should also provide some context for translators on the context of the term.

Don’t forget to include the following:

Product Names and Branding: Include translations for product names, trademarks, and branding elements to ensure consistency and accuracy in branding across different language versions.
Key Terminology: Start by listing the most important terms specific to the subject matter you’re translating. These could be industry-specific jargon, technical terms, or any words unique to the project or the field.
Term Description: Provide clear definitions for each term to ensure translators understand their precise meaning and usage in context.
Preferred Translations: If the term is not to be translated, specify it in the settings, if you want to translate it, include the preferred translations or equivalents for each term in the target language. This helps maintain consistency across all translations.
Contextual Usage: Provide examples on how each term should be used in different contexts. This helps translators understand the nuances of the term and use it appropriately.
Acronyms and Abbreviations: List any acronyms or abbreviations used in the source content along with their full meanings and translations.

Question 16

How can I prevent the translation of specific names and industry terms?

Accepted Answer

The Glossary allows you to prevent certain terms from getting translated or define correct translations for them.

You can specify that certain entries, such as specific names and industry terms, should not be translated - just make sure the “Translate to other languages?” checkbox is left unchecked.

Question 17

Can I share the glossary with other projects?

Accepted Answer

Yes, with the Connected Projects feature, you can distribute glossary terms across all your projects. Each new glossary addition in any of the connected projects will automatically be shared with the others.

Learn more about glossary sharing in the documentation

Question 18

What is the difference between glossary and translation memory?

Accepted Answer

A Glossary and a Translation Memory ™ are both tools used in the field of translation, but they serve different purposes:

Glossary: #️⃣

A glossary is a list of terms and their corresponding translations in one or more languages.
It provides translators with consistent terminology throughout a translation project, ensuring uniformity and accuracy.
Glossaries are particularly useful for technical or specialized content where specific terminology is essential.
They can also include contextual information or usage notes to clarify the meaning of terms further.

Translation Memory ™: #️⃣

A translation memory is a database that stores segments of text, such as sentences or paragraphs, and their translations.
When a translator works on new strings, the TM compares the new strings to those stored in its database. And if a similar segment has been translated before, the Localazy TM suggests the previous translation to the translator, saving time and ensuring consistency.
TMs are especially beneficial for projects with repetitive content, such as software localization or technical documentation.

In summary, while a glossary focuses on defining and standardizing terminology, a translation memory aids in reusing previously translated text segments to improve efficiency and maintain consistency across translations.

Both glossary and translation memory are included in the Free plan of the Localazy platform.

Question 19

What are the ways that I can upload and link screenshots?

Accepted Answer

Web Upload: The web upload feature is a user-friendly interface provided for uploading screenshots. You can simply drag and drop your screenshot files into the designated area or browse your files to select them. Once the screenshots are uploaded, you can link them to specific phrases in your localization project. This is particularly useful when you want to provide visual context for the phrases being translated. It’s a straightforward process that doesn’t require any technical expertise.

API: For more advanced use cases, we offer a robust API. This allows you to automate the process of uploading and linking screenshots. If you have a large number of screenshots or if you need to integrate this process into your existing development or deployment workflows, the API can be a powerful tool. The API is well-documented and provides flexibility for custom integration. This means you can tailor the API to suit your specific needs, whether you want to automate the upload process, integrate it with your CI/CD pipeline, or build custom features on top of it.

Figma Screenshots: If you’re using Figma for your UI/UX designs, you can take advantage of the our Figma plugin. This plugin allows you to directly upload your screenshots from Figma. It streamlines the process of keeping your designs and localization project in sync. Whenever you update your designs in Figma, you can easily update the corresponding screenshots in your localization project. This ensures that your translators always have the most up-to-date visual context when translating phrases. Find out more about Figma Screenshots feature.

Question 20

What are screenshot tags?

Accepted Answer

What are screenshot tags? Screenshot tags are essentially labels or identifiers that you can attach to your screenshots. They serve as a powerful tool to help you better manage and organize your screenshots.

How do tags help categorize screenshots? Tags can be used to categorize your screenshots based on any criteria that you find useful. For example, you might use tags to group screenshots by:

Feature: Group screenshots that pertain to a specific feature of your application. This can be particularly useful when you’re working on a large project with multiple features.
Screen: Group screenshots that belong to a specific screen or page of your application. This can help you quickly locate all the screenshots for a particular screen.
User Flow: Group screenshots that represent a specific user flow or journey through your application. This can be useful for understanding and visualizing the user experience.

By categorizing your screenshots with tags, you can greatly enhance your ability to organize and search through your screenshots. This can save you time and make your workflow more efficient.

Filtering with Tags: Furthermore, tags can also be used to filter your screenshots, making it easier to focus on specific parts of your project. For example, if you only want to view screenshots for a particular feature, you can filter your screenshots using the relevant tag. This can be particularly useful when you’re working with a large number of screenshots.

Updating and Managing Tags: Managing your screenshot tags is a straightforward process. You can add or remove tags from a screenshot at any time. This means you can easily update your screenshot categorization as your project evolves.

In summary, Screenshot tags are a powerful feature for managing and organizing your screenshots. They allow you to categorize your screenshots, enhance your ability to search through your screenshots, and focus on specific parts of your project. By effectively using screenshot tags, you can streamline your workflow and make your localization project more manageable.

Find out more about Screenshots feature benefits

Question 21

How to automatically translate my content with machine translations?

Accepted Answer

To automatically translate your content using machine translations, you need to set up an Automation.

Navigate to the Tools -> Automations section in your project, create new, and select the action “Use machine translations”.

Configure the trigger on events such as key uploads or updates, and specify the target languages for machine translation.

Read more about content translation on blog.

Question 22

How to set up filters for my automations?

Accepted Answer

Filters in Localazy’s Automations allow you to apply actions to specific subsets of keys or translations. You can set filters based on language, user roles, state, and tags.

To set up filters, go to the automation configuration, navigate to the third page in settings, and tick your desired filters. These filters can include or exclude specific conditions to fine-tune the trigger’s application.

Find out more in the blog article or our documentation.

Question 23

How to automatically copy translations from one language to another?

Accepted Answer

To automatically copy translations from one language to another, set up a new Automation with the action “Copy translations to another language”.

Configure the source and target languages and specify the trigger events, such as key creation or updates. This automation will ensure that translations are automatically copied whenever the specified events occur.

Question 24

How to automate the deletion of deprecated keys?

Accepted Answer

You can consider deleting deprecated keys, if you are running over the source key limit. However, be sure that deleted keys are no longer necessary for your project, as you cannot restore them if needed, and all the associated data is also deleted.

To automate the deletion of deprecated keys, create a new Automation in the Tools section of your project. Choose the action “Delete deprecated source keys” and configure it to trigger on events like key uploads. You can set filters to specify which keys to delete, such as those with a certain prefix.

Read more about topic on our blog.

Question 25

How does the Localazy Translation Memory work?

Accepted Answer

Localazy Translation Memory ™ stores all previously translated source keys, allowing them to be reused in future translations. When a new source key fully matches a stored TM entry, Localazy suggests the existing translation, saving time and ensuring project consistency.

Find out more about Translation Memory.

Question 26

Can I import my own Translation Memory to Localazy?

Accepted Answer

Yes, you can import your own Translation Memory into Localazy. Localazy supports standard TMX (Translation Memory eXchange) files, which you can upload through the platform to integrate your existing translations with Localazy’s system.

The best way to do it is to create a new project that will serve only as a translation memory source. Upload your TMX files to the project and connect it to your real translation projects using the Connected Projects feature.

Learn more about TMX integration in the documentation.

Question 27

How can I share Translation Memories between projects?

Accepted Answer

Translation Memories can be shared between projects using the Connected Projects feature.

To activate translation memory between multiple projects, go to Tools → Connected Projects to begin. Open the Translation memory tab and select a project you would like to connect(max. 5 projects).

Connecting projects translation memories allows you to re-use translations from the other projects via batch translation or as suggestions during translate and review sessions.

Find out more about Connected Projects feature.

Question 28

What is the difference between ShareTM and Translation Memory?

Accepted Answer

Translation Memory is an automatically populated database that stores and suggests previously translated segments for reuse within one project(or multiple projects with Connected Projects feature).

ShareTM, on the other hand, is a public translation memory that allows you to get suggestions from other Localazy projects and share your translations with others in return. Find out more about ShareTM.

Question 29

How does the XML/HTML tag collapse work?

Accepted Answer

The XML/HTML tag collapse feature in Localazy allows you to simplify the translation process by collapsing tags within your strings. When enabled, this feature replaces XML and HTML tags with one-letter tags, making the text easier to read and translate. The simplified tags are saved as their original versions, maintaining the content validity while helping translators focus on the actual content without being distracted by technical details. Find out more in our documentation

Question 30

What are Localazy Webhooks and what events can I hook into?

Accepted Answer

Webhooks in Localazy are user-defined custom callbacks that trigger when specific actions occur within your Localazy projects.

You can currently hook into five different events:

comment_added: Triggered when someone adds a comment to your project
import_finished: Triggered when content importing completes with changes (added, updated, or deprecated keys)
import_finished_empty: Triggered when importing finishes but no changes occurred
project_published: Triggered when your project is successfully published
tag_promoted: Triggered when a release tag is promoted to another tag

Question 31

How does Localazy's validation system prevent plural-related errors in my application?

Accepted Answer

The system automatically checks that all required plural forms have been provided for each language and ensures that variables and placeholders are consistently used across all plural variants — preventing runtime crashes due to missing placeholders.

For example, if a translator completes the “one” form but forgets the “other” form for a language, Localazy will flag this as incomplete.

This proactive validation approach means your applications will display correct plural forms across all languages.

Learn more about plural checks in Localazy

Question 32

Can I customize plural rules in Localazy to match my i18n library's implementation?

Accepted Answer

Yes, Localazy’s Professional tier and above gives you access to custom plural rules per language.

While Localazy follows CLDR standards by default (which works with most i18n libraries), some frameworks or custom implementations might require specific plural handling. Through the Developer Console, you can modify which plural categories should be available for each language in your project.

This customization ensures perfect compatibility with any i18n framework you’re using. You can enable or disable specific plural categories (zero, one, two, few, many, other) for each language, ensuring that Localazy exports exactly the plural structure your application expects.

Features

💡 Enough theory, try Localazy now! 🚀