I’ve looked at Transifex which says 88% of Bahmni is translated into French. We’ve just recently installed it and have clicked through the UI and I would say that less than 50% is translated. I’d love for someone from Thoughtworks to weigh in on this? Are we missing something?
@mohant have we pushed the latest translation key files to transifex?
Also @daniel1 do remember the above is only for the labels, and not for metadata (concepts). Are you reflecting on such metadata as well?
@angshuonline Thanks, yes - it’s the labels in the UI I’m referring to. For metadata we’re leveraging CIEL via OCL.
Does this cover the UI labels? That’s where I’m seeing much less than 88% (as per Transifex) done? How would we then pull the latest data in to our environment and would it overwrite any we might have fixed manually? (which is fine if so!) @mohant @angshuonline
I’m concerned about using Bahmni going forward, given there’s been no update / engagement here.
I believe we may have stumbled across some errors in some of the data that was already translated, for example my understanding is that code should never be translated e.g., html code would be the same in the system regardless of whether it is English or French. In the UI translations I can see the same principle has been applied to variables {{ }}, but have found (at least) one instance where the variable name has been translated to French, rather than left in the English variable coded name.
Hey @daniel1,
Thanks for bringing this to our attention. To clarify the current status: while 88% of the labels are translated, this doesn’t mean they are immediately available in the application.
Our process requires that all translated keys be reviewed and approved by native speakers before they are pulled into the codebase. Since our core team are not native French speakers, we rely on community support for this validation.
This is a perfect opportunity for community contributors to make a direct impact. We would greatly appreciate it if you or your team could assist us in reviewing these translations.
Relevant Tracking Links:
If you’re interested in helping us improve Bahmni’s French localization, you can find a step-by-step guide on becoming a translator or reviewer here: 
Getting Started as a Translator for Bahmni on Transifex
Looking forward to collaborating with you on this!
Thanks @rahu1ramesh, that’s a useful differentiation to understand.
For our French speakers, they’re not French but another country that speaks French and as such their confidence in English is even lower, so I feel they may not want to / have much to feed back.
Is it worth focusing efforts on some of the issues I identified, such as some variables being translated where they shouldn’t? I also came across a few items where there was a French word, but no English translation.
Absolutely @daniel1, we are happy to address those issues. To help us investigate effectively, could you provide a more detailed report of the bugs you’ve identified? Ideally, this would include:
- Screenshots of the behavior.
- Steps to reproduce the issue.
Once we have this information, our team will review it and get back to you with the necessary fixes.
If you or your team are interested in contributing directly, we would be more than happy to review a Pull Request against our repositories. While this is entirely optional, community contributions like yours go a long way in strengthening the platform.
A Note on Our Technology Roadmap
I also want to share some context regarding our current development focus. We are phasedly migrating away from our legacy AngularJS codebase toward a modern React-based UI. You can read more about it here.
Moving forward:
- Support and updates for the legacy AngularJS UI will be minimal.
- We strongly encourage both new and existing users to transition to our modern React apps for the best experience and long-term support.
Thank you again for your time, your patience, and your commitment to improving Bahmni. We look forward to hearing from you.
Here is one example:
I haven’t dug through the UI yet to see where it is because I’m just not at that stage yet. Our implementation partner provided us with data extracts that show the English + match French terms, which they pulled from Transifex and we’re using the latest CIEL extract (not the 3 year old one that the default Bahmni install has).
In relation to ensuring we are using the modern React apps, we’ve installed the latest Docker container etc. that you offer, so does that mean it’s already in place? Or is there a manual in place upgrade that needs to be applied?
The phased migration is currently under development, and we have not yet made a formal public release. We regularly showcase our latest progress during our weekly PAT calls. I encourage you to join these sessions to see the new UI in action. We will certainly update the entire community as soon as we are ready for a production-grade release.
In the meantime, please feel free to provide any additional details regarding missing or incorrect translations. We will investigate those specifically and get back to you with an update.
Thank you again for your engagement and for helping us improve Bahmni!
OK, so just to be clear then - we can’t actually transition to the modern React apps, as they’re not available. For us at this stage, we need to have the EMR implemented “yesterday”, so we’ll continue to focus on the version we’re already using that is your latest offering pre-React.