Unicode and HTML - Revision history

93.150.208.161: /* Frequency of usage */

2024-10-10T21:13:56Z

Frequency of usage

← Previous revision		Revision as of 21:13, 10 October 2024
Line 169:		Line 169:

	==Frequency of usage==		==Frequency of usage==
	According to internal data from [[Google]]'s web index, in December 2007 the [[UTF-8]] Unicode encoding became the most frequently used encoding on web pages, overtaking both [[ASCII]] (US) and [[ISO/IEC 8859-1\|8859-1]]/[[Windows-1252\|1252]] (Western European).<ref>~~[[Mark~~ ~~Davis~~ ~~(Unicode)~~\|~~Mark~~ ~~Davis]]:~~ ~~[http~~://googleblog.blogspot.com/2008/05/moving-to-unicode-51.html ~~Moving to Unicode 5.1]~~ Official Google ~~blog,~~ ~~5 May 2008~~</ref>		According to internal data from [[Google]]'s web index, in December 2007 the [[UTF-8]] Unicode encoding became the most frequently used encoding on web pages, overtaking both [[ASCII]] (US) and [[ISO/IEC 8859-1\|8859-1]]/[[Windows-1252\|1252]] (Western European).<ref>{{Cite web \|title=Moving to Unicode 5.1 \|url=https://googleblog.blogspot.com/2008/05/moving-to-unicode-51.html \|access-date=2024-10-10 \|website=Official Google Blog \|language=en}}</ref>

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

Apparition11: Restored revision 1227437180 by Toughpigs (talk): WP:CIRC

2024-06-28T19:24:55Z

Restored revision 1227437180 by Toughpigs (talk): WP:CIRC

← Previous revision		Revision as of 19:24, 28 June 2024
Line 28:		Line 28:
	{{Main\|Numeric character reference}}		{{Main\|Numeric character reference}}

	In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.~~<ref>~~{{~~Cite web~~ \|~~title=Unicode and HTML - Academic Kids \|url=https://academickids.com/encyclopedia/index.php/Unicode_and_HTML \|access-~~date=~~2024-06-28~~ ~~\|website=academickids.com~~}}~~</ref>~~		In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.{{citation needed\|date=June 2022}}

	The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}		The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}

Sayrikey The King: I added a citation.1 lib 1ref

2024-06-28T15:26:48Z

I added a citation.1 lib 1ref

← Previous revision		Revision as of 15:26, 28 June 2024
Line 28:		Line 28:
	{{Main\|Numeric character reference}}		{{Main\|Numeric character reference}}

	In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.{{~~citation~~ ~~needed~~\|date=~~June~~ ~~2022~~}}		In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.<ref>{{Cite web \|title=Unicode and HTML - Academic Kids \|url=https://academickids.com/encyclopedia/index.php/Unicode_and_HTML \|access-date=2024-06-28 \|website=academickids.com}}</ref>

	The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}		The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}

Toughpigs: take out tag per WP:OVERTAG -- four tags on an article discourages people from trying to improve it

2024-06-05T18:26:45Z

take out tag per WP:OVERTAG -- four tags on an article discourages people from trying to improve it

← Previous revision		Revision as of 18:26, 5 June 2024
Line 4:		Line 4:
	{{essay-like\|date=December 2011}}		{{essay-like\|date=December 2011}}
	{{refimprove\|date=January 2011}}		{{refimprove\|date=January 2011}}
	{{Rewrite\|date=July 2018}}
	}}		}}
	{{SpecialChars}}		{{SpecialChars}}

HeyElliott: MOS:FIRST

2023-12-13T04:40:06Z

MOS:FIRST

← Previous revision		Revision as of 04:40, 13 December 2023
Line 8:		Line 8:
	{{SpecialChars}}		{{SpecialChars}}
	{{Html series}}		{{Html series}}
	Web pages authored using ~~'''~~HyperText Markup Language~~'''~~ ([[HTML email\|HTML]]) may contain multilingual text represented with the ~~'''~~Unicode universal character set~~'''~~. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in an HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.		Web pages authored using HyperText Markup Language ([[HTML email\|HTML]]) may contain multilingual text represented with the Unicode universal character set. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in an HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.

	In RFC 1866, the initial HTML 2.0 standard, the document character set was defined as ISO-8859-1 (later HTML standard defaults to [[Windows-1252]] encoding). It was extended to [[ISO 10646]] (which is basically equivalent to Unicode) by {{IETF RFC\|2070}}. It does not vary between documents of different languages or created on different platforms. The external character encoding is chosen by the author of the document (or the software the author uses to create the document) and determines how the bytes used to store and/or transmit the document map to characters from the document character set. Characters not present in the chosen external character encoding may be represented by character entity references.		In RFC 1866, the initial HTML 2.0 standard, the document character set was defined as ISO-8859-1 (later HTML standard defaults to [[Windows-1252]] encoding). It was extended to [[ISO 10646]] (which is basically equivalent to Unicode) by {{IETF RFC\|2070}}. It does not vary between documents of different languages or created on different platforms. The external character encoding is chosen by the author of the document (or the software the author uses to create the document) and determines how the bytes used to store and/or transmit the document map to characters from the document character set. Characters not present in the chosen external character encoding may be represented by character entity references.

