Lokalise is a translation management system, which is designed to make the process of localization faster and easier. Our platform reduces manual work and routine tasks that appear while translating web and mobile apps, games, and other software.
With Lokalise you can: ✓ Translate your localization files (.xml, .strings, .json, .xliff, etc). ✓ Collaborate and manage all your software localization projects in one platform. ✓ Integrate translation into the development and deployment process. ✓ Set up automated workflows via API, use webhooks or integrate with other services (GitHub, Slack, JIRA, Sketch, etc). ✓ Add screenshots for automatic recognition and matching with the text strings in your projects. ✓ Upload Sketch artboards to Lokalise and allow translators to work before development starts. ✓ Preview in real-time how the translations will look like in your web or mobile app (iOS and Android SDK). ✓ Order professional translations from Lokalise translators or use machine translation.
I'm pretty sure, you'll find companies like this one which provide a nice GUI for helping with l10n or this one which offers translation services or this page that offers to convert between different formats, one of which probably has a nice GUI tool. Found them by 20 secs of googling. Source: 11 months ago
Localise has no problem reading the json files or export to json, we recently started using it in collaboration with external translators. Source: 12 months ago
Actually I don't have "my" app. But in our app we use https://lokalise.com/ to localize it even to Norwegian. Our team is not the most expensive company in the world btw. And we don't have 1B+ users all over the world. Source: about 1 year ago
Internationalization (i18n) pain for a documentation project is a process problem, not a feature gap. Documentation frameworks are not meant to translate your developer docs for you into the language of your choice. Some frameworks might offer i18n support, like the Crowdin support in Docusauraus v2. With Jekyll, you have to pick a theme like this one. I doubt if the reST or adoc frameworks would differ much from... - Source: dev.to / over 1 year ago
I've been thinking about building a micro saas very similar to this after having so many issues coordinating the localization of several products I manage. The only robust options in the market are incredibly expensive (for example https://lokalise.com/). Source: over 1 year ago
For the app I work at the moment we use https://lokalise.com/. We add translation strings to a SaaS app, and then the translation team translate them. I've written a build tool that downloads the translation JSON files from the API using the CLI, or as part of our CI process. Other teams have tools that download their language packs for different iOS and Android apps. The translations are versioned in Lokalise and... - Source: Hacker News / almost 2 years ago
In favor of typesafe-i18n: - Offers an option for asynchronous loading of locales. It's in the roadmap for i18nifty but as of today it doesn't features it. - It's lighter 1.3Kb vs 22Kb for i18nifty (I could work on reducing the size but it isn't high in my priorities). - Support third party localisation services such as https://locize.com/ https://lokalise.com/ or https://simplelocalize.io/. Source: almost 2 years ago
That's definitely a trade off. Because i18nifty enables to use React components and JS logic we are not compatible with third party translation services like https://locize.com/ https://lokalise.com/ or https://simplelocalize.io/. However, I think it is worth it. It makes life easy for the devs and get cleaner code in exchange for having to pay a bit more to for translation services. That said, if you can get... Source: almost 2 years ago
These guidelines also reference a third-party translation service called Lokalise. We chose Lokalise because it was competitive in terms of pricing, and offered a CI/CD integration so we could automate our translation process. - Source: dev.to / about 2 years ago
I can highly rocommend Lokalise. https://lokalise.com/. Source: over 2 years ago
We use Lokalise as our translation/copy tool. Keys and screenshots of the UI are pushed via Figma. Doing this for new keys is the accountability of the UX designer. Once the UX designer is happy with the suggested content they assign the keys to the copy department. Source: over 2 years ago
Do you know an article comparing Lokalise to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Lokalise. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.