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
In the use cases of ours. We are expanding our i18n to around 50+ languages. Some of the UI strings for i18n are very short, such as button labels (e.g. "Go", "Next", etc, very short and can be interpreted in many ways). We will need to provide some addition context for the translators to understand what the UI strings means. I check the vue-i18n and it seems it only has key-value format. Does it provide anyway to give additional explanatory descriptions? I know we can provide in comments. But comments in both json or yml are not standardized and normally not supported in tooling for reading. We need to send our translation requests to other 3rd-party translation tools so it's better that the input source file of vue-i18n allow official way to specify description.
Such additional information can also include author of each string / unique identifying Id / timestamps etc. Examples are
Until vue-i18n , we might use the .vscode/i18n-ally-reviews.yml which contains description for i18n strings. We are happy that an organization intlify will support vue-i18n from now on and I wonder if such metadata will be standardized and included in future roadmaps
The text was updated successfully, but these errors were encountered:
Hi authors and new authors of
vue-i18n
In the use cases of ours. We are expanding our i18n to around 50+ languages. Some of the UI strings for i18n are very short, such as button labels (e.g. "Go", "Next", etc, very short and can be interpreted in many ways). We will need to provide some addition context for the translators to understand what the UI strings means. I check the vue-i18n and it seems it only has key-value format. Does it provide anyway to give additional explanatory descriptions? I know we can provide in comments. But comments in both
json
oryml
are not standardized and normally not supported in tooling for reading. We need to send our translation requests to other 3rd-party translation tools so it's better that the input source file of vue-i18n allow official way to specify description.Such additional information can also include author of each string / unique identifying Id / timestamps etc. Examples are
Until vue-i18n , we might use the
.vscode/i18n-ally-reviews.yml
which containsdescription
for i18n strings. We are happy that an organizationintlify
will support vue-i18n from now on and I wonder if such metadata will be standardized and included in future roadmapsThe text was updated successfully, but these errors were encountered: