Mojibake
This article needs additional citations for verification. (March 2023) |
Mojibake (Japanese: 文字化け; IPA: [mod͡ʑibake], "character transformation") is the garbled or gibberish text that is the result of text being decoded using an unintended character encoding.[1] The result is a systematic replacement of symbols with completely unrelated ones, often from a different writing system.
This display may include the generic replacement character ("�") in places where the binary representation is considered invalid. A replacement can also involve multiple consecutive symbols, as viewed in one encoding, when the same binary code constitutes one symbol in the other encoding. This is either because of differing constant length encoding (as in Asian 16-bit encodings vs European 8-bit encodings), or the use of variable length encodings (notably UTF-8 and UTF-16).
Failed rendering of glyphs due to either missing fonts or missing glyphs in a font is a different issue that is not to be confused with mojibake. Symptoms of this failed rendering include blocks with the code point displayed in hexadecimal or using the generic replacement character. Importantly, these replacements are valid and are the result of correct error handling by the software.
Causes
To correctly reproduce the original text that was encoded, the correspondence between the encoded data and the notion of its encoding must be preserved (i.e. the source and target encoding standards must be the same). As mojibake is the instance of non-compliance between these, it can be achieved by manipulating the data itself, or just relabelling it.
Mojibake is often seen with text data that have been tagged with a wrong encoding; it may not even be tagged at all, but moved between computers with different default encodings. A major source of trouble are communication protocols that rely on settings on each computer rather than sending or storing metadata together with the data.
The differing default settings between computers are in part due to differing deployments of Unicode among operating system families, and partly the legacy encodings' specializations for different writing systems of human languages. Whereas Linux distributions mostly switched to UTF-8 in 2004,[2] Microsoft Windows generally uses UTF-16, and sometimes uses 8-bit code pages for text files in different languages.
For some
Original text | 文 | 字 | 化 | け | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Raw bytes of EUC-JP encoding | CA | B8 | BB | FA | B2 | BD | A4 | B1 | ||||||||||||||||
EUC-JP bytes interpreted as Shift-JIS | ハ | ク | サ | 郾 | ス | 、 | ア | |||||||||||||||||
EUC-JP bytes interpreted as GBK | 矢 | 机 | 步 | け | ||||||||||||||||||||
EUC-JP bytes interpreted as Windows-1252 | Ê | ¸ | » | ú | ² | ½ | ¤ | ± | ||||||||||||||||
Raw bytes of UTF-8 encoding | E6 | 96 | 87 | E5 | AD | 97 | E5 | 8C | 96 | E3 | 81 | 91 | ||||||||||||
UTF-8 bytes interpreted as Shift-JIS | 譁 | � | 蟄 | 怜 | 喧 | 縺 | � | |||||||||||||||||
UTF-8 bytes interpreted as GBK | 鏂 | 囧 | 瓧 | 鍖 | 栥 | 亼 | ||||||||||||||||||
UTF-8 bytes interpreted as Windows-1252 | æ | – | ‡ | å | SHY | — | å | Œ | – | ã | HOP | ‘ |
Underspecification
If the encoding is not specified, it is up to the software to decide it by other means. Depending on the type of software, the typical solution is either configuration or charset detection heuristics. Both are prone to mis-prediction.
The encoding of
user.charset
.[3]While a few encodings are easy to detect, such as UTF-8, there are many that are hard to distinguish (see
Mis-specification
Mojibake also occurs when the encoding is incorrectly specified. This often happens between encodings that are similar. For example, the
User oversight
Of the encodings still in common use, many originated from taking ASCII and appending atop it; as a result, these encodings are partially compatible with each other. Examples of this include Windows-1252 and ISO 8859-1. People thus may mistake the expanded encoding set they are using with plain ASCII.
Overspecification
When there are layers of protocols, each trying to specify the encoding based on different information, the least certain information may be misleading to the recipient. For example, consider a web server serving a static HTML file over HTTP. The character set may be communicated to the client in any number of 3 ways:
- in the HTTP header. This information can be based on server configuration (for instance, when serving a file off disk) or controlled by the application running on the server (for dynamic websites).
- in the file, as an HTML meta tag (
http-equiv
orcharset
) or theencoding
attribute of an XML declaration. This is the encoding that the author meant to save the particular file in. - in the file, as a byte order mark. This is the encoding that the author's editor actually saved it in. Unless an accidental encoding conversion has happened (by opening it in one encoding and saving it in another), this will be correct. It is, however, only available in Unicode encodings such as UTF-8 or UTF-16.
Lack of hardware or software support
Much older hardware is typically designed to support only one character set and the character set typically cannot be altered. The character table contained within the display firmware will be localized to have characters for the country the device is to be sold in, and typically the table differs from country to country. As such, these systems will potentially display mojibake when loading text generated on a system from a different country. Likewise, many early operating systems do not support multiple encoding formats and thus will end up displaying mojibake if made to display non-standard text—early versions of Microsoft Windows and Palm OS for example, are localized on a per-country basis and will only support encoding standards relevant to the country the localized version will be sold in, and will display mojibake if a file containing a text in a different encoding format from the version that the OS is designed to support is opened.
Resolutions
Applications using
The difficulty of resolving an instance of mojibake varies depending on the application within which it occurs and the causes of it. Two of the most common applications in which mojibake may occur are web browsers and word processors. Modern browsers and word processors often support a wide array of character encodings. Browsers often allow a user to change their rendering engine's encoding setting on the fly, while word processors allow the user to select the appropriate encoding when opening a file. It may take some trial and error for users to find the correct encoding.
The problem gets more complicated when it occurs in an application that normally does not support a wide range of character encoding, such as in a non-Unicode computer game. In this case, the user must change the operating system's encoding settings to match that of the game. However, changing the system-wide encoding settings can also cause Mojibake in pre-existing applications. In
Problems in different writing systems
English
Mojibake in English texts generally occurs in punctuation, such as
£
, £
, £
, £
, and so on.
Similarly, the right single quotation mark (’), when encoded in UTF-8 and decoded using Windows-1252, becomes ’
, ’
, ’
, and so on.
Some computers did, in older eras, have vendor-specific encodings which caused mismatch also for English text.
Other Western European languages
The alphabets of the North Germanic languages, Catalan, Romanian, Finnish, French, German, Italian, Portuguese and Spanish are all extensions of the Latin alphabet. The additional characters are typically the ones that become corrupted, making texts only mildly unreadable with mojibake:
- å, ä, ö in Finnish and Swedish (š and ž are present in some Finnish loanwords, é marginally in Swedish, mainly also in loanwords)
- à, ç, è, é, ï, í, ò, ó, ú, ü in Catalan
- æ, ø, å in Norwegian and Danish as well as optional acute accents on é etc for disambiguation
- á, é, ó, ij, è, ë, ï in Dutch
- ä, ö, ü, and ß in German
- á,
- á, ð, þ, æ, ö in Icelandic
- à, â, ç, è, é, ë, ê, ï, î, ô, ù, û, ü, ÿ, æ, œ in French
- à, è, é, ì, ò, ù in Italian
- á, é, í, ñ, ó, ú, ü, ¡, ¿ in Spanish
- à, á, â, ã, ç, é, ê, í, ó, ô, õ, ú in Portuguese (ü no longer used)
- á, é, í, ó, ú in Irish
- à, è, ì, ò, ù in Scottish Gaelic
- ă, â, î, ș, ț in Romanian
- £ in British English (æ and œ are rarely used)
… and their uppercase counterparts, if applicable.
These are languages for which the
In Swedish, Norwegian, Danish and German, vowels are rarely repeated, and it is usually obvious when one character gets corrupted, e.g. the second letter in the Swedish word kärlek ("love") when it is encoded in UTF-8 but decoded in Western, producing "kärlek", or für in German, which becomes "für". This way, even though the reader has to guess what the original letter is, almost all texts remain legible. Finnish, on the other hand, frequently uses repeating vowels in words like hääyö ("wedding night") which can make corrupted text very hard to read (e.g. hääyö appears as "hääyö"). Icelandic has ten possibly confounding characters, and Faroese has eight, making many words almost completely unintelligible when corrupted (e.g. Icelandic þjóðlöð, "outstanding hospitality", appears as "þjóðlöð").
In German, Buchstabensalat ("letter salad") is a common term for this phenomenon, in Spanish, deformación (literally "deformation") is used, and in Portuguese, desformatação (literally "deformatting") is used.
Some users transliterate their writing when using a computer, either by omitting the problematic diacritics, or by using digraph replacements (å → aa, ä/æ → ae, ö/ø → oe, ü → ue etc.). Thus, an author might write "ueber" instead of "über", which is standard practice in German when
An artifact of
Swedish example | Source encoding | Target encoding | Result (Characters in red are incorrect.) |
---|---|---|---|
Smörgås (open sandwich) | |||
MS-DOS 437 | ISO 8859-1 |
Sm"rg†s | |
UTF-8 | Smörgås | ||
IBM/CP037 (EBCDIC) | ë_C¶ÊÅCvË | ||
Mac Roman |
Smörgås | ||
ISO 8859-1 | SmˆrgÂs |
The same problem occurs also in Romanian, see these examples:
Romanian example | Source encoding | Target encoding | Result (Characters in red are incorrect.) |
---|---|---|---|
Cenușă (ash) | |||
UTF-8 | |||
ASCII | Cenușă | ||
ISO 8859-2 |
CenuČÄ | ||
OEM 737 | Cenu╚β─Δ | ||
Shift-JIS |
Cenuネ卞 | ||
TIS-620 |
Cenuศฤ | ||
IBM/CP037 (EBCDIC) | äÁ>ÍHrDc |
Central and Eastern European
Users of Central and Eastern European languages can also be affected. Because most computers were not connected to any network during the mid- to late-1980s, there were different character encodings for every language with diacritical characters (see ISO/IEC 8859 and KOI-8), often also varying by operating system.
Hungarian
In
Examples
Hungarian example | Source encoding | Target encoding | Result | Occurrence |
---|---|---|---|---|
ÁRVÍZTŰRŐ TÜKÖRFÚRÓGÉP árvíztűrő tükörfúrógép | ||||
UTF-8 Quoted-printable | 7-bit ASCII | =C3=81RV=C3=8DZT=C5=B0R=C5=90 T=C3=9CK=C3=96RF=C3=9AR=C3=93G=C3=89P =C3=A1rv=C3=ADzt=C5=B1r=C5=91 t=C3=BCk=C3=B6rf=C3=BAr=C3=B3g=C3=A9p | Mainly caused by incorrectly configured mail servers but may occur in SMS messages on some cell phones as well. | |
ISO 8859-2 Quoted-printable
|
=C1RV=CDZT=DBR=D5 T=DCK=D6RF=DAR=D3G=C9P =E1rv=EDzt=FBr=F5 t=FCk=F6rf=FAr=F3g=E9p | |||
CWI-2 | CP 437
|
ÅRVìZTÿRº TÜKÖRFùRòGÉP árvíztûrô tükörfúrógép |
The CP 850 ). This encoding was used very heavily between the early 1980s and early 1990s, but nowadays it is completely deprecated.
| |
CP 852
|
╡RV╓ZTδRè TÜKÖRFΘRαGÉP árvízt√rï tükörfúrógép |
This was very common in the days of CP 850 . Lowercase letters are mainly correct, except for ű and ő. Ü/ü and Ö/ö are correct because CP 437 and CP 850 were made compatible with German. Although this is rare nowadays, it can still be seen in places such as on printed prescriptions and cheques.
| ||
CP 850
|
ÁRVÍZTÙRè TÜKÖRFÚRÓGÉP árvízt¹rï tükörfúrógép | |||
Windows-1250 | µRVÖZTëRŠ TšK™RFéRŕGP rvˇztűr‹ tk"rfŁr˘g‚p |
Both encodings are Central European, but the text is encoded with the DOS encoding and decoded with the Windows encoding. The use of ű is correct. | ||
Mac Roman
|
µRV÷ZTÎRä TöKôRFÈR‡GêP †rv°zt˚rã tÅkîrf£r¢gÇp |
Also common in the days of DOS, this could be seen when Apple computers tried to display Hungarian text sent using DOS or Windows machines, as they would often default to Apple's own encoding. | ||
Windows-1250 | ¡RVÕZT€R’ T‹K÷RF⁄R”G…P ·rvÌzt˚rı t¸kˆrf˙rÛgÈp | |||
CP 852
|
┴RV═ZT█RŇ T▄KÍRF┌RËG╔P ßrvÝztűr§ tŘk÷rf˙rˇgÚp |
Both encodings are Central European, but the text is encoded with the Windows encoding and decoded with the DOS encoding. The use of ű is correct. | ||
Windows-1252 | ÁRVÍZTÛRÕ TÜKÖRFÚRÓGÉP árvíztûrõ tükörfúrógép |
The default Western European Windows encoding is used instead of the Central-European one. Only ő-Ő (õ-Õ) and ű-Ű (û-Û) are wrong, and the text is completely readable. This is the most common error nowadays; due to ignorance, it occurs often on webpages or even in printed media. | ||
UTF-8 | ÃRVÃZTÅ°RÅ TÃœKÖRFÚRÃ"GÉP árvÃztűrÅ‘ tükörfúrógép |
Mainly caused by web services or webmail clients that are configured incorrectly or not tested for international usage (as the problem remains concealed for English texts). In this case the actual (often generated) content is in UTF-8, but some older software may default to localized encodings if UTF-8 is not explicitly specified in the HTML headers. | ||
Mac Roman
|
ÁRVÍZTŰRŐ TÜKÖRFÚRÓGÉP árvíztűrő tükörfúrógép |
Polish
Prior to the creation of
The situation began to improve when, after pressure from academic and user groups,
Russian and other Cyrillic alphabets
Mojibake is colloquially called krakozyabry (кракозя́бры
Meanwhile, in the West,
Most recently, the Unicode encoding includes code points for virtually all characters in all languages, including all Cyrillic characters.
Before Unicode, it was necessary to match text encoding with a font using the same encoding system; failure to do this produced unreadable gibberish whose specific appearance varied depending on the exact combination of text and font encoding. For example, attempting to view non-Unicode Cyrillic text using a font that is limited to the Latin alphabet, or using the default ("Western") encoding, typically results in text that consists almost entirely of capitalized vowels with diacritical marks (e.g. KOI8 "Библиотека" (biblioteka, library) becomes "âÉÂÌÉÏÔÅËÁ", while "Школа русского языка" (shkola russkogo yazyka, Russian-language school) becomes "ûËÏÌÁ ÒÕÓÓËÏÇÏ ÑÚÙËÁ"). Using Code Page 1251 to view text in KOI8, or vice versa, results in garbled text that consists mostly of capital letters (KOI8 and Code Page 1251 share the same ASCII region, but KOI8 has uppercase letters in the region where Code Page 1251 has lowercase, and vice versa).
During the early years of the Russian sector of the World Wide Web, both KOI8 and Code Page 1251 were common. Nearly all websites now use Unicode, but as of November 2023,[update] an estimated 0.35% of all web pages worldwide – all languages included – are still encoded in Code Page 1251, while less than 0.003% of sites are still encoded in KOI8-R.[7][8] Though the HTML standard includes the ability to specify the encoding for any given web page in its source,[9] this is sometimes neglected, forcing the user to switch encodings in the browser manually.
In
Original text | Source encoding | Target encoding | Result |
---|---|---|---|
Кракозябры | |||
Windows-1251 | KOI8-R | йПЮЙНГЪАПШ | |
KOI8-R | Windows-1251 | лТБЛПЪСВТЩ | |
Windows-1252 | ëÒÁËÏÚÑÂÒÙ | ||
MS-DOS 855 | Çá ÆÖóÞ¢áñ | ||
Windows-1251 | Êðàêîçÿáðû | ||
UTF-8 | КракозÑбры | ||
KOI8-R | п я─п╟п╨п╬п╥я▐п╠я─я▀ (The second character is a non-breaking space) | ||
MS-DOS 855 | лџЛђл░л║лЙлиЛЈл▒ЛђЛІ | ||
Windows-1251 | Кракозябры | ||
Mac Roman | –ö—Ä–∞–∫–æ–∑—è–±—Ä—ã | ||
Mac Cyrillic |
–Ъ—А–∞–Ї–Њ–Ј—П–±—А—Л |
Yugoslav languages
Croatian, Bosnian, Serbian (the seceding varieties of Serbo-Croatian language) and Slovenian add to the basic Latin alphabet the letters š, đ, č, ć, ž, and their capital counterparts Š, Đ, Č, Ć, Ž (only č/Č, š/Š and ž/Ž in Slovenian; officially, although others are used when needed, mostly in foreign names, as well). All of these letters are defined in Latin-2 and Windows-1250, while only some (š, Š, ž, Ž, Đ) exist in the usual OS-default Windows-1252, and are there because of some other languages.
Although Mojibake can occur with any of these characters, the letters that are not included in Windows-1252 are much more prone to errors. Thus, even nowadays, "šđčćž ŠĐČĆŽ" is often displayed as "šðèæž ŠÐÈÆŽ", although ð, È, and Æ are never used in Slavic languages.
When confined to basic ASCII (most user names, for example), common replacements are: š→s, đ→dj, č→c, ć→c, ž→z (capital forms analogously, with Đ→Dj or Đ→DJ depending on word case). All of these replacements introduce ambiguities, so reconstructing the original from such a form is usually done manually if required.
The Windows-1252 encoding is important because the English versions of the Windows operating system are most widespread, not localized ones.[citation needed] The reasons for this include a relatively small and fragmented market, increasing the price of high quality localization, a high degree of software piracy (in turn caused by high price of software compared to income), which discourages localization efforts, and people preferring English versions of Windows and other software.[citation needed]
The drive to
When Cyrillic script is used (for Macedonian and partially Serbian), the problem is similar to other Cyrillic-based scripts.
Newer versions of English Windows allow the code page to be changed (older versions require special English versions with this support), but this setting can be and often was incorrectly set. For example, Windows 98 and Windows Me can be set to most non-right-to-left single-byte code pages including 1250, but only at install time.
Caucasian languages
The writing systems of certain languages of the Caucasus region, including the scripts of Georgian and Armenian, may produce mojibake. This problem is particularly acute in the case of ArmSCII or ARMSCII, a set of obsolete character encodings for the Armenian alphabet which have been superseded by Unicode standards. ArmSCII is not widely used because of a lack of support in the computer industry. For example, Microsoft Windows does not support it.
Asian encodings
Another type of mojibake occurs when text encoded in a single-byte encoding is erroneously parsed in a multi-byte encoding, such as one of the encodings for East Asian languages. With this kind of mojibake more than one (typically two) characters are corrupted at once. For example, if the Swedish word kärlek is encoded in Windows-1252 but decoded using GBK, it will appear as "k鋜lek", where "är" is parsed as "鋜". Compared to the above mojibake, this is harder to read, since letters unrelated to the problematic å, ä or ö are missing, and is especially problematic for short words starting with å, ä or ö (e.g. "än" becomes "鋘"). Since two letters are combined, the mojibake also seems more random (over 50 variants compared to the normal three, not counting the rarer capitals). In some rare cases, an entire text string which happens to include a pattern of particular word lengths, such as the sentence "Bush hid the facts", may be misinterpreted.
Vietnamese
In Vietnamese, the phenomenon is called chữ ma (Hán–Nôm: 𡨸魔, "ghost characters") or loạn mã (from Chinese 乱码, luànmǎ). It can occur when a computer tries to decode text encoded in UTF-8 as Windows-1258, TCVN3 or VNI. In Vietnam, chữ ma was commonly seen on computers that ran pre-Vista versions of Windows or cheap mobile phones.
Example | Source encoding | Target encoding | Result |
---|---|---|---|
Trăm năm trong cõi người ta 𤾓𢆥𥪞𡎝𠊛些 ( Truyện Kiều, Nguyễn Du )
| |||
UTF-8 | Windows-1258 | Trăm năm trong cõi ngÆ°á»i ta đ¤¾“đ¢†¥đ¥ªđ¡đ ›äº› | |
TCVN3 | Tr¨m n¨m trong câi ngêi ta �¤¾��¢��¥¥ª��¡�����¾ä�� | ||
VNI (Windows) | Traêm naêm trong coõi ngöôøi ta ����������������������� | ||
Mac Roman | TrƒÉm nƒÉm trong c√µi ng∆∞·ªùi ta §æì¢Ü••™û°éù†äõ‰∫õ |
Japanese
In
Original text | Source encoding | Target encoding | Result |
---|---|---|---|
このメールは皆様へのメッセージです。 | |||
UTF-8 | |||
UTF-7 | ���̃��(�q���Y�_�C�G�b�g) | ||
EUC-JP | �����<�若������罕��吾���<���祉�若�吾�с���� | ||
Shift-JIS | 縺薙�繝。繝シ繝ォ縺ッ逧�ァ倥∈縺ョ繝。繝�そ繝シ繧ク縺ァ縺吶� | ||
Mac Roman | このメールは皆様へのメッセージです。 | ||
ISO 8859-6 | كك�ك�ك�ك�ك�هن�ك�ك�ك�كك؛ك�ك�ك�كك | ||
Windows-1252 | ã“ã®ãƒ¡ãƒ¼ãƒ«ã¯çš†æ§˜ã¸ã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã§ã™ã€‚ | ||
EUC-JP | ¤³¤Î¥á¡¼¥ë¤Ï³§ÍͤؤΥá¥Ã¥»¡¼¥¸¤Ç¤¹¡£ | ||
Shift-JIS | ‚±‚̃[ƒ‹‚ÍŠF—l‚ւ̃ƒbƒZ[ƒW‚Å‚·B |
Chinese
In
It is relatively easy to identify the original encoding when luànmǎ occurs in Guobiao encodings:
Original text | Source encoding | Target encoding | Result | Note |
---|---|---|---|---|
三國志曹操傳 | Big5 | GB | �T瓣в变巨肚 | Garbled characters with almost no hint of original meaning. The red character is not a valid codepoint in GB 2312. |
文字化けテスト | Shift-JIS | 暥帤壔偗僥僗僩 | Kana is displayed as characters with the 亻 (Chinese: 單人旁; pinyin: dānrénpáng) radical, while kanji are other characters. Many of the substitute characters are extremely uncommon in modern Chinese. Somewhat easy to identify due to the presence of multiple consecutive 亻 characters. | |
디제이맥스 테크니카 | EUC-KR | 叼力捞钙胶 抛农聪墨 | Random simplified characters which in most cases make no sense. Probably the easiest to identify because of spaces between every several characters. |
An additional problem in Chinese occurs when rare or antiquated characters, many of which are still used in personal or place names, do not exist in some encodings. Examples of this are:
- The Yu Shyi-kun (simplified Chinese: 游锡堃; traditional Chinese: 游錫堃; pinyin: Yóu Xíkūn), and the "喆" (zhé) in the name of singer David Tao(Chinese: 陶喆; pinyin: Táo Zhé),
- GB 2312's lack of the "镕" (róng) in ex-PRC Premier Zhu Rongji (Chinese: 朱镕基; pinyin: Zhū Róngjī), and
- GBK's lack of the copyright symbol "©".[10]
Newspapers have dealt with missing characters in various ways, including using image editing software to synthesize them by combining other radicals and characters; using a picture of the personalities (in the case of people's names), or simply substituting homophones in the hope that readers would be able to make the correct inference.
Indic text
A similar effect can occur in Brahmic or Indic scripts of South Asia, used in such Indo-Aryan or Indic languages as Hindustani (Hindi-Urdu), Bengali, Punjabi, Marathi, and others, even if the character set employed is properly recognized by the application. This is because, in many Indic scripts, the rules by which individual letter symbols combine to create symbols for syllables may not be properly understood by a computer missing the appropriate software, even if the glyphs for the individual letter forms are available.
One example of this is the old Wikipedia logo, which attempts to show the character analogous to "wi" (the first syllable of "Wikipedia") on each of many puzzle pieces. The puzzle piece meant to bear the Devanagari character for "wi" instead used to display the "wa" character followed by an unpaired "i" modifier vowel, easily recognizable as mojibake generated by a computer not configured to display Indic text.[11] The logo as redesigned as of May 2010[ref] has fixed these errors.
The idea of Plain Text requires the operating system to provide a font to display Unicode codes. This font is different from OS to OS for Singhala and it makes orthographically incorrect glyphs for some letters (syllables) across all operating systems. For instance, the 'reph', the short form for 'r' is a diacritic that normally goes on top of a plain letter. However, it is wrong to go on top of some letters like 'ya' or 'la' in specific contexts. For Sanskritic words or names inherited by modern languages, such as कार्य, IAST: kārya, or आर्या, IAST: āryā, it is apt to put it on top of these letters. By contrast, for similar sounds in modern languages which result from their specific rules, it is not put on top, such as the word करणाऱ्या, IAST: karaṇāryā, a stem form of the common word करणारा/री, IAST: karaṇārā/rī, in the Marathi language.[12] But it happens in most operating systems. This appears to be a fault of internal programming of the fonts. In Mac OS and iOS, the muurdhaja l (dark l) and 'u' combination and its long form both yield wrong shapes.[citation needed]
Some Indic and Indic-derived scripts, most notably Lao, were not officially supported by Windows XP until the release of Vista.[13] However, various sites have made free-to-download fonts.
Burmese
Due to Western sanctions
Due to these ad hoc encodings, communications between users of Zawgyi and Unicode would render as garbled text. To get around this issue, content producers would make posts in both Zawgyi and Unicode.[19] Myanmar government designated 1 October 2019 as "U-Day" to officially switch to Unicode.[14] The full transition was estimated to take two years.[20]
African languages
In certain
.Arabic
Another affected language is
Examples
Arabic example | Browser rendering | Source encoding | Target encoding | Result |
---|---|---|---|---|
(Universal Declaration of Human Rights) | ||||
الإعلان العالمى لحقوق الإنسان | ||||
UTF-8 | KOI8-R | ь╖ы└ь╔ь╧ы└ь╖ы├ ь╖ы└ь╧ь╖ы└ы┘ы┴ ы└ь╜ы┌ы┬ы┌ ь╖ы└ь╔ы├ьЁь╖ы├ | ||
Windows-1250 | الإعلان العالمى Ů„ŘŮ‚ŮŮ‚ الإنسان | |||
Windows-1251 | Ш§Щ„ШҐШ№Щ„Ш§Щ† Ш§Щ„Ш№Ш§Щ„Щ…Щ‰ Щ„ШЩ‚Щ€Щ‚ Ш§Щ„ШҐЩ†ШіШ§Щ† | |||
Windows-1252 | الإعلان العالمى Ù„Øقوق الإنسان | |||
Windows-1256 | ط§ظ„ط¥ط¹ظ„ط§ظ† ط§ظ„ط¹ط§ظ„ظ…ظ‰ ظ„طظ‚ظˆظ‚ ط§ظ„ط¥ظ†ط³ط§ظ† | |||
ISO 8859-5
|
иЇй�иЅиЙй�иЇй� иЇй�иЙиЇй�й�й� й�ий�й�й� иЇй�иЅй�иГиЇй� | |||
ISO 8859-6
|
ظ�عظ�ظ�عظ�ع ظ�عظ�ظ�عع ع عظععع ظ�عظ�عظ�ظ�ع | |||
CP 852
|
ěž┘äěąě╣┘äěž┘ć ěž┘äě╣ěž┘ä┘ů┘ë ┘äěş┘é┘ł┘é ěž┘äěą┘ćě│ěž┘ć | |||
CP 866
|
╪з┘Д╪е╪╣┘Д╪з┘Ж ╪з┘Д╪╣╪з┘Д┘Е┘Й ┘Д╪н┘В┘И┘В ╪з┘Д╪е┘Ж╪│╪з┘Ж | |||
Mac Arabic
|
ظ'عÑظ٪ظ٩عÑظ'عÜ ظ'عÑظ٩ظ'عÑعÖعâ عÑظ-عÇعàعÇ ظ'عÑظ٪عÜظ٣ظ'عÜ | |||
Mac Roman
|
الإعلان العالمى لحقوق الإنسان | |||
Mac Arabic
|
«‰≈Ÿ‰«Ê†«‰Ÿ«‰ÂȆ‰Õ‚Ë‚†«‰≈Ê”«Ê | |||
Windows-1256 | «·≈⁄·«‰ «·⁄«·„Ï ·ÕfiÊfi «·≈‰”«‰ | |||
Windows-1252 | ÇáÅÚáÇä ÇáÚÇáãì áÍÞæÞ ÇáÅäÓÇä |
The examples in this article do not have UTF-8 as browser setting, because UTF-8 is easily recognisable, so if a browser supports UTF-8 it should recognise it automatically, and not try to interpret something else as UTF-8.
See also
- Code point
- Replacement character
- Substitute character
- data comparisontools) can get substantially more difficult to use if not adhering to one convention.
- in-band way to store the encoding together with the data – prepend it. This is by intention invisible to humans using compliant software, but will by design be perceived as "garbage characters" to incompliant software (including many interpreters).
- HTML entities – An encoding of special characters in HTML, mostly optional, but required for certain characters to escape interpretation as markup. While failure to apply this transformation is a vulnerability (see cross-site scripting), applying it too many times results in garbling of these characters. For example, the quotation mark
"
becomes"
,"
,"
and so on. - Bush hid the facts
References
- .
- ^ WINDISCHMANN, Stephan (31 March 2004). "curl -v linux.ars (Internationalization)". Ars Technica. Retrieved 5 October 2018.
- ^ "Guidelines for extended attributes". 2013-05-17. Retrieved 2015-02-15.
- ^ "Unicode mailinglist on the Eudora email client". 2001-05-13. Retrieved 2014-11-01.
- ^ "sms-scam" (in Norwegian). June 18, 2014. Retrieved June 19, 2014.
- ISBN 1-59921-039-8.
- ^ "Usage statistics of Windows-1251 for websites". w3techs.com.
- ^ "Usage statistics of KOI8-R for websites". w3techs.com.
- ^ "Declaring character encodings in HTML".
- ^ "PRC GBK (XGB)". Microsoft. Archived from the original on 2002-10-01. Conversion map between Code page 936 and Unicode. Need manually selecting GB 18030 or GBK in browser to view it correctly.
- ^ Cohen, Noam (June 25, 2007). "Some Errors Defy Fixes: A Typo in Wikipedia's Logo Fractures the Sanskrit". The New York Times. Retrieved July 17, 2009.
- ^ "Marathi Typing | English to Marathi | Online Marathi Typing". marathi.indiatyping.com. Retrieved 2022-08-02.
- ^ "Content Moved (Windows)". Msdn.microsoft.com. Retrieved 2014-02-05.
- ^ a b "Unicode in, Zawgyi out: Modernity finally catches up in Myanmar's digital world". The Japan Times. 27 September 2019. Archived from the original on 30 September 2019. Retrieved 24 December 2019.
Oct. 1 is "U-Day", when Myanmar officially will adopt the new system.... Microsoft and Apple helped other countries standardize years ago, but Western sanctions meant Myanmar lost out.
- ^ a b Hotchkiss, Griffin (March 23, 2016). "Battle of the fonts". Frontier Myanmar. Retrieved 24 December 2019.
With the release of Windows XP service pack 2, complex scripts were supported, which made it possible for Windows to render a Unicode-compliant Burmese font such as Myanmar1 (released in 2005). ... Myazedi, BIT, and later Zawgyi, circumscribed the rendering problem by adding extra code points that were reserved for Myanmar's ethnic languages. Not only does the re-mapping prevent future ethnic language support, it also results in a typing system that can be confusing and inefficient, even for experienced users. ... Huawei and Samsung, the two most popular smartphone brands in Myanmar, are motivated only by capturing the largest market share, which means they support Zawgyi out of the box.
- ^ a b Sin, Thant (7 September 2019). "Unified under one font system as Myanmar prepares to migrate from Zawgyi to Unicode". Rising Voices. Retrieved 24 December 2019.
Standard Myanmar Unicode fonts were never mainstreamed unlike the private and partially Unicode compliant Zawgyi font. ... Unicode will improve natural language processing
- ^ "Why Unicode is Needed". Google Code: Zawgyi Project. Retrieved 31 October 2013.
- ^ "Myanmar Scripts and Languages". Frequently Asked Questions. Unicode Consortium. Retrieved 24 December 2019.
"UTF-8" technically does not apply to ad hoc font encodings such as Zawgyi.
- ^ LaGrow, Nick; Pruzan, Miri (September 26, 2019). "Integrating autoconversion: Facebook's path from Zawgyi to Unicode - Facebook Engineering". Facebook Engineering. Facebook. Retrieved 25 December 2019.
It makes communication on digital platforms difficult, as content written in Unicode appears garbled to Zawgyi users and vice versa. ... In order to better reach their audiences, content producers in Myanmar often post in both Zawgyi and Unicode in a single post, not to mention English or other languages.
- ^ Saw Yi Nanda (21 November 2019). "Myanmar switch to Unicode to take two years: app developer". The Myanmar Times. Archived from the original on 24 December 2019. Retrieved 24 December 2019.