UTF-8 - Revision history

Zzo38: Describe the difference between UTF-M-8, UTF-G-8, and UTF-E-8.

2020-08-23T19:09:59Z

Describe the difference between UTF-M-8, UTF-G-8, and UTF-E-8.

2019-05-21T02:36:35Z

2019-05-19T19:43:56Z

Add identifiers

2017-02-22T12:11:36Z

‎External links

2016-03-04T22:26:23Z

2015-07-23T00:32:03Z

‎See also

2015-01-10T22:12:24Z

‎External links

2014-06-25T12:34:23Z

‎In MySQL

2014-06-25T12:34:01Z

2013-02-22T20:46:39Z

@@ Line 13: / Line 13: @@
 == Format ==
-A Unicode code point is encoded as either 1, 2, 3, or 4 bytes. (Early versions of UTF-8 defined sequences with more than 4 bytes, but they are obsolete.) Code points U+0000 to U+007F use 1 byte, U+0080 to U+07FF use 2, U+0800 to U+FFFF use 3, and U+10000 to U+10FFFF use 4.
+A Unicode code point is encoded as either 1, 2, 3, or 4 bytes. (Early versions of UTF-8 defined sequences with more than 4 bytes, but they are not valid Unicode.) Code points U+0000 to U+007F use 1 byte, U+0080 to U+07FF use 2, U+0800 to U+FFFF use 3, and U+10000 to U+10FFFF use 4.
 == In MySQL ==

@@ Line 2: / Line 2: @@
 |formattype=electronic
 |subcat=Character encoding
 |charset=UTF-8
 |charsetaliases=csUTF8

@@ Line 2: / Line 2: @@
 |formattype=electronic
 |subcat=Character encoding
 }}
 '''UCS Transformation Format—8-bit''' ('''UTF-8''') is a byte-oriented [[Unicode]] [[Character Encodings|character encoding]]. It offers good compatibility with [[ASCII]], because codes 0–127 (00–7F hexadecimal) represent the equivalent ASCII characters, and these codes are never used in any other context.

← Older revision		Revision as of 12:11, 22 February 2017
Line 34:		Line 34:
	* [http://doc.cat-v.org/plan_9/4th_edition/papers/utf Hello World or Καλημέρα κόσμε or こんにちは世界] ([http://plan9.bell-labs.com/sys/doc/utf.pdf PDF])		* [http://doc.cat-v.org/plan_9/4th_edition/papers/utf Hello World or Καλημέρα κόσμε or こんにちは世界] ([http://plan9.bell-labs.com/sys/doc/utf.pdf PDF])
	* [http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are-%F0%9D%92%9Cwesome/ Character encoding bugs are 𝒜wesome!]		* [http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are-%F0%9D%92%9Cwesome/ Character encoding bugs are 𝒜wesome!]
		+	* [http://doc.cat-v.org/bell_labs/utf-8_history The history of UTF-8 as told by Rob Pike]

@@ Line 1: / Line 1: @@
 {{FormatInfo
 |formattype=electronic
-|subcat=Character Encodings
+|subcat=Character encoding
 }}
 '''UCS Transformation Format—8-bit''' ('''UTF-8''') is a byte-oriented [[Unicode]] [[Character Encodings|character encoding]]. It offers good compatibility with [[ASCII]], because codes 0–127 (00–7F hexadecimal) represent the equivalent ASCII characters, and these codes are never used in any other context.

@@ Line 19: / Line 19: @@
 * [[Byte Order Mark]]
 * [[CESU-8]]
 == Specifications ==

← Older revision		Revision as of 22:12, 10 January 2015
Line 33:		Line 33:
	* [[Wikipedia:UTF-8]]		* [[Wikipedia:UTF-8]]
	* [http://doc.cat-v.org/plan_9/4th_edition/papers/utf Hello World or Καλημέρα κόσμε or こんにちは世界] ([http://plan9.bell-labs.com/sys/doc/utf.pdf PDF])		* [http://doc.cat-v.org/plan_9/4th_edition/papers/utf Hello World or Καλημέρα κόσμε or こんにちは世界] ([http://plan9.bell-labs.com/sys/doc/utf.pdf PDF])
		+	* [http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are-%F0%9D%92%9Cwesome/ Character encoding bugs are 𝒜wesome!]

@@ Line 14: / Line 14: @@
 == In MySQL ==
-[[MySQL]] [https://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html calls it utf8mb4], after making the unfortunate move of using the name 'utf8' to designate a limited subset that extends only to three bytes covering the BMP range (excluding characters past U+FFFF, or #65535 decimal). This continues a long computer-industry tradition of mangling character encoding standards, from [[PETSCII]] to serving [[Windows-1252]] as [[ISO 8859-1]].
+[[MySQL]] [https://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html calls it utf8mb4], after making the unfortunate move of using the name 'utf8' to designate a limited subset that extends only to three bytes covering the BMP range (excluding characters past U+FFFF, or #65535 decimal). This continues a long computer-industry tradition of mangling character encoding standards, from [[PETSCII]] to serving [[Windows 1252]] as [[ISO 8859-1]].
 == See also ==

← Older revision		Revision as of 12:34, 25 June 2014
Line 11:		Line 11:

	A Unicode code point is encoded as either 1, 2, 3, or 4 bytes. (Early versions of UTF-8 defined sequences with more than 4 bytes, but they are obsolete.) Code points U+0000 to U+007F use 1 byte, U+0080 to U+07FF use 2, U+0800 to U+FFFF use 3, and U+10000 to U+10FFFF use 4.		A Unicode code point is encoded as either 1, 2, 3, or 4 bytes. (Early versions of UTF-8 defined sequences with more than 4 bytes, but they are obsolete.) Code points U+0000 to U+007F use 1 byte, U+0080 to U+07FF use 2, U+0800 to U+FFFF use 3, and U+10000 to U+10FFFF use 4.
		+
		+	== In MySQL ==
		+
		+	[[MySQL]] [https://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html calls it utf8mb4], after making the unfortunate move of using the name 'utf8' to designate a limited subset that extends only to three bytes covering the BMP range (excluding characters past U+FFFF, or #65535 decimal). This continues a long computer-industry tradition of mangling character encoding standards, from [[PETSCII]] to serving [[Windows-1252]] as [[ISO 8859-1]].

	== See also ==		== See also ==