-
Notifications
You must be signed in to change notification settings - Fork 819
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
Missing fonts after following INSTALL.md #3655
Comments
Hi @Phyks and thanks for the report.
Summary: Technically this are non-issues. But I suppose we should make a better description in the INSTALL.md file… |
A better description would be good. When I first started using Mapnik, I didn't know the warnings about fonts where normal and that it would load without them. So it would be good if there was at least a mention of the fact that the warnings are normal and don't effect anything. |
Hi @sommerluk, Thanks a lot for the detailed explanations! I think replicating your comment #3655 (comment) in the |
Hi,
I followed https://github.com/gravitystorm/openstreetmap-carto/blob/master/INSTALL.md#installation-on-ubuntudebian (on Ubuntu bionic) and was expecting the required fonts to be installed. However, when running Kosmtik, I get the following warnings:
It seems there are two issues with the fonts:
First,
ttf-unifont
package does not seem to provide aMedium
font, from looking at the files within the package. Is theunifont Medium
font supposed to be provided by this package?Second, Noto Emoji is not packaged nor installed, which was already discussed in Where to find "Noto Emoji Regular" #2379. However, there seems to be now a package for Ubuntu (starting from bionic / 18.04 LTS) called
fonts-noto-color-emoji
which provides the font. Still, the font is named "Noto Color Emoji" and not "Noto Emoji", so simply installing the package is not enough. Same seems to be available in Debian, but only intesting
for now. Would it be worth mentionning this in theINSTALL.md
(and eventually use the "Color" font)?Best,
The text was updated successfully, but these errors were encountered: