%%
%% This file will generate fast loadable files and documentation
%% driver files from the doc files in this package when run through
%% LaTeX or TeX.
%%
%% 
%% This file is part of the PSNFSS2 package
\def\batchfile{psfonts.ins}
{\immediate\openin15 docstrip.tex
\ifeof 15
\newlinechar `@
\message{@@**************************************************@}
\message{* I can't find the file `docstrip.tex'.@}
\message{* @}
\message{* It is not in the search path for \noexpand\openin.@}
\message{* @}
\message{* This means that you either don't have the@}
\message{* DOC package MZ0 installed, or that your@}
\message{* installation doesn't have the same search path@}
\message{* for \noexpand\openin and \noexpand\input.@}
\message{* @}
\message{* In the latter case you need to copy `docstrip.tex'@}
\message{* to the current directory. Otherwise you have to@}
\message{* get the DOC package (MZ0) first.@}
\message{* @}
\message{* I'm giving up now.@}
\message{***************************************************@@}
\expandafter\aftergroup\csname @@end\expandafter\endcsname
\expandafter\aftergroup\csname end\expandafter\endcsname \fi
\ifx\firsttime\undefined\global\let\firsttime\relax\else
\ifx\currbatchFile\undefined
 \newlinechar `@
 \message{*** WHOA!!! I'm dying ...@}
 \message{*** Upgrade to a 
          new docstrip release v2.1a or higher !!!!!!@@}
 \message{*** This installation routine works only with the new@}
 \message{*** docstrip.tex program which is part of the doc@}
 \message{*** package (MZ0).@@}
 \message{Please install this package first.@@}
 \message{I'm giving up now.@}
 \endinput \csname @@end\endcsname \csname end\endcsname \fi \fi}
\input docstrip.tex
\preamble
%%

Copyright (C) 1993 by Sebastian Rahtz
All rights reserved.

This file is part of the PSNFSS2 package.

^^J\def\string\betaout{\immediate\write16 }
^^J\string\betaout{***************************************************}
^^J\string\betaout{*\string\space\space This\string\space\space file
^^J\string\space\space is\string\space\space part\string\space\space 
^^Jof\string\space\space a\string\space\space 
^^J\space version\string\space\space of\string\space\space PSNFSS.}
^^J\string\betaout{***************************************************}
\endpreamble

\def\batchfile{psfonts.ins}   % ignored in distribution
\input docstrip.tex           % ignored in distribution 

\Ask\answer{************************************************************
   ^^J* There are three possible ways to set up the font declaration 
   ^^J* files for PostScript fonts:
   ^^J* 
   ^^J*   1) use the fonts as is, with Adobe layout. This is not supported
   ^^J*      here
   ^^J* 
   ^^J*   2) use the old TeX encoding, with virtual fonts to change the
   ^^J*      layout 
   ^^J* 
   ^^J*   3) use the new Cork-encoding, which will need virtual fonts
   ^^J*      to change the layout, and some re-encoding in the font header.
   ^^J* 
   ^^J* Option 3) should be preferred because it will be compatible in
   ^^J* the long run with TeX, but for simplicity's sake you might prefer
   ^^J* option 2). You can now choose to install font files for 2),
   ^^J* 3), or both
   ^^J* 
   ^^J* Shall I use new Cork-encoding (c) or old TeX (o), or both (b)?
   ^^J*************************************************************}

\keepsilent

\Msg{*** Generating .fd files  ***}

\preamble
Copyright (C) 1993 Sebastian Rahtz. All rights reserved.
This is a generated file for *PSNFSS2*.  Permission is granted to to
customize the declarations in this file to serve the needs of your
installation.  However, no permission is granted to distribute a
modified version of this file under its original name.

I recommend that you copy the relevant portions of the original
source file into a private .fdd instead of modifying this file directly. 
\endpreamble

