Second issue is fixed by this
AddDefaultCharset UTF-8 in .htaccess
Does anything turn up in a search for the first issue ?
just adding the
AddDefaultCharset UTF-8 in .htaccess
didn’t solve the problem.
I saw this solution http://wordpress.org/support/3/10648 but when I did it I got:
error 500: Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Sdchruch, change everything back to the way it was before Podz’ suggestion. I’ll try to explain how to fix in this in the next post, but it’s a lot of typing. Just change everything back as I type it.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Ok, so change everything back the way it was before Podz’s suggestion.
Solution:
Go to this post:
http://www.sandiegochurches.org/2004-11/22/the-vertex/
Now, delete the apostrophes and quote marks in the quote and replace them with your own (enter them again). Save the edited post and check your feed again. it should be fine.
Explanation:
FeedValidator gave you this error, “Your feed appears to be encoded as “UTF-8”, but your server is reporting “US-ASCII””. While FeedValidator is the best feed validator, this error is often incorrect. If you get that error, check your feed at http://validator.w3.org/ . The resulting error was:
“Sorry, I am unable to validate this document because on line 142 it contained one or more bytes that I cannot interpret as us-ascii (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.”
I downloaded your feed and checked line 142. Sure enough, curly quotes and apostrophes (it’s almost always quotes and apostrophes, especially if you’re copying from another site). Basically, these characters are not part of UTF-8 encoding. If you delete them and replace them with your own UTF-8 apostrophes and quote marks, your feed will be fine again. If FeedValidator continues to display the error, go to http://validator.w3.org/ to find which line the problem character is on, and repeat the process.
This always happens to me quite often because I do a lot of copying from other sites when I post (yes, I always cite the source).
thanks. I blame Microsoft. (post was done in Word and it added those fancy-pants quotes.)
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Ick. Word is horrible to write posts in, specifically for that reason. I’d recommend using a good text editor, like NotePad.
I had the same problem, fixed the curly quote pasted in from Word (I’ll not do that again). Now, my comment RSS2 feed is declared invalid by the W3C Feed Validator, because “line 2, column 0: XML parsing error: <unknown>:2:0: xml declaration not at start of external entity “
Does this only mean that <?xml version=”1.0″ encoding=”UTF-8″?><!– generator=”wordpress/2.0.2″ –> is not on the first line?
If so, can WordPress be set to put it on the first line? or should I just forget it if there are no other errors?
