Chrome displaying symbols weirdly? 
Autor: Melissa K.
Visitado 72,
Seguidores 1,
Compartilhado 0
Hi there,
I'm having a bit of an issue I found recently. In my client's website there are symbols, such as an apostrophe, that show up as:

[It's supposed to be don't].
A few notes:
- it doesn't happen in all instances of the font [Gotham Book].
- happens with other symbols such as the degrees symbol, and the registered symbol
- only happens in Chrome [I checked Firefox and it shows fine]
- started happening since 1 or 2 updates ago?
- I checked in two different computers, same issue: always Chrome, not Firefox.
Any ideas?
Thank you!
Publicado em

I once asked the AI and got this answer, see
-----
1. Character set error (the web server "lies")
The most common problem: The website uses “smart” or typographic apostrophes (curly quotes), but signals the wrong character set to the browser (e.g. ISO-8859-1 instead of UTF-8).
Why only in Chrome? Firefox is extremely tolerant and has a very aggressive, automatic detection of character set errors. It corrects the error independently in the background. Chrome, on the other hand, strictly adheres to what the web server reports to it.
The result: Instead of the apostrophe, Chrome shows cryptic characters such as ’, â or a hash with a question mark.
Solution: Since Chrome removed the manual character set switching some time ago, a browser extension like Set Character Encoding in the Chrome Web Store helps here to force the page to UTF-8 as a test.
-----
Autor
Thanks for the insight Daniel.
However, my client's concern is what happens when their customers try to view the website. We have no way of asking them "hey download this extension to view the website properly". Is there a way for the program to resolve this?
Thank you.
Normally WebSite X5 is set to UTF-8 by default.
Maybe take a look at the source code of the website to see what is displayed there.
----- My demo shop -----
Test with the preview in Chrome, see
-----
I asked the AI whether the web server could change something despite the UTF-8 setting on the website, here is the answer
-----
Why is the server providing the wrong format?
The fact that the server delivers ISO-8859-1 even though your file is saved and declared as UTF-8 is usually due to one of these server-side settings:
Apache web server: The AddDefaultCharset ISO-8859-1 directive is set in the server configuration or in an .htaccess file. This forces the server to set the character set in the HTTP header for all HTML files.
PHP configuration: If your website uses dynamic content, a default character set may be defined in php.ini (e.g. default_charset = "iso-8859-1") that overrides the HTML header.
-----
Perhaps the Incomedia employees or other users can also comment on this, as I have no experience with this error myself.
Autor
Mine also shows the charset as UTF-8 in the source code.
It does seem like, whatever the problem is, it's baked into it, because this is how it looks in the source code:
It shows fine in the program and again, wasn't a problem a few versions ago.
I use WebSite X5 in the current version Pro 2026.2.3 and don't see any errors in Chrome, not even in the source code, see link
My test page >> https://findelinks.de/123test-aufklappmenue-2/test-123.html
Autor
Right, I understand you don't have that issue. Until recently, I didn't have that issue either. My question is why this is happening to my client's site now, and how I can get it resolved through the program.
If the customer's website cannot be mentioned here, then wait for the Incomedia employees, who are online during office hours in Italy.
Incomedia employees could test the project or website internally to find the cause of the problem.