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

VillaPazza woff anomaly. #6

Open
HinTak opened this Issue Apr 24, 2016 · 9 comments

Comments

Projects
None yet
2 participants
@HinTak
Copy link

HinTak commented Apr 24, 2016

I had a working private svg font example from Adobe so it is quick to adapt that to your VillaPazza-take1.woff . Interestingly, your font works under icecat-38.7.1 but not firefox-45.0.2 (and they are supposed to be related and not too far off).

chrome's behavior seems to depends on not having --disable-accelerated-video , which is annoying.

@HinTak

This comment has been minimized.

Copy link

HinTak commented May 1, 2016

If you just duplicate the whole 'cmap_format_4 platformID="0" platEncID="3" language="0"' entry as 'cmap_format_4 platformID="3" platEncID="1" language="0"', it would work.

Bugs elsewhere(!), not your fault:

See khaledhosny/ots#106 , khaledhosny/ots#107 , https://lists.w3.org/Archives/Public/public-webfonts-wg/2016Jan/0000.html , opentypejs/opentype.js#185 .

@HinTak

This comment has been minimized.

Copy link

HinTak commented May 1, 2016

Filed at firefox's bug tracker also.

https://bugzilla.mozilla.org/show_bug.cgi?id=1269187

@tomlechner

This comment has been minimized.

Copy link
Contributor

tomlechner commented May 4, 2016

At some point I'll probably make a public repository for helper scripts used to make the Villa Pazza font (image -> svg chopper -> ttx builder -> ttx). The font itself is somewhat in the "embarassing" state of development. ttx compiles without errors, but there are a lot of glyph spacing issues I haven't figured out yet. Not quite ready to release it into the world, and still working on the opentype-svg renderer for Laidout.

@HinTak

This comment has been minimized.

Copy link

HinTak commented May 4, 2016

there are a lot of glyph spacing issues

Yes, I ran FontValidator against it and there are piles on warnings :-). There is a particular one about that:

E2135 The xAvgCharWidth field does not equal the calculated value actual = 629, calc = 414

I'll send the whole thing to you via e-mail.

@HinTak

This comment has been minimized.

Copy link

HinTak commented May 4, 2016

The bounding box for almost all glyphs is also wrong....

@tomlechner

This comment has been minimized.

Copy link
Contributor

tomlechner commented May 5, 2016

Yeah, I was kind of hurrying to get something visible to show at LGM. Thanks for the list, it gives me lots of things to add to my todo list!

I tried FontValidator from git (https://github.com/Microsoft/Font-Validator), and it tells me XML viewing is not implemented on non-windows, and also does not let me copy the filename of the xml file, I have to retype it to get at the file. It also says SVG is not an opentype table, but I see it is listed in what you emailed. Is there some other newer FontValidator version somewhere?

As a shortcut to get a minimally functional glyf table, I just grabbed the bottom most color layer of the svg glyph, and used that for the outline of the fallback glyf table, but still need to implement better path conversion from the original traced image svg. I think I read somewhere that the SVG glyph metrics should be the same as the glyf metrics, though does that mean bounding box, or just advance values? (just one of many things I don't yet understand about font files)

@tomlechner

This comment has been minimized.

Copy link
Contributor

tomlechner commented May 5, 2016

Also I see that the list you sent accepts SVG, but claims CPAL is not an opentype table.

@HinTak

This comment has been minimized.

Copy link

HinTak commented May 5, 2016

https://github.com/HinTak/Font-Validator is much newer :-). Yes, the CPAL one is straight, need to look into that...

@HinTak

This comment has been minimized.

Copy link

HinTak commented May 5, 2016

Oh, xml viewing isn't falling working on my version either, todo.

Can you not match the svg bound box to the glyf one? I haven't read that part of the spec either, but that's probably safest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment