I'm going to start recording this for the sake of posterity, should posterity turn out to be interested ;. This works for me (as discussed in chat) but the OP is still having a few fontinst teething troubles.
This answer assumes a Unix-ish system such as GNU/Linux, OS X, BSD or similar. It will not work unmodified on Windows.
Introduction
To use a font with (pdf)(La)TeX, you need a good number of support files in addition to the type1 font itself.
This answer is based on the initial, basic fontinst installation method covered in the first tutorial in The Font Installation Guide. In most cases, it will produce a working, though not entirely perfect, result. In other cases, it may fail or it may produce as perfect a result as is possible given the nature of the font.
For the font which is the subject of this question, it should produce a working result.
Prepare font support package
Start by renaming the .pfm sckr.pfm and the .pfb sckr.pfb.
Then
pf2afm sckr
mv sckr.afm sckr8a.afm
mv sckr.pfb sckr8a.pfb
Then the OP created a file sck-drv.tex:
\input fontinst.sty
\needsfontinstversion{1.926}
\recordtransforms{sck-rec.tex}
\latinfamily{sck}{}
\endrecordtransforms
\bye
and another sck-map.tex:
\input finstmsc.sty
\resetstr{PSfontsuffix}{.pfb}
\adddriver{dvips}{sck.map}
\adddriver{pltotf}{sck-pltotf.sh}
\input sck-rec.tex
\donedrivers
\bye
Then:
tex sck-drv.tex
to produce sck-rec.tex and a bunch of .fd, .pl and .vpl files. The .pl files get converted to .tfm:
for i in *.pl
do
pltotf $i
done
and the .vpl to .vf:
for i in *.vpl
do
vptovf $i
done
Then
tex sck-map.tex
produces sck.map and a script sck-pltotf.sh which can be run using sh:
sh sck-pltotf.sh
You can now delete the *.pl *.vpl sck-rec.tex sck-pltotf.sh etc. as they are no longer needed.
Then you can make a package, sck.sty:
\NeedsTeXFormat{LaTeX2e}
\ProvidesPackage{DAX}[2015/09/06 v1.0 DAX]
\DeclareOption{default}{%
\renewcommand{\sfdefault}{sck}}
\ProcessOptions
\DeclareRobustCommand{\sckfamily}{%
\fontseries{m}%
\fontshape{n}%
\fontfamily{sck}%
\selectfont}
\DeclareTextFontCommand{\sck}{\sckfamily}
\endinput
Testing
At this point, you can say
\documentclass{article}
\pdfmapfile{+sck.map}
\usepckage[T1]{fontenc}% optional
\usepackage{sck}
\begin{document}
\sck{Some text}
{\sckfamily More text including off, office, affluent, fluorine, infinitude, --- and --
\slshape This is fake, oblique.
The results will not be as good as a designed italic or oblique shape.
\upshape\scshape You may also get faked small-caps.
Again, the results won't be as good as real small-caps.
\upshape\itshape Italics should give us the oblique as a substitute.
\par}
\end{document}
and it should work when you latex or pdflatex the test file, provided your test file is in the same directory as all the font files you've created.
Don't proceed to installation until you are happy with the results.
Installation
When you are happy with the results of testing, you can install the font files.
For reasons I explain here, it is not recommended to install into your personal TEXMF tree unless you have no choice.
Instead, install into your system-wide local TEXMF tree. You can find out where this is using kpsewhich:
kpsewhich -var TEXMFLOCAL
If you are using upstream's TeX Live and haven't changed texmf.cnf, then this will likely return a single directory. For example, I get
/usr/local/texlive/texmf-local
So this is the directory I would use. If you are using a packaged version of TeX Live - from a GNU/Linux distro, for example - then you might get more than one directory. For example, on Arch Linux, you would get
/usr/local/share/texmf:/usr/share/texmf
Thanks to the OP for this information. In this case, you should pick the directory which is not managed by your Linux distro's package manager. In most cases, this will begin with /usr/local. So, on Arch Linux, you'd use
/usr/local/share/texmf
In the rest of this answer I refer to the selected directory as <TEXMFLOCAL>. If kpsewhich returned exactly one result, you can substitute $(kpsewhich -var TEXMFLOCAL). Otherwise, substitute the relevant directory path appropriately.
The remaining steps may need to be done with root privileges, depending on your system's configuration.
Very likely, you will need to create some directories here. This is normal.
mkdir -p <TEXMFLOCAL>/fonts/type1/public/sck
mkdir -p <TEXMFLOCAL>/fonts/tfm/public/sck
mkdir -p <TEXMFLOCAL>/fonts/afm/public/sck
mkdir -p <TEXMFLOCAL>/fonts/vf/public/sck
mkdir -p <TEXMFLOCAL>/fonts/map/dvips/sck
mkdir -p <TEXMFLOCAL>/tex/latex/sck
mkdir -p <TEXMFLOCAL>/source/fonts/sck
You can use something other than sck for the directory name - just substitute appropriately.
Now, from the working directory in which you prepared the font files:
mv *.pfb *.pfm <TEXMFLOCAL>/fonts/type1/public/sck/
mv *.tfm <TEXMFLOCAL>/fonts/tfm/public/sck/
mv *.afm <TEXMFLOCAL>/fonts/afm/public/sck/
mv *.vf <TEXMFLOCAL>/fonts/vf/public/sck/
mv *.map <TEXMFLOCAL>/fonts/map/dvips/sck/
mv *.fd *.sty <TEXMFLOCAL>/tex/latex/sck/
mv sck-drv.tex sck-map.tex <name of test file>.tex <notes> <TEXMFLOCAL>/source/fonts/sck/
Putting things in source is optional and just for reference. I find it useful so I can find things.
Now, you need to update the file name database:
mktexlsr <TEXMFLOCAL>
There are two ways to enable the .map file fragment. One has certain advantages but I'm not sure how it works with Arch's packages, so I suggest the second:
updmap-sys --enable Map=sck.map
Retest
You should now be able to drop any root privileges and recompile your test document from another directory, commenting out or deleting the \pdfmapfile... line, to get the same results.
Best Answer
Follow ONLY steps 1-4 from the linked instructions. Steps 5-6 and 8 are simply wrong. Step 9 is pointless and step 7 is inefficient.
Instead, after completing step 4, do this:
If you are on Mac OS X and have not enabled
rootand are using a default MacTeX installation, you'll have to prefix every step withsudoor runsudo shto get a privileged shell before you start.Note that this is not tested as I do not use FontPro and am not using a Mac. I'm assuming that the instructions are basically right about how FontPro works. Given they are not reliable on how TeX Live works, this may not be a safe assumption.
Caveat emptor...