RFC 1766: Tags for the Identification of Languages
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3066, RFC 3282.
Current document in this lineage: RFC 3282 — Content Language Headers; RFC 4647 — Matching of Language Tags; RFC 5646 — Tags for Identifying Languages
In plain English — editorial summary, not part of the RFC
This document describes a language tag for use in cases where it is desired to indicate the language used in an information object. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1766
- Published
- March 1995
- Authors
- H. Alvestrand
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 9
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4646Tags for Identifying LanguagesObsoleted
September 2006
- RFC 4647Matching of Language TagsCurrent
September 2006
- RFC 1767MIME Encapsulation of EDI ObjectsCurrent
March 1995
- RFC 1759Printer MIBObsoleted
March 1995
- RFC 1777Lightweight Directory Access ProtocolObsoleted
March 1995
- RFC 1778The String Representation of Standard Attribute SyntaxesObsoleted
March 1995
- RFC 1779A String Representation of Distinguished NamesObsoleted
March 1995
- RFC 1781Using the OSI Directory to Achieve User Friendly NamingObsoleted
March 1995
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?