Skip to content

Dhivehi localization and RTL #15

Closed

Description

@n4ff4h
  • Every user-facing string is translatable, with en and dv lines via @javaabu/i18n
  • Real Dhivehi translations; uncertain ones are listed for human review
  • Views and components work in RTL (logical utilities only) and free-text inputs support Thaana
  • Tests use Thaana for user-facing behaviour

Activity

  1. added
    next-genNext-gen Javaabu packages
    featurePackage feature from the spec
    on Nov 4, 2026
  2. added a commit that references this issue on Nov 4, 2026
    c2a5fc1
  3. n4ff4h commented on Nov 4, 2026

    @n4ff4h
    CollaboratorAuthor

    Done on next-gen (c2a5fc1).

    • Strings: every user-facing string goes through @javaabu/i18n, with en and dv lines (Use @javaabu/i18n for every string #11).
    • Translations to review: 41 Dhivehi lines were written by the agent rather than taken from javaabu/forms v1's human-written file. They're listed for a native speaker in docs/advanced-usage/dhivehi-and-rtl.md#dhivehi-lines-to-review.
    • RTL: layout uses logical properties only, enforced by an ESLint rule. Side-pointing arrows flip in RTL. Fields with thaana get dir="rtl" lang="dv". Email, URL, phone, password and number inputs stay LTR.
    • Thaana input: with Onu, Onu's own Thaana support handles it. Every other adapter uses the core's thaanaKeyDown, the JTK phonetic layout that Onu also uses. It inserts at the caret and fires onChange.
    • Tests: tests of user-facing behaviour use Thaana text, with the RTL and Thaana cases in src/core/rtl.test.tsx.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featurePackage feature from the specnext-genNext-gen Javaabu packages

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions