There are two options for fonts with the same internal names on the desktop, plus to avoid the problem entirely, there is an approach to making font names unique, and some links to web-based test sites. When working this way, as best as I recall, in the past 10–15 years, I have only hit font caching problems once! I suspect that was just a failure to apply my method religiously enough. This applies to both Mac and Windows, and across all apps as well. Here are some approaches for reliably swapping versions of fonts that have the same internal names, to new versions. So if you are not having trouble, and you are swapping fonts some other way, good for you! But if you are having trouble, here are some more options. Note that latest versions of Adobe CC apps may recognize fonts swapped on the fly. The app you are using a font in may sometimes still display/use the old version, even though you replaced it! So for people who need to be absolutely sure they are getting the new version, here are some options. # External function that builds a list of all valid font files in input_pathįont.ulCodePageRange1 = ulCodePageRange1įont.ulCodePageRange1 = ulCodePageRange2įont.For people who design fonts, swapping versions of your font can be a problem, as your operating system or apps have font caches which may become confused when you replace your fonts on the fly. SCapHeight=0, usDefaultChar=0, usBreakChar=32, usMaxContext=2):
I ignore if there's a way to recalculate values as ulCodePageRange1 and ulCodePageRange1.ĭef set_os2_v4(input_path, ulCodePageRange1=0, ulCodePageRange2=0, sxHeight=0, If the version number is just changed without adding the supplementary fields, FontTools (not TTX) doesn't save the font at all, but prints the name of the first missing field and exits.ĭoesn't seem an easy thing to do, unless you know the values of those fields so to pass them as parameters.
0 kommentar(er)
