Closed GoogleCodeExporter closed 9 years ago
I expected this report as well. :)
Apparently ISO/IEC JTC 1/SC34 are working on a new font top-level metatype. But
on
the other hand they also recognize "application/x-font-ttf" as being the
experimental (read: not standardized) de facto MIME type for Truetype fonts.
Number of Google hits for all three possibilities:
"application/x-truetype-font" 2100
"application/x-font-truetype" 4100
"application/x-font-ttf" 45900
So "application/x-font-ttf" it is. It beats the other two by an order of
magnitude. I know it's not an *official* standard, but it is a de facto one,
and even ISO/IEC JTC 1/SC34 recognizes it. So it should probably be enforced as
an industry best practice.
Original comment by Strahinja.Markovic@gmail.com
on 3 Oct 2010 at 9:52
But need it be an error? Can't it be just a warning? :)
Original comment by jel...@gmail.com
on 3 Oct 2010 at 9:58
Making it a warning would require special-casing this particular mimetype.
Besides, I think it should be an error. If the ISO/IEC JTC 1/SC34 recognizes it
as the "unofficial" standard and it's an order of magnitude more used than the
next contender, it's the mime that should be used.
Original comment by Strahinja.Markovic@gmail.com
on 5 Oct 2010 at 10:00
I am using Indesign to generate ePub. In the resource file all TTF fonts are
listed with the "application/vnd.ms-opentype" media type, but only the "Times
New Roman" font generates an error from FLight Crew.
I changed the property for the items listed and now there are no more errors.
Does this mean that the remainin TTF fonts are of type "Opentype" or is the
validator omitting an error for some reasons?
Thanks for a great product, Rolf
Original comment by RolfJack...@gmail.com
on 30 Nov 2012 at 1:27
Original issue reported on code.google.com by
jel...@gmail.com
on 3 Oct 2010 at 9:43