- From: Jon Knight <J.P.Knight@lut.ac.uk>
- Date: Thu, 3 Aug 1995 18:09:27 +0100 (BST)
- To: Gavin Nicol <gtn@ebt.com>
- Cc: masinter@parc.xerox.com, glenn@stonehand.com, html-wg@oclc.org, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
On Thu, 3 Aug 1995, Gavin Nicol wrote:
> I don't mind where the information is put, but one reason
> for preferring:
> http:[EUC]//www.jacme.co.jp/%B0%F5%BA%FE.html
> over
> http://www.jacme.co.jp/[EUC]%B0%F5%BA%FE.html
> is that the latter could very will be a legal name within the system,
> leading to ambiguity.
But surely the character set in use is a server issue and thus should be
in the opaque data portion of the URL? The second scheme will be
understood by server for which that is the correct URL and can be handled
with current browsers, whereas the first version will probably cause most
current browsers severe stomach cramps even if the server understood it.
If the URL is valid for the server its pointing to there shouldn't be any
ambiguity with legal names in the system as the server will be expecting
the [EUC] or whatever.
However, I'd rather see something tacked onto the _end_ of the URL rather
than at the start of the opaque data section. Maybe something like:
http://www.jacme.co.jp/%B0%F5%BA%FE.html;charset=EUC
It just seems more inkeeping with other things I've seen suggested in the
past.
Jon
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon Knight, Researcher, Sysop and General Dogsbody, Department of Computer
Studies, Loughborough University of Technology, Leics., ENGLAND. LE11 3TU.
*** Nothing looks so like a man of sense as a fool who holds his tongue ***
Received on Thursday, 3 August 1995 10:12:43 UTC