feat(i18n): es-419 cv translation support and separating some base strings for idiomatic context
#1505
Conversation
|
|
✅ Deploy Preview for elk-docs canceled.
|
✅ Deploy Preview for elk-zone ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
mrcego
changed the title
es-419 cv translation supportes-419 cv translation support and separating some base strings for idiomatic context
.vscode/settings.json
Outdated
| @@ -22,7 +22,7 @@ | |||
| ], | |||
| "i18n-ally.preferredDelimiter": "_", | |||
| "i18n-ally.sortKeys": true, | |||
| "i18n-ally.sourceLanguage": "en-US", | |||
| "i18n-ally.sourceLanguage": "es-419", | |||
There was a problem hiding this comment.
Should I add this file to gitignore?
There was a problem hiding this comment.
@userquin do you know what is best practice here?
There was a problem hiding this comment.
I don't use VSCode, I don't add IntelliJ stuff to my GIT, I think it should be excluded
There was a problem hiding this comment.
I reverted it, and I will keep it untouched until Core team decides how to proceed for this.
| }, | ||
| "language": { | ||
| "display_language": "Idioma en pantalla", | ||
| "translations": { |
There was a problem hiding this comment.
translations entry should be included in base es file
There was a problem hiding this comment.
It is included, actually
There was a problem hiding this comment.
on main, it is missing from es file
|
@mrcego César, remember to send new entries to i18n channel 🙏 |
First entries for
es-419country variant support.Will create PR as draft until some discussion.There are some work separating entries from base locales to CV for idiomatic contextualization.
cc @patak-dev @alvarosabu for LATAM translations discussion
cc @userquin for correcting i18n idiomatic use