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

Multi lingual support #80

Open
stp-ip opened this issue Mar 15, 2019 · 0 comments
Open

Multi lingual support #80

stp-ip opened this issue Mar 15, 2019 · 0 comments

Comments

@stp-ip
Copy link
Member

stp-ip commented Mar 15, 2019

**Is this a BUG REPORT or FEATURE:
feature

What happened:
We currently don't allow translations of the resume.

What you expected to happen:
Support translation of field.

Anything else we need to know?:
General suggestion to use the meta data section and fallback to the main resume data, if a string isn't translated.
This might need a bit more thinking as it uses the section names as identifiers. They might night be unique (we could enforce this) and might change without the user noticing and breaking their existing translations.

jsonresume/resume-schema#35 (comment)

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

No branches or pull requests

1 participant