\def\GenerateFDs{%
\generateFile{\codestyle T1pag.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1pag}}
\generateFile{\codestyle T1pbk.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1pbk}}
\generateFile{\codestyle T1pcr.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1pcr}}
\generateFile{\codestyle T1phv.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1phv}}
\generateFile{\codestyle T1pnc.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1pnc}}
\generateFile{\codestyle T1ppl.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1ppl}}
\generateFile{\codestyle T1ptm.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1ptm}}
\generateFile{\codestyle T1pzc.fd}{t}{
	\from{psfonts.fdd}{fd,\codestyle T1pzc}}
}


\def\codestyle{O}
\def\canswered{c}
\def\oanswered{o}
\def\banswered{b}
\def\anything{n}
{\ifx\answer\canswered 
\Msg{*** Generating font defs for PostScript text fonts (T1) ***}
   \gdef\anything{y}
   \gdef\codestyle{}
   \GenerateFDs
\fi}
{\ifx\answer\oanswered 
\Msg{*** Generating font defs for PostScript text fonts (OT1) ***}
   \gdef\anything{y}
   \gdef\codestyle{O}
   \GenerateFDs
\fi}
{\ifx\answer\banswered 
\Msg{*** Generating font defs for PostScript text fonts (T1 and OT1) ***}
   \gdef\anything{y}
   \gdef\codestyle{O}
   \GenerateFDs
   \gdef\codestyle{}
   \GenerateFDs
\fi}

\Msg{*** Generating styles files for using PostScript fonts ***}

\generateFile{nftimes.sty}{t}{
	\from{psfonts.fdd}{style,nftimes}}
\generateFile{nfpalat.sty}{t}{
	\from{psfonts.fdd}{style,nfpalat}}
\generateFile{nfhelve.sty}{t}{
	\from{psfonts.fdd}{style,nfhelve}}
\generateFile{nfavant.sty}{t}{
	\from{psfonts.fdd}{style,nfavant}}
\generateFile{nfnewce.sty}{t}{
	\from{psfonts.fdd}{style,nfnewce}}
\generateFile{nfbookm.sty}{t}{
	\from{psfonts.fdd}{style,nfbookm}}
\generateFile{nfpi.sty}{t}{
	\from{psfonts.fdd}{style,nfpi}}
%{\ifx\answer\banswered 
%\Ask\xanswer{************************************************************
   %^^J* I asked you just now about encoding. I have generated
   %^^J* both sets of font files, but I need to know which your
   %^^J* default setup should use, if you just use say nftimes.sty.
   %^^J* 
   %^^J* Shall I set new Cork-encoding (c) or old TeX (o) [default c]?
   %^^J*************************************************************}
%{\ifx\xanswer\oanswered
   %\gdef\codestyle{O}
 %\else
   %{\ifx\xanswer\canswered
	%\gdef\codestyle{}
    %\fi}
 %\fi}
%\fi}
%
% utility styles which redefines encodings etc
%
\generateFile{nft1ot1.sty}{t}{
	\from{psfonts.fdd}{nft1ot1}}

\generateFile{nfot1var.sty}{t}{
	\from{psfonts.fdd}{nfot1var}}

\Msg{*** Generating font defs for PostScript symbol fonts (unencoded) ***}

\generateFile{Upzd.fd}{t}{
	\from{psfonts.fdd}{fd,Upzd}}
\generateFile{Upsy.fd}{t}{
	\from{psfonts.fdd}{fd,Upsy}}

\Msg{*** Generate the documentation driver ***}

\preamble

Copyright (C) 1993 Sebastian Rahtz
All rights reserved.

This file is part of the PSNFSS2 package.
---------------------------------------

Permission is granted to modify this file for producing a different
layout. However, no permission is granted to distribute a modified
version of this file under its original name.

\endpreamble

\generateFile{psfonts.drv}{t}{%
  \from{psfonts.fdd}{driver}}


\Msg{***********************************************************}
\Msg{*}
\Msg{* To finish the installation you have to move the following}
\Msg{* files into a directory searched by TeX:}
\Msg{*}
\Msg{* \space\space All *.fd, and *.sty}
\Msg{*}
\Msg{* To produce the documentation run the files ending with}
\Msg{* `.drv' through LaTeX.}
\Msg{***********************************************************}


\endinput