RFC 2130:The Report of the IAB Character Set Works...
RFC-Ref

UTF-8


Click on the red underlined text to get to the source

... In protocols that up to now have used US-ASCII only, UTF-8 [UTF-8] forms a simple upgrade path; however, its use should be negotiated ...


... achieve a particular level of quality for the purpose of displaying a text stream. For example, UTF-8 encoded Han may require transmission of a language tag to select the specific glyphs to be displayed at a ...
... Character Encoding Schemes are ISO 2022 [ISO-2022] and UTF-8 [UTF-8]. A given CES ...
... CES is typically associated with a single CCS; for example, UTF-8 applies only to ISO 10646. ...
... For text-oriented protocols, new protocols should use UTF-8, and protocols that have a backwards compatibility requirement ...
... meet this model in the future. For other protocols, the default should be UTF-8 as this initially allows US-ASCII to be entered as-is, and enables the full repertoire ...


... G: Register UTF-8 as a Character Encoding Scheme for MIME. ...


... RFC 1522(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft) forms an adequate framework for supporting text; UTF-8 alone is not a possible solution, because the mail pathways are assumed to be 7-bit ...
... The identifiers carried as information about parties are already defined to be in UTF-8. FTP Protocol ...
... are defined in terms of US-ASCII only. One possible solution would be to define a "UTF-8" mode for the transfer of filenames and directory information; this would need to be a negotiated facility, with fallback to US-ASCII ...
... identifiers; there is strong reason to allow non-ASCII characters in these. A UTF-8 negotiation might be the most appropriate thing, however, UTF-8 ...
... UTF-8 negotiation might be the most appropriate thing, however, UTF-8 is awkward to use. Unfortunately, UTF-7 isn't suitable because it conflicts with ...
... ASCII range. A single solution is the best; problems resulting from UTF-8 should be investigated. ...
... ISO 8859-1. The next version will use UTF-8. The currently designed changes will also allow the specification of individual attributes on attribute names; ...


... an encoding which may be more suitable for specific purpose. For example, UTF-8 is a character encoding scheme for ISO 10646. ...


... ISO/JTC1), "Amendment 2:1993, UCS Transformation Format 8 (UTF-8)", in ISO/IEC 10646-1:1993 Information technology - Universal Multiple-Octet Coded Character Set (UCS ...


... Inc., et.al. August 1995. Yergeau, F. "UTF-8, a transformation format of Unicode and ISO 10646 ...



Google
Web
RFC-Ref