Bug 201251 - x11-fonts/noto: include Noto emoji
Summary: x11-fonts/noto: include Noto emoji
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Sunpoet Po-Chuan Hsieh
Depends on:
Reported: 2015-07-01 13:56 UTC by Sascha Brawer
Modified: 2018-12-27 08:52 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Sascha Brawer 2015-07-01 13:56:32 UTC
Thanks for packaging the Google Noto fonts! Do you also want to include Emoji characters? Seems to be missing in here:

(To work around GitHub size limits, we just split our repos in multiple parts, and the Emoji fonts are easy enough to miss).

Upstream repo:

Feel free to contact me if you've questions. Even better: file a GitHub issue, then it can't get lost.

Cheers to FreeBSD,

-- Sascha
   Sascha Brawer, sascha@google.com
Comment 1 Andrey Fesenko 2015-07-01 14:22:19 UTC
To increase the probability of response is probably to change the subject "x11-fonts/noto: Noto emoji" and add a copy (CC) of kevlo@FreeBSD.org which is listed as MAINTAINER this port.
Comment 2 commit-hook freebsd_committer 2015-07-02 03:26:31 UTC
A commit references this bug:

Author: kevlo
Date: Thu Jul  2 03:26:11 UTC 2015
New revision: 391127
URL: https://svnweb.freebsd.org/changeset/ports/391127

  Include Noto emoji.

  PR:	201251
  Submitted by:	Sascha Brawer

Comment 3 Kevin Lo freebsd_committer 2015-07-02 03:27:34 UTC
Added Noto emoj, thanks.
Comment 4 Sascha Brawer 2015-07-02 12:17:31 UTC
Hello Kevin,

have you noticed that the font needs to be built before getting packaged, using source code that is in the repo? I believe that right now, you've taken one of the input sources that is used for producing the actual font. (Sorry if I'm wrong, I'm not really familiar with BSD packaging).

Perhaps we could offer a pre-built binary file upstream, as has been requested here?

But personally, I'm not sure if this is such a great idea. Shipping binary fonts feels a little like shipping binary drivers, or pre-compiled code, without the sources. Obviously, the downside is that it makes life more painful for distributions. For example, it means that a distro like FreeBSD needs a C compiler, libcairo, python and other tools as part of the build chain when packaging the font file. The font is a bit special because of the colored flags, which we generate from SVG [also in the source repo]. From your perspective as package maintainers, what do you think -- would you rather build from source, or would you rather take a pre-built binary from upstream?

By the way, do tell if our makefiles should change so that this becomes easier for downstream package maintainers. Feel free to send patches (GitHub pull requests), or file bugs:

By the way, sorry for not having a README file yet that explains this. You're sort of a guinea pig here. :-)   <-- Emoji in ASCII

-- Sascha
Comment 5 Kevin Lo freebsd_committer 2015-07-03 01:59:11 UTC
Hi  Sascha,

Sorry I didn't notice that.  If so, someone has to create another port.
I tried building noto-emoji, but it seems it requires nototools [1].
Since nototools is not portable enough,  I finally gave up on getting it
to work...

[1] https://github.com/googlei18n/nototools
Comment 6 Sascha Brawer 2015-07-03 08:04:25 UTC
Hi Kevin,

thanks for trying, and apologies for all the trouble! You said “nototools is not portable enough”; tell me, how should we change the nototools makefile (or anything else) so it would work better for you? For example, I was wondering if the noto-emoji package should perhaps pull in at least some of its build dependencies as git submodules. From your perspective as a maintainer of fonts packages, would this be a good or a bad idea?

With the font in initial version of your FreeBSD package, you will probably see Emoji in black-and-white. Perhaps that's good enough for now, in case you're getting tired of wasting time on this one font.

In  case it helps, here's how I was testing how Emoji are handled on Debian:
$ lynx -dump https://en.wikipedia.org/wiki/Emoji | grep 1F60x

Note that when using lynx without -dump, the Emoji won't show up (at least on Debian). But I believe this is unrelated to the font, it seems to be a bug in lynx or ncurses:


-- Sascha
Comment 7 Kevin Lo freebsd_committer 2015-07-04 14:54:17 UTC
Hi Sascha,

As I mentioned, someone else would like to create separate port noto-emoji.
Sorry I really don't have time to do that.
Comment 8 Axel Gonzalez 2016-01-09 22:59:03 UTC
At this time noto-emoji fails to fetch from main site.

=> Attempting to fetch https://github.com/googlei18n/noto-emoji/raw/master/NotoEmoji-Regular.ttf
fetch: https://github.com/googlei18n/noto-emoji/raw/master/NotoEmoji-Regular.ttf: Not Found
=> Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/NotoEmoji-Regular.ttf
NotoEmoji-Regular.ttf                         100% of  431 kB 1045 kBps 00m01s

Is there another place to fetch it?
Comment 9 Sascha Brawer 2016-01-11 06:39:16 UTC
This seems to work:


— Sascha
Comment 10 Rene Ladan freebsd_committer 2018-01-12 11:22:19 UTC
Maintainer reset.
Comment 11 Walter Schwarzenfeld freebsd_triage 2018-02-05 15:58:57 UTC
Feedback please, resp. is this still relevant?
Comment 12 Tobias Kortkamp freebsd_committer 2018-12-27 08:52:04 UTC
(In reply to w.schwarzenfeld from comment #11)
> Feedback please, resp. is this still relevant?

Doesn't look like it.  Both x11-fonts/{noto,noto-lite} include Noto Emoji
and both are fetchable.