Font Book's secret: "Save Report" will help you finding what's wrong with the font validation
Joël Galeran
Posts: 1
Hi!
I just discovered this not too long ago...
I searched for something like this before, but nobody was talking about it so I'm posting it here as it looks like nobody knows...! I hope you'll like it.
The report is in fact a simple ".plist" that can be opened in text mode or with Xcode.
It can help figuring out why the validation didn't pass but it is complimentary with `ftxvalidator` that is a lot more verbose.
I just discovered this not too long ago...
I searched for something like this before, but nobody was talking about it so I'm posting it here as it looks like nobody knows...! I hope you'll like it.
- Open the font with the Font Book app
- "Install"
- Wait for the validation error message
- Menu: "File" > "Save Report..."
The report is in fact a simple ".plist" that can be opened in text mode or with Xcode.
It can help figuring out why the validation didn't pass but it is complimentary with `ftxvalidator` that is a lot more verbose.
8
Comments
-
Wonderful, thanks! Also be aware that some of those results seem to get cached pretty deeply, so reinstalling fonts seems to not always update changes in this preview (not sure about the actual report you pointed out), although a new file version might actually fix an issue.0
-
Also, I couldn't find this link about fixing font caching issues when I was replying, but thought of it - and now found it.0
Categories
- All Categories
- 43 Introductions
- 3.7K Typeface Design
- 803 Font Technology
- 1K Technique and Theory
- 622 Type Business
- 444 Type Design Critiques
- 542 Type Design Software
- 30 Punchcutting
- 136 Lettering and Calligraphy
- 83 Technique and Theory
- 53 Lettering Critiques
- 485 Typography
- 303 History of Typography
- 114 Education
- 68 Resources
- 499 Announcements
- 80 Events
- 105 Job Postings
- 148 Type Releases
- 165 Miscellaneous News
- 270 About TypeDrawers
- 53 TypeDrawers Announcements
- 116 Suggestions and Bug Reports