" ... without any possibility of decrypting the files even if the ransom is paid" hence In these situation always ask for 'proof of life' before paying. I learned that watching TV
When the content isn't encoded properly in the database, it converts specials characters to ? or something else. The problem usually happens due to the HTML editors as they have to get the content and allow it to be edited in the comments box.
In that case the easiest way to fix the problem is to use the PHP function (htmlentities) in the original article. That way the special characters are already converted to their html entities before the string is inserted into the forum database.
I also get the ? problem on the accented e on Windows 10 using Chrome in the forum only.
Perhaps the pages need some sort of character set indentifer in their meta tags.
This has been a problem with a few of the forum software platforms used. They have to copy the articles from the home page into the forum software. When the content isn't encoded properly in the database, it converts specials characters to ? or something else. The problem usually happens due to the HTML editors as they have to get the content and allow it to be edited in the comments box.
The format would be retained by manually copy/pasting the article into a new forum thread. The following is copy/pasted from the article and the accented characters work ok:
"Researcher Marc-Etienne M.Léveillé found two different that used the same code"
It may even be better to copy the HTML source from the article page into the plain text part of the editor using the Toggle HTML View button but the article's images use lazy loading (only loads images after you scroll over them) so it won't copy embedded images over, they'd have to be fixed manually. They can be dragged into place from the article. The main article uses htmlentity encoding for special characters, if you copy Léveillé into the following page and hit the button to encode it, it shows how it's stored in the database:
There's most likely an automated button to copy it directly to the forum. The function that does that would have to run it through the same forum process that encodes comments first.
I don't know much about your forum platform but had thought you may be running your own custom forum code (sounds like not). In my apps we store rich comments/narrative text in a SQL datatype that supports unicode characters, then render them back into the final page's content like your main stories likely do. I had figured your forum pages would just retrieve the same exact content rather than copy it into a separate forum database or whatnot, but sounds like that isn't how it works. In any event, hopefully they figure it out.
Looks normal to me. It's a lowercase e with a slanted line over it that the French use. I'd cut and paste it here for you, but you obviously can't see it. Must have something to do with the fonts on your Mac. I have the standard assortment of fonts and the special e rendered fine for me. Good luck.
Comments
In that case the easiest way to fix the problem is to use the PHP function (htmlentities) in the original article. That way the special characters are already converted to their html entities before the string is inserted into the forum database.
Nah, it doesn't have anything to do with typefaces on my client. It's not being rendered in the story itself here in the forums.