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

Unwanted vulgar fractions #1

Open
laughinghan opened this issue Jun 3, 2016 · 5 comments
Open

Unwanted vulgar fractions #1

laughinghan opened this issue Jun 3, 2016 · 5 comments

Comments

@laughinghan
Copy link
Member

For some reason, vulgar fractions like 1/2 and 1/3 are also ending up in Symbola-basic, even though we aren't asking for them.

@laughinghan
Copy link
Member Author

Conjecture: Latin-1 (specifically, ISO 8859-1) is included in its entirety by default, rather than just ASCII?

@jwmerrill
Copy link
Contributor

Glyphs we ask for:

̱!()*+,-./0123456789:;<=>˂˃[]{|}~μ÷⟨⟩π–—∂∏∑−√∫≈≤≥

Glyphs we end up with:
screen shot 2016-06-03 at 2 36 23 pm

@jwmerrill
Copy link
Contributor

So it's not like we're getting all of latin 1. It's really just the vulgar fractions. And space for some reason.

@laughinghan
Copy link
Member Author

Bizarre

Han

On Fri, Jun 3, 2016 at 11:40 AM, Jason Merrill notifications@github.com
wrote:

So it's not like we're getting all of latin 1. It's really just the vulgar
fractions. And space for some reason.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AANyEVmMv3Nu6r9xbYhg7mZqcgua4Cu7ks5qIHUSgaJpZM4ItuMv
.

@jwmerrill
Copy link
Contributor

I just took a look at using the pyftsubset tool that's part of fonttools (which can be installed via HomeBrew on OS X), instead of the random perl library that's currently being used. The good news is that pyftsubset doesn't include vulgar fractions for no reason. The bad news is that its output crashes Chrome 51!

It has a lot of options, but I tried a bunch of the obvious ones, and I can't find anything that keeps the output from crashing Chrome.

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

No branches or pull requests

2 participants