5 ms·

By the way... what is the raison d'etre of this gem? I just don't get why anyone think it's a good idea to replace a character with an image. It's like to repla

by _ZeD_ 12y ago

By the way... what is the raison d'etre of this gem? I just don't get why anyone think it's a good idea to replace a character with an image. It's like to replace all "e" characters in this comment with a .png congaing a fancy custom "e"...

slapresta 12y ago
> It's like to replace all "e" characters in this comment with a .png congaing a fancy custom "e"... So, uh, like Web Fonts, then?
- _ZeD_ 12y ago
  you mean "in a totally different way", do you? you are comparing a gem replacing, in a string with html content, a text fragment with an '<img />' tag, with a way to load and apply custom font from a remote location to a web page text region. While, closing one eye, the effect of the two solution are similar, the solutions are totally different from the technological point of view, from the abstraction layer when they are applied to the practical implications (try to do a simple cut-n-paste from the browser to a text editor, for example)
  - slapresta 12y ago
    I know they're technically different; what I wanted to point out is that it's not such a far-fetched idea.
yuchi 12y ago
Mostly because a lot of browsers do not support emojis at all, and they’ve become pretty ubiquitous.
- NhanH 12y ago
  They're a mean to be expressive via text ... and I really hate the fact that apps are replacing the text with the image. I can always recognize what a string of emoji is supposed to be (there will be obscure one, but then that's entirely dependent on who you're communicating with). Replacing the emoji with the image means that I now have to decipher the image. Not to mention that everyone does it differently. For example, ":))" and "=))" is not the same, and it's really hard to guess which one is which in most of the apps. Yes, I know this whole comment is silly...
  - jonhohle 12y ago
    This is in reference to the Emoji Unicode code pages, not ASCII emoticons. Characters like 👾🍭💔💩 It seems like the image pack they were using did not represent the full Unicode set. ATM, there are still many applications which either don't have access to fonts with those characters or don't otherwise work with code points in that range.

by _ZeD_ 12y ago

slapresta 12y ago

> It's like to replace all "e" characters in this comment with a .png congaing a fancy custom "e"... So, uh, like Web Fonts, then?

_ZeD_ 12y ago
you mean "in a totally different way", do you? you are comparing a gem replacing, in a string with html content, a text fragment with an '<img />' tag, with a way to load and apply custom font from a remote location to a web page text region. While, closing one eye, the effect of the two solution are similar, the solutions are totally different from the technological point of view, from the abstraction layer when they are applied to the practical implications (try to do a simple cut-n-paste from the browser to a text editor, for example)
- slapresta 12y ago
  I know they're technically different; what I wanted to point out is that it's not such a far-fetched idea.

yuchi 12y ago

Mostly because a lot of browsers do not support emojis at all, and they’ve become pretty ubiquitous.

NhanH 12y ago
They're a mean to be expressive via text ... and I really hate the fact that apps are replacing the text with the image. I can always recognize what a string of emoji is supposed to be (there will be obscure one, but then that's entirely dependent on who you're communicating with). Replacing the emoji with the image means that I now have to decipher the image. Not to mention that everyone does it differently. For example, ":))" and "=))" is not the same, and it's really hard to guess which one is which in most of the apps. Yes, I know this whole comment is silly...
- jonhohle 12y ago
  This is in reference to the Emoji Unicode code pages, not ASCII emoticons. Characters like 👾🍭💔💩 It seems like the image pack they were using did not represent the full Unicode set. ATM, there are still many applications which either don't have access to fonts with those characters or don't otherwise work with code points in that range.