HeyElliott: /* External links */ WP:SORTKEY

2023-11-07T03:54:48Z

External links: WP:SORTKEY

← Previous revision		Revision as of 03:54, 7 November 2023
Line 198:		Line 198:

	[[Category:HTML]]		[[Category:HTML]]
	[[Category:Unicode]]		[[Category:Unicode\|HTML]]

SunDawn: Reverted edits by 31.94.66.32 (talk) (HG) (3.4.10)

2023-06-01T15:44:46Z

Reverted edits by 31.94.66.32 (talk) (HG) (3.4.10)

← Previous revision		Revision as of 15:44, 1 June 2023
Line 6:		Line 6:
	{{Rewrite\|date=July 2018}}		{{Rewrite\|date=July 2018}}
	}}		}}
	{{SpecialChars}}~~name.cmake LH James d black hayes~~		{{SpecialChars}}
	{{Html series}}		{{Html series}}
	Web pages authored using '''HyperText Markup Language''' ([[HTML email\|HTML]]) may contain multilingual text represented with the '''Unicode universal character set'''. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in an HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.		Web pages authored using '''HyperText Markup Language''' ([[HTML email\|HTML]]) may contain multilingual text represented with the '''Unicode universal character set'''. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in an HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.

31.94.66.32 at 15:44, 1 June 2023

2023-06-01T15:44:29Z

← Previous revision		Revision as of 15:44, 1 June 2023
Line 6:		Line 6:
	{{Rewrite\|date=July 2018}}		{{Rewrite\|date=July 2018}}
	}}		}}
	{{SpecialChars}}		{{SpecialChars}}name.cmake LH James d black hayes
	{{Html series}}		{{Html series}}
	Web pages authored using '''HyperText Markup Language''' ([[HTML email\|HTML]]) may contain multilingual text represented with the '''Unicode universal character set'''. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in an HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.		Web pages authored using '''HyperText Markup Language''' ([[HTML email\|HTML]]) may contain multilingual text represented with the '''Unicode universal character set'''. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in an HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.

Zz2yyx at 14:02, 6 May 2023

2023-05-06T14:02:44Z

← Previous revision		Revision as of 14:02, 6 May 2023
Line 8:		Line 8:
	{{SpecialChars}}		{{SpecialChars}}
	{{Html series}}		{{Html series}}
	Web pages authored using '''HyperText Markup Language''' ([[HTML email\|HTML]]) may contain multilingual text represented with the '''Unicode universal character set'''. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in a HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.		Web pages authored using '''HyperText Markup Language''' ([[HTML email\|HTML]]) may contain multilingual text represented with the '''Unicode universal character set'''. Key to the relationship between Unicode and HTML is the relationship between the "document character set", which defines the set of characters that may be present in an HTML document and assigns numbers to them, and the "external character encoding", or "charset", used to encode a given document as a sequence of bytes.

	In RFC 1866, the initial HTML 2.0 standard, the document character set was defined as ISO-8859-1 (later HTML standard defaults to [[Windows-1252]] encoding). It was extended to [[ISO 10646]] (which is basically equivalent to Unicode) by {{IETF RFC\|2070}}. It does not vary between documents of different languages or created on different platforms. The external character encoding is chosen by the author of the document (or the software the author uses to create the document) and determines how the bytes used to store and/or transmit the document map to characters from the document character set. Characters not present in the chosen external character encoding may be represented by character entity references.		In RFC 1866, the initial HTML 2.0 standard, the document character set was defined as ISO-8859-1 (later HTML standard defaults to [[Windows-1252]] encoding). It was extended to [[ISO 10646]] (which is basically equivalent to Unicode) by {{IETF RFC\|2070}}. It does not vary between documents of different languages or created on different platforms. The external character encoding is chosen by the author of the document (or the software the author uses to create the document) and determines how the bytes used to store and/or transmit the document map to characters from the document character set. Characters not present in the chosen external character encoding may be represented by character entity references.

176.245.17.229 at 13:52, 9 March 2023

2023-03-09T13:52:25Z

