Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss i18n options #473

Open
acka47 opened this issue Dec 16, 2021 · 0 comments
Open

Discuss i18n options #473

acka47 opened this issue Dec 16, 2021 · 0 comments

Comments

@acka47
Copy link
Contributor

acka47 commented Dec 16, 2021

From #432 (comment):

i18n: Adding the name property for persons and projects/products, I used two different approaches: language maps for products/projects as we want to list German and English names and just a key for persons as we do not intent to add a person's name in different languages. However, this would result in two different schemas for the same property. One way towards a common approach would be to use different files per language (and indicating the file's @language in the context) instead of one file per entry with language maps. Then we wouldn't have to use language maps at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant