Jump to content

Replacing the HTML entity by the actual Unicode character

"which are not HTML-encoded, and why just then the opening brace and not the closing brace???"

If you want to write <var> for example, you only need to escape the first bracket (&lt;var>).

Thibaut (talk)18:52, 16 February 2022
Edited by author.
Last edit: 19:37, 16 February 2022

Herr Professor, this message is not parsed by MediaWiki as wikitext.

In HTML, there's never the need to HTML-encode braces, only &amp; or &lt;, and sometimes as well &gt; or &quot; in some HTML nodes (like attribute values). So don't explain to me what I know and that is not the topic.

Your revert comments just said "there must be some reason", so you clearly say that you don't have a suitable answer to explain this caveat: you don't know !

The original message in English as it appears in the Translate UI, along with instructions asking to not change the "var" contents; now it is clearly different in the translated French, and contradicts the doc.

TWN displays unencoded plain braces in its Translate/Review interface for the original English (using the MediaWiki editor is not supported for many messages, and not for messages that are not using the MediaWiki syntax, it will bring false displays in that case, and this is the case here).

And as I replied to you, it's not the "community" that can solve this problem, only developers of the Mediawiki API, or developers of TWN. And they must clarify what is really expected here. Otherwise you will pass your time to change edits/reviews made by any one else, in every language, still without knowing why you do that.

Note also that TWN does NOT display the last edit comment of the messages we are editing/reviewing. So once you revert it, the message is to review again, and any one can later revert you againg without being aware (or remembering) that there's some reason for that: there's also nothing about it in the "/qqq" doc. So your own action has no long term effect. It's no productful to threat other people that can't even kwno what was discussed somewhere else (and not even hinted by the Translate UI with the data that it already maintains or generated itself). Any translator in this site can fall in this trap, at any time, don't accuse someone with bad intents when it is not their fault and the reason is technical (and unexplained anywhere).

I did not insist, but YOU only insisted to use HTML encoding which is absent from the source English, and you are contradicting the existing "/qqq" doc by your own insistance. You cannot solve it without hearing something from Mediawiki API developers (in Phabricator).

Note: I have not attacked you, you were the first one to use the term "insist" here, while first hiding the polite message I had sent to you in your talk page. Instead of replying there, you created this thread here. Please don't mix the order of events.

Verdy p (talk)18:58, 16 February 2022

"YOU only insisted to use HTML encoding which is absent from the source English, and you are contradicting the existing "/qqq" doc by your own insistance."

There’s clearly a HTML entity in the original English message, now please stop with the personal attacks and walls of text and let the TWN admins respond on what we should do when we encounter HTML entities within var or code tags in original English messages (not only these two messages), thanks.

Thibaut (talk)19:12, 16 February 2022