This page is a compilation of formal public feedback received so far. See Feedback for further information on this issue, how to discuss it, and how to provide feedback.
Date/Time: Thu Oct 12 15:36:08 CDT 2017
Name: David Corbett
Report Type: Error Report
Opt Subject: PRI #356: Extended_Pictographic is too broad
The proposed extension to Extended_Pictographic in http://www.unicode.org/Public/emoji//6.0/emoji-data.txt for forwards-compatibility includes some symbols that are not likely to ever be emoji. U+2686 to U+2689 are technical symbols used in go notation. They are not pictographs, so it would not be appropriate to add this property to them, which implies that they might be emoji one day. U+1F540 to U+1F545 and U+1F900 to U+1F90B are technical symbols used in Typicon notation. They are not pictographs, nor are they the kind of popular symbol that gets used as a dingbat.
Feedback above this line was reviewed in the October 2017 UTC meeting.
Date/Time: Thu Nov 16 18:32:05 CST 2017
Name: Seigo Nonaka
Report Type: Public Review Issue
Opt Subject: PRI #356: Design Guidelines of unsupported emoji sequence
The proposed example of the indication for the unsupported emoji sequence located at the end of the "Section 2. Design Guidlines". All of the examples, Cartouche, Stacked, Stacked Cartouche, Small Trailing, Bridging are not easy to implement in the major text layout engines. They may be technically possible but at least it is hard to implement on Android framework. Please reconsider to include the current behavior, just shows an individual emoji, as an option of the unsupported emoji sequence indication.
Date/Time: Fri Dec 8 17:59:08 CST 2017
Name: Joel Bradshaw
Report Type: Public Review Issue
Opt Subject: Blonde hair explanation in UTS #51
Hello, I am excited about many of the changes in the most recent UTS #51 draft, particularly those regarding guidelines around generic skin tone and gender. I have a suggestion that is in line with other changes in this draft: section 2.2 "Diversity", below the now-removed "gray as the generic skin tone" illustration, contains the following wording: "...dark hair is generally regarded as more neutral because people of every skin tone can have black (or very dark brown) hair." I recommend changing this to something similar to: "...because black (or very dark brown) hair is widespread among people of every skin tone." The previous wording is suboptimal because it implies that some skin tones *can't* have blond hair. While blonde hair is more common among some skin tones than others, there are all kinds of variations, and I believe it does occur with varying frequency in all skin tones. There are even populations that very commonly have both dark Fitzpatrick-V skin and blonde hair, such as Aboriginal Australians[1]. Thanks for all the good work, Joel Bradshaw [1] https://en.wikipedia.org/wiki/Blond#Geographic_distribution
Date/Time: Sat Dec 9 07:01:50 CST 2017
Name: Charlotte Buff
Report Type: Public Review Issue
Opt Subject: PRI #356: Standardizing Hair Style and Direction Modifier Syntax
The latest draft of UTS #51 introduces two new tools for modifying emoji: Hair style and direction. These are realized with ZWJ sequences, so as usual the UTC intends to publish a list of combinations that are recommended for general interchange. However, these two mechanisms are clearly meant to be generic and extensible by vendors or private persons, so it is useful to define the proper syntax even when not all possible options are ever going to be RGI. In particular, the UTC should define the exact ordering of modifiers. A fixed order is bound to break backwards compatibility with older sequences eventually in some way or form, but we should not desperately try to preserve archaic fallback display if it means weโre getting idiosyncratic specifications and interoperability issues in return. Consider the two emoji RUNNER and DANCER. RUNNER is an obvious candidate for directional sequences and DANCER with different hair styles could be very popular with users, so we might hypothetically include the following two sequences as RGI: โข Runner Pointing Right: ๐โโก๏ธ (RUNNER, ZWJ, BLACK RIGHTWARDS ARROW, VS16) โข Dancer with Red Hair: ๐โ๐ฆฐ (DANCER, ZWJ, EMOJI COMPONENT RED HAIR) Later, however, there could also be calls for the inverse: RUNNER with hair style and DANCER with direction. Naturally, both modifiers can be present on the same emoji at the same time, but if we try to preserve the sequences we have already added and simply push all additional modifiers to the end of the stack we get the following situation: โข Runner with Red Hair, Pointing Right: ๐โโก๏ธโ๐ฆฐ (RUNNER, ZWJ, BLACK RIGHTWARDS ARROW, VS16, ZWJ, EMOJI COMPONENT RED HAIR) โข Dancer with Red Hair, Pointing Right: ๐โ๐ฆฐโโก๏ธ (DANCER, ZWJ, EMOJI COMPONENT RED HAIR, ZWJ, BLACK RIGHTWARDS ARROW, VS16) Devices that support the older sequences but not the newer ones will see acceptable fallback display โ a right-pointing runner followed by a hair modifier, and a ginger dancer followed by an arrow โ but the underlying codepoints are inconsistent and unpredictable. One emoji has the arrow before the hair and the other has the hair before the arrow. If we also add gender modifiers into the mix there are already six technically valid arrangements of modifiers, all of them identical in appearance but none of them equivalent under any Unicode process. The canonical ordering should try to group similar modifiers together while also producing sensible fallback behaviour if an end user does not have support for the full sequence. In my opinion the ideal order of modifiers is as follows: โข Skin tone, hair style, gender/profession, direction Skin tone and hair style both affect physical appearance, so they should form one contiguous group. They must come before all others because Fitzpatrick modifiers always directly succeed their base character. Next up are gender modifiers and emoji used in professional sequences (e.g. ๐พ in ๐จโ๐พ) since those also affect the fundamental appearance of the person, but not anything about their body. Direction should be last because it makes the least significant changes. Everyone would recognize horizontally mirrored versions of the same symbol as indeed representing the same concept. Using this approach arbitrarily complex combinations can be build up without different vendors potentially using different sequences to encode the same emoji: โข ๐ (RUNNER) โข ๐๐พ (RUNNER, EMOJI MODIFIER FITZPATRICK TYPE-5) โข ๐๐พโ๐ฆณ (RUNNER, EMOJI MODIFIER FITZPATRICK TYPE-5, ZWJ, EMOJI COMPONENT WHITE HAIR) โข ๐๐พโ๐ฆณโโ๏ธ (RUNNER, EMOJI MODIFIER FITZPATRICK TYPE-5, ZWJ, EMOJI COMPONENT WHITE HAIR, ZWJ, MALE SIGN, VS16) โข ๐๐พโ๐ฆณโโ๏ธโโก๏ธ (RUNNER, EMOJI MODIFIER FITZPATRICK TYPE-5, ZWJ, EMOJI COMPONENT WHITE HAIR, ZWJ, MALE SIGN, VS16, ZWJ, BLACK RIGHTWARDS ARROW, VS16) Note that the hair (๐ฆณ) comes before the gender (โ๏ธ), even though the gendered sequence โ๐+๐พ+โ๏ธโ was added to Unicode first. An older application that is unaware of hair modifiers will thus not be able to form a male runner but rather cancel the ligature after the Fitzpatrick character, but in exchange for that the fallback rendering is much clearer. Consider a farmer with default hair and with curly hair. The canonical sequence order proposed here is as follows: โข ๐ฉโ๐พ (WOMAN, ZWJ, EAR OF RICE) โข ๐ฉโ๐ฆฑโ๐พ (WOMAN, ZWJ, EMOJI COMPONENT CURLY HAIR, ZWJ, EAR OF RICE) The second example wonโt look like a farmer unless the curly-haired sequence is explicitly supported, but in fully unconnected form the meaning can be deduced. โIt is a woman. After the woman is some curly hair in a dashed box, so itโs probably meant to be a woman with curly hair. After that is a rice plant, so maybe itโs supposed to be a curly-haired woman who does something with rice.โ If instead we tried to preserve the pre-existing sequence โ๐ฉ+๐พโ under all circumstances and tacked the hair (or any other modifier) onto the end of the sequence, the curly hair would follow the rice plant (๐ฉ๐พ๐ฆฑ), which is a nonsensical construct and most likely harder to interpret for users who donโt know how the ZWJ process functions. Imagine if Fitzpatrick modifiers worked the same way in ZWJ sequences: ๐ฉ๐พ๐ฝ instead of ๐ฉโ๐ฝ๐พ. If new kinds of modifiers are ever added in the future, their position in the modifier stack should also be determined according to their function. For example, letโs say we add an eye colour modifier. In sequences it should come after hair style rather than at the very end because eye colour is a physical characteristic of the human body and all body modifiers should stay together. There are no expectations that any of this stuff is ever going to be RGI, but the beauty of ZWJ sequences is that they are not bound by the limits of the Unicode standard. Microsoftโs Segoe font includes over fifty thousand family emoji; I wouldnโt put it past them to also add interchangeable hair pieces to a wide array of characters, or allow the mirroring of each and every asymmetrical emoji there is. Besides, anyone can design and distribute their own fonts relatively easily nowadays. Itโs better to set clear guidelines now than having to deal with the fallout of mutually incompatible systems cropping up all over the place because the specifications were too vague.
Feedback above this line was reviewed in the January 2018 UTC meeting.
Date/Time: Fri Jan 26 20:22:20 CST 2018
Name: Mathias Bynens
Report Type: Error Report
Opt Subject: UTR51 bug
(Note: This was sent to the emoji subcommittee already.)
Even the latest draft of UTR51 says `Emoji_Combining_Keycap_Sequence`. It should be `Emoji_Keycap_Sequence` instead (assuming `emoji-sequences.txt` is correct).
Date/Time: Fri Jan 26 20:24:19 CST 2018
Name: Mathias Bynens
Report Type: Error Report
Opt Subject: Bug in https://unicode.org/Public/emoji/5.0/emoji-sequences.txt
(Note: This was sent to the emoji subcommittee already.)
https://unicode.org/Public/emoji/5.0/emoji-sequences.txt
# type_field: any of {Emoji_Combining_Sequence, Emoji_Flag_Sequence, Emoji_Modifier_Sequences}
`Emoji_Modifier_Sequences` should be `Emoji_Modifier_Sequence`
Date/Time: Sun Jan 28 03:38:12 CST 2018
Name: Asif Ansari
Report Type: Error Report
Opt Subject: Problem With Emoticon/Emoji
(Note: This was sent to the emoji subcommittee already.)
Team, I spotted a major issue with the emoticon used as Neutral-Gender. For Example, [No.780 U+1F646 Person Gesturing OK] The Emoticon used is same as used for the Female Gender. Another Example, [834 U+1F647 person bowing] Here, the emoticon used is same as Male gender. I recommend using a minimal Emoticon for them not the Round 3d one. With no facial hair or character that will represent a male of female. Hope you find this Feedback Valuable. Asif Ansari
Date/Time: Sat Feb 17 08:07:35 CST 2018
Name: Charlotte Buff
Report Type: Public Review Issue
Opt Subject: Emoji 11.0: Sorting Position of Hair Components
In the charts for Emoji 11.0 (https://www.unicode.org/emoji/charts/emoji- list.html), the four hair components are sorted amongst the regular emoji (No. 1539โ1542, between ๐๐ฟ and ๐ฃ), but none of the other emoji components (Fitzpatrick modifiers, keycap bases, regional indicators, VS16, ZWJ, tags, and Combining Enclosing Keycap) are. Since the hair characters mean nothing on their own and are unusable as independent emoji, they should not be included in the main list. Either that or all the other emoji components, or at the very least just the Fitzpatrick modifiers and regional indicator symbols, should be added to the table as well.
Date/Time: Wed Feb 28 04:22:57 CST 2018
Name: Christoph Pรคper
Report Type: Public Review Issue
Opt Subject: UTS#51 Animal Emoji Glyph Choice
Emoji 11.0 is about to describe Emoji ZWJ Sequences to indicate glyph direction in general without recommending any specific sequences yet. http://unicode.org/reports/tr51/proposed.html#Direction The reasoning for this new capability is mainly to reduce miscommunication caused by different glyph designs (which vendors are free to choose) and to add new syntactic freedom for authors writing emoji sequences either left to right or right to left. Emoji glyphs differ in other regards as well. One common instance is the style of animal emojis that neither have "FACE" in their UCD name nor have, for legacy reasons, a counterpart that does: Some vendors choose to display them as head or bust portraits while others show the complete body, e.g. several birds have always been head-only in Apple's emoji sets and Apple even sorts animal emojis in their GUI picker by their design choice. Other than that, this only affects mammals. I therefore propose that UTS#51 also adds a general description of Emoji ZWJ Sequences to choose between facial and body glyphs. I suggest ๐ค U+1F464 Bust in Silhouette as the right-hand component for portraits, but I do not have a good suggestion for full body sequences. (๐พ U+1F43E Paw Prints kind of works because it indicates that the feet, if the animal has any, should be visible, but it could also be interpreted as a sequence describing the prints left by the animal.) Perhaps full body rendering could simply be specified as the default (rendering many current implementations non- conforming). The animal emoji characters that have "FACE" in their UCD names but no counterpart without it are: - U+1F438 ๐ธ FROG FACE - U+1F439 ๐น HAMSTER FACE - U+1F43A ๐บ WOLF FACE - U+1F43B ๐ป BEAR FACE (except U+1F9F8 TEDDY BEAR in Unicode 11.0) - U+1F43C ๐ผ PANDA FACE - U+1F981 ๐ฆ LION FACE - U+1F984 ๐ฆ UNICORN FACE - U+1F98A ๐ฆ FOX FACE - U+1F992 ๐ฆ GIRAFFE FACE - U+1F993 ๐ฆ ZEBRA FACE The final two of those, Giraffe and Zebra, are shown with full body in some implementations. The following list shows animal emojis that have been shown as face-only by one vendor or another, but are lacking "FACE" in their UCD names. I'm not sure whether my selection is exhaustive. - U+1F414 ๐ CHICKEN (contrasted with U+1F413 ๐ ROOSTER) - U+1F417 ๐ BOAR - U+1F424 ๐ค BABY CHICK (contrasted with U+1F425 ๐ฅ FRONT-FACING BABY CHICK) - U+1F426 ๐ฆ BIRD - U+1F427 ๐ง PENGUIN - U+1F42A ๐ช DROMEDARY CAMEL (contrasted with U+1F42B ๐ซ BACTRIAN CAMEL) - U+1F989 ๐ฆ OWL - U+1F98C ๐ฆ DEER - U+1F98D ๐ฆ GORILLA - U+1F98F ๐ฆ RHINOCEROS - U+1F995 ๐ฆ SAUROPOD - U+1F996 ๐ฆ T-REX Finally, U+1F987 ๐ฆ BAT is a special case in that it is shown upside down in some implementations because bats often hang from the ceiling. Furthermore, some animals are sexually dimorphic, i.e. males and females look considerably different. For many of those, one sex is much more iconic, usually the male. For some animals, Unicode includes an emoji with a specific sex (e.g. ROOSTER, RAM) and an alternative with an unspecified or only an implied sex (CHICKEN, SHEEP instead of HEN, EWE). Only COW and OX make an explicit pair. UTS#51 should mention that vendors may apply established Emoji ZWJ Sequences with U+2640 VENUS and U+2642 MARS as right- hand part to these, and should make the default glyph as neutral as possible. Emojis affected are at least: - U+1F410 ๐ GOAT - U+1F417 ๐ BOAR - U+1F984 ๐ฆ UNICORN FACE (maybe) - U+1F981 ๐ฆ LION FACE - U+1F983 ๐ฆ TURKEY - U+1F986 ๐ฆ DUCK - U+1F98C ๐ฆ DEER The authors of UTS#51 could then also add a recommendation to make all those new choices available via the same mechanism skin tone or gender choices are made for human-like emojis, i.e. usually a popup. This would work regardless how the difference is actually encoded, i.e. as separate code points or as a sequence.
Date/Time: Tue Mar 6 18:49:25 CST 2018
Name: Ken Lunde
Report Type: Public Review Issue
Opt Subject: PRI #356 (UTS #51) Feedback
Per the "What are emoji?" FAQ item, please change "็ตต (e โ picture) ๆ (mo โ writing) ๅญ (ji โ character)" in Section 1 to "็ตต (e โ picture) + ๆๅญ (moji โ written character)." See: https://www.unicode.org/faq/emoji_dingbats.html#1 ็ตต + ๆๅญ is the correct way to segment the Japanese word ็ตตๆๅญ.
Date/Time: Tue Apr 10 00:50:37 CDT 2018
Name: Marius Spix
Report Type: Error Report
Opt Subject: PRI #356: Special consideration regarding U+1F46F WOMAN WITH BUNNY EARS
In section โ2.2.1 Multi-Person Groupingsโ it should be mentioned that there are currently two implementations of U+1F46F WOMAN WITH BUNNY EARS. The first one shows only the face of one person, the second one shows two persons dancing. Currently the gender and skin colors is applied to both persons. The latter variant should be avoided, that the default representation shows only a single person (either the face only or the whole body). If a vendor decides to show two dancing people with bunny ears in a single glyph, a ZWJ sequence may be used. Example: U+1F46F U+1F3FE U+200D U+2642 U+FE0F U+200D U+1F46F U+1F3FB U+200D U+2640 U+FE0F (๐ฏ๐พโโ๏ธโ๐ฏ๐ปโโ๏ธ), which means โman with bunny ears with medium skin tone partying with woman with bunny ears with light skin toneโ
Date/Time: Wed Apr 11 09:02:06 CDT 2018
Name: Charlotte Buff
Report Type: Public Review Issue
Opt Subject: PRI #356: Use of Incorrect CLDR Short Names
In section 2.1 of UTS #51, U+1F574 is referred to as โman in business suit levitatingโ, but its CLDR short name is โman in suit levitatingโ according to the latest charts. In section 2.2.1, U+1F931 is referred to as โwoman breast feedingโ, but its CLDR short name is โbreast-feedingโ. The UTC should consider always using the stable character names instead of volatile short codes as identifiers in UTS #51 to prevent discrepancies like these from happening in the future.
Date/Time: Tue Apr 17 08:59:49 CDT 2018
Name: Christoph Pรคper
Report Type: Public Review Issue
Opt Subject: PRI 356 Emoji disambiguation sequences
Amending my earlier comments on this, there are some other categories of emojis that a) are, b) have been or c) could likely be represented differently on different platforms. I'm proposing to specify general sequences to distinguish them as well, without recommending specific sequences for general interchange just yet. Sports ------ Several sports are represented in emojis just by the ball (or similar object) used, others include the stick (or other tool) to drive the "ball" or they show the goal or a person playing the sport in typical gear. The UCD names or original sample glyphs for the basketball, tennis, golf and billiard emojis (and possibly others) suggest additional details, but are sometimes shown as just a single ball. - ๐ U+1F3C0 BASKETBALL AND HOOP: ball only on Apple, Whatsapp, Facebook, Twitter, LG; Google and Emojione since 2017, Microsoft since 2016, Samsung since 2018 - ๐พ U+1F3BE TENNIS RACQUET AND BALL: ball only on Apple, LG, Whatsapp, Twitter; Facebook before 2017, Emojione before 2016 - โณ U+26F3 FLAG IN HOLE (๐๏ธ U+1F3CC GOLFER) ball only on Apple before 2011 - ๐ฑ U+1F3B1 BILLIARDS ball only on Apple, Whatsapp, Facebook, Twitter, Emojione; Google and Microsoft since 2016, Samsung since 2018 U+1F939 JUGGLING, on the other hand, is most often shown as a person (applicable to skin tone and gender specification) juggling, not just as balls flying through the air. The only exceptions are Facebook and Twitter before late 2016. I'd like to suggest Emoji ZWJ Sequences with 1. โฝ U+26BD SOCCER BALL as a fixed right-hand part to indicate item-only glyphs, 2. either ๐ฅ U+1F945 GOAL NET or ๐ฉ U+1F6A9 TRIANGULAR FLAG ON POST or ๐ฏ U+1F3AF DIRECT HIT as a fixed right-hand part to indicate target or ball and target glyphs, 3. โน๏ธ U+26F9 PERSON WITH BALL (with optional characters for skin tone and gender following it) as a fixed left-hand part to indicate player glyphs, 4. ๐ ๏ธ U+1F6E0 HAMMER AND WRENCH as a fixed right-hand part to indicate driving tool glyphs, 5. ๐บ๏ธ U+1F5FA WORLD MAP as a fixed right-hand part to indicate playing field, table or board glyphs. Since 4. and 5. have not much of an established use case, they are of minor importance. (Also, their determiner may seem rather arbitrary.) Again, this is only asking for describing these as general mechanisms, not for recommending specific sequences. Emotions -------- There is a number of mostly first-generation emojis that has always been recognized as being used to visually describe feelings and emotions in Western comics or Eastern mangas or classic emoticons composed of mostly characters from the Basic Latin block. They were therefore anticipated to be used the same way in emoji sequences. Many of them frequently are used like that indeed. Some proposed facial emojis (e.g. from L2/16-313/314 and L2/17-244/245) have been rejected on the grounds that they could reasonably well be represented by sequences of existing emojis. UTS#51 should explicitly name these components. Vendors should feel free (but not forced) to add them as right-hand parts in ligatures with either a generic face emoticon (most likely โบ๏ธ U+263A WHITE SMILING FACE) or a semantically more appropriate one. I suggest to list the following: ### Symbols - โจ U+2728 SPARKLES 'amazed, dazzled' - โค๏ธ U+2764 HEAVY BLACK HEART 'liking', `<3` - ๐ U+1F494 BROKEN HEART 'heartbroken, sad, disappointed', `</3` - ๐ U+1F49E REVOLVING HEARTS 'loving' - ๐ U+1F4A0 DIAMOND SHAPE WITH A DOT INSIDE 'cute, kawai' - ๐ข U+1F4A2 ANGER SYMBOL 'angry' - ๐ค U+1F4A4 ZZZ 'sleeping, tired' - ๐ฅ U+1F4A5 COLLISION SYMBOL 'exploding', 'baffled' - ๐ซ U+1F4AB DIZZY SYMBOL 'dizzy, dazed' - ๐ฌ U+1F4AC SPEECH BALLOON 'speaking, talking' - ๐ญ U+1F4AD THOUGHT BALLOON 'thinking', `.oO()` - ๐ฏ๏ธ U+1F5EF RIGHT ANGER BUBBLE 'shouting' ### Objects - โก U+26A1 HIGH VOLTAGE 'electric, charged', '(super) charged' - โ ๏ธ U+2620 SKULL AND CROSSBONES 'dead', 'poisonous, poisoned' - โ๏ธ U+2699 GEAR 'working, busy', 'tinkering' - โ๏ธ U+2744 SNOWFLAKE 'cold, freezing' - ๐ก๏ธ U+1F321 THERMOMETER 'sick, fever': variants of U+1F912 - ๐ก U+1F4A1 ELECTRIC LIGHT BULB 'idea, inventive' - ๐ฃ U+1F4A3 BOMB 'explosive, angry', `o~*`, `@=` - ๐ฆ U+1F4A6 SPLASHING SWEAT SYMBOL 'sweating', 'spitting', `"` - ๐ง U+1F4A7 DROPLET 'tear, crying', 'drooling', `'` - ๐จ U+1F4A8 DASH SYMBOL 'moving, running', 'steaming, farting' - ๐ฅ U+1F525 FIRE 'hot, burning' - ๐ฌ U+1F6AC CIGARETTE 'smoking', `==~` ### Body parts and headwear - ๐ U+1F445 TONGUE 'tongue stuck out': variants of ๐ U+1F61B etc. `:-P` - ๐ U+1F451 CROWN 'crowned, royal', 'best' - ๐ U+1F453 GLASSES 'nerdy': variants of ๐ค U+1F913 `8-)` - ๐ U+1F48B KISS MARK 'kissed', 'blushing', 'kissing': variants of ๐ U+1F617 etc. `:-*` - ๐ถ๏ธ U+1F576 SUNGLASSES 'cool': variants of ๐ U+1F60E `B-)` ### Hand gestures - โ๏ธ U+261D WHITE UP POINTING INDEX 'shush', 'loser sign', 'nose picking' - โ๏ธ U+270C VICTORY HAND 'watching you', 'peace' - โ U+270B RAISED HAND 'stop', 'talk to the hand' - ๐ U+1F44C OK HAND SIGN 'okay', 'small', 'meditating' - ๐ช U+1F4AA FLEXED BICEPS 'strong', 'enduring', 'show-off' - ๐ค U+1F918 SIGN OF THE HORNS 'rock on' - ๐ค U+1F91A RAISED BACK OF HAND 'cover', 'slap' - ๐ค U+1F91E HAND WITH INDEX AND MIDDLE FINGERS CROSSED 'promising, swearing', 'wishing luck' Signs ----- A handful of emojis have been represented by a button or traffic sign design by some vendors, but by a more pictorial glyph by others. In one case, i.e. Potable Water, some vendors changed from sign to picture while others changed in the opposite direction. It could be beneficial to have a method recommended that would discern the two approaches, but I have no good suggestion for it; it would be handy if there was a generic button/sign emoji available for this use case. - ๐ฆ U+1F3A6 CINEMA - ๐ง U+1F3E7 AUTOMATED TELLER MACHINE - ๐ฐ U+1F6B0 POTABLE WATER SYMBOL Some object emojis come paired with a negated prohibition sign: Alarm Bell, Walking, Biking, Drinking Water, Smoking. - ๐ U+1F515 BELL WITH CANCELLATION STROKE - ๐ U+1F514 BELL - ๐ท U+1F6B7 NO PEDESTRIANS - ๐ถ U+1F6B6 PEDESTRIAN - ๐ณ U+1F6B3 NO BICYCLES - ๐ฒ U+1F6B2 BICYCLE - ๐ฑ U+1F6B1 NON-POTABLE WATER SYMBOL - ๐ฐ U+1F6B0 POTABLE WATER SYMBOL - ๐ญ U+1F6AD NO SMOKING SYMBOL - ๐ฌ U+1F6AC SMOKING SYMBOL Littering is the only pair consistently represented by a prohibition and a guidance sign. - ๐ฏ U+1F6AF DO NOT LITTER SYMBOL - ๐ฎ U+1F6AE PUT LITTER IN ITS PLACE SYMBOL The Loudspeaker is a special case in that it has four states overall. - ๐ U+1F507 SPEAKER WITH CANCELLATION STROKE - ๐ U+1F508 SPEAKER - ๐ U+1F509 SPEAKER WITH ONE SOUND WAVE - ๐ U+1F50A SPEAKER WITH THREE SOUND WAVES The Mobile Phone also has two additional, related states. - ๐ต U+1F4F5 NO MOBILE PHONES - ๐ฑ U+1F4F1 MOBILE PHONE - ๐ด U+1F4F4 MOBILE PHONE OFF - ๐ณ U+1F4F3 VIBRATION MODE The Adult Only emoji is the only prohibition sign without an obvious counterpart. - ๐ U+1F51E NO ONE UNDER EIGHTEEN SYMBOL - ๐ธ U+1F6B8 CHILDREN CROSSING To make these and some others into road signs according to the Vienna Convention, they could be used as determiners in a sequence with two obvious existing emojis, but it is less obvious which component should go to the left and which to the right-hand side of the sequence. For prohibitions, UTS#51 used to recommend U+20E0 COMBINING ENCLOSING CIRCLE BACKSLASH' instead, but the general trend is to use only existing emoji characters in sequences with other emojis. - ๐ซ U+1F6AB PROHIBITED - ๐ต U+1F535 BLUE CIRCLE Other ----- Finally, an emoji whose different renditions on platforms may have severe consequences is the Pistol emoji. Some vendors show it as a toy gun, scifi weapon or water pistol, while others display a more realistic firearm. To complicate matters, Microsoft switched towards a lethal weapon in 2016, while Apple (2016), Samsung and Twitter (both 2018) switched towards a toy, which makes it even a backwards compatibility issue within a single platform. Unless Unicode intends to encode a distinct Water Pistol emoji rather soon, I suggest to use sequences with components listed in the Emotions section, e.g. ๐ซโ๐ฆ or ๐ซโ๐ง. Unlike all other sequences in this document, those are not generic but specific sequences that should be recommended for general interchange. - ๐ซ U+1F52B PISTOL
Date/Time: Tue Apr 24 02:23:09 CDT 2018
Name: Peter Edberg
Report Type: Public Review Issue
Opt Subject: PRI #356: Proposed change to ED-15a
The proposed addition to definition ED-15a introduces more parser complexity (combining 2 emoji mechanisms) without a clear benefit. With respect to the suggested example: if tag sequences are extended to support representing arbitrary emoji from an external registry, such things (with variable levels or support) would seem to be bad candidates for inclusion in a standardized ZWJ sequence; and if arbitrary emoji are available, why would a ZWJ sequence be needed anyway? Are there other use cases envisioned for this mechanism?
Date/Time: Sun Apr 29 09:08:09 CDT 2018
Name: Nobuoka Yuya
Report Type: Error Report
Opt Subject: Little fix for UTS #51 (Unicode Emoji)
Hi, I'm software developer in Japan. UTS #51 ( https://www.unicode.org/reports/tr51/proposed.html ) says : > > The word emoji comes from the Japanese: > > ็ตต (e โ picture) ๆ (mo โ writing) ๅญ (ji โ character). Although ใๅญใ means โcharacterโ, however, ใๆๅญใ also means โcharacterโ in Japanese. See https://ejje.weblio.jp/content/%E6%96%87%E5%AD%97 or https://www.nihongomaster.com/dictionary/entry/48636/moji-monji . In the context of ใ็ตตๆๅญใ, the following description is correct : > > ็ตต (e โ picture) ๆๅญ (moji โ character) Thanks.