Closed GoogleCodeExporter closed 9 years ago
My opinion about the name changes in N3711=L2/09-370:
Mostly I am fine with the names either way. Many suggestions are for adding
"happy" or
"sad" or "smart" etc. I am ok with adopting most name changes.
Renaming e-326=U+1F606 EXPRESSIONLESS FACE to UNAMUSED FACE is good, as pointed
out in
N3713, because of the agreed glyph change seems significant.
e-32E=U+1F60E FACE WITH MASK->SAD FACE WITH MEDICAL MASK: "medical" is good,
but "sad"
seems a little off. Maybe "tired" or "downtrodden" or "weary"?
The one suggestion that I don't understand is renaming e-325=U+1F605 from
EXASPERATED
FACE to IMPATIENT FACE. I would keep "exasperated" unless convinced otherwise.
Original comment by markus.icu
on 29 Jan 2010 at 11:34
I agree with those:
e-321=U+1F601: I agree ANGUISHED is a bit off. If you look at the source
KDDI="ほえー", it is onomatopoeia that
suggests the person is tired and whining. WEARY sounds more appropriate for
this (WHINING might be a good one also).
e-325=U+1F605: I also agree with this in that EXASPERATED is a bit off. The
sources are KDDI="あせり" literary
meaning "be hasty", SoftBank="おろおろ” literary meaning someone is off
balance or upset. both suggest someone is
not clam, lost his composure and don't know what to do. I am not sure though
IMPATIENT is the right word.
e-338=U+1F616 & e-335=U+1F1F615. I think "RAISED EYEBROWS" is a bug. For e-338
the only source from SoftBank
does not have eyebrows. It has eyes closed in reverse U shape as an expression
of happy face. The same part is used
with e-335 Softbank source. However its KDDI source has eyebrows it is not
something that is characterizing the
expression. So, removing "RAISED EYEBROWS" is appropriate I think.
e-326=U+1F606. for the same reason Markus mentioned.
I am fine either way for ones that add HAPPY, SAD, etc..
Original comment by k...@apple.com
on 30 Jan 2010 at 5:44
See WG2 doc:
Comments accompanying the U.S. negative vote on FPDAM 8 to ISO/IEC 10646:2003
http://std.dkuug.dk/jtc1/sc2/wg2/docs/n3790-ANSI.pdf
Original comment by markus.icu
on 20 Apr 2010 at 11:13
Original issue reported on code.google.com by
pedb...@apple.com
on 22 Jan 2010 at 8:09