How To Install All Fonts At Once

0 views
Skip to first unread message

Violette Taps

unread,
Aug 5, 2024, 1:14:19 AM8/5/24
to tiocontfunclen
WellI did search through AskUbuntu and found some threads where people are asking about how can they install multiple fonts at once? I know the process. I have to copy-paste all the fonts, .ttf/.otf files inside of .font hidden folder and then rebuild the font cash via this command...

I downloaded 10+ .zip font files. When I extracted the .zip folders I see within each folder there are couple of files. A readme file, a .ttf/.otf file and in some cases some variants of the fonts. Like bold.ttf, ultra_bold.ttf, semi_bold.ttf, black.ttf etc. I am not sure what these additional files are but I guess these are mainly variants of the core fonts. However my question is...


Do I need to extract all the .zip files manually and then copy only .ttf/.otf files and then paste them manually in .font folder? Or I can use a terminal command which will do everything on behalf of me. Here by the word everything I meant...


I just switched over from Windows to Linux Mint. However, as I do web design, there are many fonts on my Windows hard disk that I would want to carry over to my Linux installation.It is possible to install fonts by double-clicking them from within a file manager and then pressing the 'install' button, but this only works for one font at a time.


Also it may be possible that non true type fonts don't display properly in Linux Mint as well as other types. I am guessing here and I could be totally wrong, but some of your fonts simply may not be compatible. Perhaps if you posted what fonts are not showing correctly others may be able to help further. Perhaps only a certain type is not working.


I have a collection of free fonts that I want to install on my Mac. But it is too tedious to double click every one of them and then click "Install font". Is there a quick way to do this? Like a certain context menu to "install all the fonts selected" or a terminal command.


While in Finder, hold option key and click on Go menu then choose Library. In Library, find Font folder, drag and drop the fonts into this folder. I keep my fonts organised into separate folders inside Font folder and the OS picks them up.


When you install fonts with the Font Viewer Install button, they end up in the User Fonts folder.

This was added in a Windows 10 update to enable users without admin rights to install fonts.

Always better to install fonts using Install for All Users if you can.


The issue "2.5.x Windows users missing fonts after updating" (REF: AF-3196) has been fixed by the developers in internal build "2.5.2.2483".

This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.

Customer beta builds are announced here and you can participate by following these instructions.

If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.


This is an old topic but it comes up on google searches a lot, and I can see the whole issue (and fix) is not completely explained. So I thought I'd sign in and try to do that. Sorry, this reply is really long, but I think it clears up pretty much ALL windows font-related issues like this. Problems like:


Thank you for the detail explanation, very helpful. I wonder why the average user has to engage in this bug fixing exercise of what it is a well known bug. Why Microsoft or Adobe are not addressing this issue to the root of the cause, or at least create a small App that take care of all above instructions with minimum fuss? I should probably direct this question to them. Thank you again.


I am having the same type problem, only I do not believe the fonts came from as Mac. As far as I know they are Windows fonts that appear to install in Windows/Fonts. But, they do now show up in InDesign. Any fixes?


Which particular fonts? You have another thread going that mentions Arial Narrow, and there is a known issue withthat and one or two other fonts supplied by Microsoft that have an internal error in the font name.


What I figured out is this - when you install a new font, windows copies the font file to the windows font folder, and at the same time updates a list of available fonts in the windows registry.


If the font doesn't exist in the windows font folder, but exists in the registry list, windows thinks it's installed. Even if it's not working anywhere, even if it's been moved or deleted from the windows font folder, windows considers it "installed" because it's on this list.


If the list has the font, but the list has incorrect info about the font's file name... like the list thinks it's called "font1.ttf" but the actual font file is called "font2.otf"... you can't use the font.


Also, the windows font folder gives you a weird specialized view of your files, which looks different from other folders. The actual filenames are replaced with the font name, so instead of seeing "times_0.ttf" you see "Times New Roman Regular". The listed fonts can act like "folders" that you can double click to see the full font family within. This 'special' font folder view is controlled by this hidden registry list. So let's say gotham-bold.ttf is in the windows font folder, but it's not in the registry list... gotham bold will NOT show in that special view of the font folder either. It's actually there in C:\windows\fonts\ , but you can't see it. And if you right click gotham-bold.ttf (from any folder) and choose install, you'll get that annoying error about it already being installed. Worse, even if you say "yes, replace it"... you still might not see the font appear in the folder.


That's how you end up with a ton of duplicate font files with names like font.ttf, font_0.ttf, font_1.ttf, whatever_0.otf, etc. If you are prompted to reinstall the font, and choose yes... windows won't overwrite the file, just create a renamed copy. So you might end up with 2-5 copies of the same font in your windows font folder, and these separately installed files can get listed twice in the registry too.


1. Open up an explorer window (e.g. by pressing the windows key + E) and at the top, click in the address bar and paste this: \\localhost\c$\Windows\Fonts ...this gives you a true, normal view of the windows font folder, where you see a complete list of the files within your windows font folder, with their actual filenames (e.g. "times.ttf"). Every variation is listed by its filename too, so times italic will be in there as maybe "times_it.ttf" and not combined with (or hidden by) other font names. You don't see the convenient previews and full font names, but you DO see a true, accurate list of your files without the registry list screwing things up by hiding some of them.


2. Click any font inside the folder, ctrl+A, ctrl+C to copy every font to the clipboard. Then make a new folder (let's call it fontbackup) and ctrl+V to paste all those font files into a backup folder. Now close the backup folder. That's important because you don't want to get the two folders confused.


3. Keep the original font folder open. Run regedit. If you're unsure about how to do that, I'll let you google that and see all the scary warnings about how you might break the computer if you're not careful. Within regedit, navigate to this "folder": HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Fonts


Once you click it, you should see a bunch of fonts listed on the right. Look for the font that's giving you trouble, click that item in the list (the "list" is actually a bunch of separate registry items called "values", one value per line) and tap delete on the keyboard. Be careful doing this, make sure it's the font you want to fix, not some other font with a similar name. It'll ask you to confirm deletion, say yes. Note it might be in the registry multiple times, so delete multiple values if necessary.


4. Go back to your font folder (make sure it's the "true view" of the font folder, as described in step 1). Find the file associated with your problem font. Note that sometimes the filenames are a little cryptic, like "Book Antiqua Bold Italic" might be called "ANTQUABI.TTF". You can always double click a file to see a preview and confirm it's the font you're looking for. You want to remove that font from the windows font folder completely, including any copies. So if you're removing Cooper Black, be sure to get cooperbk.ttf, cooperbk.otf, cooperbk_0.ttf, cooperbk_1.ttf, and so on. By "remove" I mean delete, which should be safe if you made a backup in step 2. If you're the cautious type though, you could also ctrl+X to cut a font from the folder, and then ctrl+V to paste it somewhere else, like your desktop.


5. Now that the font is removed in the registry and from your windows font folder, you can install it "fresh" in a way that won't give errors or problems. Find the font file and install it in the usual way (I like right click --> install). If you see a warning about "do you want to overwrite the existing font" that means you screwed up somewhere in step 3 or 4 and didn't remove the font from either the registry list, or the windows font folder. If you see no warning at all though, everything probably worked fine and you can start using the font immediately in Word, Photoshop, etc.


Optional but recommended - you can search for and delete a bunch of duplicates. This may slightly help with performance but mostly it's just to keep things tidy. The downside is that if you're careless or unlucky you might delete a windows system font. To be honest though I've actually done that, and it wasn't impossible to recover from. Still, it's a pain, so be careful.


Once the duplicate files are gone from the font folder, you also need to nuke them from that registry list. So you just go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Fonts and skim over it for any filenames (the data on the right) that end in _0, _1, _2, etc. ...then you delete those items from the list. Again, don't delete any system fonts like arial, times new roman, MS-anything, or any file named something.FON.

3a8082e126
Reply all
Reply to author
Forward
0 new messages