This already came up in #601 (closed) (and CC #164), but I want to have a separate issue for it: The only way to produce emojis should be to actually spell out the emoji in colons, i. e., :smile:. Regular smileys, like :), :D, :/, should be text, not emoji images.
(My main issue is with :) and :/, which look very different from their emoji counterparts 😄 and 😔. 😄 looks way too similar to 😀, and 😔 looks a lot more sad than :/.)
Designs
An error occurred while loading designs. Please try again.
Child items
0
Show closed items
GraphQL error: The resource that you are attempting to access does not exist or you don't have permission to perform this action
No child items are currently open.
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Wouldn't that just be a placebo? If I set it so that I see :) instead of 😄 but others still see 😄 then it's not really doing what I want. Or do you mean a per-room option?
I think the :) should turn into :grinning:😀 instead of 😄
To me what I associate with :) is http://unicode.org/emoji/charts/full-emoji-list.html#263a , especially when looking at the most simplistic icons. In the icon set this is supposedly :relaxed:☺️
My association with those "open mouthed grins" is one of happiness, of exuberance.
So why not leave the typed smileys alone and add a special button for inserting emojis?
The same way that mobile applications like Whatsapp do it, if I type :) it stays that way and if I want to insert an emoji I use the button (this also makes it unnecessary to figure out what the emoji I want is called)
I don't agree, if you have absolutely no idea how the emoji is called you can type all you want but you won't find it. I literally had to look up the emoji's name I put in my previous message on Google to be able to type it. Heck even GMail has a emoji selector!
I agree with precedent here; the colon is sufficient. For searching, there's http://www.emoji-cheat-sheet.com. It would be a duplicated effort to index them all within gitter again. If it's really necessary, it could link out to a static index.
Though perhaps it may be a good idea to add synonyms or flexible searching, but this is probably a rabbit hole for the current issue and it is certainly bikeshedding it.
👎 I don't agree with this. The :) is as much a smiley as :smile:. Both are same. Why see a text instead of an image? But I agree with that the smiley image must be modified to actually represent a smile instead of a laughing emoticon.
Consistency. GitHub issues does not render :) as a smiley.
Confusion. It is confusing when character sequences containing special characters, but which were not intended to represent emoticons, get overaggressively mangled that way. (See e.g. property :property_name example above.)
@ctrueden If someone wants to write something as a part of code or something related which they don't want to be rendered into an image, then they may wrap the text with two backticks :property_name or they can put a \ (backslash) and escape the character from parsing.
Moreover, Github is not a messaging site. But gitter.im is and it should behave and work to some extend like any other IM services (though it's more programmer oriented).
Backticks are not always available, especially on mobile (and this is a messaging site, it should work well on mobile).
And not all IM services are equal. Automatic emojis might be appropriate for a casual chat app, but less so for a service where we want to have serious development discussions.
@abhisekp perfect, working like other chat apps would be great. All other group chat apps that I've used either do not emoji-fy ascii at all unless it's real colon-string-colon emoji, or they provide an option for automatically emoji-fying non-emoji. Either would be perfect for gitter.
Some people here seem to be forgetting that you can still type emoji in gitter using :smile: or :joy_cat: or whatever. Those who know how to access them (such as users on mobile) could also add the literal Unicode characters as well.
This issue is only about the automatic replacement of :) with 😄 and so on. :) could still itself be used as an emoticon (just not an emoji)! This doesn't prevent non-serious developer discussions.
An on/off option would be fantastic, and the : smile : is quite extreme, a closed-mouth smile would be fantastic for those not meaning to grin at everything said with a smile... :)
@Demon000 That is not something defined by the Gitter team. The Emoji are used all over including on GitHub. I guess they could specifically override that one smiley but even so, that would be a separate issue to this one.
Please feel free to take this "which emoji should :) be turned into" discussion elsewhere, this issue is about not turning :) into ANY emoji. Please stay on topic.
Or at least ensure that if you convert :) to a picture, it is its own word. In one of my rooms we were talking about binding to a :port, and it rendered as :stuck_out_tongue_winking_eye:ort which is unacceptable.
I agree with @mholt
If :P is rendered, it should be a word in itself. And for other smileys, it should be possible to write as :smile::smile::smile: (without any spaces between them)
Apart from the fact that it's a terrible UX for a chat that's targeted at developers to automatically transform : into an unrelated image, it's also a terrible design simply because the damn smiley emoticons look like LAUGHTER instead of smileys. You can't put a smiley on gitter unless you use one of these: ☺️😇😋😌😏😊😉😍
Problem is, none of them are even close to a proper smiley that's just :)
This is how a smiley emoticon should look like: http://usefulshortcuts.com/imgs/yahoo-smileys/1.gif
Don't post about that here. We don't want it to get off-topic. That's an unrelated issue, which has its own thread
Only show emojis for :emoji:, not regular smileys
Sorry if I didn't make myself clear @georgiel, but I do have an issue with :) (and others) getting automatically translated to an emoji (which I can't even preview until I hit send), and I would prefer if we could avoid such behaviour. And the fact that I don't feel like any emoji expresses :) makes it even worse.
To me, the fact that the emoji doesn't fully correlate with the smiley is a secondary issue. Because there isn't one I would be happy with anyways (at list from the pool of emojis that Gitter makes available to us).
@dasilvacontin I realise that was part of what you said, but still, if it contains a seperate issue too in the comment it can make discussion go even further off-topic, now the issue has been split off to it's own thread #1027 (closed) .
Why is this closed? The linked PR does not fix this issue of where things like :p or :) are getting translated into emoticons when they absolutely should not be.
Sorry, this was linked to the PR because it made references to people wanting better :) translation but thanks for pinging as the changes do not fix the issue originally raised.