summaryrefslogtreecommitdiff
path: root/language/gurmukhi/singh/install.dos
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
committerNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
commite0c6872cf40896c7be36b11dcc744620f10adf1d (patch)
tree60335e10d2f4354b0674ec22d7b53f0f8abee672 /language/gurmukhi/singh/install.dos
Initial commit
Diffstat (limited to 'language/gurmukhi/singh/install.dos')
-rw-r--r--language/gurmukhi/singh/install.dos106
1 files changed, 106 insertions, 0 deletions
diff --git a/language/gurmukhi/singh/install.dos b/language/gurmukhi/singh/install.dos
new file mode 100644
index 0000000000..2ac424b986
--- /dev/null
+++ b/language/gurmukhi/singh/install.dos
@@ -0,0 +1,106 @@
+The purpose of this file is to help in installation of "Gurmukhi for TeX"
+software package on DOS. In addition to this file Readme and manual.gm,
+are also provided which provide information about how and why to use this
+package.
+
+Lets assume that you have installed TeX and TeX can call METAFONT for
+font creation. I do not have TeX, METAFONT, and C-compiler on my machine
+in DOS environment, so was not able to install or test this software.
+Please let me know if you are successfully able to setup this package.
+
+Following help is extracted from "Devanagari for TeX" readme file, and
+and is modified a little for "Gurmukhi for Tex" in hope that this will
+be helpful in installation.
+
+In order to install the software you have to put the files in the right
+directories and rename them (if necessary).
+
+* GMMACS.TEX, BANI.GM, EG.GM, MANUAL.GM must be in the directory
+ where TeX expects it's input. This is something like C:\TEX\INPUTS on
+ MS-DOS systems.
+
+* Compile GURMUKHI.C file to create an executable of preprocessor, with
+ a name may be GURMUKHI.EXE. Move it in a directory specified in the
+ PATH environment-variable. Preferably it should be put in the directory
+ where other executable files are kept, often called BIN.
+
+* If you do have a 300dpi black-writing laser-printer then you can use
+ the included PK and TFM files. The TFM-files have to be put in the
+ directory where TeX keeps its TFM-files, mostly called C:\TEX\FONTS
+ or something like that. The organization of the fontfiles (PK-files)
+ varies from installation to installation. Sometimes all the fontfiles
+ are put together in one large directory and the different magnifications
+ of a font are distinguished by their filename extension, as is the case
+ with the fonts in this package.
+
+ Instead of in a directory the font files are sometimes put in a library.
+ This is the way it is done in emTeX. And sometimes there are different
+ directories for each magnification. These directories have 'names' like
+ 300, 329 etc. The fontfiles within these directories have no extensions
+ or just the extension 'PK'.
+
+ According to which fontfile-organization is used on your system, you
+ have to copy and rename the fontfiles in the PK300 directory in this
+ package.
+
+* If your printer is not a 300dpi black-writing laser-printer, or if you
+ want to change the appearance of the font or of some characters in it
+ then you have to run METAFONT and use the .MF files as input. There
+ are METAFONT source files for 3 different sizes: 8,9 and 10 point:
+ GRMK8.MF, GRMK9.MF and GRMK10.MF.
+ All of these three source-files make use of DEFS.MF and GMCHARS.MF.
+
+ The following is taken from: FAQ about TeX
+
+ METAFONT allows you to create your own fonts. METAFONT, unlike TeX,
+ requires some customization. Each output device for which you will be
+ generating fonts needs a mode associated with it. Modes are defined
+ using the mode_def convention described on page 94 of _The METAFONTbook_.
+ The person who installed METAFONT on your system should know which
+ modes are defined.
+
+ The usual way to create a font with plain METAFONT is to start
+ it with the line
+ \mode=<mode name>; mag=<magnification>; input <font file name>
+ in response to the * prompt or on the METAFONT command line. If
+ <mode name> is unknown or omitted, then the mode defaults to proof
+ mode. If this has happened METAFONT will produce an output file
+ called <font file name>.2602gf. The <magnification> is a floating
+ point number or magstep (magsteps are defined in _The METAFONTbook_
+ and _The TeXbook_). If mag=<magnification> is omitted, then the
+ default is 1. For example, to generate dvng10 at 12pt for an epson
+ printer you would type
+ mf \mode=epson; mag=1.2; input dvng10
+
+ If you need a special mode that isn't defined for your METAFONT,
+ you can put its commands in a file (e.g., ln03.mf) and invoke
+ it on the fly with the \smode command. For example, to create
+ dvng10.300gf for an LN03 printer, using the file
+ % This is ln03.mf as of 2/27/90
+ % mode_def courtesy of John Sauter
+ proofing:=0;
+ fontmaking:=1;
+ tracingtitles:=0;
+ pixels_per_inch:=300;
+ blacker:=0.65;
+ fillin:=-0.1;
+ o_correction:=.5;
+ (note the absence of the mode_def and enddef commands), we would type
+ mf \smode="ln03"; input dvng10
+
+* After this setup you are ready to use this package. You can use
+ example file bani.gm and eg.gm to see if everything is alright. A
+ typical set of commands can be given as follows. This information
+ is in greater detail in manual.ps
+
+ gurmukhi bani
+ tex bani
+
+ You can send dvi file generated here to your printer.
+
+------------------------------------------------------------------------
+Amarjit Singh
+E-mail Address: asingh@evovling.com
+Postal Address: 8405 E. Hampden Ave #11N Denver CO 80231 USA (Current)
+ A-3 Mansarover Garden, New Delhi 110015 India(Permanent)
+------------------------------------------------------------------------