Apertium VS Lokalise

This is very cool, looking forward to it! I've been doing the same thing with Spanish Wikipedia articles for a while, using a few lines of Bash + Regex. I was using Apertium for it. https://apertium.org/ It's definitely worse than most ML-based solutions, but it works reliably and fast; you can run it entirely offline. With Spanish translations, the main problem I was facing is lack of vocabulary, so I created - Source: Hacker News / 9 months ago

I used to keep track of the state of machine translation some years back. I think the way you measure the success of an automated translation is edit distance, i.e. How many manual edits you need to make to a translated text before you reach some acceptable state. I suppose it's somewhat subjective, but it is possible to construct a benchmark and allow for multiple correct results. The best resources I knew back... - Source: Hacker News / almost 2 years ago

Apertium is one of them. We make open-source rule-based machine translation systems, and our core tools are in C++. A few of our proposed ideas involve modifying those C++ tools with new features or improvements to existing features. Source: about 3 years ago

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: about 1 year 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