# OTF installation - error - files must be included entirely

Argh! Maybe the fonts I got are useless? I got a set of OTF fonts and am trying to install them for use with MikTeX pdflatex. (Yes I know about XeTeX and LuaTeX and that it could be easier with them. Unfortunately, for various reasons, we're using pdflatex.)

When I use the work flow described here, How do I use TrueType Fonts with PDFTeX using otftotfm? (modified for MikTeX 2.9), I get the following error message when compiling with pdflatex:

``````'OTF Files must be included entirely'
``````

Is there something I need to do to insure the entire OTF file is included? (I thought pdflatex only embeds those glyphs discovered in the document?)

p.s. I found this old old link, http://tug.org/pipermail/pdftex/2003-January/003412.html and not much else when googling/and searching here. I doubt I'm the only person experiencing this. Can it be I'm using sub-optimal keywords?

• What is the content of the map-file created by the workflow? – Ulrike Fischer Nov 11 '14 at 10:28
• '% Automatically maintained by otftotfm or other programs. Do not edit.' 'berkeleystd-book--lcdfj BerkeleyStd-BookLCDFJ "" <BerkeleyStd-BookLCDFJ.pfb' 'berkeleystd-book--base BerkeleyStd-Book "AutoEnc_5yjl5y33w6e7fvg5fphscaz2jd ReEncodeFont" <[a_5yjl5y.enc <berkeleystd-book.otf' – infowanna Nov 11 '14 at 13:22
• `<<BerkeleyStd-BookLCDFJ.pfb` should do full inclusion. – egreg Nov 11 '14 at 13:23
• The second entry with .otf at the end should use `<<` instead of `<`. pdflatex can't subset otf-fonts. With the pfb `<` should be ok. – Ulrike Fischer Nov 11 '14 at 13:30
• Thanks - I still think the original font file has Problems. the pdflatex run completes and creates the pdf, but without a font. Now I get a slew of the following line (with various characters) 'Missing character: There is no e in font T1-berkeleystd-book--lcdfj! Missing character: There is no t in font T1-berkeleystd-book--lcdfj! Missing character: There is no e in font T1-berkeleystd-book--lcdfj! Missing character: There is no r in font T1-berkeleystd-book--lcdfj! – infowanna Nov 11 '14 at 13:44

## 1 Answer

As egreg and Ulrike commented, using two greater-than signs

``````'<<'
``````

got rid of the offending error message that I asked about.

(I still have Problems with using the fonts, but thats due to other Problems - probably with the font files themselves.)

• egreg and Ulrike provided the answer in the comments above- if any up-votes are assigned, click up there. I only noted that their Suggestion(s) worked. – infowanna Nov 13 '14 at 10:32