To release multilingual products, you add localization to your workflow. You should make sure it’s automated so it won’t delay your next release. At Crowdin, we believe that localization should go in parallel with the development process. Meaning that each new text string created or modified by you goes to the translator right away. This way, once you’re ready to deploy your next update, you can simply merge translations into the master or feature branch and hit deploy.
Where to Start?
What are the first steps? How to set up an automated localization workflow?
from DZone.com Feed https://ift.tt/3mYtKfd
No comments:
Post a Comment