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

Translation for multiple languages #35

Open
lusu007 opened this issue Jan 16, 2021 · 1 comment
Open

Translation for multiple languages #35

lusu007 opened this issue Jan 16, 2021 · 1 comment
Labels
priority: low The referenced issue/pr has a medium priority. scope: backend The referenced issue/pr is about the backend package scope: frontend The referenced issue/pr is about the frontend package type: feature The referenced issue/pr is about a feature.
Milestone

Comments

@lusu007
Copy link
Contributor

lusu007 commented Jan 16, 2021

  • Frontend translation for multiple languages
@lusu007 lusu007 added priority: low The referenced issue/pr has a medium priority. scope: backend The referenced issue/pr is about the backend package scope: frontend The referenced issue/pr is about the frontend package type: feature The referenced issue/pr is about a feature. labels Jan 16, 2021
@Keimeno
Copy link
Contributor

Keimeno commented Jan 17, 2021

I think a backend solution would be better suited for our use case since the application is rendered in the backend. If we add a frontend implementation the user will see the default text for a moment.

Possible solutions for a backend solution include setting a locale slug, to determine the locale. This would look like the following: /en/schematics.

Another solution would be to store the locale as a cookie.

@lusu007 lusu007 added this to the v1.2.0 milestone Jan 17, 2021
@lusu007 lusu007 changed the title Frontend translation for multiple languages Translation for multiple languages Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The referenced issue/pr has a medium priority. scope: backend The referenced issue/pr is about the backend package scope: frontend The referenced issue/pr is about the frontend package type: feature The referenced issue/pr is about a feature.
Projects
None yet
Development

No branches or pull requests

2 participants