Skip to content
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

Also load TTC font files #142

Merged
merged 1 commit into from
Oct 10, 2016
Merged

Conversation

vholten
Copy link
Contributor

@vholten vholten commented Oct 6, 2016

Fixes #141 .
As discussed in gravitystorm/openstreetmap-carto#2391 and gravitystorm/openstreetmap-carto#2397 , the Noto CJK fonts that the openstreetmap-carto style uses are currently not used on the rendering servers. They have the extension ".ttc" and are supported by Mapnik.
I have not tested this pull request, but I assume it will solve the problem.

@Firefishy
Copy link
Member

This has been deployed, renderd restarted but a force re-render has not been started. @zerebubuth can update.

@zerebubuth
Copy link
Contributor

It's worth merging this in and making a new release. My package includes this as a "back port" patch, but it would be better to have a new version number.

I don't know how to test this - presumably force-rerender a tile containing a something with a name in a script which falls back to Noto? Anyone know of any examples?

@vholten
Copy link
Contributor Author

vholten commented Oct 7, 2016

Thanks! For example, you could rerender 17/111771/50757.png, which currently looks like
50757

@zerebubuth
Copy link
Contributor

image

That was rendered a moment ago. The Korean text definitely looks different, so hopefully that means the new fonts are enabled and it looks better?

@littlebtc
Copy link

I can confirm that Noto Sans CJK is enabled, the new font is much better in Taiwan. 👍

@jburgess777 jburgess777 merged commit 7211cb7 into openstreetmap:master Oct 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants