-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASCII emoticons #114
Comments
the existing mapping is just what i/we came up with manually. they are intended for mapping a user-entered emoticon to an emoji, so are very conservative. for the opposite direction (representing a given emoji in ascii), the map would be a lot more liberal. might be worth adding a new property for that. they also don't need to be unique. i've been planning (for some time) to add kaomoji as a distinct property, since there's a semi-official mapping as part of the unicode spec draft |
ASCII ↦ Unicode can be n:1. The requirement for Unicode ↦ ASCII should be that the ASCII sequence maps back to the same Unicode emoji. In other words, I believe they need to be unique. Anyway, some of the current mappings don't make sense if expanded. Current mappings expanded
Other mappingsGood documentation on existing replacement patterns in instant messengers and elsewhere is often surprisingly hard to find. While Skype, for instance, does list the ASCII emoticons they support, the mapping is to graphics that do not have a documented (and not always unambiguous) mapping to Unicode. Skype
As for Unicode emoji libraries, Gemoji and Twemoji do not have methods to convert from or to ASCII, whereas Emojione seems to adopt random, uncoordinated choices as well. Emojione
KaomojiKaomoji did evolve into something more like drawing where there is a large number of character sequences that essentially represent the same. For starters, while Westerners will usually type |
Many apps and libraries support the replacement of ASCII emoticons by Unicode emojis or by proprietary graphics that relate to emojis. They do not all agree, to put it mildly.
Is there some authoritative source for the existing mappings in
build/data_text_toemoji.txt
? Should new ones be added there? Should kaomoji live in the same file?Note that sometimes new Unicode versions bring emojis that are a better match for character line art.
I'd like to establish some conventions:
Hat or Hair or Horns or Forehead
d
orq
>
=
{
8
'
~
=|
c|
*<
or*<|
O
oro
or0
<
or<|
(
}
]
)
[
Eyes
:
=
8
B
;
p
orb
X
orx
!
?
%
#
+
&
9
6
3
Cheeks
'
or,
"
=
~
Nose
-
*
o
^
(:)
Upper Lip
'
or,
~
{
.
Mouth
)
C
orc
D
O
oro
or0
p
orP
orb
d
orq
(
]
[
}
{
<
-
) or pouting>
/
or\
S
ors
or$
L
*
3
X
B
J
|
orI
<>
^
V
orv
or\/
#
&
@
()
(|)
or(I)
{}
{|}
or{I}
[]
[|]
or[I]
Neck or Chin
=
3
8
-
~
'
*
)
Horizontal
Mouth and Nose
_
.
3
m
Eyes and Cheeks
.
^
*
@
+
'
°
-
=
>
and<
T
Q
;
:
o
O
or0
Ears, Arms and Accessories
\
and/
d
andb
*\
and/*
The text was updated successfully, but these errors were encountered: