< Documentation | FAQ | General
Installing TrueType Fonts on Windows 7. The font selected is now installed. Confirm installation by opening your control panel. Open the “Fonts” folder. Installing fonts on Windows 7/2008 with a login script. Monday, June 27th, 2011| Uncategorized| Mike Smith It is possible using a simple VBS script to install fonts via a logon script on Windows 7 or Server 2008 operating systems.
How can I add fonts to OpenOffice?
OpenOffice uses the fonts that are installed in your system. Add new fonts using the Font management tools for your Operating System (for example in Microsoft Windows, you add new fonts via Control Panel > Fonts). You may need to restart OpenOffice (including the Quickstarter), to see the new fonts in the Font Name list box.
Retrieved from 'https://wiki.openoffice.org/w/index.php?title=Documentation/FAQ/General/How_can_I_add_fonts_to_OpenOffice%3F&oldid=238226'
Installing TeX fonts
This web page is about installing a font that has already beenprepared for use with TeX (typically pdftex and/or dvips). Using a fontthat did not come with your TeX distributionrequires several steps. Before we go into those details, consider thesetwo alternatives:
- If the font can be made generally available on your computer (e.g.,to other word processing programs), you can use XeTeX or LuaTeXto access it directly, without any TeX-specific installation at all.
- If the font is one of several nonfree families, you can run thegetnonfreefonts program. Rungetnonfreefonts --lsfonts to see the list of fonts it caninstall. (This script essentially performs the steps below.)
Also, this web page doesn't try to cover everything (it's alreadyplenty complicated). Limitations:
- This web page is not about the work of preparing the support files.That is a much more complicated job; see the brief list of utilities here and the vast andgeneral FontInstallation Guide and Fontinst documentation forstarters, if you want to delve into that.
- This web page is about installing fonts in a system-wide directory.If you don't have permission or don't want to do that, you'll have touse a personal directory (such as TEXMFHOME). Instructions forinstalling fonts in a personaldirectory are given separately.
The TUG fonts page has references to fontscommonly used with TeX, and general information on TeX font usage.
1. Destination texmf-local: your local TeX tree
The first step is to determine in what directory the new font willlive. You can't choose just any directory, it has to be part of the TeXhierarchy. The best choice is your “local texmf” tree,which you can determine as follows:
Start > Programs > MiKTeX > Maintenance > Roots
(or MiKTeX Settings, in older versions). Some paths shown there have a Description such as Install, UserConfig, or UserData. A tree labeled UserConfig (but not any of the others) is an acceptable target for your new fonts, if you have no permission to create a new tree. However, it is better to use a tree without a description, as follows:
You can create a new local tree by clicking on Add. The folder must not contain files at its root level or MiKTeX will reject it. Files in the folder must be in subfolders similar to the subfolders in the Install root. (MiKTeX info.)
If you are not using one of the above TeX distributions, you'll needto consult other documentation.
2. The TeX Directory Structure: unpacking your archive
After determining your local tree for installation (see previoussection), the next step is to copy the new files into subdirectories ofthat tree. Hopefully, your new font came as a zip or other archive filethat is already arranged according to the standard TeXDirectory Structure (TDS). If this is the case, you can simplyunpack it at the top level of your chosen tree.
You can check by inspecting your archive (withunzip -l yourfile.zip, for example). If it hassubdirectories such as fonts/ and tex/, it's mostlikely arranged according to the TDS.
If you're getting a flat list of font files without any directories,then you have to move the files yourself into the appropriatesubdirectory. Please read the TeX FAQentry and TDS document (html, pdf).
Warning: some unzip programs take it upon themselves to create theirown top-level directory, usually named after the zip file. You mustavoid these programs. The plain unzip program, version 5.52 orthereabouts, which is the usual unzip on MacOSX and other Unix-likesystems, works fine; you can run unzip --version to checkwhat you've got. The UnZiphome page lists working unzip binaries for many systems.
3. The TeX filename database
After getting your new files into their proper location (see previoussections), you must update the so-called “TeX filenamedatabase”.
- MiKTeX
- Navigate through the MiKTeX program:
Start > Programs > MiKTeX > Maintenance > Settings > General > Refresh FNDB
(In older versions of MiKTeX, it may be under a menu called MiKTeX Options instead of Maintenance.) There may also be a Maintenance(Admin) entry if you have administrative privileges; if so, that is usually the better choice. Or, if you prefer a DOS command line: initexmf --update-fndb. - MacTeX
- Run the command sudo -H mktexlsr. (The -H setsHOME for the sudo environment.)
- TeX Live
- Run the command mktexlsr (the command texhash is asynonym). On Unix-like systems, run sudo -H mktexlsrif you installed your system as root (not recommended).
4. Font map files: telling TeX about the new font
After recording the new files (see the previous sections), the last(and most complicated) step is to update various so-called“map” files with the information about your new font.
The commands below assume your new font comes with a map file. Ifyou have no map file, then it has to be created, and that is not an easyjob. See the references at the end.
The commands below use newfont.map for the name of this mapfile. There are no standard conventions for the name, so it can't beguessed; check your original archive for the name used.
initexmf --edit-config-file updmap
You'll want to edit this in a text editor such as Notepad.
Second, add this one line to updmap.cfg and save it:
Map newfont.map
Map newfont.map
Third, back at the DOS prompt, run:
initexmf --mkmaps
(Ignore any error messages.)
initexmf --mkmaps
(Ignore any error messages.)
updmap-sys --force --enable Map=newfont.map
On MacOSX, this is typically done as system administrator, so:
sudo -H updmap-sys ...
sudo -H updmap-sys ...
Again, this page is about installing fonts in a system-wide directory. If you need or want to use a personal directory such as TEXMFHOME, please see the separate page about installing fonts in a personal directory.
After doing this, you should remake the filenamedatabase again, as explained above; this is not always necessary,depending on your setup, but should never hurt.
5. Testing and debugging
Once all the above seems to have gone ok, to test if the new font isproperly recognized, you can use the standard testfont.texfile, like this (prompts also shown):
It is imperative to enter the exact name of a .tfm file thatwas installed, not a system font name or a PostScript font name oranything else. The only thing TeX will recognize is the .tfmfilename. Furthermore, leave off the .tfm extension.
The result of the above run should be a DVI or PDF file, according towhichever tex you invoked, showing the characters in that TFM.
If there are problems, typically dvips or pdftex will try to makebitmaps from the font, perhaps with “missing font”messages. If you get that frustrating result:
- First, try updating the filename databases andredoing the test.
- If that doesn't help, try running (from the command line)kpsewhich newfont.map, where newfont.map isthe map file you added to the system. It should return the location ofthe map file; if it doesn't, somehow it is not visible to TeX.System-level permissions? Remake the filename database?
- If still no joy, it may be time to turn to the general TeX help resources. Search around forpeople talking about (La)TeX and your specific font; any given fontoften has unique issues not addressed here.
Good luck. If you have technical questions or problems withinstalling fonts, please try writing [email protected]. For correctionsto this web page, contact the TUG webmaster (link below).
$Date: 2019/07/16 15:32:49 $;TUG fonts page;