[Pro] Apostrophe/quotes shenanigans

The web site text encoding is set to UTF-8 as recommended, yet when I transfer the site from the test server:

http://www.communique-test.co.uk/JEA/residential-property-surveys.html

the apostrophe near the end of the first line of body copy on this page becomes re-encoded as ’ ’ ’ on the live server, as per the link below. I suspect the live server (a different hosting company from the test server), is screwing things up, but have no idea how to fix things if this is the case.

Any ideas on how to solve this would be greatly appreciated. Does someone need to switch the encoding on the live server?

Thanks,

Ian

http://www.johnenglish.co.uk/residential-property-surveys.html


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Did you do something to fix this already? I’m not seeing that issue here.

Walter

On Dec 20, 2013, at 7:09 AM, Ian Halstead wrote:

The web site text encoding is set to UTF-8 as recommended, yet when I transfer the site from the test server:

http://www.communique-test.co.uk/JEA/residential-property-surveys.html

the apostrophe near the end of the first line of body copy on this page becomes re-encoded as ’ ’ ’ on the live server, as per the link below. I suspect the live server (a different hosting company from the test server), is screwing things up, but have no idea how to fix things if this is the case.

Any ideas on how to solve this would be greatly appreciated. Does someone need to switch the encoding on the live server?

Thanks,

Ian

http://www.johnenglish.co.uk/residential-property-surveys.html


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Interesting…

Definitely get the problem here. I’ll make local enquiries about what people see/don’t see and report back. Thanks Walt.

Safari on my local Mac is set up for viewing websites with the default encoding of UTF-8 by the way.

Cheers,

Ian


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

What language/keyboard is your Mac set to? What version of the OS/Safari?

Walter

On Dec 20, 2013, at 9:21 AM, Ian Halstead wrote:

Interesting…

Definitely get the problem here. I’ll make local enquiries about what people see/don’t see and report back. Thanks Walt.

Safari on my local Mac is set up for viewing websites with the default encoding of UTF-8 by the way.

Cheers,

Ian


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hi Walt — British English for both keyboard and language.

Safari is at 7.0.1, and the OS is 10.9.1

Ian


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Okay, I am looking at it in 10.7.latest and Safari 6.1.latest.

Walter

On Dec 20, 2013, at 10:12 AM, Ian Halstead wrote:

Hi Walt — British English for both keyboard and language.

Safari is at 7.0.1, and the OS is 10.9.1

Ian


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Same results on iPad2, running iOS 7.0.4

Ian


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Just checked it on Mavericks with all the latest updates. Question – is your Safari up to date on your Mavericks machine? There was an update early this week.

I am seeing the correct character, and more to the point, the correct meta tag and raw source code. It is still possible for your host to be sending the wrong charset header, but the meta tag is supposed to disambiguate that.

Walter

On Dec 20, 2013, at 10:29 AM, Ian Halstead wrote:

Same results on iPad2, running iOS 7.0.4

Ian


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I think we have a bug somewhere. After swapping the text encoding in Safari (View menu > Text encoding) from the ‘Default’ setting to a completely random setting (Arabic Windows) and then to UTF-8, I now see the correct display.

The default setting should have picked up the fact that the Safari Preferences were set to UTF-8. Setting the View menu back to ‘Default’ retains the correct display.

Quick note to Apple I think.

Thanks for the push to accidentally solve this Walt — much appreciated.

Ian


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

More on this…

After extensive questioning of friends and acquaintances, it became apparent that some received the correct curly quotes, and some received the wrongly coded ‘junk’ instead.

The server running the website was overriding the page text coding request, probably via an Apache setting. I have overridden this in turn with a command placed in a htaccess file:

AddDefaultCharset Off

This has resulted in the correct display irrespective of browser/platform. So far anyway!


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options