Most, but not all, emoji are included in the Supplementary Multilingual Plane (SMP) of Unicode. Supplementary Multilingual Plane support Versions of iOS prior to 5.1 encoded emoji in the SoftBank private use area scheme, with later versions using standard Unicode. Mostly, these five schemes do not overlap, but au's primary private use scheme partly collides with SoftBank's. Īll three vendors and Google (for GMail) each developed at least one scheme for encoding their emoji in the Unicode Private Use Area (with au developing two) DoCoMo, for example, used the range U+E63E through U+E757. These often matched the encodings of similar KDDI emoji where they existed: for example, the camera (📷) was represented in Shift JIS as F8E2 by DoCoMo, F6EE by KDDI, and F948 by SoftBank, but as 7670 in JIS by all three.
ĭoCoMo and SoftBank also developed their own schemes for representing their emoji sets in extended JIS X 0208 between 7522 and 7E38. The SoftBank 3G format collides with the overlapping Shift JIS ranges used by the other vendors: for example, the Shift JIS representation F797 is used for a convenience store (🏪) by SoftBank, but for a wristwatch (⌚️) by KDDI. SoftBank Mobile emoji support colors and animation, and use different formats on 2G versus 3G: in the 2G format, they are encoded in sequences using the Escape and Shift In control characters, whereas in the 3G format, they are encoded in Shift JIS between F741 and FBDE. Emoji pictograms on au by KDDI are specified using the IMG tag, encoded in Shift JIS between F340 and F7FC, or encoded in extended JIS X 0208 between 7521 and 7B73. When transmitted in Shift JIS on NTT DoCoMo, emoji symbols are specified as a two- byte sequence in the range F89F through F9FC (as expressed in hexadecimal). Various, often incompatible, character encoding schemes were developed by the different mobile providers in Japan for their own emoji sets. Technical aspects JIS, Shift JIS and Private Use Area encodings 2 Implementation by different platforms.1.2 Supplementary Multilingual Plane support.
0 kommentar(er)
