10-31-2018, 11:12 PM
(10-29-2018, 09:12 AM)rich2005 Wrote:Quote:..the issue is only affecting fonts whose names end with weight=101...I think that is going to be difficult to solve.
Looking at the situation before updating to Gimp 2.10.6.
The fonts were working. Then the fonts do not work. What changed?
Not Gimp, so you need to look at any Windows updates or additional software installed. Something interfering with Gimp.
Then there is the form of the font name as it appears in Gimp. I have never come across anything like FONTNAME weight = 101. Although I do have a font 'family' that refers to the weight in the font name.
Are these regular ttf or otf fonts installed in the Windows fonts folder? I could not find those as free fonts. Assuming they are commercial and not able to give them a try-out, or are they from some service such as Typekit?
If I had this problem, I would change the internal font name using FontForge (No good just renaming the font file). Put the font in the Gimp fonts folder (where most decorative fonts should be anyway) and check if working.
Hello! Just view this post--these last days, Gimp has begun to append weight = 101 to some of my fonts, as shown:
However:
- Yesterday, weight = 101 appeared in the name of some installed (windows) fonts (MSwhatever weight = 101 )
- Today, it has disappeared there, and only persists in some fonts in Gimp's fonts folder (not installed).
So, I suspect
- one of Windows updates of having messed up the fonts configuration
- a later one to have solved it, and that has corrected whatever messed fontconfig for that folder
- the chaged in names persists for Gimp's font folder, but as it doesn't seem to affect the rendering of the fonts in question, I am ready to wait for a further run of fontconfig to mend that bit of trouble...
Hope this helps.