You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
**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)
The text was updated successfully, but these errors were encountered: