Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

[WORK IN PROGRESS]

Introduction

What was the challenge?

Supporting multiple text directions, specifically RTL and LTR, presented a challenge because most modern web applications are designed with LTR layouts as the default. This creates a hurdle when expanding the user base to regions where languages like Arabic, Hebrew, and Urdu, which use RTL, are commonly spoken. Without proper support, the UX in these regions becomes inconsistent, not intuitive, and potentially unusable.

Why do we want to support multiple text directions?

The primary reason for supporting both RTL and LTR directions is to provide an inclusive and accessible user experience for all users, regardless of the language they speak or the region they are from. This ensures that the OpenLMIS App can cater to a global audience, improving usability for RTL language speakers. By offering a layout that automatically adjusts based on the language, we can provide a more intuitive, user-friendly interface, contributing to better adoption and engagement in international contexts.

Overview

What was the idea behind the RTL Support?

What do you need to do to enable RTL Support for a specific language?

How does the App automatically adjust layouts based on language?

Documentation

Guidelines

  • No labels