Frans wrote on Feb 6, 2021, 05:29:
I was going to add one more weird observation about the replacement characters, but since last night I'm not getting them anymore during dozens of refreshes in multiple browsers. So perhaps the issue resolved itself just as mysteriously as it popped up...
Wishful thinking... the replacement mark returned for me too (some days ago but I didn't have time for this until now).
The earlier observation is that in a browser's dev tools (F12) in the Network panel, one can view the response headers and body of the GET request for the URL with the problem
. In that response body, the accented e is indeed shown as such in <title> tag and news post header, even when the browser's main window renders it as the replacement character in those spots. But the dev tools renderer may behave differently from the main window in this respect, so I'm not drawing conclusions, it merely contributes to the weirdness of the problem.