Retrieve context, comments and reference via translate directive#102
Retrieve context, comments and reference via translate directive#102felixpis wants to merge 1 commit into
Conversation
Tests added and fixed
|
Why this is not merged yet?? 😢 |
|
@felixpis just a suggestion, I've added the pipe and function as well for the extraction (later I've noticed that the pipe will need some work), if you want to include this base :) picheli20@a3e1987 |
|
Nice @picheli20, however there are some failing tests now ( |
|
Also when the same string is used multiple times, only one path is registered in the |
|
@picheli20 Apologies if this is an inappropriate place to ask, but would be great if you could clarify the following. Let's say that I use the pipe: How can I pass along/express context and comments there? @felixpis made it clear how it works in the HTML tags, e.g.
|
|
@felixpis do you think you could release this separately on NPM? It doesn't look like it's going to get merged anytime soon |
|
still no merge, please do something! @felixpis, I've noticed that all the comments are being removed upon .po update. For instance my config is |
|
You can use forked version with added context and comment support. This version adds file path to the item in .po file also. https://www.npmjs.com/package/@shavenzov/ngx-translate-extract |
|
Hello, any reason why this is not merged yet? Any workarounds available? |
Now in html we can write
<span translate translate-context="VERB" translate-comment="This is a title one">Title</span>And then in generated .pot file:
# This is a title one#: example/example.htmlmsgctxt "VERB"msgid "Title"msgstr ""#37