Skip to content

Internationalization support #51

Open
@sprocketc

Description

@sprocketc

We have two main options regarding the library that is going to be used. Both have pros and cons.

  1. Map based. Easier to implement, but creating and editing translation requires handling EDN files. The translations are coupled with the code.
  1. PO based. Decouples translations and code, but requires some additional tooling that scans the codebase to generate PO files.

After making a decision on the translation library, we need to either replace all strings with translatable keys, or modify our pipeline to generate translation files. We need to also add a language switch control to our UI, persist the selection, and try to use the system language to pick the correct language Trying to support another language (Greek) while implementing this, would help us avoid some issues early. We should also investigate adding RTL support.

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions