locize documentation
Help CenterBlogSign inlocize.com
Search…
Introduction
Using locize
What's inside?
The different views
Checks/Issues
Using locize as a translator
Integration
Getting started
Instrumenting your code
API
Webhook
Slack
Microsoft Teams
CLI
I18n Formats
File Formats
Guides / Tips & Tricks
Find unused translations
How to search
Going to production
Keeping track of new translations
Working with translators
Migrating an i18next project
Migrating from ...
More
InContext Editor
Figma Plugin
Versioning
Namespaces
Notifications
Multi-Tenant
Caching
Backend Fallback
Latency Optimization – Tips for Optimal Performance
2-factor authentication
Convince Your Boss Letter
General questions
Which integration option should I use?
Do I have to use the locize CDN or can I host / bundle the translations directly?
How is locize different from the alternatives?
Why do I get “The passed json is nested too deeply.” when consuming the API?
Is locize only for developers and translators or is project management within the process too?
What is the regular way to update the translation memory?
Is there any visibility on project’s level of completion that shows how translators are progressing?
Why is my namespace suddenly a flat json?
How to change the publish format?
Why does my namespace contain an array with a lot of null items?
Why is the pricing so complicated?
How to change credit card or billing information or download the invoices?
How to import translations from a file?
How to manually publish a specific version?
How to delete or rename a namespace?
Why is there such a high download amount?
Where do I find the namespace backups?
How can a segment/key be copied/moved or renamed?
Why a new namespace is created, when I upload a translation file?
I want to use the locize CDN, but would like to have a fallback that uses local/bundled translations
Is it possible to integrate multiple projects in the same app/website?
Why do I see strange new keys marked as ONE, FEW, MANY, OTHERS?
Powered By GitBook
Is locize only for developers and translators or is project management within the process too?
We agree on the focus of locize is translation of software / applications / websites / etc. Project management plays a big role in the process of getting translations ready for the upcoming release. We would more say it lets everyone focus on their job, i.e. developers in writing code instead of merging translation files, while translators can focus on the translation job.

How to handle

What a project manager expects from being used to document translation, is uploading a document (word, eps, pdf whatever) and to be able to translate that. Based on the different focus of locize you create a namespace which is our term for a technical set of translations. On that namespace you can start importing translations using technical formats (json, po, yaml, xliff, xml, …). But developers will instrument their code so new segments will be added automatically by using the API or our i18n framework. So there will be a constant flow of new segments during development and you can start immediately with the translations. So in best case developers will only login to locize to fix typos in initial source language. From there the translation / terminology responsible (PM) will pick up and check consistency using the built in translation memory. After that he or she will ping the translators for translation / or order via included agencies / or export new segments and sent them for translation to their partners - import again what comes back from them.
Previous
Why do I get “The passed json is nested too deeply.” when consuming the API?
Next
What is the regular way to update the translation memory?
Last modified 1yr ago
Copy link