You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
@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.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 thegenFontmap.vbs
.Originally posted by @ivankokan in #626 (comment)
The text was updated successfully, but these errors were encountered: