Oneway you can change the style of a document is by adding a new text font. To add a font to Word, download and install the font in Windows, where it will become available to all Microsoft 365 applications.
All fonts are stored in the C:\Windows\Fonts folder. Optionally, you can add fonts by simply dragging font files from the extracted files folder into this folder. Windows will then automatically install them. To see what a font looks like, open the Fonts folder, right-click the font file, then select Preview.
Edit: I can open the Properties dialog by right-clicking a single font (not a font family), but the files that cannot be opened due to the bad privileges, don't even show up in the font list.
I wanted to suggest an alternate fix. The UNC trick above works great, but annoyingly it won't let you use a popular tool for dealing with un-deletable files, Unlocker. (you can still run unlocker on a font file via the command prompt, but it's tedious)
If the registry has entries for fonts that don't exist, you'll get problems. If it has an entry, but the entry points to the wrong file, you'll get problems. And finally, if you have a font in your font folder, but it doesn't exist in that registry list... you'll get problems. So try to straighten out that registry list, which is pretty self explanatory if you're comfortable with the registry.
And by the way, that _0 at the end of the filename means that at some point, you tried to copy the font (or install it) to the windows font folder, and a copy was already there... windows won't overwrite the older font, it will put in a second copy with a new name ending in _0, and then _1, _2, etc. You might have several copies of old fonts that gave you problems in the fast, and if you're careful you can clean these up and fix their registry entries.
Using File Explorer to copy desktop.ini to c:\windows\fonts may not work if the Windows system refuses to allow the copy process, specificly because desktop.ini is not (according to Windows) a font file.
A Windows application can use the fonts to render content to a screen, allow that content to be edited, and allow that content to be output to a device, like a printer. Here are answers to common questions about using these fonts.
Some of the fonts supplied with Windows were created specifically for Microsoft by leading type designers and type design companies (known as font foundries). Other fonts were licensed to Microsoft from font foundries for inclusion with Windows.
Unless you are using an application that is specifically licensed for home, student, or non-commercial use, we do not restrict you from selling the things you print and make using the Windows-supplied fonts.
The brief answer:If an application follows the rules and restrictions defined in the OpenType or TrueType specification, you can use it to embed Windows supplied fonts in any document file it creates. For example, Microsoft Word and PowerPoint follow the rules and restrictions, so you can use these applications to create documents (such as Word documents, PowerPoint decks and PDFs) that include embedded fonts.
Font files contain flags that indicate if and how they can be embedded within a document file. Applications that support document font embedding look at these flags and determine if and how it may be embedded in a document file, and when they open a document containing embedded fonts, they will also look at these flags to determine if and how a document can be viewed or edited.
If the applications follow the rules and restrictions documented in the OpenType and TrueType font specifications around document font embedding, you are allowed to use them to embed the Windows-supplied font. Please check the documentation associated with the application and document file format to confirm it is compliant with the OpenType or TrueType specs.
No, converting Windows fonts to other formats does not change the rules around embedding or redistribution, and format conversion itself is not allowed. Many Microsoft supplied fonts are available for app and game licensing through the original font foundry or Monotype.
Yes, you can (provided you're using a product that is not specifically licensed for home, student or non-commercial use). The graphic file must be an image of a word, phrase or passage of text. Converting the font to a bitmap font (where each letter is treated individually) is not allowed.
Apart from the document embedding rights described previously, you may not redistribute the Windows fonts. You may not copy them to other computers or servers, and you may not convert them to other formats, including bitmap formats, or modify them.
In most cases you will need to upgrade Windows to get the latest font updates. Occasionally, font updates will be available via the download center, most commonly to add currency symbols to common document and UI fonts.
choosing the visual way (GUI). Reboot is required at this point.
2/ I navigated to my windows folder (C:\Windows), and created a link to the fonts folder. I moved that link into my Ubuntu home folder, and renamed the link to .fonts
Now all my windows fonts are available in LibreOffice (Ubuntu)
ttf-mscorefonts-installer is a classic example. Microsoft (M$) have open-sourced all the fonts available in their original versions of Windows (11 fonts in 30 versions). Very useful, especially if you distribute files between Linux & M$. Available within every distribution. Use standard techniques to install (I use Synaptic). Auto-puts everything in the right place.
Fontconfig-2.13.1 is the system/binary that controls all modern aspects of font maintenance & usage. You will never deal with it directly, but instead may use one of many small Apps directly related to it.
You don't need that .lst file. But you do need .pfb and .pfm files to go along with the .afm file (the pfb and pfm files have the same name as the .afm file). Place them in the same folder, then right-click the .pfm file and select Install. (In fact, you don't need the .afm file on Windows.)
Thanks for the reply. The other files I got with the .afm's and .lst's were very small files, not even 1KB, compared to the 16KB .afm's. I think the files she's given me haven't been exported properly/all the data isn't there.
I've been thinking that because my teacher is a notorious pro-Mac user. I guess I'll just grab a hold of a Mac for a while and see whether those fonts will be suitable, and if so, find a converter of some sort.
I decided to install the TTF fonts on one of my machines: the family desktop running Lubuntu 22.04. I followed one of the many articles on the Web regarding installing TTF fonts in Ubuntu, but LibreOffice did not list the new fonts in its drop-down menu of fonts. It turned out I needed one more step in order to make the new fonts accessible: I needed to change the permissions of the TTF files that I had copied to the Linux fonts directory. Anyway, below I list all the steps I followed in order to install the new TTF fonts.
News and views of some obscure guy Replies continue belowRecommended for youconst urltitle=document.getElementsByTagName("title")[0];urlin = urltitle.innerHTML;urlout=urlin.substring(0, urlin.length - 11);console.log(urlout);new MoreLikeThis( text: [urlout], pubCodes: ["ENGCOM"], include: postTypes: ["post"], limit: 4 ,); RE: Viruses hidden in font files? smah (MIS)2 Aug 03 22:58I've never heard of a true font file being infected, because as you said, font definitions aren't executable. There are however virii that install themselves into the c:/windows/fonts directory, but they are .exe or .vbs files. Just make sure it doesn't have one of those double extentions like somefont.ttf.exe RE: Viruses hidden in font files? petey (Programmer)(OP)3 Aug 03 20:09Thanks for the reply, smah!
-Petey
News and views of some obscure guy googletag.cmd.push(function() googletag.display('div-gpt-ad-1406030581151-2'); ); Red Flag This PostPlease let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.
CancelRed Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.
My group has been asked to push a package of True Type fonts to our Windows 10 users. I found a script in a knowledge base article in Quest support that says it should do this but I have been unable to get it to work. I am able to successfully copy the font files to the local computer but the "Install" for the fonts will not work.
if I export a file with text in a field (Arial Bold) as PDF the text is shown like character salad. If I use the Microsoft PDF printer or change the text to regular the exported PDF is showing correct.
The character salad looks like font cache corruption.
Note how the Arial-BoldMT Encoding says "Custom" - mine says "Identity-H" like the others.
That could be another indication of font cache corruption.
There are tutorials out there on clearing the Windows font cache.
If you are using a font manager it may also have its own font cache.
And APub has its own font cache - and I have not found a way to manually delete it.
Shutting-down APub and then installing/un-installing some fonts seems to trigger it to rebuild upon restarting APub.
That may work.
After that I downloaded the Arial fonts from the Microsoft TrueType core fonts at Sourceforge, unzipped the archives and copied the .ttf files into the WINDOWS/Fonts directory. After restart the Publisher the exported PDF is showing well. I think the fonts were destroyed.
Curious. I extractet the fonts directory from the install.wim of the installation iso. Then I copied the font files into the C:\WINDOWS\Fonts directory of my system. And the error is there again. Tomorrow I'll try to solve the error.
3a8082e126