System.FormatException in head table (E0041) about font-validator HOT 7 OPEN

The version string is "1.0 ", which has an extra space but not unusual.

As for the 2.1 crash message, that's a strange feature of the microsoft code - it deletes the incomplete report whenever anything goes wrong. Unfortunately, when doing so, it can occasionally get confused when one part of it is still holding on while the other tries to delete (on multi-CPU systems); and thus making whatever problem it encounters seems worse. But it is a same issue with number parsing.

I think that's all the information needed. You could try changing to US/UK locale, but it is probably not worth the trouble. You had a good report from me anyway. If anybody else wants to investigate further, please feel free.

(I am just maintaining a "community fork" - has no relationship with microsoft, and do not represent them in any way at all).

from font-validator.

What is your expectation for how Font Validator should behave? Extracted font streams from pdf's are, by their own very nature, not well-formed or complete font files. It often just has the minimum amount of information to make pdf work, to keep the pdf file size small.

from font-validator.

With several tools that I test the head table for this font seems ok. also the version number and revision.
According to the specs, the revision number is Fixed type and defined by the manufacturer.

Fixed | fontRevision | Set by font manufacturer.

So I don't expect to see some kind of call stack in font validator for that number that seems ok.

I agree that embedded fonts in pdf not always contain all data, but the top part of the head table to me looks valid.
(If not, I would like to learn why not).

from font-validator.

I am not keen on find out why it was broken, but it works fine now. Please use v 2.1 from here:
https://github.com/HinTak/Font-Validator/releases
and remember to donate if you find it useful.

This is the output.
IFOEGC+LucidaGrande-Bold.ttf.report.zip

from font-validator.

Oh I was still using the font validator version 1.0.1286.23890 from the MS typography website...

v2.1 crashes when validating the font:

Application: FontVal.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
at System.IO.__Error.WinIOError(Int32, System.String)
at System.IO.File.InternalDelete(System.String, Boolean)
at System.IO.File.Delete(System.String)
at FontVal.Progress.DeleteTemporaryFiles(System.Collections.Generic.List`1<System.String>)
at FontVal.Progress.OnException(System.Exception)
at OTFontFileVal.Driver.RunValidation(OTFontFileVal.Validator, System.String[])
at FontVal.Progress.Worker()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

from font-validator.

from font-validator.

Windows 10 Pro x64 (English)

Control Panel\Clock, Language, and Region\Language:

• Nederlands (België)
  Keyboard layout: Belgian (Period) (Date, time, and number formatting)

Control Panel\Clock, Language, and Region:

• Region -> Format: Dutch (Belgium)

from font-validator.