[NTG-context] Error concerning "pdfmapline"

Rudolf Bahr quasi at quasi.de
Fri Apr 19 21:22:03 CEST 2019


On Fri, Apr 19, 2019 at 09:19:24AM +0200, Hans Hagen wrote:
> On 4/18/2019 8:37 PM, Wolfgang Schuster wrote:
> 
> > 2. Use a font in Truetype/Opentype format:
> > http://unifraktur.sourceforge.net/
> Which is actually a quite nice and even readable fraktur.
> 
> Hans


Yes, perhaps. In the next days I will have a look at it. What do you mean with
"even readable"? Of course the font should be readable, not only to me.

During the last days I tried "1. Use the Type1 version of the fonts: [1], proposed by
Wolfgang. There a pair of .afm and .pfb files is needed by "new" ConTeXt and I got
an "even unreadable" fraktur with plenty of errors. See appended "Fraktur-afm-pfb.pdf". 

My MWE to this has been:

--------------------------------------------------------------------------------
\definefontsynonym [Fraktur] [name:yfrakregular] [features=default]

\definefont [BalladenFont]  [Fraktur at 12pt] [.75]

\def\b{\hskip3pt}

\starttext

{\BalladenFont
\char 020, \char 021, \char 022, \char 023, \char 024, \char 025, \char 026, \char 027, \char 028, \char 029,\\
\char 030, \char 031, \char 032, \char 033, \char 034, \char 035, \char 036, \char 037, \char 038, \char 039,\\
\char 040, \char 041, \char 042, \char 043, \char 044, \char 045, \char 046, \char 047, \char 048, \char 049,\\
\char 050, \char 051, \char 052, \char 053, \char 054, \char 055, \char 056, \char 057, \char 058, \char 059,\\
\char 060, \char 061, \char 062, \char 063, \char 064, \char 065, \char 066, \char 067, \char 068, \char 069,\\
\char 070, \char 071, \char 072, \char 073, \char 074, \char 075, \char 076, \char 077, \char 078, \char 079,\\
\char 080, \char 081, \char 082, \char 083, \char 084, \char 085, \char 086, \char 087, \char 088, \char 089,\\
\char 090, \char 091, \char 092, \char 093, \char 094, \char 095, \char 096, \char 097, \char 098, \char 099,\\
\char 100, \char 101, \char 102, \char 103, \char 104, \char 105, \char 106, \char 107, \char 108, \char 109,\\
\char 110, \char 111, \char 112, \char 113, \char 114, \char 115, \char 116, \char 117, \char 118, \char 119,\\
\char 120, \char 121, \char 122, \char 123, \char 124, \char 125, \char 126, \char 127, \char 128, \char 129,\\

\vskip2\lineheight

Victor's: Sohn jagt zw*olf Boxk*ampfer quer *uber den Sylter Deich.

\vskip\lineheight

Victor's\b Sohn\b jagt\b zw\"olf\b Boxk\"ampfer\b quer\b \"uber\b den\b Sylter\b Deich.
}

\stoptext

----------------------------------------------------------------------------------------


Now, in the meantime, I had also a look into your book [2]
There is to be read: 

"Most natural is to use OpenType or Type1 fonts. In the case of Type1 a matching pair
of afm and pfb files is needed. However, there can be situations where there is only
a tfm and pfb file (or not even that: just a bitmap file)."

What do you mean with that? Will "new" ConTeXt be capable in mastering a situation with 
"only a tfm and pfb file" as "old" ConTeXt did? 
With "old" ConTeXt I had with "yfrak.mf, yfrak.pfb, yfrak.tfm", a wonderfull Fraktur,
without errors.

Rudolf

[1] https://ctan.org/tex-archive/fonts/ps-type1/yfonts
[2] http://pragma-ade.com/general/manuals/fonts-mkiv.pdf, page 60, chapter 4.6 
    ("Old fuzzy fonts")
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Fraktur-afm-pfb.pdf
Type: application/pdf
Size: 24697 bytes
Desc: not available
URL: <http://mailman.ntg.nl/pipermail/ntg-context/attachments/20190419/e07a3e08/attachment-0001.pdf>


More information about the ntg-context mailing list