Howdy, Stranger!
Categories
- All Categories
- 39 Introductions
- 3.6K Typeface Design
- 764 Font Technology
- 1K Technique and Theory
- 589 Type Business
- 435 Type Design Critiques
- 527 Type Design Software
- 30 Punchcutting
- 132 Lettering and Calligraphy
- 79 Technique and Theory
- 53 Lettering Critiques
- 461 Typography
- 289 History of Typography
- 111 Education
- 61 Resources
- 479 Announcements
- 74 Events
- 104 Job Postings
- 147 Type Releases
- 153 Miscellaneous News
- 259 About TypeDrawers
- 52 TypeDrawers Announcements
- 109 Suggestions and Bug Reports
Options
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