Re: [NTG-context] pk-directory
![](https://secure.gravatar.com/avatar/ab73c799733cb79686500b0adbf33bb8.jpg?s=120&d=mm&r=g)
On 27 Mar 2010 at 12:00, ntg-context-request@ntg.nl wrote:
That being said, I realize that it means Metafont fonts can't be used in Mark IV, am I right?
Dumping a ready-made pk file in the local directory worked last time I tried it.
No success! Neiter *.pk nor *.600pk and not with a local subdir /dpi600 What extension have you used? Is there a debug-switch which informs the user what and where luatex is searching? Wolfgang
![](https://secure.gravatar.com/avatar/a0f6b595b0e3b7f3abba19eeb8261fc2.jpg?s=120&d=mm&r=g)
Is there a debug-switch which informs the user what and where luatex is searching?
If you're working in a shell, try setting the KPATHSEA_DEBUG environment variable to -1, you will get tons of information about path lookups and directory searches. Arthur
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Wolfgang Werners-Lucchini wrote:
On 27 Mar 2010 at 12:00, ntg-context-request@ntg.nl wrote:
That being said, I realize that it means Metafont fonts can't be used in Mark IV, am I right? Dumping a ready-made pk file in the local directory worked last time I tried it.
No success! Neiter *.pk nor *.600pk and not with a local subdir /dpi600
What extension have you used?
.600pk (but that was ages ago, when I still cared about pk fonts) Best wishes, Taco
participants (3)
-
Arthur Reutenauer
-
Taco Hoekwater
-
Wolfgang Werners-Lucchini