RFC 2070 on HTML Internationalization (fwd)

From: Martin J. Duerst (mduerst@ifi.unizh.ch)
Date: Wed Jan 08 1997 - 04:49:43 EST

Finally, the document on the internationalization of HTML
(in which Unicode/ISO 10646 plays a crucial role) has been
published as an RFC (see below).

Regards, Martin.

---------- Forwarded message ----------
Date: Fri, 03 Jan 97 15:02:47 PST
From: RFC Editor <rfc-ed@isi.edu>
To: IETF-Announce: ;
Cc: rfc-ed@isi.edu
Subject: RFC 2070 on HTML Internationalization

A new Request for Comments is now available in online RFC libraries.

        RFC 2070:

        Title: Internationalization of the Hypertext Markup
        Author: F. Yergeau, G. Nicol, G. Adams, M. Duerst
        Date: January 1997
        Mailbox: fyergeau@alis.com, gtn@ebt.com,
                    glenn@spyglass.com, mduerst@ifi.unizh.ch
        Pages: 43
        Characters: 91887
        Updates/Obsoletes: None

        URL: ftp://ds.internic.net/rfc/rfc2070.txt

This document is meant to address the issue of the
internationalization (i18n, i followed by 18 letters followed by n) of
HTML by extending the specification of HTML and giving additional
recommendations for proper internationalization support. This document
is the product of the HyperText Markup Language Working Group of the

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:33 EDT