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

Intl #56

Open
jagu-sayan opened this issue Sep 29, 2021 · 2 comments
Open

Intl #56

jagu-sayan opened this issue Sep 29, 2021 · 2 comments

Comments

@jagu-sayan
Copy link

Hello @treyhuffine ,

Great project 🔥

It is possible to support multiple languages ? (In API and UI)

Good luck :)

@treyhuffine
Copy link
Member

@jagu-sayan I would love to do this. I need to scope out the effort of it. I do plan to open source a large chunk of the codebase at some point, so this may be a feature better suited for that once there are people who have more experience with it.

What is the typical way to handle it for an API? My initial thought is that you would pass a query string for the desired locale, and it will return either a resume or data formatted/translated appropriately.

@florian0410
Copy link

Maybe you could inspire from the way it is done in Linkedin. It sounds like they use locale object type.

https://docs.microsoft.com/en-us/linkedin/shared/references/v2/standardized-data/languages

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

3 participants