Hans Hagen wrote:
\def\loadmapline
{\dodoubleempty\loadmapline}
\def\loadmapline[#1][#2]%
{\loadallfontmapfiles % ! ! !
\doloadmapline{#1}{#2}}
I'd be surprised if that worked. The second \def overwrites the first.
Christopher
___
ntg-context
Christopher Creutzig wrote:
Hans Hagen wrote:
\def\loadmapline
{\dodoubleempty\loadmapline}
\def\loadmapline[#1][#2]%
{\loadallfontmapfiles % ! ! !
\doloadmapline{#1}{#2}}
I'd be surprised if that worked. The second \def overwrites the first.
it did when i tested it with two args -)
Hi Stefan,
Stefan Wachter wrote:
Hi all!
Fonts are driving my crazy! I have the following document that clearly
states that the font encoding should be ec. Yet, somewhere behind the
scenes the ec-encoded font uhvr8t is mapped into the 8r-encoded font
uhvr8r.
Can someone reveal this deep
Taco Hoekwater wrote:
Can someone reveal this deep secret?
The uhvr8t font is a virtual font, probably created by fontinst.
Can we create a section in the wiki where such nice explanations can go into?
Something: some details about how tex works
Stefan Wachter wrote:
Fonts are driving my crazy! I have the following document that clearly
states that the font encoding should be ec. Yet, somewhere behind the
scenes the ec-encoded font uhvr8t is mapped into the 8r-encoded font
uhvr8r.
\starttext
\def\loadmapline
Hi all!
Fonts are driving my crazy! I have the following document that clearly
states that the font encoding should be ec. Yet, somewhere behind the
scenes the ec-encoded font uhvr8t is mapped into the 8r-encoded font
uhvr8r.
Can someone reveal this deep secret?
Best regards,
--Stefan
PS: The