← Previous revision		Revision as of 13:52, 9 March 2023
Line 60:		Line 60:
	Many HTML documents are served with inaccurate encoding information, or no encoding information at all. In order to determine the encoding in such cases, many browsers allow the user to manually select an encoding name from a list. They may also employ an encoding auto-detection algorithm that works in concert '''with''' or{{snd}} ''in the case of the BOM and in case of HTML served as XML''{{snd}} '''against''' the manual override.		Many HTML documents are served with inaccurate encoding information, or no encoding information at all. In order to determine the encoding in such cases, many browsers allow the user to manually select an encoding name from a list. They may also employ an encoding auto-detection algorithm that works in concert '''with''' or{{snd}} ''in the case of the BOM and in case of HTML served as XML''{{snd}} '''against''' the manual override.

	For HTML documents which are <code>text/html</code> serialized, manual override may apply to all documents, or only those for which the encoding cannot be ascertained by looking at declarations and/or byte patterns. The fact that the manual override is present and widely used hinders the adoption of accurate encoding declarations on the Web; therefore the problem is likely to persist. But note that Internet Explorer, Chrome and Safari{{snd}} for both XML and <code>text/html</code> serializations{{snd}} do not permit the encoding to be overridden whenever the page includes the BOM.<ref>~~[http://www.w3.org/Bugs/Public/show_bug.cgi?id=12897~~ ~~Bug~~ 12897 - In some parsers, UTF-8 BOM trumps the HTTP charset attribute (Encoding sniffing algorithm)]</ref>		For HTML documents which are <code>text/html</code> serialized, manual override may apply to all documents, or only those for which the encoding cannot be ascertained by looking at declarations and/or byte patterns. The fact that the manual override is present and widely used hinders the adoption of accurate encoding declarations on the Web; therefore the problem is likely to persist. But note that Internet Explorer, Chrome and Safari{{snd}} for both XML and <code>text/html</code> serializations{{snd}} do not permit the encoding to be overridden whenever the page includes the BOM.<ref>{{Cite web \|title=12897 – In some parsers, UTF-8 BOM trumps the HTTP charset attribute (Encoding sniffing algorithm) \|url=https://www.w3.org/Bugs/Public/show_bug.cgi?id=12897 \|access-date=2023-03-09 \|website=www.w3.org}}</ref>

	For HTML documents serialized with the preferred XML label{{snd}} <code>application/xhtml+xml</code>, manual encoding override is not permitted. To override the encoding of such an XML document would mean that the document stopped being XML, as it is a fatal error for XML documents to have an encoding declaration with detectable errors. Currently, Gecko browsers such as Firefox, abide to this rule, whereas the bulk of the other common browsers that support HTML as XML, such as Webkit browsers (Chrome/Safari) <ref>~~[https://bugs.webkit.org/show_bug.cgi?id=66189~~ ~~Bug~~ 66189 - XML parser doesn't emit FATAL ERROR for all, detectable encoding errors]</ref> do allow the encoding of XHTML documents to be manually overridden.		For HTML documents serialized with the preferred XML label{{snd}} <code>application/xhtml+xml</code>, manual encoding override is not permitted. To override the encoding of such an XML document would mean that the document stopped being XML, as it is a fatal error for XML documents to have an encoding declaration with detectable errors. Currently, Gecko browsers such as Firefox, abide to this rule, whereas the bulk of the other common browsers that support HTML as XML, such as Webkit browsers (Chrome/Safari) <ref>{{Cite web \|title=66189 – XML parser doesn't emit FATAL ERROR for all, detectable encoding errors \|url=https://bugs.webkit.org/show_bug.cgi?id=66189 \|access-date=2023-03-09 \|website=bugs.webkit.org}}</ref> do allow the encoding of XHTML documents to be manually overridden.

	==Web browser support==		==Web browser support==

← Previous revision		Revision as of 19:24, 28 June 2024
Line 28:		Line 28:
	{{Main\|Numeric character reference}}		{{Main\|Numeric character reference}}

	In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.~~<ref>~~{{~~Cite web~~ \|~~title=Unicode and HTML - Academic Kids \|url=https://academickids.com/encyclopedia/index.php/Unicode_and_HTML \|access-~~date=~~2024-06-28~~ ~~\|website=academickids.com~~}}~~</ref>~~		In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.{{citation needed\|date=June 2022}}

	The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}		The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}

← Previous revision		Revision as of 15:26, 28 June 2024
Line 28:		Line 28:
	{{Main\|Numeric character reference}}		{{Main\|Numeric character reference}}

	In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.{{~~citation~~ ~~needed~~\|date=~~June~~ ~~2022~~}}		In order to work around the limitations of legacy encodings, HTML is designed such that it is possible to represent characters from the whole of Unicode inside an HTML document by using a [[numeric character reference]]: a sequence of characters that explicitly spell out the Unicode code point of the character being represented. A character reference takes the form '''<code>&#</code>'''<var>N</var>'''<code>;</code>''', where <var>N</var> is either a [[decimal]] number for the Unicode code point, or a [[hexadecimal]] number, in which case it must be prefixed by <code>x</code>. The characters that compose the numeric character reference are universally representable in every encoding approved for use on the Internet.<ref>{{Cite web \|title=Unicode and HTML - Academic Kids \|url=https://academickids.com/encyclopedia/index.php/Unicode_and_HTML \|access-date=2024-06-28 \|website=academickids.com}}</ref>

	The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}		The support for hexadecimal in this context is more recent, so older browsers might have problems displaying characters referenced with hexadecimal numbers{{snd}} but they will probably have a problem displaying Unicode characters above code point 255 anyway. To ensure better compatibility with older browsers, it is still a common practice to convert the hexadecimal code point into a decimal value (for example <code>&#21512;</code> instead of <code>&#x5408;</code>).{{citation needed\|date=June 2022}}