-
AuthorPosts
-
October 12, 2012 at 2:16 pm #181391
Hello,
I’m testing our new website http://www.tservice.nl
The apearance of the text differs with the browsers. BUT, this does not happen with all the pages!
See what mean:Who can give me a clue why this is happing.
rgs. Coen
Stork11 FriendStork11
- Join date:
- March 2011
- Posts:
- 2273
- Downloads:
- 0
- Uploads:
- 142
- Thanks:
- 55
- Thanked:
- 431 times in 393 posts
October 15, 2012 at 6:57 am #470055<em>@tservice 342108 wrote:</em><blockquote>Hello,
I’m testing our new website http://www.tservice.nl
The apearance of the text differs with the browsers. BUT, this does not happen with all the pages!
See what mean:Who can give me a clue why this is happing.
rgs. Coen</blockquote>
Hello tservice,Maybe you used font that doesn’t exist on your computer. I checked on my computer with 3 browsers. None of them can display correctly. Please check my screenshots for:
FirefoxChrome
Safari
Regards.
- October 18, 2012 at 9:07 am #470428
Hi Stork,
Thanks, you made me think, but the problem is not solved.
I’m not a wizkid, so my aproach is basic.
This template goes to google and askes for a font: in template.css you will find: @import url(http://fonts.googleapis.com/css?family=Questrial); So to my logic, the computer knows the the font.What did I do sofar, based on your idea I overruled the google API setting (@import url(http://fonts.googleapis.com/css?family=Questrial); I have set the global font to Arial.
The problem does not go away.
(Than I should mention that the cache is making me crazy, showing pages based on old cache info. Even firefox private navigation uses a little cache)
Every bit help is more than appreciated.
Coen
October 18, 2012 at 10:05 am #470434Hi,
This is what http://validator.w3.org tells me:
Warning Character Encoding mismatch!
The character encoding specified in the HTTP header (iso-8859-1) is different from the value in the <meta> element (utf-8). I will use the value from the HTTP header (iso-8859-1) for this validation.
–//–
If I look in the html of our website it says: <meta content=”text/html; charset=utf-8″ http-equiv=”content-type”>
–//–
Now is the question: how to solve this????
rgs. Coen
Stork11 FriendStork11
- Join date:
- March 2011
- Posts:
- 2273
- Downloads:
- 0
- Uploads:
- 142
- Thanks:
- 55
- Thanked:
- 431 times in 393 posts
October 23, 2012 at 10:03 am #470876Hello tservice,
Did you resolve encoding mismatch problem? I went to validator.w3.org and didn’t see “Warning Character Encoding mismatch” error.
Regards.
AuthorPostsViewing 5 posts - 1 through 5 (of 5 total)This topic contains 5 replies, has 2 voices, and was last updated by Stork11 12 years, 1 month ago.
We moved to new unified forum. Please post all new support queries in our New Forum
Jump to forum