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

Feature proposal: Automate updating the Fontmap.MiKTeX (ghostscript package) upon update of every other package (server-side) #658

Open
ivankokan opened this issue Nov 7, 2020 · 4 comments
Labels

Comments

@ivankokan
Copy link
Contributor

ivankokan commented Nov 7, 2020

Have you considered to include updating the associations within the "Refresh font map files" action?

@edocevoli Actually, my original idea about "Refresh font map files" will not do: Although MiKTeX knows about all *.pfb file resources (package-manifests.ini), it does not know anything about the underlying font specified by /FontName if the file/package is not really installed - at least not until something like the "font manifests" is implemented.

That's not possible at the moment. Mainly because the script (genFontmap.vbs) is not portable across supported platforms.

On the other hand, having Fontmap.MiKTeX up-to-date is feasible from the MiKTeX's point of view (i.e. it can be automated when you prepare any updates). To achieve this, genFontmap.vbs could be rewritten in any other scripting language (supported on the servers you use to prepare updates) with the assumption that all packages (or those having *.pfb file resources, at least) are present. Please let me know which scripting language is appropriate and I will rewrite the genFontmap.vbs.

Originally posted by @ivankokan in #626 (comment)

@stale
Copy link

stale bot commented Jan 7, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 7, 2021
@stale stale bot removed the wontfix label Jan 7, 2021
@ivankokan
Copy link
Contributor Author

Please let me know which scripting language is appropriate and I will rewrite the genFontmap.vbs.

I am still interested to help with this one.

@ivankokan
Copy link
Contributor Author

On the other hand, having Fontmap.MiKTeX up-to-date is feasible from the MiKTeX's point of view (i.e. it can be automated when you prepare any updates). To achieve this, genFontmap.vbs could be rewritten in any other scripting language (supported on the servers you use to prepare updates) with the assumption that all packages (or those having *.pfb file resources, at least) are present. Please let me know which scripting language is appropriate and I will rewrite the genFontmap.vbs.

Originally posted by @ivankokan in #626 (comment)

I am still interested to contribute with this one.

@edocevoli
Copy link
Member

Thank you. For me it seems that the script would very generic (not MiKTEX-specific). Maybe it would be worth to contribute it to CTAN (/support/...)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants