Describe the feature
Ensure Kival's frontend works correctly with non-English and right-to-left content, without requiring Kival to provide a complete set of translated interface strings.
User-authored content should render and edit correctly across writing systems, including mixed LTR/RTL content. The application layout should avoid assumptions that make the UI unusable when displayed in RTL direction.
The frontend should also be structured so interface strings can be localized in the future without requiring a major redesign.
Areas to cover include object titles and bodies, comments, search results, navigation, forms, the editor, and other places where user-authored text is displayed.
Additional context
English can remain the only bundled interface language initially.
The goal is to make Kival usable internationally and establish the technical foundations for future community or maintained translations, rather than requiring translations to be produced as part of this issue.
Describe the feature
Ensure Kival's frontend works correctly with non-English and right-to-left content, without requiring Kival to provide a complete set of translated interface strings.
User-authored content should render and edit correctly across writing systems, including mixed LTR/RTL content. The application layout should avoid assumptions that make the UI unusable when displayed in RTL direction.
The frontend should also be structured so interface strings can be localized in the future without requiring a major redesign.
Areas to cover include object titles and bodies, comments, search results, navigation, forms, the editor, and other places where user-authored text is displayed.
Additional context
English can remain the only bundled interface language initially.
The goal is to make Kival usable internationally and establish the technical foundations for future community or maintained translations, rather than requiring translations to be produced as part of this issue.