![]() This led to its adoption by X/Open as its specification for FSS-UTF, which would first be officially presented at USENIX in January 1993 and subsequently adopted by the Internet Engineering Task Force (IETF) in RFC 2277 ( BCP 18) for future internet standards work, replacing Single Byte Character Sets such as Latin-1 in older RFCs. Ken Thompson and Rob Pike produced the first implementation for the Plan 9 operating system in September 1992. UTF-8 was designed as a superior alternative to UTF-1, a proposed variable-length encoding with partial ASCII compatibility which lacked some features including self-synchronization and fully ASCII-compatible handling of characters such as slashes. ![]() It was designed for backward compatibility with ASCII: the first 128 characters of Unicode, which correspond one-to-one with ASCII, are encoded using a single byte with the same binary value as ASCII, so that valid ASCII text is valid UTF-8-encoded Unicode as well. Code points with lower numerical values, which tend to occur more frequently, are encoded using fewer bytes. UTF-8 is capable of encoding all 1,112,064 valid Unicode code points using one to four one- byte (8-bit) code units. Defined by the Unicode Standard, the name is derived from Unicode Transformation Format – 8-bit. UTF-8 is a variable-length character encoding standard used for electronic communication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |