Here actually are two questions and one side effect(?), and I haven’t found them here in full detail so I’ll post it all and come what may.
1. I took the entire DejaVu fonts (the latest, 2.37 of 2016) collection and unpacked all the fonts into a folder, let’s say, C:\my\fonts\d. (d for DejaVu: I planned to unpack a great many fonts to other subfolders nearby.) Then I right-clicked on the whole bunch of font files and selected Install as shortcut for all users. Fonts now are installed in the system, they can be found in the font picker in MS Word, or GIMP, or in a system Fonts folder, but Inkscape’s font picker doesn’t list them. If I manually write font name like DejaVu Sans, it shows red strikethrough.
2. I unpacked several other font families to subfolders nearby, like Roboto all in C:\my\fonts\rob etc.. Then I opened Inkscape preferences, went to the tab Text and entered into Additional font directories both the parent folder C:\my\fonts and all the individual subfolders, for a great measure. I ensured the settings are still there on the next launch of Inkscape, but the fonts are missing from the font picker, as in the first case. If I write a font name from this bunch, it’s the same red strikethrough too. (Also the folder itself is okay, as GIMP sees fonts in it when configured accordingly.)
3. But surprisingly, the font applies to the text if used! (See the screenshot.) So in principle it’s alright but very uncomfortable to work with (no font preview in the font dialog either). This means Inkscape is very able to load fonts from my folder (and DejaVu fonts are loaded either from the folder or from the installed system shortcut) but somehow is not “consciously aware” of them. This behavior puzzles me, maybe you know what to make of it and if it’s fixable without having to install all the fonts into the system (I’d prefer not to do that, there are too many and it’s easier to manage them “the folder way” even if using a font manager.)
This all is on win10 Pro x64 (version 2004, build 19041.572), Inkscape 1.0.1 (3bc2e813f5, 2020-09-07), installed via the x64 installer.
@TylerDurden Thanks! Now that I have finally read into those issues, I see the first one is closely related, so I commented right there. Let’s hope it’s easy to resolve!
UPD: If anybody has the same issue, after reading more there yesterday, I may advice downgrading to 1.0 for a while. That version handles custom font directories okay!
Beginners' Questions Another topic about font issues
Inkscape.org
Here actually are two questions and one side effect(?), and I haven’t found them here in full detail so I’ll post it all and come what may.
1. I took the entire DejaVu fonts (the latest, 2.37 of 2016) collection and unpacked all the fonts into a folder, let’s say,
C:\my\fonts\d. (dfor DejaVu: I planned to unpack a great many fonts to other subfolders nearby.) Then I right-clicked on the whole bunch of font files and selected Install as shortcut for all users. Fonts now are installed in the system, they can be found in the font picker in MS Word, or GIMP, or in a system Fonts folder, but Inkscape’s font picker doesn’t list them. If I manually write font name likeDejaVu Sans, it shows red strikethrough.2. I unpacked several other font families to subfolders nearby, like Roboto all in
C:\my\fonts\robetc.. Then I opened Inkscape preferences, went to the tab Text and entered into Additional font directories both the parent folderC:\my\fontsand all the individual subfolders, for a great measure. I ensured the settings are still there on the next launch of Inkscape, but the fonts are missing from the font picker, as in the first case. If I write a font name from this bunch, it’s the same red strikethrough too. (Also the folder itself is okay, as GIMP sees fonts in it when configured accordingly.)3. But surprisingly, the font applies to the text if used! (See the screenshot.) So in principle it’s alright but very uncomfortable to work with (no font preview in the font dialog either). This means Inkscape is very able to load fonts from my folder (and DejaVu fonts are loaded either from the folder or from the installed system shortcut) but somehow is not “consciously aware” of them. This behavior puzzles me, maybe you know what to make of it and if it’s fixable without having to install all the fonts into the system (I’d prefer not to do that, there are too many and it’s easier to manage them “the folder way” even if using a font manager.)
This all is on win10 Pro x64 (version 2004, build 19041.572), Inkscape 1.0.1 (3bc2e813f5, 2020-09-07), installed via the x64 installer.
This may be related to a couple of reported bugs:
https://gitlab.com/inkscape/inkscape/-/issues/1977
https://gitlab.com/inkscape/inkscape/-/issues/1178 (closed)
You could post a new report and see if the Devs think it is the same as one of the above. https://gitlab.com/inkscape/inkscape/-/issues
@TylerDurden Thanks! Now that I have finally read into those issues, I see the first one is closely related, so I commented right there. Let’s hope it’s easy to resolve!
UPD: If anybody has the same issue, after reading more there yesterday, I may advice downgrading to 1.0 for a while. That version handles custom font directories okay!