Use Localazy, a software localization suite & translation management system, to take care of your JSON5 localization.
Choose from multiple developer-friendly options to start with Localazy. Integrate your JSON5 project the way that suits your workflow.
The best option for developers that want to make localization an automated part of their workflow.
Upload your texts and existing translations in any format directly to start quickly.
Add source keys via the web interface online and sync them into your project later.
Use the API to export translations and import content from/to Localazy programmatically.
There is no hard limit at the moment, but it’s recommended to keep the size of each individual item under 4kB. This corresponds to 4,000 characters encoded as UTF-8 and 2,000 characters encoded as UTF-16. Uploading longer texts won’t yield any errors, but might get refused by some external translation engines integrated in Localazy.
If you come across this issue, it is likely because you have exceeded your account’s source key limit or the changes you made haven’t been published yet. To resolve this, please go to the Billing section of your account to check your source key limit and consider upgrading if necessary. Additionally, you can visit your Project Activity Stream to verify if the project has been published.
We do not offer refunds. Please read Terms & Conditions of Localazy before purchase.
While many digital product makers choose machine translations for the very start (and it’s a standard best practice for early stages of development where MT-pre translate is a rational decision), they often forget that machine translation alone yields subpar results.
It’s vital to focus on the highest possible quality of translation when it comes to product interfaces and product marketing. But enlisting professional translators is not a silver bullet solution. You need to be diligent and prepare a sound basis for successful localization.
These are best practices to ensure the best translation quality:
In Localazy, every key can be in different states, which makes it invisible from the translation process.
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.
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.
You can either disable or delete a language if you no longer need it.
Disabling a language hides it from the translation interface but retains all translations and keys. On the other hand, deleting a language completely removes it from the project, optionally including all translations, keys, and associated metadata.
To delete a language in Localazy:
It’s important to note that deleting a language is permanent and can’t be undone. It’s recommended to double-check and ensure that the language deletion is intentional and necessary. Disabling a language may be a better option if you are unsure whether you’ll need the language in the future.
When working with external translators or agencies that are used to their own solution for translating, you may need a few extra features - language statistics and import/export.
You can find both of them in a single place - in our console. As you may already know, the console is our place for features that are relevant to a small subset of our users only and for features that are still being heavily improved over time. We are committed to making Localazy better every single day, so your feedback is welcomed. Feel free to share all your suggestions with us!
Learn more about Language Statistics
Some translation agencies are used to work with their own solution. There are numerous reasons for it - e.g., it helps them to calculate rewards for their translators and contractors. We are prepared for it, and you can easily export all your texts or only the untranslated ones as a CSV file, which any agency should easily be able to use.
Please note that we don’t recommend this for a variety of reasons - it adds extra manual work, and you also need to ensure that the agency has all the necessary context information in order to provide a high-quality translation. You wouldn’t need to care about it while using Localazy directly.
However, if there is no other way around it, here are a few simple steps on how to do it:
Learn more about CSV Import/Export
To change the source language of your project in Localazy, follow the steps outlined below:
A modal window appears asking you how and to which language you would like to change the source language.
You have two options here.
Select this option if you already have another language that is fully translated and you want to swtich its place with the current source language. You can choose any fully translated language in your project and the previous source language will continue to be treated as the normal Localazy language.
Sometimes, it happens that your source files are in en_GB
but you would like to use simply en
while keeping the content intact. Select this option to preserve the current source content but change the source locale code.
You can either choose a blank language or an existing hidden language. When changing the source to a language that is currently hidden, its data is purged first.