Encoding Issue

I noticed an encoding issue in the post Re^4: Useless use of string in return statement. When I dislpayed it for the first time, it showed a double encoded UTF-8 character:

ItĀ’s one

After I voted for the node, though, the encoding issue was gone:

It’s one

I made screenshots of both the versions.

Update: I'm using Firefox 78.9.0esr on Linux.

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

Comment on Encoding Issue Download Code

Replies are listed 'Best First'.
Re: Encoding Issue by talexb (Chancellor) on Apr 13, 2021 at 16:17 UTC
I've been trying to chase a similar issue -- a string that appears to be doubly encoded one moment, magically corrects itself later, as I try to fix the encoding. This UTF-8 stuff can be like chasing smoke. :/ Alex / talexb / Toronto Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.	[reply]
Re: Encoding Issue by Bod (Parson) on Apr 13, 2021 at 15:33 UTC
After I voted for the node, though, the encoding issue was gone Perhaps not attach too much to it going away after voting. I have an internal webpage that has a similar encoding issue that I cannot debug^* because every time I refresh the page, the issue goes away. So any changes I make, I don't know if they have solved the problem or Chrome has decided to display it more legibly. ^* of course I could debug it but it is only me and one other person who looks at the page. The encoding bug doesn't affect the information so it is very low priority and just gets looked at occasionally when I notice it.	[reply]