14

After successfully deleting a tag synonym on https://ru.stackoverflow.com/tags/synonyms, the popup-message shown consists almost entirely of HTML entities.

Found the line in Traducir: https://ru.traducir.win/strings/12445

Tag synonym deleted successfully.

Синоним метки успешно удалён.

enter image description here

Improve this question
9
  • 8
    I would think that by now you speak fluent HTML entities. I'm a bit disappointed that you've not reached that level yet ...
    – rene Mod
    Commented May 11, 2023 at 10:08
  • I don't speak russian or HTML entities, but I wonder if its a bit of translation strangeness
    – Journeyman Geek Mod
    Commented May 11, 2023 at 10:20
  • 1
    @JourneymanGeek or there's a lack of some entity unescaping.
    – aepot
    Commented May 11, 2023 at 10:28
  • 1
    Related issues with encoding of translated strings: Incorrect encoding while removing access for applications, Encoding issue for error message when editing is not possible
    – V2Blast Staff
    Commented May 11, 2023 at 18:05
  • 1
    Eh, is this issue being fixed one-by-one? is there no unified way to handle notifications in the codebase (although from what I've seen client-side, it is likely there is none)? There is a whole list of bug reports, but we still find new places.
    – 0Valt
    Commented May 11, 2023 at 19:15
  • 2
    Possibly related, if not the exact same bug: meta.stackoverflow.com/q/417220/6296561 - they never looked into it and fixed all of them (in spite of it coming from a single change, therefore being trivial to track, but whatever; their time to waste). I'd half assume this might be the exact same bug. Seeing as Russian uses a whole bunch of non-ascii letters, whatever the bug was that caused the HTML encoding in banners might've stuck around until now, because the english variant (and by extension, all the major sites where synonyms occur regularly) does not contain any (1/2)
    – Zoe - Save the data dump
    Commented May 11, 2023 at 19:16
  • 2
    characters that gets HTML encoded. That alone is probably a solid indicator that one commit from over a year ago still has the buggy variant lingering around in the code
    – Zoe - Save the data dump
    Commented May 11, 2023 at 19:17
  • 2
    Other instances of this bug: meta.stackoverflow.com/q/417252/6296561 meta.stackoverflow.com/q/417289/6296561 meta.stackoverflow.com/q/417430/6296561 meta.stackoverflow.com/q/417407/6296561 meta.stackoverflow.com/q/417220/6296561
    – Zoe - Save the data dump
    Commented May 11, 2023 at 19:23
  • 3
    @JourneymanGeek It's not translation problems, see the above. It's also not entity unescaping; the russian characters are (presumably) stored as HTML entities, which itself is fine, but the popup renderer does a second sanitisation step. instead of the text containing &#x421, the popups sanitise the characters further to at least &#x421 (not sure if # is HTML encoded as well, but doesn't matter), at which point, it's rendered as a literal string instead of the Russian character (or other encoded character, including quotes, angle brackets, etc.)
    – Zoe - Save the data dump
    Commented May 11, 2023 at 19:29

0

Reset to default

You must log in to answer this question.