How did you extract the font that it came out in an SFNT container?
I would not expect an SFNT given those /Font and /FontDescriptor objs.
Is the pdf itself available?
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6
___
Hi,
The font was extracted by dumping the stream with 'peepdf'.
peepdf project: https://code.google.com/p/peepdf/
dumpstream patch: https://code.google.com/p/peepdf/issues/detail?id=6
The PDF is available at: http://derp.ltd.uk/borked-font.pdf
Regards,
- Harry
On 11 November 2012
HR == Harry Roberts ha...@midnight-labs.org writes:
HR The font was extracted by dumping the stream with 'peepdf'.
HR The PDF is available at: http://derp.ltd.uk/borked-font.pdf
I was curious whether the font was embedded into the sfnt by the
extractor, but it was not. It already claims to
After some digging it seems it's Acrobat X 'Optimization' stage that's
causing the problems, and *not* Enfocus Pitstop (my apologies there).
Attached is another weird font file (ZDIWMH+BodoniXT' that even FontForge,
Acrobat Reader 9.5 and Poppler 0.20.5 refuse to open.
I have a feeling that the
Recently I have come across many fonts embedded within PDF files which
cannot be loaded by FreeType v2.4.10.
I suspect Enfocus PitStop is mangling the fonts when the PDF file is
'optimized'.
Attached is the font file (extracted from a PDF) and test case.
Adobe Acrobat and Photoshop are able to
Thank you for providing a sample.
For first, please let me comment to your question why. An OpenType
embedded in PDF should not be expected to be usable as a self standing
OpenType font. It is a component of PDF, and some essential information
are removed (because the identical or substitution
Here is a preliminary patch to permit a font WITHOUT essential tables,
if its header declares CFF/OpenType (by OTTO tag) and CFF table is
included.
This patch does not use cmap table, it uses the character-glyph mapping
info (Encoding dict) in CFF table. It is NOT expected behaviour, because
BTW, in my understanding, the font embedded by sfnt-container with
OTTO tag is introduced to use its cmap table, so, when
CFF is included and cmap is not, it should be taken as invalid font
(if we focus about PDF). If the PDF generator do not want to use
cmap in embedded CFF/OpenType, it should
Here is a preliminary patch to permit a font WITHOUT essential
tables, if its header declares CFF/OpenType (by OTTO tag) and CFF
table is included.
Hmm, the demo font works without this your patch.
This patch does not use cmap table, it uses the character-glyph
mapping info (Encoding dict)
