Question 1

What are source keys?

Accepted Answer

A source key is a segment of text stored in Localazy, representing content in your source language. It’s a single string of text in your source language, e.g., a button label or a short paragraph of text in a dialogue window of your application. It can even be a short blog article written in Markdown syntax. In the picture below, there are three source keys; as you can see, each contains a different type of content.

You can imagine a source key as a single row in a spreadsheet you were previously using for translations.

Examples of source keys in localazy

Translations to other languages are unlimited, and translating your project to more languages does not affect the number of source keys used. I.e., the content of one source key translated into 10 languages still counts as one source key.

Question 2

What happens when I reach the source key limit?

Accepted Answer

Don’t worry! You will still be able to use Localazy and all features in your plan without any restrictions. However, you won’t be able to publish your changes until you upgrade your plan.

Question 3

How can I increase the source key limit?

Accepted Answer

You can increase your source key limit plus unlock additional features by upgrading to a higher tier.

Or, you can increase your source key limit for free! Visit the Community section and support Localazy with reviews, referrals, etc., to earn your rewards.

Question 4

What is the difference between hidden and deprecated source keys?

Accepted Answer

In Localazy, every key can be in different states, which makes it invisible from the translation process.

Hidden: Hidden keys are not available to translators, but other than that, they are processed the same way as all the others. They are also exported in the output file.

Keys are automatically marked hidden under certain circumstances - when the source language translation is empty or when they are linked to another one using our Duplicity Linking feature.

Deprecated: Deprecated keys are invisible in the translation process and are not exported in the output file. Under certain circumstances, they can be exported for our Android/iOS SDK when the update is required from the older version of the app. If the key reappears in the input data, it’s restored along with its complete state (context, translation, contributors, etc.)
Deleted: Deleted keys are removed with all their data - comments, translations, screenshot linking, contributors’ history, etc. Once the key is deleted, it’s no longer counted against the key limit, and it’s impossible to restore it.

Question 5

Should I delete deprecated keys?

Accepted Answer

If you are running over the source key limit, you can consider deleting deprecated keys. 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.

It’s not only about the translations you can easily store and restore if needed when using deprecated keys instead of deleting them, but also about context information, comments, user interactions, etc. Once the key is deleted, it’s no longer counted against the key limit, and it’s impossible to restore it.

Question 6

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 7

What is the difference between hidden and active string?

Accepted Answer

The difference between “active” and “hidden” keys is that “hidden” keys are not available to translators but are otherwise handled the same as all others. They are also exported to the output file.

Keys are automatically marked as hidden under certain circumstances - when the source language translation is empty or when they are linked to another translation using the Duplicity Linking feature available in the Business Plan.

You can hide keys you don’t need to translate. Hidden keys will remain hidden until you reactivate them.

Learn more about the different states your source strings can be in in the docs article

Accounts & Billing

💡 Enough theory, try Localazy now! 🚀