Skip to content
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.

Need a way to provide a comment/hint in package.nls.json #32

Closed
Colengms opened this issue Apr 14, 2021 · 5 comments
Closed

Need a way to provide a comment/hint in package.nls.json #32

Colengms opened this issue Apr 14, 2021 · 5 comments
Labels
feature-request Request for new features or functionality
Milestone

Comments

@Colengms
Copy link

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.

I don't see any comment/hint field handled for package.nls.json, in the implementation of createXlfFiles(). I see that it supports specifying an object with a message field instead of a string field. But, I don't see anywhere that it also handles a comment/hint field in that object.

@dbaeumer dbaeumer added the feature-request Request for new features or functionality label Apr 16, 2021
@dbaeumer
Copy link
Member

Makes sense. PR welcome.

@dbaeumer
Copy link
Member

I published 4.0.0-next.1 which contains support form comments in messages.

@dbaeumer dbaeumer added this to the 4.0.0 milestone May 27, 2021
@tnarik
Copy link

tnarik commented Aug 20, 2021

Will there be a replacement for createXlfFiles() on 4.0.0 as part of removing Transifex support? Or is the removed support related only to import/export?

@dbaeumer
Copy link
Member

Not sure I understand this since createXlfFiles is still there and independent of Transifex.

@tnarik
Copy link

tnarik commented Aug 23, 2021 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants