Fwd: Warning and I18N question (Adams #60).

I asked Jeff about this one.

As a result, I think we are best leaving things as they are, particularly
since it would be a new feature.
			- Jim

Forwarded message 1

  • From: Jeffrey Mogul <mogul@w3.org>
  • Date: Mon, 16 Nov 98 11:06:58 PST
  • Subject: Re: Warning and I18N question (urgent)
  • To: jg@pa.dec.com (Jim Gettys)
  • Cc: masinter@parc.xerox.com, mogul
  • Message-Id: <9811161906.AA18325@acetes.pa.dec.com>
    Is it safe to update the reference in 14.46 to RFC 2231?
    > 60. Section 13.1.2, 7th para., has "a server might provide the same
    > warning with texts in both English and Basque". How would a UA
    > discrimitate among different warnings using different languages unless
    > the language were explicitly marked? Unfortunately, RFC2047 does not
    > address this issue. I'd suggest permitting the extensions specified by
    > RFC2231 (which updates RFC2047) to be used to provide explicit language
    > tagging of quoted strings.
I don't have any gripes about *allowing* the use of RFC2231.
I'm not sure I would require it, though, since I don't know
how widely implemented this is.  (Maybe Larry knows.)

However, my recollection of the history behind the Warning
internationalization discussion was that we assumed that either
the reader would understand the warning text or s/he wouldn't.
The expectation is that the warning-generator (probably a proxy)
would use the Accept-Language field in a request to guess at
the appropriate language for a Warning in the response.  If
the guess was hazy, it might give back several Warning texts,

	Warning: 113 proxy.foo.com "Heuristic Expiration"
	Warning: 113 proxy.foo.com "Expiration Heuristique"
	Warning: 113 proxy.foo.com "Heuristischer Verfall"

(warning: translations courtesy of AltaVista) and the browser
might display this in a pop-up as

	Warning #113 from proxy.foo.com:

		Heuristic Expiration
		Expiration Heuristique
		Heuristischer Verfal

and let the user figure it out.  (Of course, to most users,
such a warning would be incomprehensible in any language.)

Adding RFC2231-style tagging would let the browser avoid
displaying Warnings not in the user's native language, I
suppose.  But I'm not sure that a proxy implementor should
count on this being available.

Also, it's a new "feature" that probably hasn't been tested
for our implementation report.


Received on Monday, 16 November 1998 16:38:15 UTC