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

Font Validator 2.0 crashes when I open a font. #19

Closed
DunwichType opened this issue Aug 6, 2016 · 9 comments
Closed

Font Validator 2.0 crashes when I open a font. #19

DunwichType opened this issue Aug 6, 2016 · 9 comments

Comments

@DunwichType
Copy link

DunwichType commented Aug 6, 2016

Opening this font will crash Font Validator 2.0 on Windows. Mac Font Validator 2.0 will stay open after the file is loaded, but crashes as soon as I click a button. It works fine with 1.0.1286
RhodiumLibre-Regular.otf.zip

@HinTak
Copy link
Owner

HinTak commented Aug 6, 2016

Hmm, that's unusual. It works here on linux, your file is not even that interesting. does it help if you use the net2 binary instead?

https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font%20Validator/FontVal-2.0.0-bin-net2.zip/download

One possibility is that the mac binary was built from the net4 one, and there is something wrong with that one - though I can't see how (yet), since I did use it as it was for mac.

Anyhow, if you are interested in the warnings/errrors from that font file, here they are:

W   | W0022 | Recommended table is missing
        DSIG
W   | W0020 | Tables are not in optimal order
        table 'maxp' precedes table 'head'
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[2]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[28]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[29]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[30]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[31]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[32]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[33]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[42]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[43]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[267]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[268]
E   | E5700 | The LookupFlag reserved bits are not all set to zero
        LookupList, Lookup[269]
W   | W2106 | The version number is valid, but less than 5
        3
W   | W2117 | The value of sTypoAscender minus sTypoDescender is greater than unitsPerEm
        sTypoAscender = 1152, sTypoDescender = -532
W   | W2101 | A CodePage bit is set in ulCodePageRange, but the font is missing some of the printable characters from that codepage
        bit #29, Mac character set (missing chars: UFB01 UFB02)
W   | W1305 | The lowestRecPPEM value may be unreasonably small
        lowestRecPPEM = 3

@HinTak
Copy link
Owner

HinTak commented Aug 6, 2016

BTW, is there any crash messages? On windows, there should be a pop up - from the OS.

On mac it might be a bit harder, but FontVal 2.0 keeps a log of itself in /tmp or /var/tmp/ of the form ".FontVal.log". The precise name I don't have it with me, but the name should contain both FontVal and a number . Minor details: the number is the process id, just so it is a different log for different runs - normally only the most recent one is of interest, if something bad happens. /var/tmp is wiped by the OS on reboot, so it does not leave a mess behind.

@DunwichType
Copy link
Author

Thanks. I’ll do some more testing on Monday and let you know what happens
and send you any log files. I can also try it on Linux if there’s a distro
that can run it it without me having to start compiling and installing
stuff (dependency hell drives me crazy).

On Sat, Aug 6, 2016 at 4:13 PM, HinTak notifications@github.com wrote:

BTW, is there any crash messages? On windows, there should be a pop up -
from the OS.

On mac it might be a bit harder, but FontVal 2.0 keeps a log of itself in
/tmp or /var/tmp/ of the form ".FontVal.log". The precise name I don't have
it with me, but the name should contain both FontVal and a number . Minor
details: the number is the process id, just so it is a different log for
different runs - normally only the most recent one is of interest, if
something bad happens. /var/tmp is wiped by the OS on reboot, so it does
not leave a mess behind.


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

Best,

James Puckett

@HinTak
Copy link
Owner

HinTak commented Aug 7, 2016

On Fedora Linux 24, you should not need to compile anything. You may need to install stuff to run. I think you should be able to get all the runtime dependencies with:

sudo dnf install -y mono\* libgdiplus\* webkit-sharp gtk-sharp2

After this, you should be able to just unzip

https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font%20Validator/FontVal-2.0.0-py-bin-net4.zip/download

somewhere, then, depend on your inclination, to launch the GUI and click away:

mono where_you_unzipped/bin/FontVal.exe

or just running the command-line tool against one of your fonts and display the outcome right away:

mono where_you_unzipped/bin/FontValidator.exe -file yourfont.otf -stdout

the rasterization test (for truetype fonts only) depends on a customized version of freetype, so you haven't lost anything. The system's freetype is sufficient to do the rest.

@HinTak
Copy link
Owner

HinTak commented Sep 5, 2016

It has been a month - have you managed to figure out what's wrong?

@HinTak
Copy link
Owner

HinTak commented Feb 9, 2017

@DunwichType - any follow up on your issue? FWIW, the I made two newer snapshot builds (the two most recent here, look at the date column) - for windows:

https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font%20Validator/misc/

These might behave differently. Although ideally I'd like to understand how the 2.0 release didn't work on your system.

@HinTak
Copy link
Owner

HinTak commented Jul 16, 2017

@DunwichType - did you get to the bottom of the issue? Anyway, v2.1 is out in a couple of weeks, so I'll just close this unless you have a better idea or more information. Hope you have better luck with v2.1.

@HinTak HinTak closed this as completed Jul 16, 2017
@HinTak HinTak reopened this Aug 17, 2017
@HinTak
Copy link
Owner

HinTak commented Aug 17, 2017

I have another report which seems to suggest the 64-bit windows backend is buggy, but only cause problems for some fonts.
This is a slight variant build of v2.1 which runs in 32-bit mode even on 64-bit host. @DunwichType

https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font%20Validator/misc/FontVal-2.1.0-py-bin-net4-x86.zip/download

@HinTak
Copy link
Owner

HinTak commented Nov 18, 2018

Issue likely the 64-bit windows one; the mac one, XIM? The latter is avoided with Georg's GUI.

@DunwichType : Leave a comment if still a problem with 2.1.2

@HinTak HinTak closed this as completed Nov 18, 2018
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