UTF-8: Perbedaan antara revisi
Konten dihapus Konten ditambahkan
Wagino Bot (bicara | kontrib) k →top: minor cosmetic change |
k Clean up, replaced: metoda → metode using AWB |
||
Baris 1:
'''UTF-8''' ('''[[:en:Universal Character Set|Universal Character Set (UCS)]] Transformation Format{{mdash}}8-bit'''<ref>{{Cite book|publisher=[[Unicode Consortium|The Unicode Consortium]]|title=The Unicode Standard|url=http://www.unicode.org/versions/Unicode6.0.0/|edition=6.0|publisher=The Unicode Consortium|location=Mountain View, California, USA|isbn=978-1-936213-01-6|chapter=Chapter 2. General Structure}}</ref>) adalah sebuah pengkodean karakter dengan lebar variabel tertentu (''[[:en:variable-width encoding|variable-width encoding]]'') yang mewakili setiap karakter komputer (''character'') dalam himpunan karakter [[Unicode]]. Didesain untuk ''[[:en:backward compatibility|backward compatibility]]'' dengan [[ASCII]] dan untuk menghindari komplikasi ''[[:en:endianness|endianness]]'' dan ''[[:en:byte order mark|byte order mark]]'' dalam [[UTF-16]] dan [[:en:UTF-32|UTF-32]].
UTF-8 telah menjadi
| url = http://trends.builtwith.com/encoding/UTF-8
| title = UTF-8 Usage Statistics
Baris 25:
==History==
By early 1992 the search was on for a good byte-stream encoding of multi-byte character sets. The draft [[Universal Character Set|ISO 10646]] standard contained a non-required [[Addendum|annex]] called [[UTF-1]] that provided a byte-stream encoding of its 32-bit code points. This encoding was not satisfactory on performance grounds, but did introduce the notion that bytes in the range of 0–127 continue representing the ASCII characters in UTF, thereby providing backward compatibility with ASCII.
In July 1992, the [[X/Open]] committee XoJIG was looking for a better encoding. Dave Prosser of [[Unix System Laboratories]] submitted a proposal for one that had faster implementation characteristics and introduced the improvement that 7-bit ASCII characters would ''only'' represent themselves; all multibyte sequences would include only bytes where the high bit was set. This original proposal, FSS-UTF (File System Safe UCS Transformation Format), was similar in concept to UTF-8, but lacked the crucial property of self-synchronization.<ref name=pikeviacambridge>{{cite web|url=http://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt|title=UTF-8 history|first=Rob|last=Pike|date=30 Apr 2003 | accessdate=September 7, 2012}}</ref><ref>{{cite web|url=https://plus.google.com/u/0/101960720994009339267/posts/Rz1udTvtiMg|title=UTF-8 turned 20 years old yesterday|first=Rob |last=Pike|date=September 6, 2012 | accessdate=September 7, 2012}}</ref>
Baris 681:
{{Ken Thompson navbox}}
-->
{{DEFAULTSORT:Utf-08}}▼
▲{{DEFAULTSORT:Utf-08}}
[[
[[Kategori:Unicode]]
[[
[[Kategori:Komputer]]
| |||