Having reviewed the proposal and the current challenges with the manual process for form translations, I’m excited about the potential for a more intuitive, user-friendly approach that empowers non-developers. I’m currently exploring how we might integrate this solution with the existing Form Builder and would love to dive deeper into the implementation details.
At this point, any guidelines or advice would be much appreciated. @nethmi , are there particular frameworks or integration considerations I should focus on?
Looking forward to your thoughts and hopefully collaborating as mentors if selected.
For the interactive translation builder project, should we include support for right-to-left languages (like Arabic), meaning that when a user switches to such a language, the UI adjusts its layout (e.g., text direction, element ordering) accordingly? Or is RTL support considered out of scope for this project? @nethmi@grace@jayasanka@beryl
Yeah i had runned from the openmrs core repo and i understand that our system supports RTL layouts, and typically the overall UI adjusts when the main language changes. However, in the translation builder, the language is switched only within that specific interface. Should we also implement dynamic RTL adjustments in the translation builder—so that when an RTL language is selected (e.g., Arabic), the translation editor itself updates its layout to RTL? Is this RTL behavior part of the project scope?
I don’t know if we can localize the language change to a specific part of the user interface, but basically what should happen is, a user should be able to change the language of a form just to be able to preview only the form in the selected language. Ideally, this would be seperate from the overall language switcher in the navbar. So unless you change the overall language from the navbar, the layout shouldn’t need to change for RTL languages. But if you a user does change the overall language, the layout of the editor should update if its a RTL language. Does that make sense?
That makes sense—so to clarify, you’re saying that the language change within the Translation Builder should only affect the form preview for that specific form, without altering the overall UI layout (e.g., RTL adjustments) unless the user changes the overall language from the navbar. Is that correct?