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
Strings directly defined in walkthroughs can be localised with the usual %walkthroughs.mykey% mechanism.
However, walkthroughs depend heavily on references to resources like images and Markdown documents.
"walkthroughs.howToPrint.title": "Premiers pas avec l’impression",
"walkthroughs.howToPrint.description": "Découvrez l’impression dans l’éditeur pour le code source et la documentation.",
"walkthroughs.steps.printEditorActive.title": "Imprimer l’intégralité du contenu de l’éditeur actif",
"walkthroughs.steps.printEditorActive.media": "assets/print-entier-content-editeur-actif.fr.md",
As you can see in the above excerpt from a package.nls.fr.json, the path to walkthroughs.steps.printEditorActive.media was inappropriately localised.
After some discussion on the linked issue, our tentative proposal is
Define a token {locale}
Path strings requiring this kind of localisation are marked by the presence of {locale}
Localise them by replacing the token with the locale code for each generated file
This approach makes no assumptions about the structure of the resource path; the locale might name a directory, or it might be part of the filename. It does require that resource filenames for the default language have literal {locale} in the name or path. The below examples are in the context of contributed settings in package.json
For context see microsoft/vscode-l10n#180
Strings directly defined in walkthroughs can be localised with the usual
%walkthroughs.mykey%
mechanism.However, walkthroughs depend heavily on references to resources like images and Markdown documents.
As you can see in the above excerpt from a
package.nls.fr.json
, the path towalkthroughs.steps.printEditorActive.media
was inappropriately localised.After some discussion on the linked issue, our tentative proposal is
{locale}
{locale}
This approach makes no assumptions about the structure of the resource path; the locale might name a directory, or it might be part of the filename. It does require that resource filenames for the default language have literal
{locale}
in the name or path. The below examples are in the context of contributed settings inpackage.json
or
This should extend to the properties of object values.
The text was updated successfully, but these errors were encountered: