I wanted to quickly discuss how we want to approach fixing, or not fixing OLMIS-5665 (https://openlmis.atlassian.net/browse/OLMIS-5665)
To summarize the reported bug: on some of the screens (not all) if one uses a translation plug-in (in this case - Google Translate, but the same may be valid for any other as well) the numbers/data that is displayed in our grids may become incorrect. The reason for that is that those plugins modify the HTML markup of the page, what is causing some of our calculations to get lost.
There’s a potential fix for this issue: adding notranslate class to the element that is not meant to be translated. This works fine for Google Translate, but it will likely not solve the problems for other translation plugins. Also, for this change to make sense we would need to go over all our UI screens and add this class to all the cells that contain numeric/calculated values or other stuff that is not meant to be translated.
OpenLMIS currently uses Transifex to support translations, but of course, the content needs to be translated by someone first, which is a downside comparing it to the translation plugins.
I wanted to get your feedback on whether we should invest time to fix the problem with external plugins, likely not all, but at least the most popular Google translate should work as expected. I’d estimate this to be a few days of work at a minimum. On the other hand, we could just state that we don’t support translation plugins and encourage to provide translations via Transifex.
What do you think?