Go to listserv.cesnet.cz LWGate Home Page.From: =?ISO-8859-2?Q?krem=BEsk=E1_HO=D8=C8ICE?= <Barry.Bouwsma@TUKE.SK>
Subject: Re: META HTTP-EQUIV and Netscape2.0
Date: Sat, 9 Dec 1995 11:02:18 +0000
Next Article (by Date): Internet na Ukrajine Vaclav Trojan
Previous Article (by Date): Re: META HTTP-EQUIV and Netscape2.0 Barryr Bowsma
Top of Thread: Re: META HTTP-EQUIV and Netscape2.0 Barryr Bowsma
Articles sorted by: [Date] [Subject]
To follow-up my previous posting, here are some references I did not
mention in that message, and a follow-up to my observations...
On Sat, 9 Dec 1995, Barryr (*AHEM*) Barry Bouwsma wrote:
> On Wed, 6 Dec 1995, Hynek Med wrote:
>
> > Is this <META> + encoding tag already in the HTML3 specs? Or is it just
> > another "Netscape initiative"?
>
> Here is how I understand it from reading the following documents...
The release notes describing this capability of Nutscape can be found at
http://home.netscape.com/eng/mozilla/2.0/relnotes/unix-2.0b2.html#Languages
(Presumably the non-Unix flavors of Netscape have similar pages, although
I have not taken the time to reference these.)
> According to the section:
> http://www.w3.org/hypertext/WWW/MarkUp/html3/HTMLandMIME.html
> the only value that is defined even in the proposed HTML3 spec still
> remains ISO-8859-1, which is also assumed to be the default.
Extensions to this are specified in the Internet Draft, which can be
found in your nearest repository, as draft-ietf-html-i18n-02.txt
The internet-draft repository closest to me, if you do not know the
location of the server nearest you with these documents, is
ftp://ftp.muni.cz/pub/internet-drafts/draft-ietf-html-i18n-02.txt.Z
Discussion of this can be found in section 6 of this document,
found shortly before halfway through it.
To summarize, three methods are offered -- the server charset
parameter, which it is noted that most servers ignore, but should be
taken to be the most authoritative; the META tag in the document HEAD,
which suddenly now seems to work for me -- I wonder what I just did...
and the CHARSET value of a document which refers to the document with the
non-default encoding.
Again, this is an Internet Draft, and may or may not be accepted.
> I changed the document which can be found at
> http://www.vszbr.cz/~guest/czdocs.html
> so that this META tag is found in the header, rather than in the body
...and while it did not work earlier, it works now, without the
pop-up windows that had been experienced earlier. So you can safely
ignore about half of my previous message in which I wondered about this.
Barry Bouwsma, <barryb@tuke.sk>
sorry to be writing in English, but I hope you find this information
useful in spite of that...
Next Article (by Date): Internet na Ukrajine Vaclav Trojan
Previous Article (by Date): Re: META HTTP-EQUIV and Netscape2.0 Barryr Bowsma
Top of Thread: Re: META HTTP-EQUIV and Netscape2.0 Barryr Bowsma
Articles sorted by: [Date] [Subject]