Hello Karl,
Interesting series of articles. For this one, there's quite a lot to be said,
and fitting it all in in a way the novice can understand in progressive steps
it is a bit of a challenge.
Just a few thoughts
[1] For text/html it is best to define the character encoding in the HTTP
Hi Lachlan, Philippe, and all,
So I made a simplified version of my opening page (removed counters and
other impedimenta) and removed the meta tags. All I got was Chinese and
gobbledegook! So I uploaded it to:
http://www.rhh.myzen.co.uk/rhh/gam/test.php
I was stunned to find that it works
designer skrev:
So I made a simplified version of my opening page (removed counters
and other impedimenta) and removed the meta tags. All I got was
Chinese and gobbledegook! So I uploaded it to:
http://www.rhh.myzen.co.uk/rhh/gam/test.php
I was stunned to find that it works a treat when
Hi Karl,
An interesting piece, well done. However, it still leaves me with some
confusion.
I have been using Neil Crosby's PHP approach on [1] (see signature,
below) and it works 'OK', BUT, if I omit the meta tag:
meta http-equiv=Content-Type content=application/xhtml+xml;
charset=utf-8 /
Hi Bob,I modified Neil's script (I'm no PHP scripter though so it took a little trial and error) and the code I published worked for me. My test site is on the home PC but if I recall correctly I think you need to remove any hardcoding of meta http-equiv=Content-Type content=application/xhtml+xml;
designer wrote:
I have been using Neil Crosby's PHP approach on [1] (see signature,
below) and it works 'OK', BUT, if I omit the meta tag:
meta http-equiv=Content-Type content=application/xhtml+xml;
charset=utf-8 /
...
Lachlan says this is simply incorrect, so I'm a bit confused by all this.
Karl Dawson wrote:
From the Top is a series of articles that I am publishing to
concisely explain how and why to construct a high quality,
web-standards compliant head section for a web page. The second
article, just released, examines MIME and Content Negotiation.
Thanks for the feedback, I made a few amendments / corrections this morning including:xhtml-xml - D'oh! Got it right twice before :owell-formedness versus validation - Got it right once before ;-) (more coffee at proof-reading time)
On 16/01/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
# The XML
Lachlan Hunt wrote: [snip]
Did you read my article [1] which Rimantas referred you to? That
explains what you're supposed to do. You need to use real HTTP
headers, not the inferior meta element. The end of that article links
to another that actually explains how to set the charset
At 04:02 AM 1/16/2006, Lachlan Hunt wrote:
(The charset parameter is only really needed for text/* media types,
for XML served with an application/* media type, the XML declaration
is recommended for use instead which may be omitted for UTF-8 and UTF-16)
Paul Novitski wrote:
At 04:02 AM 1/16/2006, Lachlan Hunt wrote:
(The charset parameter is only really needed for text/* media types,
for XML served with an application/* media type, the XML declaration
is recommended for use instead which may be omitted for UTF-8 and UTF-16)
On 16 Jan 2006, at 11:53 pm, designer wrote:
However, I remain confused in the particular case of the PHP
approach. The PHP looks to see if(stristr($_SERVER
[HTTP_ACCEPT],application/xhtml+xml)) and on that basis it
describes the appropriate prolog, mimetype and charset. So the
final
designer wrote:
However, I remain confused in the particular case of the PHP approach.
The PHP looks to see
if(stristr($_SERVER[HTTP_ACCEPT],application/xhtml+xml)) and on
that basis it describes the appropriate prolog, mimetype and charset. So
the final three lines of the php code (where
13 matches
Mail list logo
