Philippe Verdy scripsit:
> But today the global httd.conf does not specify any charset in the content-type,
In fact I have seen the current httpd.conf, and it does specify UTF-8 as the
DefaultCharset.
--
"While staying with the Asonu, I met a man from John Cowan
the Candensian plane, which
Doug asked:
> I'm sure this is a dumb question, but why would there be any pages in
> non-Unicode charsets on the Unicode Web site?
Legacy, just as for many sites.
The question is whether it makes sense to go back to
older, archived material and:
a. delete it, because it is in Latin-1 or CP 1
Philippe Verdy scripsit:
> You can instruct Apache to serve a part of the site with another default
> encoding by uploading with your FTP client a .htaccess file containing a
> different default MIME type association.
.htaccess cannot do anything that hacking the httpd.conf file can't do.
In this
From: <[EMAIL PROTECTED]>
> Jon Hanna scripsit:
>
> > [T]he default encoding on the server (which really should be utf-8
> > on www.unicode.org at this stage).
>
> Currently it is, but there are sticky issues: in particular, a default
encoding
> overrides information in HTML meta elements as well a
Doug Ewell scripsit:
> John Cowan wrote:
>
> > Consequently, random pages that happen to be in non-Unicode charsets
> > are getting mis-served and mis-displayed. The site will probably
> > revert to having no default as a result, which is a great pity.
>
> I'm sure this is a dumb question, but
John Cowan wrote:
> Consequently, random pages that happen to be in non-Unicode charsets
> are getting mis-served and mis-displayed. The site will probably
> revert to having no default as a result, which is a great pity.
I'm sure this is a dumb question, but why would there be any pages in
non
Jon Hanna scripsit:
> This is passing strange, for the problem was UTF-8 being mis-interpreted as a
> legacy encoding, not the other way around.
a) Not everyone uses a modern browser.
2) The problem might have been speculative (or memorious) rather than actual.
--
John Cowan
Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
> Jon Hanna scripsit:
>
> > [T]he default encoding on the server (which really should be utf-8
> > on www.unicode.org at this stage).
>
> Currently it is, but there are sticky issues: in particular, a default
> encoding
> overrides information in
Jon Hanna scripsit:
> [T]he default encoding on the server (which really should be utf-8
> on www.unicode.org at this stage).
Currently it is, but there are sticky issues: in particular, a default encoding
overrides information in HTML meta elements as well as browser heuristics,
at least for mod
Quoting Michael Everson <[EMAIL PROTECTED]>:
> At 15:39 +0100 2004-05-21, Jon Hanna wrote:
>
> >Were the headers correct?
>
> It is plain text.
HTTP has headers separate to the content (the headers come first and the content
comes next). These headers can contain encoding information and other
At 15:39 +0100 2004-05-21, Jon Hanna wrote:
Were the headers correct?
It is plain text.
--
Michael Everson * * Everson Typography * * http://www.evertype.com
> >As a side note to Michael or the other 6 RA members (Ken, and Rick notably),
> I
> >don't think it's even a good idea to ZIP this reference plain-text file due
> to
> >its very small size (which smaller than each of the HTML versions of
> >codelists).
>
[snip]
> Everyone has a zip tool.
>
>
12 matches
Mail list logo
