Forum Moderators: martinibuster

Message Too Old, No Replies

UTF-8 and UTF-16 issues?

Advise from Adsense support

         

Rastarr

2:06 pm on Oct 27, 2006 (gmt 0)

10+ Year Member



Hi,

I'm having rather a lot of difficulty in getting my Adsense ads served as English for some reason. I don't publish anything other than English content and I contacted Adsense support and this is what they replied:

<snip>

To be honest, I haven't a clue on how to go about fixing this problem and would ask this group for any ideas they might suggest. The site is based on the Joomla platform and I don't see anywhere that UTF settings are configurable.

It's currently set to show non-Google ads from another URL which is a blank HTML file. Site is question is <snip>
Any ideas would certainly be appreciated.
Cheers
Martin

[edited by: engine at 2:18 pm (utc) on Oct. 27, 2006]
[edit reason] No e-mails See TOS [webmasterworld.com] [/edit]

sailorjwd

2:12 pm on Oct 27, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Interesting problem.

Knock Knock...

Hello..

We are the url police. You are under arrest for putting a url in your message text. Come with us!

ps.. I think I have a heavy metal problem.. (music that is).

encyclo

2:18 pm on Oct 27, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



This is a coding problem, usually caused by a mess-up when editing files. Do you use Notepad?

A search that might help you:

  • Search WebmasterWorld for "byte-order mark" (BOM) [google.com]

    Also use the Live HTTP headers extension in Firefox to see what the server is sending as the charset. If the page is identified as UTF-16 it is usually because of a rogue BOM.

  • Rastarr

    11:37 pm on Oct 27, 2006 (gmt 0)

    10+ Year Member



    Oops, apologies for the TOS error with the URL in the post.

    I'll check out the Firefox extension and the byte-order mark stuff and see how I progress.

    UserFriendly

    1:49 am on Oct 28, 2006 (gmt 0)

    10+ Year Member



    Does anyone know if Saxon leaves a BOM on the pages it produces with XSLT? If it does, that would explain why I was getting Spanish ads on my photo pages (generated from an XML catalogue).