Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GSF2PK failed on postscript font #428

Closed
1 task done
mtreuden opened this issue Dec 3, 2019 · 1 comment
Closed
1 task done

GSF2PK failed on postscript font #428

mtreuden opened this issue Dec 3, 2019 · 1 comment
Assignees
Projects
Milestone

Comments

@mtreuden
Copy link

mtreuden commented Dec 3, 2019

I have a certain postscript font for which Yap won't generate PK fonts. The problem appears to be that the program miktex-makepk.exe passes the option --miktex-disable-maintenance to gsf2pk.exe, which always fails since that option is unknown to gsf2pk.exe. Taking a standard font that comes with MiKTeX, for instance, the command

gsf2pk.exe --miktex-disable-maintenance utmb8r NimbusRomNo9L-Medi "TeXBase1Encoding ReEncodeFont" 8r.enc utmb8a.pfb 1000 utmb8r.pk

fails while

gsf2pk.exe utmb8r NimbusRomNo9L-Medi "TeXBase1Encoding ReEncodeFont" 8r.enc utmb8a.pfb 1000 utmb8r.pk

produces the PK font file. So, in my case, one work-around is to use gsf2pk.exe to manually generate all the PK fonts one at a time. I would much prefer the PK fonts to be automatically generated, however.

Based on examining miktex-makepk.log, I wonder if there should be a miktex-gsf2pk.exe that miktex-makepk.exe calls which allows the --miktex-disable-maintenance option (similar to miktex-makemf, miktex-ttf2pk, and miktex-ps2pk.exe).

Remark: I realize that most people compile directly to PDF files, and my problem font does work when pdfLaTeX is used to obtain a PDF file, or when DVIPS is used to obtain a PS file from the DVI file. Nevertheless, if it is not too much trouble, I would appreciate it if the issue is fixed.

MiKTeX Report.txt

@edocevoli edocevoli self-assigned this Dec 3, 2019
@edocevoli edocevoli added this to the 2.9.7300 milestone Dec 3, 2019
@edocevoli edocevoli added this to To do in What's next via automation Dec 3, 2019
@edocevoli edocevoli moved this from To do to In progress in What's next Jan 25, 2020
@edocevoli
Copy link
Member

This has been fixed.

What's next automation moved this from In progress to Done Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
What's next
  
Done
Development

No branches or pull requests

2 participants