Yes, you are right. I didn't validate the CSS. I guess I figured that
any CSS involved would get validated as it's used in the HTMLl?
According to how I learned it and used for at least 5 or 6 years that
hack is in the right place. Not saying I'm right but that's where I was
instructed it goes it's always worked there.
So, is it wise to ignore that encoding error, change it in my code to
1252, or change it to UTF-8?
Thanks,
Mike
On 2/14/2013 10:05 AM, Philip TAYLOR wrote:
Michael Stevens wrote:
Hmmm...
That's an old PNG hack I've used forever. I actually just validated it
(index at least) and did not receive this error. I'll see if I can't
figure out why and fix it...
I think you may have validated the HTML but not the CSS, Mike.
And that particular fragment looks far more like JavaScript
than CSS to me : is it in the correct place ?
I do get this warning:
Line 11, Column 72: Using windows-1252 instead of the declared encoding
iso-8859-1.
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
Which I have absolutely no idea what it means. But, since the data I'll
be eventually pulling out of a database for my gallery will be UTF-8 I
suspect I should change that to charset=UTF-8? Don't know nearly enough
about character encoding... :(
That is an HTML 5 issue : why they decided to prefer a proprietary
encoding to an ISO one is not something I pretend to understand.
Philip Taylor
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/