Skip to content

Add support for internationalization #38

Open
@mikesparr

Description

@mikesparr

Although most i18n is configured client side, if an application may store different versions of content based on language, we could add a reference implementation of handling language-specific content (likely with fallback to default language: en_US).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions