| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 23:24:24 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:32:03 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 21:04:19 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bf808fc9d8ec20
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=izg6xu5NQjCOXlsVfJB6bdXLztyLKt.paThW95Cu6R4-1760225064-1.0.1.1-jKj2qjiMz7K_qt92S6pN80buKQ_XcFX0gCe2MGG2YPj.fzLQJXp3Z72a5ay.KxZE4zNVRHkgMByts2AUX0.gJyZI90zjmzeaGDPh_K_5vYY; path=/; expires=Sat, 11-Oct-25 23:54:24 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98d21c57dbacd86d-BLR
alt-svc: h3=":443"; ma=86400
Re: Clarify `UTF-8' from TAMURA Kent on 2000-07-10 (w3c-ietf-xmldsig@w3.org from July to September 2000)
Re: Clarify `UTF-8'
- From: TAMURA Kent <kent@trl.ibm.co.jp>
- Date: Mon, 10 Jul 2000 16:12:53 +0900
- To: "Joseph M. Reagle Jr." <reagle@w3.org>
- CC: TAMURA Kent <kent@trl.ibm.co.jp>, w3c-ietf-xmldsig@w3.org
- Message-Id: <200007100712.QAA27904@ns.trl.ibm.com>
In message "Re: Clarify `UTF-8'"
on 00/07/07, "Joseph M. Reagle Jr." <reagle@w3.org> writes:
> I'm plodding through email in my inbox for the next version and unless you
> can provide a standard reference for UTF-8N we'll continue using the UTF-8
> reference in the context of the XML specification that Boyer pointed out.
I asked some Unicode people about standardization of UTF-8N.
But anyone did not know about it. We should use the name
'UTF-8' in the specification but I hope adding short note about
no-BOM to the specification.
--
TAMURA Kent @ Tokyo Research Laboratory, IBM
Received on Monday, 10 July 2000 03:13:28 UTC