Accumulated Feedback on PRI #435

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: Wed Nov 17 12:46:22 CST 2021
Name: Charlotte Buff
Report Type: Public Review Issue
Opt Subject: 435

• Since Unicode uses British spelling for its identifiers, Gray Heart should
  be called Grey Heart in both its formal character name and CLDR
  shortname. Both spellings should be listed in the keywords.

• Moose Face should simply be called Moose. There is no reason why this
  emoji in particular should specify that it includes only the head,
  especially since UTS #51 states that the presence or absence of the
  word “face” in a character’s name does not affect whether it is shown as
  only a head or a full-body animal; vendors could choose to depict Moose
  Face as a full moose and still be in accordance with Unicode’s
  recommendations. The name Moose Face could lead to the same situation
  that plagues U+1F992 GIRAFFE FACE which almost every vendor has drawn as
  a full giraffe, thus creating an unnecessary and potentially confusing
  disconnect between its formal name and expected appearance.

• It is unclear from the candidate list and proposal document whether Black
  Bird is intended to be encoded as an atomic character or a ZWJ sequence.
  The latter would make more sense because it is consistent with the
  implementation of the Black Cat sequence. Also, the colour-modifier
  mechanism in UTS #51 is severely underutilised and could need some
  attention.

Date/Time: Mon Nov 22 19:35:05 CST 2021
Name: David
Report Type: Public Review Issue
Opt Subject: 435

Moose is not easily identifiable as a moose due to the drawing facing 
dirctly to the user. Would be far easier if the moose face was looking 
to a side, on profile. The other solution would be making it full body 
looking to a side just like the donkey. 

Date/Time: Sun Nov 28 12:51:12 CST 2021
Name: Tim Partridge
Report Type: Public Review Issue
Opt Subject: 435

Should number 9 have a CLDR short name of feathered wing? A bat wing is a 
wing, but would not be regarded as angelic.

Date/Time: Tue Nov 30 18:32:37 CST 2021
Name: Eduardo Marín Silva
Report Type: Public Review Issue
Opt Subject: 435

1. The 'black bird' should be encoded as a ZWJ sequence, just like the black
cat was. This would also allow the inclusion of the 'Black swan' as a new
emoji ZWJ sequence, due to their use in the as a metaphor for unexpected
events. But if it must be included, the formal name (and short name) should
be CROW, as it is the kind of bird people mean, and is the more inclusive
term as compared to "raven". The keyword 'nevermore' can be added,
referencing the well known poem by Edgar Allan Poe.

2. The glyph for the goose looks too much like the swan 🦢, which that can
already represent a white goose. The design could follow the Canadian
goose, as amongst the more visually distinct species, it is the most likely
one people tend to talk about, due to their large presence in Canada and
well known aggressive behavior. If this change is made, the
keyword 'Canada' can be added. Likewise, the moose is highly associated
with Canada, and so that keyword can be included as well.

3. The formal name for 'ginger' should be GINGER ROOT, as it can otherwise
be confused with the adjective for red hair or red-haired people. The short
name is good as is.

4. The inclusion of the keyword 'toot' for the flute seems fitting, but then
one must be consistent and add other onomatopeias to other instruments,
like 'doot' for the trumpet, 'twang' for the banjo, and so on. The
term 'bamboo' only has a marginal relation to the instrument as a whole,
and so I recommend to exclude that keyword.

5. For the donkey, I would add the keyword 'beast of burden' and add that
keyword to the llama, the camels, the ox and possibly the horse.

6. For 'wireless' I would strongly recommend for the formal name to be WIFI
SYMBOL, since there are many other wireless technologies represented in
different manners; like a radio tower with concentric circles, a parabolic
dish, cellular data bars, the Bluetooth symbol, the NFC symbol, infrared
remotes, wireless charging and (more recently) laser relay communications.
In order to not equivocate the WiFi symbol with all kinds of wireless
technologies, and permit the future inclusion of other symbols (like some
of those above), the name has to change to actually describe what the glyph
is meant to represent. The short name would then become 'wifi',
with 'wireless' being another keyword. The keyword 'connection' also seems
fitting. The term 'computer' seems out of place, since many devices that
people don't call 'computer', use wireless technology (including wifi).

The glyph itself in the codechart can omit the enclosure, so that the emoji
presentation of the character (including the enclosure) can be more
distinctive.

Date/Time: Tue Jan 25 11:24:52 CST 2022
Name: Alexei Chimendez
Report Type: Public Review Issue
Opt Subject: 435

In the PDF list of emoji candidates, no (provisional) code points are given,
and the issue discription states that the candidates "have not yet been
assigned code points". However, on the Pipeline page, it appears the emoji
candidates are given (provisional) code points.

In particular, the emoji candidate KHANDA is given the code point U+1FAAF.
However, this symbol already exists as U+262C ADI SHAKTI (which has the
informal alias "khanda"). The same character is mentioned in the proposal
document L2/21-223:

> The symbol Adi Shakti was approved as part of Unicode 1.1 in 1993.
 However, this Unicode character has no emoji version. This symbol should
 be updated to become KHANDA [...]

Rather than allocating a new code point, it seems more proper to include
KHANDA as an emoji sequence U+262C U+FE0F.