I recently added [[ https://translatewiki.net/wiki/Wikimedia:Convenient-discussions-toc-commentcount-new-full/ja | a Japanese translation ]] of [[ https://translatewiki.net/wiki/Wikimedia:Convenient-discussions-toc-commentcount-new-full/en | convenient-discussions-toc-commentcount-new-full ]] (`$1 comments +$2 new`), but there's an issue with the display of the message.
As the doc says, the `A +B` notation isn't a summand, so I translated the message into a Japanese equivalent of `$1 comments >$2 new`, with the comparison operator of `>`. The problem is, this operator is displayed as the HTML entity of `>` below section headings, although it is correctly displayed in the TOC. I also tried enclosing the operator with `<nowiki></nowiki>` and then the reverse happened; I mean the operator is correctly displayed below section headings but in the TOC as `$1 comments <nowiki>></nowiki>$2 new`.
I guess there's some parsing issue (possibly not with CD but with `mw.messages`).
Could you have a look? Thanks.
**Update:**
Sorry I confused some of the interface messages of CD. It appears that the message regulating the links below section headings is [[ https://translatewiki.net/wiki/Wikimedia:Convenient-discussions-section-metadata-commentcount-new/ja | convenient-discussions-section-metadata-commentcount-new ]], not `convenient-discussions-toc-commentcount-new-full`. I just edited the right one and here's more accurate info:
| name | message | display
| ----- | ----- | -----
| convenient-discussions-section-metadata-commentcount-new | $1 comments >$2 new | $1 comments >$2 new
| | $1 comments <nowiki>></nowiki>$2 new | $1 comments >$2 new
| convenient-discussions-toc-commentcount-new-full | $1 comments <nowiki>></nowiki>$2 new | $1 comments <nowiki>></nowiki>$2 new
| | $1 comments >$2 new | $1 comments >$2 new
The first ones for each message are potentially problematic (and it's quite confusing that `nowiki` behaves in an inconsistent manner).
I have set the second ones as Japanese translations so on the surface level, there isn't a display issue at the moment. But if there indeed is a parsing issue, please check it out. Otherwise, this task can be closed.