joypixels / emojione-assets Goto Github PK
View Code? Open in Web Editor NEW[Archived] JoyPixels Emoji Assets now maintained at https://github.com/joypixels/emoji-assets.
Home Page: https://www.joypixels.com
License: Other
[Archived] JoyPixels Emoji Assets now maintained at https://github.com/joypixels/emoji-assets.
Home Page: https://www.joypixels.com
License: Other
From: @Crissov
Original issue: joypixels/emojione#343
The current spritemaps all have a character at position (0, 0)
. This is problematic when adding CSS classes for an icon that does not exist.
For example, here I tried to create an emoji picker but made a mistake in some of the codepoint classes:
This results in the first emoji being shown, because there is no offset as defined by the appropriate codepoint class.
While this example is a bit contrived, we had the problem in Threema Web that newer emojis sent by iOS devices would be rendered as policeman because the appropriate emoji was missing:
threema-ch/threema-web#187
threema-ch/threema-web#194
threema-ch/threema-web#199
(The reason was a modifier that was not supported in emojione 2.0...)
To alleviate this issue and to prevent problems with the wrong emoji showing, it would be better to put a placeholder at position (0, 0)
of the spritemap, e.g. a light grey square, a box with a quesiton mark, something like that.
Building fonts is a rather complicated process, only a few had time and desire to dig into this and understand how it works, thus you rely on community to provide the fonts for every release. But this whole process shouldn't be that complicated!
I made a Docker image to build fonts (Android/Linux only for now). It has all the dependencies built in, so anyone on any platform can build a font out of the latest emojione-assets
using just these two commands:
$ docker pull maximbaz/emojione-fonts-build
$ docker run --rm -v $(pwd):/fonts maximbaz/emojione-fonts-build
However we can do even better!
I'm suggesting to create a Travis job for emojione-assets
repository, that will run automatically every time you create a tag, build the font files and attach them to your releases.
I'm totally willing to help with setting this up. Do you like the idea?
I made the Docker image with the idea of adding more target fonts in the future. For example, if someone wants to contribute building emojione-apple.tt*
, they only need to add build dependencies to the Dockerfile and the build command itself to the build.sh.
There's obviously a dependency on naming the font files properly #24, for now the files are renamed according to the patterns discovered manually.
I haven't go to the reason why but only some of the emojis are displayed right on my Linux machine. This is both on my browser and in terminal. How can I debug this? I saw @maximbaz is the maintainer of this and understood that this is the right place for this issue.
A while ago you added these TTF fonts to the latest release, but now the PG version of the font is missing. Please add it back, or let me know if it is gone forever.
From: @salty-horse
Original issue: joypixels/emojione#386
I came here via a comment in from: https://aur.archlinux.org/packages/ttf-emojione-color/
It seems the AUR package emojione-fonts
has been removed.
Which package do you suggest to use? ttf-emojione-color
?
I can't get the last version, the one from github with 24px sprites, on npm the last one is 3.1.0.
from @salty-horse @ issue #536 in emojione repo.
The EmojiOne image for U+1F996 T-REX shows it nearly upright. While this is a popular look for the dinosaur, it does not reflect current scientific understanding. "Canonizing" it in an emoji will help perpetuate the myth.
For more info:
https://en.wikipedia.org/wiki/Tyrannosaurus#Posture
http://news.cornell.edu/stories/2013/02/blame-barney-students-perception-t-rex-outdated
From: @Crissov
Original issue: joypixels/emojione#344
Seems Travis is still broken ๐
Anyways, I'm attaching .ttf
files for the latest release, please add those to the release on Github ๐
I'm not sure if you decided to abandon -alt
variant or not, it is attached just in case as well.
The archive is too big for Github, download from here: link
New location: link
/cc @caseyahenson
From: @Crissov
Original issue: joypixels/emojione#460
From: @FloEdelmann
Original issue: joypixels/emojione#418
From: @hotgeart
Original issue: joypixels/emojione#339
Hello,
I have a question about license and distribution of font files, @caseyahenson, @thinkrick or anyone else, I would very much appreciate an official reply from your team on this matter.
I am investigating a possibility of including ttf-emojione
in official package distribution of Arch Linux. For end-users this means simplifying discoverability and installation process of EmojiOne font. From the packaging point of view, the font file will be downloaded from Github releases, added to an archive and stored on archlinux.org servers, where users will be downloading it from.
I would like to confirm with you if this violates your license or not.
I'm confused, because on the one hand your website states "Free license - May not redistribute assets", but on the other hand I'm not sure whether the license even applies to me providing an alternative download location, it feels the end users who downloaded font file are the ones who need to be checking the license.
There is also a precedent of Firefox including Twitter Emoji instead of EmojiOne in the distribution of the browser, but that action might have happened because Mozilla didn't want to implement a way to disable emojis in the browser, while in my case it's purely user's decision whether to install ttf-emojione
package or not.
I'm waiting for your response before doing anything further.
From: @Crissov
Original issue: joypixels/emojione#327
We just bought a premium license of emojione today. It seems just after v3.1 shipped. So I'm sure v3.1 sprites are coming, but I was curious what the timeline looks like for that.
From: @Crissov
Original issue: joypixels/emojione#461
From: @Crissov
Original issue: joypixels/emojione#326
From: @Crissov
Original issue: joypixels/emojione#325
From: @Crissov
Original issue: joypixels/emojione#419
See joypixels/emojione#524 for more details.
In order to correctly build emoji font we have to rename image files to include 200d
in them. Otherwise the resulting font cannot distinguish between two separate emojis and a single "complex" emoji:
Font built with current image files:
Font built with renamed image files:
We have identified the following renaming rules (they can be applied multiple times to the same png file):
-1f308 => -200d-1f308
-1f33e => -200d-1f33e
-1f373 => -200d-1f373
-1f393 => -200d-1f393
-1f3a4 => -200d-1f3a4
-1f3a8 => -200d-1f3a8
-1f3eb => -200d-1f3eb
-1f3ed => -200d-1f3ed
-1f466 => -200d-1f466
-1f467 => -200d-1f467
-1f468 => -200d-1f468
-1f469 => -200d-1f469
-1f48b => -200d-1f48b
-1f4bb => -200d-1f4bb
-1f4bc => -200d-1f4bc
-1f527 => -200d-1f527
-1f52c => -200d-1f52c
-1f5e8 => -200d-1f5e8
-1f680 => -200d-1f680
-1f692 => -200d-1f692
-2642 => -200d-2642
-2695 => -200d-2695
-2696 => -200d-2696
-2708 => -200d-2708
-2764 => -200d-2764
However it is easy to make a manual mistake, plus these rules are not permanent and will change as new emojis are released. That's why I'm asking to consider renaming the files in this repo (unless you have special reasons not to do it).
You have the emoji.json
file with base
and output
codepoints, but neither of them defines the correct file name for a png file. For example, the woman mage
file must be named 1f9d9-200d-2640
, not 1f9d9-2640
(as per base code points) and not 1f9d9-200d-2640-fe0f
(as per full code points). If there is a reason not to rename files, could you at least consider adding the correct file name to the emoji.json
, so we can script the renaming process?
Congrats on v4 release!
@caseyahenson looks like you tagged a commit from Github UI and that didn't trigger Travis build... Could you please either trigger Travis build manually or tag master and push this tag? You can remove that tag afterwards.
Writing from memory:
git pull
git tag release-4.0
git push --tags
If everything goes as planned, emojione-android.ttf will be attached to your release in 10 mins.
Thanks!
From: @Crissov
Original issue: joypixels/emojione#402
This can be seen in the wild with Firefox here: https://www.emojione.com/emoji/v3. The emojis are blurry on a MacBook Pro Retina display because they aren't using the @2x styles. MDN docs (https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queries/Using_media_queries#-moz-device-pixel-ratio) suggest using min-resolution: 2dppx
, but also might need a fallback to 192dpi.
Using Firefox 54.x
Followup, I would submit a PR to help with this, but I wasn't sure how you generate the final .CSS files...is it automated, or do you build them by hand?
From: @Crissov
Original issue: joypixels/emojione#362
From: @Artoria2e5
Original issue: joypixels/emojione#454
From: @mikeparadinas
Original issue: joypixels/emojione#348
The repository doesn't currently contain any SVG files, only PNGs. Are SVG assets going to be re-added as the repository is being set up or will EmojiOne 3.0 be limited to PNGs?
SVG images look much crisper than resized PNGs and it's not always possible to stick to the PNGs' native resolutions, so obviously losing that option would be detrimental.
Should we re-raise Artwork issues already opened at the Emojione code repository? Will/can they be moved here?
From: @Crissov
Original issue: joypixels/emojione#420
I noticed that starting in 4.0 several emoji are missing such as โข๏ธ, ยฉ๏ธ, ยฎ๏ธ, and others. There's a ticket open here:
But I think this might be the more appropriate repo.
We're using 32x32 sprites. I see the symbols in the file emojione-sprite-32-symbols.png
and I see the data in emoji.json
so I'm not sure what's going on.
This is still present in 4.5 and blocking us from upgrading.
Hey
Super pumped about the 4.0 release. Looks great ๐๐ผ
Seems like packagist does not have the latest 4.0 tag though. You might have to manually hit "Update" there or set up the proper webhooks. https://packagist.org/about
https://packagist.org/packages/emojione/assets
Thanks
From: @Crissov
Original issue: joypixels/emojione#331
When I try to access CDN of version 3.1.1 emojione-assets shows the message below:
"Package size exceeded the configured limit of 50 MB."
Eg.: https://cdn.jsdelivr.net/npm/[email protected]/png/32/002a.png
This is not only true with this release and not only with the assets, but the emojione.js too. Are there any predictions for a solution to the problem with jsdelivr?
I don't see scripts that is used for sprites/css generation, there is scripts in 2.2.7 tag, but not for version 3 as I could find. Actually I want to generate css classes based on percentage instead of fixed position, as related issues is fixed already in google chrome? (or not?) There is related tickets joypixels/emojione#243 joypixels/emojione#220
Anyway, have build scripts in open source (as for 2 version) would be great. Thanks!
I know you have 2 versions of pistol: a more realistic pistol and a water pistol. The android ttf is using the realistic pistol. Are there plans to release a water pistol version of the ttf?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.