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
{{ message }}
This repository was archived by the owner on Apr 19, 2024. It is now read-only.
This is a request to provide support for specifying a comment/hint in package.nls.json, for translators
We'd like to start using the markdownDescription field for some of our extension settings. We'd like to be able to provide a comment/hint to translators that these strings (in package.nls.json) contain markdown, so translators are aware of it and avoid removing or corrupting the markdown syntax.
This is a request to provide support for specifying a comment/hint in
package.nls.json, for translatorsWe'd like to start using the
markdownDescriptionfield for some of our extension settings. We'd like to be able to provide a comment/hint to translators that these strings (inpackage.nls.json) contain markdown, so translators are aware of it and avoid removing or corrupting the markdown syntax.I don't see any comment/hint field handled for
package.nls.json, in the implementation ofcreateXlfFiles(). I see that it supports specifying an object with amessagefield instead of a string field. But, I don't see anywhere that it also handles a comment/hint field in that object.