W3C home > Mailing lists > Public > www-international@w3.org > October to December 1996

Re: charset issues

From: Larry Masinter <masinter@parc.xerox.com>
Date: Sat, 21 Dec 1996 00:24:10 PST
To: Ed_Batutis/CAM/Lotus@crd.lotus.com
CC: www-international@www10.w3.org
Message-Id: <96Dec21.002410pst."2694"@golden.parc.xerox.com>
# Lacking any new mechanisms, servers should assume the form data is in the
# same encoding as the form document. Maybe this is the state-of-the-art
# anyway. In any case, this is obviously inefficient because if the server
# serves documents with different encodings it places an undue burden on the
# server. It would be better to tag the return data so that the server does
# not need to look at the original document.

Gavin Nicol suggested the method used by EBT as a short term
workaround if you're using application/x-www-form-urlencoded (either
because the browser doesn't implement application/form-data or because
you want a GET URL):

  include a hidden field in the form, where the field value is a
  string with characters in it that, when sent back, can be used to
  figure out what charset the rest of the form was typed with.

This poses no compatibility difficulty.

Received on Saturday, 21 December 1996 03:24:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:16 UTC