Windows can not install .pfa files so what you can do is, download onlinefontconvertor and use to convert .pfa files to .pfb which is said to be recognized by windows(This tool also generates a .afm file along with .pfb file)
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.
Install Afm Fonts Windows 10
Then, in your LocalTeXMF\fontsdirectory, create a type1 directory and copy the pfbs in it, renaming them as indicated in pad.map; do the same for the pfms (actually, I think these are not really necessary, as TeX uses the tfms).
I found this script somewhere in the Microsoft website that enables to install fonts, but it doesn't support ".pfm" and ".pfb" files, it says it should be enabled somehow. I'm looking to fix the script but don't manage to do it on my own. I'll attach the script I have right now and mention the changes I've done to it to try and support these files. If anyone can send me a version that enables those extensions or can lead me to a good direction I'd be very thankful.
6. Confirm the font was installed. Settings will automatically show the new font as the first item in the list of installed fonts below the drag-and-drop interface to confirm it was successfully installed. (The fonts will be alphabetically sorted again if you return to the page.) The app will also group multiple font faces, such as Roboto Bold or Roboto Italic, under a single font to prevent duplicates from cluttering up the list.
It seems to me that the origin of the error comes from a failure in the .ttf file. Navigate over to FontForge and download the open-source software. When installed, open your .ttf file and resave it as a .ttf using the Generate Fonts... option in the File menu. You might get a message that warns you that there is something slightly wrong with the font - you can review it if you like, but I went ahead and clicked Generate anyway.
Two files are needed for each PostScript Type 1 font: the.afm Adobe Font Metric (AFM) and the.pfb PostScript Font Binary (PFB) files.You must have both types of file for each separate font before you start. If you only have thenear-obsolete .pfa PostScript Font ASCII (PFA) files, it maybe possible to generate the .pfb filesusing the t1binary program from thet1utils suite (see ) or the excellent FontForge fonteditor (from ).There are unfortunately still some companies distributingType 1 fonts in .pfa format(Mathematica is one reported recently).
This is not the full descriptive name (eg Baskerville Italic Bold Extended) but an encoded font name in the format fnnsseev, devised by Karl Berry, which stores the same information in no more than eight characters for compatibility with systems which cannot handle long filenames (and incidentally makes it far easier to type). The letters in the format above have the following meanings (see the fontname documentation on your computer for more details). Lists of the codes used are in the files supplier.map, weight.map, width.map, variant.map, and the various .map files for each foundry, which are in your TEX installation.
The Adobe Font Metric files have to be converted to TEX Font Metric and Virtual Font files. The afm2tfm and vptovf programs are standard TEX utilities in the bin directory of your main TEX installation.
Confusingly, Bitstream fonts (and others fromsimilar sources) mostly have different names from theoriginal fonts, to avoid copyright issues, so whatthey call Humanist 521 is actually Gill Sans. Untilrecently, US law only allowed thenames of typefaces to becopyrighted, not the font designs themselves, leadingto widespread piracy.
I have built a basic msi project to install True Type and Postscript fonts for a customer. The TT fonts install perfectly and while the Postscript fonts are in the right location and are in the registry they do not appear in the Fonts applet and the CharMap utility. If I double click a Postscript font file *.pfm, and choose Install for all users, a dialog is displayed indicating the font is already installed. After completing the install the font appears in both the Fonts applet and the CharMap utility.
I am at a loss as to what else to do. It is obvious that something has to happen, although this does not appear to be in the registry as there are no differences between the msi install and double clicking a *pfm file. Previously the Postscript font install was achieved using the shell CopyHere method, however this now installs the font in the user font location, which is not recognized by the application that requires these fonts.
Multiple master metricsAdobe Systems has kindly agreed to provide access to AMFM and AFMfont metrics for all the multiple master fonts in the AdobeType Library. Mmafmuses these files to generate single-instance AFM metrics files.mm-metrics-1.2.tar.gz (TGZ format,2608466 bytes)mm-metrics-1.2.zip (ZIP format,3009430 bytes)Thanks to Terry O'Donnell for making this possible.
Mmafm and mmpfb create instances of multiple-masterfonts: mmafm creates the AFM file (font metrics) for an instance,given the AMFM and AFM files distributed with the multiple master;mmpfb creates a normal, single-master font for an instance, giventhe multiple master font itself. These tools help multiple master fontswork with UNIX programs for single-master fonts, like afm2tfm, ps2pk,GhostScript ps2pdf, and the X11 Type 1 font server. Mmafm andmmpfb were previously distributed in their own package,mminstance.
Changes in version 0.16: Change automatic-mode storagelocation for dvips files to TEXMF/dvips/VENDOR (usuallyTEXMF/dvips/lcdftools); you may need to move your old files and runmktexlsr. Prefer shorter ligatures made out of regular letters(Bruce D'Arcus). Add --coding-scheme option (Marco Kuhlmann). Add --ligkernand --unicoding options. Remove any virtual font foo.vf wheninstalling a non-virtual font foo.tfm, to reduce the risk that anold virtual font will screw up your installation.
Version 1.13: A thorough rewrite of t1disasm forconsistency with the other programs. All programs can read binary PFA fonts(requested by Tom Kacvinsky ). T1asm andt1disasm can handle synthetic fonts, like many older Obliquefonts.
Version 1.7.2: A patch from Tom Kacvinsky so that t1asm will work on fontswithout /Subrs arrays. Removed spurious debugging messages fromt1disasm. Includes patches from Jan-Jaap van der Heijden to support buildingt1utils under 32-bit Windows.
Version 1.5: All programs have configure scripts foreasier installation, and accept long options including --help.t1asm and t1disasm have been extended with Type 2 charstringcommands, which also occur in some multiple master fonts like Adobe Jenson.Bugs in t1ascii have been fixed.
Autofont can automatically transform fonts based on "instructions"embedded in the font name. For example, "Times-Roman--sl167" refers to anartificially slanted version of Times Roman, and "ACaslon-Regular--f"refers to a version of Adobe Caslon Regular that includes the ff, ffi, andffl ligatures found in Adobe Caslon Expert. Again, there is no need toinstall anything explicitly; simply refer to the fonts by name and Autofontwill take care of the required virtual font manipulations.
On Windows, the font list is derived from the fonts that are installed on the system along with the fonts available on the current default printer. A small printer icon before the font name identifies printer fonts. True Type fonts are associated with a TTF icon.
On UNIX, the font list is derived by querying the X-server display on which the application is running for the available fonts. The command is similar to the UNIX xlsfonts command, which lists all of the available fonts for the X-server display. From this font list, Reports Builder generates a list of usable fonts with the valid style, weight, width, size, and encoding characteristics to match the character set. The character set is driven by the NLS_LANG environment variable. Reports Builder includes only those fonts with an encoding of iso8859-1, unless specified differently in the toolkit resource file, Tk2Motif*fontMapCs. For more information on Tk2Motif*fontMapCs, refer to Section 4.3, "Font Configuration Files".
During report formatting, fonts associated with the layout objects are first checked against the font alias file, uifont.ali, (refer to Section 4.3, "Font Configuration Files"). If an entry in the font alias file is found, the mapped font is used instead of the original one. The mapped font is then searched for in the list of fonts available on the system or printer. If a particular font is not found, Oracle Reports will look for the nearest matching font under the same character set which can be used instead.
On Windows, the font lookup mechanism is simple due to the availability of printer drivers, which have the capability of uploading fonts from the system as needed. Any output from Oracle Reports running on Windows will contain fonts from either one of the following:
If the printers are present, the printer definition files are loaded and the information in these files is read along with the information related to the fonts available for the printer. If these printers are not found, then Oracle Reports uses ScreenPrinter.
If a particular font is needed but not found in the PPD file or if an AFM file is not found, Oracle Reports will look for the nearest matching font according to its matching rules. For example, suppose a report is originally designed with a Simplified Chinese font SimSun and in the uifont.ali file no mapping for this font is found. Oracle Reports will look for the font SimSun in the list of available fonts generated by the Font lookup algorithm. If this font name is not in that list, Oracle Reports tries to look for the closest matching font from the list of fonts given in the printer definition file. 2ff7e9595c
Comments