From 18dd9efec69d7fe8cd3694a9562a6d0723ff4170 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Sat, 17 Jun 2006 22:31:18 +0000 Subject: new package name velthuis, updating/replacing devanagari git-svn-id: svn://tug.org/texlive/trunk@1691 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/generic/velthuis/README | 203 +++ Master/texmf-dist/doc/generic/velthuis/captions.dn | 40 + Master/texmf-dist/doc/generic/velthuis/changes | 299 ++++ Master/texmf-dist/doc/generic/velthuis/copying | 340 ++++ Master/texmf-dist/doc/generic/velthuis/examples.dn | 159 ++ .../texmf-dist/doc/generic/velthuis/examples.pdf | Bin 0 -> 65265 bytes Master/texmf-dist/doc/generic/velthuis/manual.pdf | Bin 0 -> 516820 bytes Master/texmf-dist/doc/generic/velthuis/manual.tex | 1662 ++++++++++++++++++++ Master/texmf-dist/doc/generic/velthuis/misspaal.dn | 98 ++ .../texmf-dist/doc/generic/velthuis/misspaal.pdf | Bin 0 -> 27874 bytes .../texmf-dist/doc/generic/velthuis/vedasample.dn | 87 + .../texmf-dist/doc/generic/velthuis/vedasample.pdf | Bin 0 -> 27802 bytes 12 files changed, 2888 insertions(+) create mode 100644 Master/texmf-dist/doc/generic/velthuis/README create mode 100644 Master/texmf-dist/doc/generic/velthuis/captions.dn create mode 100644 Master/texmf-dist/doc/generic/velthuis/changes create mode 100644 Master/texmf-dist/doc/generic/velthuis/copying create mode 100644 Master/texmf-dist/doc/generic/velthuis/examples.dn create mode 100644 Master/texmf-dist/doc/generic/velthuis/examples.pdf create mode 100644 Master/texmf-dist/doc/generic/velthuis/manual.pdf create mode 100644 Master/texmf-dist/doc/generic/velthuis/manual.tex create mode 100644 Master/texmf-dist/doc/generic/velthuis/misspaal.dn create mode 100644 Master/texmf-dist/doc/generic/velthuis/misspaal.pdf create mode 100644 Master/texmf-dist/doc/generic/velthuis/vedasample.dn create mode 100644 Master/texmf-dist/doc/generic/velthuis/vedasample.pdf (limited to 'Master/texmf-dist/doc') diff --git a/Master/texmf-dist/doc/generic/velthuis/README b/Master/texmf-dist/doc/generic/velthuis/README new file mode 100644 index 00000000000..8bcd55ffc63 --- /dev/null +++ b/Master/texmf-dist/doc/generic/velthuis/README @@ -0,0 +1,203 @@ +============================================================================== +Velthuis Devanagari for TeX Installation Notes +Version 2.14 27 May 2006 +============================================================================== + + +This package provides support for typesetting texts in Devanagari script +(Sanskrit and Hindi) in plain TeX and LaTeX. the text is entered in Velthuis +transliteration. + +The package is included in famous TeX distributions such as TeX Live and +MikTeX. You have to install this package separately only if: + +1. A bug that bothers you was discovered and fixed and the corrected version + of this package is not yet available in your favourite distribution. + +2. A new feature that is important for you was added to the package and it is + not yet included in the TeX distribution of your choice. + +3. You use a distribution which comes without this package. + +4. You wish to test our work before it is released for inclusion in standard + distributions. + +5. You wish to help us with develompment. + + +Release numbering scheme +======================== + +The project is hosted on a CVS server which means that each file has its own +version number. This is not practical for milestone releases prepared for +publishing on Sarovar, CTAN or elsewhere. Moreover, the preprocessor has its +own version number advanced manually when a new feature is added or a bug is +fixed. Since release 2.14 the whole package shares version number of the +preprocessor. If only macros and/or fonts were changed since the previous +release and the preprocessor remains unchanged, another digit is added to the +version number. Thus release 2.14.1 would mean that the preprocessor remained +at version 2.14 but some macros and/or fonts were modified. Users who update +their distributions will thus know whether they have to compile a new version +of the preprocessor or whether they can keep the existing executable. + + +Obtaining the package +===================== + +The project is officially hosted at http://devnag.sarovar.org and the package +may be downloaded from there. The package may also be downloaded from the +Comprehensive TeX Archive Network (CTAN). Its primary location in UK TUG is +ftp://ftp.tex.ac.uk/tex-archive/language/devanagari/velthuis/ + +The development version may also be obtained by anonymous CVS. Set your +CVSROOT variable to :pserver:anonymous@cvs.devnag.sarovar.org:/cvsroot/devnag +and log to the server by: + +cvs login + +When you are asked for the pasword, just press ENTER. + +Get the package by: + +cvs -z3 co -P velthuis + +If you wish to update your existing working copy, "cd" to its top directory +(default is "velthuis") and type: + +cvs -z3 up -P + + +Unpacking +========= + +Since version 2.14 the package conforms to the TeX Directory Structure (TDS). +This structure is used in modern TeX distributions on all platforms. Unless +you are a TeXpert we recommend you to keep the package in a separate +directory. If you do it this way, you can easily remove it after you install +upgraded TeX distribution with a new version of Velthuis Devanagari. + + +Compiling the preprocessor +========================== + +The CVS version contains the source code and the Windows executable in the +"bin" directory. Users of other platforms are supposed to compile the +preprocessor themselves. See important notes inside devnag.c. + +Releases both on devnag.sarovar.org and CTAN contain also an executable for +OS/2 (eComStation) and statically linked executable for Linux. + +Enter the directory with the executable to the PATH variable or move or +symlink the executable to a directory listed in PATH. In UNIX systems you can +verify by "which devnag" that the file can be located. + + +Install the macros and fonts +============================ + +You must instruct your TeX distribution to include your directory into the +beginning of search paths. If you have web2c based system (TeX Live, teTeX), +find file texmf.cnf (typically in texmf/web2c directory) and modify the TEXMF +variable. It typically contains: + +TEXMF = {!!$TEXMFLOCAL,!!$TEXMFMAIN} + +Define the location of the package (before definition od TEXMF) as: + +DEVNAG = /path/to/velthuis + +and then modify the TEXMF definition as: + +TEXMF = {!!$DEVNAG,!!$TEXMFLOCAL,!!$TEXMFMAIN} + +Rebuild the file database either by running mktexlsr from the command prompt +or from the texconfig menu (be sure that mktexlsr and/or texconfig come from +the same distribution as tex, latex, etc.). + +If you are a MikTeX user, find MikTeX menu, open MikTeX Options, select the +Roots tab, use the Add button to add the "velthuis" directory, move it to the +top location by the Up button. MikTeX also needs to know about the fonts. +Locate your updmap.cfg file. It usually resides in X:\texmf\web2c directory (X: +is the drive with your MikTeX installation) or you may have a local copy in +X:\localtexmf\web2c. The file must contain the following line: + +MixedMap dvng.map + +If it is not present, put it to the end of the file. Finally refresh the file +database pushing the Refresh FNDB button. + +Note: We rarely add new files or remove files or change their locations. Once +you install the package from CVS and update it by "cvs up -P" without removing +the "ls-R" file, TeX will immediatelly use the new files. It is NOT necessary +to rebuild the database. + +Test your installation +====================== + +The kpathsea library now should be able to find your files. Try the following +commands: + +kpsewhich dev.sty +kpsewhich dvng10.tfm +kpsewhich dvng10.mf +kpsewhich dvng10.pfb + +If the files are not found or if files from other directories are found +instead, there is something wrong with your installation. It makes no sense to +continue. Return to the previous step and fix the installation. + + +Make font information files +=========================== + +Drivers dvips, dvipdfm, pstopk as well as pdftex require information on fonts. +Create them by: + +updmap --enable=MixedMap dvng.map + +If it says that the fonts are already known and nothing will be changed, it +means that updmap knows some older version. In such a case just run updmap +without any arguments. + +This step is not necessary with MikTeX because it was already done during macro +installation (updmap just adds the mentioned line to updmap.cfg and generates +necessary *.map files). + + +Run a sample document +===================== + +Make a copy of a sample file doc/generic/velthuis/misspaal.dn into another +directory. Now "cd" to that directory and run the file through the +preprocessor by: + +devnag misspaal + +The resulting misspaal.tex file can then be processed by latex into +misspaal.dvi or by pdflatex directly to misspaal.pdf. If you get the same +result as doc/generic/velthuis/misspaal.pdf, then -- {\dn "saabaa"s} -- your +installation is correct. Now you can read the manual (available both as +manual.tex and manual.pdf in the doc/generic/velthuis/ directory) and create +your own Devanagari documents. + + +Frequent errors +=============== + +* (La)TeX cannot find files (*.sty, *.fd, dnmacs.tex) + + Make sure that the directory with Velthuis Devanagari is mentioned in the + TEXMF variable (teTeX, TeX Live) or selected in MikTeX options in the Roots + tab. Refresh the filename database (it never harms anything). + +* PostScript files created by dvips does not contain Type 1 fonts, they are + replaced by roman fonts although dv*.pfb were loaded + + You probably have an old version of dvng.map earlier in the search path or + different version of Type 1 fonts earlier in the search path. The PostScript + names of the fonts have changed. PdfTeX can often cope with it but dvips + cannot and the resulting PostScript file is damaged and unusable. Be sure + that the directory with the Velthuis Devanagari package is at the beginning + of the TEXMF variable (teTeX, TeX Live) or selected in MikTeX options in the + Roots tab as the first one. Then refresh the filename database. Non-MikTeX + users should also run updmap without arguments. diff --git a/Master/texmf-dist/doc/generic/velthuis/captions.dn b/Master/texmf-dist/doc/generic/velthuis/captions.dn new file mode 100644 index 00000000000..689ca67448f --- /dev/null +++ b/Master/texmf-dist/doc/generic/velthuis/captions.dn @@ -0,0 +1,40 @@ +@modernhindi +\def\datemodernhindi{\def\today{\@datenumeric\day\space\ifcase\month\or +{\dn janavarii}\or +{\dn faravarii}\or +{\dn maarca}\or +{\dn apraila}\or +{\dn maI}\or +{\dn juuna}\or +{\dn julAI}\or +{\dn agasta}\or +{\dn sitambara}\or +{\dn aktuubara (ak.tobara)}\or +{\dn navambara}\or +{\dn disambara}\fi\space\@datenumeric\year}} + +\def\captionsmodernhindi{% +\def\abstractname{{\dn saaraa.m"sa}}% +\def\appendixname{{\dn pari"si.s.ta}}% +\def\bibname{{\dn sa.mdar"sa grantha}}% (?) +\def\ccname{}% +\def\chaptername{{\dn adhyaaya}}% +\def\contentsname{{\dn vi.saya-suucii}}% +\def\enclname{{\dn }}% +\def\figurename{{\dn citra}}% rekhaacitra +\def\headpagename{{\dn p.r.s.tha}}% +\def\headtoname{}% +\def\indexname{{\dn suucii}}% +% suucaka +% anukrama.nikaa +% anukrama.ni +\def\listfigurename{{\dn citro.m kii suucii}}% +\def\listtablename{{\dn taalikaao.m kii suucii}}% +\def\pagename{{\dn p.r.s.tha}}% +\def\partname{{\dn kha.n.da}}% +\def\prefacename{{\dn prastaavanaa}}% praakkathana +\def\refname{{\dn havaale}}% +\def\tablename{{\dn taalikaa}}% +\def\seename{{\dn dekhie}}% +\def\alsoname{{\dn aur dekhie}}% +\def\alsoseename{{\dn aur dekhie}}} diff --git a/Master/texmf-dist/doc/generic/velthuis/changes b/Master/texmf-dist/doc/generic/velthuis/changes new file mode 100644 index 00000000000..c539db11f42 --- /dev/null +++ b/Master/texmf-dist/doc/generic/velthuis/changes @@ -0,0 +1,299 @@ +============================================================================= +Devanagari for TeX Release Notes +Version 2.14 14 May 2006 +============================================================================= + += 14 May 2006: version 2.14 + + - The preprocessor can read files with any line endings on all platforms + (i.e. DOS CRLF, UNIX LF as well as Macintosh CR). More precisely: each + CR followed by LF is ignored and each CR followed by anything else is + treated as end of line. The line endings of the output file always + conform to conventions used on the operating system where the + preprocessor runs. + + - @novconjunct implemented as an opposite of @vconjunct. + +----------------------------------------------------------------------------- + += 5 April 2006: version 2.14 + + - Type 1 fonts replaced with better free Type 1 fonts from + CTAN:fonts/ps-type1/indic (author Karel Piska [p\'{\i}\v{s}ka]) + +----------------------------------------------------------------------------- + += 3 April 2006: version 2.14 + + - Preprocessor: characters with code above 128 allowed in {\rm ...} inside + {\dn } text (UTF-8 not implemented yet) + + - Preprocessor: the filename extensions are not fixed but may e given by + the user. Greater details in comments inside devnag.c as well as in + Chapter 5 of the manual + + - Macros: code from dev.sty moved to devanagari.sty and dev.sty is kept + for compatibility with old files + + - Organization: files in CVS reorganized according to the TeX Directory + Standard (TDS) so that installation as well as inclusion in standard + distributions such as TeX Live and MikTeX is easier. Detailed + installation instructions are in the README file. + +----------------------------------------------------------------------------- + += 20 October 2005: version 2.13 + + - Preprocessor: ligature disabling character "+" implemented + + - Preprocessor: bug fix in handling <> characters + + - Preprocessor: ~m is now a synonym for /, i.e. candrabindu. Thus {\dn hU/} + and {\dn hU~m} is the same. + + - Localization captions (\chaptername, \tablename, \today) etc. for Hindi + and Modern Hindi were implemented. Sample file useful for customization + distributed in the input directory. + + - Type 1 fonts regenerated because the METAFONT sources have changed + slightly. + + - Type 1 version of the Pen Nepali fonts created. + + - File dvng.map is now created automatically during conversion to Type 1. + + - Modifications in the manual, compiled again with pdfTeX using the newly + created fonts + + - The releases for CTAN and TeX Live should conform to the TeX Directory + Standard. The README file was updated according to that. + + Note: The new Type 1 fonts have not been tested extensively. The previous + version is therefore temporarily available from + http://hroch486.icpf.cas.cz/velthuis/ and will be removed when we + know that the new version does not cause any problems. + +----------------------------------------------------------------------------- + += 26 March 2005: version 2.12 + + - Modifed avagraha to remove the gap in the top-line between characters. + + - Corrected test parameters for Nepali family in Nepali fonts. + + - Regenerated TFM files for Nepali fonts. + +----------------------------------------------------------------------------- + += 21 March 2005: version 2.12 + + - Revised alternate (Nepali) numeral 9. + + - Regenerated TFM files for Nepali fonts. + +----------------------------------------------------------------------------- + += 14 March 2005: version 2.12 + + - Created Nepali Pen family METAFONT files, metric files, and LaTeX font + description file. + + - Revised dev.sty to add new package options (bombay, calcutta, nepali, + pen, penbombay, pencalcutta, pennepali) for global selection of the font + family (it will work with automatically generated captions). If none are + used, \dnoriginal will be used by default. + + - Added new macro to dev.sty, \dnfamilydefault, which stores the default + family of DN fonts. Default depends on the above mentioned package + options. The user is allowed to redefine it by \renewcommand. + + - Added new \pen macro to dev.sty, which switches to the "pen" variant of + the current family. + + - Added Vedic intonation marks macros \dnveda and \dnsamaveda to dev.sty. + Implemented according to the code from dnmacs.tex. + +----------------------------------------------------------------------------- + += 28 February 2004: version 2.12 + + - Added Vedic intonation mark macros to dnmacs.tex. + + - Revised definitions for letter macros in dnmacs.tex. + +----------------------------------------------------------------------------- + += 2 December 2004: version 2.1 + + - Added correct values for \baselineskip for the defined font sizes in + dnmacs.tex. + +----------------------------------------------------------------------------- + += 1 December 2004: version 2.1 + + - Corrected erroneous output of ~a. + + - Removed redundant definitions of \qa and \qb from dnmacs.tex. + +----------------------------------------------------------------------------- + += 8 April 2004: version 2.1 + + - Created Nepali regional variants for numerals 1 and 9. + +----------------------------------------------------------------------------- + += 14 March 2004: version 2.1 + + - Created a font family for Nepali regional variants. Created new glyphs + for Nepali jha and half-jha. Created Calcutta regional variants for + .l and .L + +----------------------------------------------------------------------------- + += 5 March 2004: version 2.1 + + - Modified preprocessor to provide support for protected text. + Material within {\dn ... } (or $ ... $) may be enclosed within + angle brackets < ... >; it is then not processed, but is passed + through verbatim to the output file. + + - Modified the preprocessor to correct the output of the "half j~na" + glyph in @hindi and @modernhindi modes. + + - Modified the preprocessor to avoid using the control symbols \", \#, + \$, \%, \&, \'. + +----------------------------------------------------------------------------- + += 28 February 2004: version 2.1 + + - Created font families for Bombay and Calcutta regional variants. Removed + general alternate font family. + + - Removed "sba glyph and replaced it with an open-ya. This open-ya is + used to create better conjuncts with word-final ya. Created new .n.na + conjunct based on Calcutta regional form. + +----------------------------------------------------------------------------- + += 13 February 2004: version 2.1 + + - Created new alternate characters for 5 and 8. Modified the alternate + .na and half-.na characters + +----------------------------------------------------------------------------- + += 09 February 2004: version 2.1 + + - Created new alterate la, alternate "sa, alternate lla conjunct, and + alternate half-"sa characters. Modified the alternate front-a, initial + .r, initial .R, cha, jha, chya conjunct, and half-jha characters. + +----------------------------------------------------------------------------- + += 25 January 2004: version 2.1 + + - Minor modifications to the documentation. + +----------------------------------------------------------------------------- + += 01 July 2003: version 2.1 + + - Alternates for several characters have been developed and can be used in + separate alternate fonts along with standard fonts. The alternate + characters are: initial a, initial .r, .na, cha, jha, and their half + letters and ligatures; and the j~na and k.sa ligatures. + + - The source code for the fonts has been reorganized, making the + generation of custom fonts easier. The standard Metafont parameter mag + is now used to control the generation of fonts. All numeric parameters + that were in the control files have been moved to dndefs.mf, and only + mag is declared in the control files of the normal standard font. + Appropriate calculations and assignments are made in dndefs.dn. + Several optional variables have been added for use in base font files. + Boolean values optionally set in a control file determine whether to + select standard or alternate characters, and whether to select bold + and/or italic. The thick and thin paramters that were set directly in + some control files are now modified from a default value by multipliers + (thickmag, subthickmag, and thinmag). The advantage of this is that a + multiplier should remain constant, or nearly constant, for all point + sizes. This technique is used in the pen font control files. The bold + and italic boolean values set these multipliers transparently. defs.mf + has been renamed dndefs.mf. dnchars.mf contains both standard and + alternate characters. + + - The Plain TeX macros have been enhanced to make switching between + Devanagari fonts easier. Enhancements include support for all new + fonts, including pen, alternate, bold, and italic, at all the old + font sizes. + + - New font definition files have been added: udna.fd, upn.fd, upna.fd. + Also new Metafont control files dngen.mf, and dninit.mf. New macros + have been added to dev.sty to enable switching to the four new font + families. + +----------------------------------------------------------------------------- + += 09 June 2003: version 2.02a + + - Bold, italic, bold italic, and pen fonts have been added. + + - The preprocessor was changed. Please refer to the change log + in devnag.c for specific details. + + - udn.fd has been changed to incorporate new font shapes and variants. + + - dev.sty was changed. The macro definitions have been made more robust. + + +----------------------------------------------------------------------------- + += 09 April 2003: version 2.02 + + - Version 2.02 of the preprocessor has been released. The preprocessor was + modified to output all ^^* characters as \3XXw because it is more robust. + It also puts a definition of \DevnagVersion at the beginning of the + output file so that the new preprocessed files can be automatically + recognized. This version also defines a new preprodessor directive + @modernhindi, which functions in the same way as @hindi but uses far + fewer Sanskrit-style ligatures, preferring conjuncts built from + half-consonant forms wherever possible. The definition of @sanskrit has + been changed so that it now restores all the ligatures disabled by + @modernhindi, not just those disabled by @hindi. The sequences dmya and + hmya have been modified to produce d&mya, h&mya (rather than, as + previously, dm&ya, hm&ya). The special warning message prompted by the + long-defunct preprodessor directive @obeylines has been removed. + + - dev.sty was revised to make macros more robust. Several incompatibilities + with other packages have been remediated. Catcode problems may be + avoided by using the 'nocatcodes' option: \usepackage[nocatcodes]{dev} + +----------------------------------------------------------------------------- + += 21 March 2002: version 2.0a + + - Postscript Type 1 version of the dvng fonts have been created and + are now part of this package. Please refer to the readme file in the + misc/type1 directory for installation instructions. + + - Tom Ridgeway's dvpn fonts are now part of this distribution and + reside in the misc/dvpn directory. + +----------------------------------------------------------------------------- + += 23 January 2000: version 2.0 + + - devnag.c has been updated and greatly enhanced. If you have a previously + installed version of devnag, you must recompile the source. + A 32-bit DOS/Win95 executable (devnag.exe) has been provided. + + - dev.sty has been revised to fix certain \catcode problems. Several + new features have been implemented in the package. Refer to the manual + for descriptions. + + - The fonts have been revised. Certain characters have been modified. + The font metrics have not changed. + +============================================================================= diff --git a/Master/texmf-dist/doc/generic/velthuis/copying b/Master/texmf-dist/doc/generic/velthuis/copying new file mode 100644 index 00000000000..60549be514a --- /dev/null +++ b/Master/texmf-dist/doc/generic/velthuis/copying @@ -0,0 +1,340 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/Master/texmf-dist/doc/generic/velthuis/examples.dn b/Master/texmf-dist/doc/generic/velthuis/examples.dn new file mode 100644 index 00000000000..410c4b16b55 --- /dev/null +++ b/Master/texmf-dist/doc/generic/velthuis/examples.dn @@ -0,0 +1,159 @@ +@hyphen +\documentclass[12pt]{article} +\usepackage{dev} +\parindent=0pt + +\begin{document} + +\section{Examples} + +{\dn +\begin{center} +\setlength{\fboxrule}{2pt} +\framebox[3.2cm][s]{.o ga.ne"saaya nama.h} +\end{center} +} + +\verb+{\+{\tt dn} +\begin{verbatim} +\begin{center} +\setlength{\fboxrule}{2pt} +\framebox[4cm][s]{.o ga.ne"saaya nama.h} +\end{center} +} +\end{verbatim} + +\hrule +\medskip + +{\dn\dnnum +atha ga.nitapraarambhe.abhii.s.tadevataa.m namaskaroti| +\begin{itemize} +\setlength{\itemsep}{0mm} +\item nanu pratyadhyaayamabhii.s.tadevataapra.natipratij~nota +granthaarambhe k.rtanamaskaare.naabhii.s.tasiddhirbhavati| +punari.s.tadevataanamaskaare.na ki.m saadhya.m| +\item ucyate divya.m hyatiindriya.m j~naana.m ga.nita.m +munibhirmata.m para.m brahmeva durj~neya.m vidyaanaamuttama.m +tata.h| atho vidyottamatvaatpraarambhe.abhii.s.tadevataasmarana.m +tathaa caadau madhye tathaa caante granthe kaarye.svapi +sm.rta.m ma"ngalaacarana.m ce.s.tadevataapuujanaadi ca| +\end{itemize} +} + +\begin{verbatim} +\documentclass[12pt]{article} +\usepackage[hyphenate]{dev} +\end{verbatim} +%\vspace*{-.45cm} +%\vspace*{-.40cm} +%\begin{verbatim} +\verb+\+\verb+begin{document}+ \\ +%\end{verbatim} +%\vspace*{-.35cm} +\verb+{\+{\tt dn}\verb+\+{\tt dnnum} +\begin{verbatim} +atha ga.nitapraarambhe.abhii.s.tadevataa.m namaskaroti| +\begin{itemize} +\setlength{\itemsep}{0mm} +\item nanu pratyadhyaayamabhii.s.tadevataapra.natipratij~nota +granthaarambhe k.rtanamaskaare.naabhii.s.tasiddhirbhavati| +punari.s.tadevataanamaskaare.na ki.m saadhya.m| +\item ucyate divya.m hyatiindriya.m j~naana.m ga.nita.m +munibhirmata.m para.m brahmeva durj~neya.m vidyaanaamuttama.m +tata.h| +atho vidyottamatvaatpraarambhe.abhii.s.tadevataasmarana.m +tathaa caadau madhye tathaa caante granthe kaarye.svapi +sm.rta.m ma"ngalaacarana.m ce.s.tadevataapuujanaadi ca| +\end{itemize} +} +\end{verbatim} + +\hrule +\medskip + +{\dn \dnnum +ata ubhayathaa smara.na.m yuktatara.m| +\begin{verse} +liilaagalalulallolakaalavyaalavilaasine|\\ +\hspace*{10mm} ga.ne"saaya namo niilakamalaamalakaantaye|| 12|| +\end{verse} +} + +\verb+{\+{\tt dn}\verb+\+{\tt dnnum} +\begin{verbatim} +ata ubhayathaa smara.na.m yuktatara.m| +\begin{verse} +liilaagalalulallolakaalavyaalavilaasine|\\ +\hspace*{10mm} ga.ne"saaya namo niilakamalaamalakaantaye|| 12|| +\end{verse} +} +\end{verbatim} + +\hrule +\medskip + +{\dn \bfseries +ata ubhayathaa smara.na.m yuktatara.m| +} + +\verb+{\+{\tt dn} +\begin{verbatim} + \bfseries ata ubhayathaa smara.na.m yuktatara.m|} +\end{verbatim} + +\hrule +\medskip + +{\dn \Large ata ubhayathaa smara.na.m yuktatara.m|} + +\verb+{\+{\tt dn} +\begin{verbatim} + \Large ata ubhayathaa smara.na.m yuktatara.m|} +\end{verbatim} + +\hrule +\medskip + +{\dn \dncalcutta ata ubhayathaa smara.na.m yuktatara.m|} + +\verb+{\+{\tt dn} +\begin{verbatim} + \dncalcutta ata ubhayathaa smara.na.m yuktatara.m|} +\end{verbatim} + +\hrule +\medskip + +{\dn \dnpen ata ubhayathaa smara.na.m yuktatara.m|} + +\verb+{\+{\tt dn} +\begin{verbatim} + \dnpen ata ubhayathaa smara.na.m yuktatara.m|} +\end{verbatim} + +\newpage +\hrule +\medskip + +{\dn\dnnum +"sriibhaaskaraacaaryaga.nita"saastrebhya udaahara.naani +\begin{enumerate} +\item liilavaatii +\item biijaga.nita.m +\item grahaga.nita.m +\end{enumerate} +} + +\verb+{\+{\tt dn}\verb+\+{\tt dnnum} +\begin{verbatim} +"sriibhaaskaraacaaryaga.nita"saastrebhya udaahara.naani +\begin{enumerate} +\item liilavaatii +\item biijaga.nita.m +\item grahaga.nita.m +\end{enumerate} +} +\end{verbatim} + +\end{document} diff --git a/Master/texmf-dist/doc/generic/velthuis/examples.pdf b/Master/texmf-dist/doc/generic/velthuis/examples.pdf new file mode 100644 index 00000000000..5ba3405f86a Binary files /dev/null and b/Master/texmf-dist/doc/generic/velthuis/examples.pdf differ diff --git a/Master/texmf-dist/doc/generic/velthuis/manual.pdf b/Master/texmf-dist/doc/generic/velthuis/manual.pdf new file mode 100644 index 00000000000..be4e608daff Binary files /dev/null and b/Master/texmf-dist/doc/generic/velthuis/manual.pdf differ diff --git a/Master/texmf-dist/doc/generic/velthuis/manual.tex b/Master/texmf-dist/doc/generic/velthuis/manual.tex new file mode 100644 index 00000000000..f9e928da856 --- /dev/null +++ b/Master/texmf-dist/doc/generic/velthuis/manual.tex @@ -0,0 +1,1662 @@ +% +% manual.tex v2.14 +% +% LaTeX source file for the manual for the Devanagari for TeX" package. +% Copyright (C) 1991-2003 University of Groningen, The Netherlands +% +% Author : Anshuman Pandey +% $Id: manual.tex,v 1.6 2006/05/29 09:00:12 icebearsoft Exp $ +% +% This program is free software; you can redistribute it and/or modify +% it under the terms of the GNU General Public License as published by +% the Free Software Foundation. +% +% This program is distributed in the hope that it will be useful, +% but without any warranty; without even the implied warranty of +% merchantability or fitness for a particular purpose. See the +% GNU General Public License for more details. +% + +\documentclass[10pt]{article} +\def\DevnagVersion{new} +\usepackage{geometry,fancyhdr,multicol,mflogo,textcomp,parskip,array,color} +\usepackage{devanagari} +\renewcommand{\rmdefault}{ptm} + +\geometry{paperwidth=8.5in, + paperheight=11in, + top=.875in, + bottom=1in, + left=1.25in, + right=1.25in, + headheight=0pt, + headsep=0pt, + } + +\usepackage{hyperref} + +% High resolution pk fonts for pdfTeX +\ifx\pdfpkresolution\undefined \else + \pdfpkresolution 600 +\fi + +\newcommand{\moddate}{27 May 2006} +\newcommand{\version}{2.14} +\renewcommand{\headrulewidth}{0pt} +\setcounter{secnumdepth}{3} +\setcounter{tocdepth}{3} +\setlength{\columnseprule}{0pt} + +\newcommand{\devnag}{Devan\=agar{\=\i}} + +\def\diatop[#1|#2]{{\leavevmode\setbox1=\hbox{{#1{}}}\setbox2=\hbox{{#2{}}}% + \dimen0=\ifdim\wd1>\wd2\wd1\else\wd2\fi% + \dimen1=\ht2\advance\dimen1by-1ex% + \setbox1=\hbox to1\dimen0{\hss#1\hss}% + \rlap{\raise1\dimen1\box1}% + \hbox to1\dimen0{\hss#2\hss}}}% + +\def\underrng #1{\oalign{#1\crcr\hidewidth + \vbox to.2ex{\hbox{\char"17}\vss}\hidewidth}} + +\clubpenalty 10000 +\widowpenalty 10000 + +\begin{document} +\pagestyle{fancy} +\fancyhf{} +\fancyfoot[C]{\thepage} + +\fontsize{10}{13}\selectfont + +\title{{\LARGE \bfseries \devnag{} for \TeX{}} \\ Version \version{}} +\author{Anshuman Pandey} +\date{\large \moddate{}} +\maketitle + +\tableofcontents +%\newpage + +\listoftables + +\section{Introduction} + +The \textit{\devnag{} for \TeX{}} (\textsf{devnag}) package provides a +way to typeset high-quality \devnag{} text with \TeX{}. +\devnag{} is a script used for writing and printing Sanskrit and +a number of languages in Northern and Central India such as Hindi and +Marathi, as well as Nepali. The \textsf{devnag} package was originally +developed in May 1991 by Frans Velthuis for the University of Groningen, +The Netherlands, and it was the first system to provide support for +the \devnag{} script for \TeX{}. + +Several individuals have contributed to the \textsf{devnag} package +over the years. Kevin Carmody proposed a method for managing variant +glyphs. Marc Csernel revised the preprocessor to handle standard +\LaTeX{} commands. Richard Mahoney generated PostScript Type~1 +versions of the \devnag{} fonts. These fonts were later (in version~2.14) replaced with optimized +Type~1 fonts created by Karel P\'{\i}\v{s}ka. Fran\c{c}ois Patte enhanced the \LaTeX{} package by +introducing +a feature to produce citations in \devnag{}. Zden\v{e}k Wagner greatly improved the \LaTeX{} +package by revising macro definitions and catcodes, eliminating +conflicts with other packages, and by introducing support for +section headings and captions in \devnag{}. Rob Adriaanse, Hans Bakker, +Roelf Barkhuis, and Henk van Linde provided advice and support +to Frans Velthuis when this package was being developed. + +The \textsf{devnag} package is presently maintained by the following +individuals: + +\begin{quote} +\begin{tabular}{ll} +% Frans Velthuis & \verb+velthuis@rc.rug.nl+ \\ +John Smith & \verb+jds10@cam.ac.uk+ \\ +Anshuman Pandey & \verb+apandey@u.washington.edu+ \\ +Dominik Wujastyk & \verb+d.wujastyk@ucl.ac.uk+ \\ +%Fran\c{c}ois Patte & \verb+patte@math-info.univ-paris5.fr+ \\ +Zden\v{e}k Wagner & \verb+wagner@cesnet.cz+ \\ +Kevin Carmody & \verb+i@kevincarmody.org+ +\end{tabular} +\end{quote} + + +\section{Project Information} + +The \textit{\devnag{} for \TeX{}} package is now a project +officially housed at Sarovar. The homepage is + +\begin{quote} +\texttt{http://devnag.sarovar.org/} +\end{quote} + +This package is available from the project homepage at Sarovar and +from the Comprehensive \TeX{} Archive Network (CTAN). The CTAN path +for the package at the primary UK TUG site is + +\begin{quote} +\texttt{ftp://ftp.tex.ac.uk/tex-archive/language/devanagari/velthuis/} +\end{quote} + +Please use the tracking system at the project homepage at Sarovar to +submit feature requests, bugs, comments, and questions to the development +team. + + +\section{Producing \devnag{} Text with \TeX{}} + +\devnag{} text may be included in any \TeX{} document. There are three steps +to producing \devnag{} text with \TeX{}. First, since \TeX{} does +not support \devnag{} natively, it is necessary to type \devnag{} using +\hbox{7-bit} (ASCII) roman characters that represent \devnag{} characters. +Secondly, transliterated \devnag{} text must be entered within +\textsf{devnag}-specific delimiters. These delimiters allow the preprocessor +to recognize the \devnag{} sections of the \TeX{} document. Third, the +transliterated input must be converted by the preprocessor into a format +that \TeX{} understands. The preprocessor scans the document for +\textsf{devnag} delimiters. Once it finds a delimiter, the program operates +on the text only within the scope of the delimiter. All other document text, +with the exception of \TeX{} macros and \textsf{devnag}-specific preprocessor +directives, is ignored. + +Shown below is a \devnag{} passage followed by the 7-bit transliterated +input that produced it. + +\begin{quote} +{\dn Dm\0\322w\?/\? \7{k}z\322w\?/\? smv\?tA \7{y}\7{y}(sv,.\\ +mAmkA, pA\317wXvA\396w\4v Ekm\7{k}v\0t s\2jy..\par} +\end{quote} + +\begin{quote} +\begin{verbatim} +{\dn dharmak.setre kuruk.setre samavetaa yuyutsava.h | \\ +maamakaa.h paa.n.davaa"scaiva kimakurvata sa.mjaya ||} +\end{verbatim} +\end{quote} + +\subsection{Macros and Font Definition Files} + +\begin{description} +\item[\texttt{dnmacs.tex}] This file contains Plain \TeX{} macros for +\textsf{devnag} and various font-sizing commands. It must be loaded at +the beginning of the document with the command \verb+\input dnmacs+. + +\item[\texttt{devanagari.sty}] This file provides \LaTeX{} support for +\textsf{devnag}. It must must be loaded in the preamble of the document +with the command \verb+\usepackage{devanagari}+. Section \ref{catcodes} +discusses advanced package options that may be declared with +\texttt{devanagari.sty}. The associated font definition files \texttt{udn*.fd} +provide NFSS support for \LaTeX{} for the \textsf{dvng} fonts. + +\item[\texttt{dev.sty}] This file is kept for compatibility with old documents. +It merely loads \texttt{devanagari.sty}. Do not use it in new documents. + +\item[\texttt{dev209.sty}] This file provides legacy support for the +obsolete \LaTeX{} 2.09. It should not be used. \end{description} + +\subsection{Text Delimiters} + +The preprocessor recognizes the text it is to act upon by use of +delimiters, of which there are two types. The basic delimiter is the +\verb+\dn+ macro. This delimiter is used by enclosing \devnag{} text +between \verb+{\dn ... }+, eg. \verb+{\dn acchaa}+. + +The second delimiter is the \verb+$+ character. \devnag{} text +is enclosed between \verb+$ ... $+, eg. \verb+$acchaa$+. The +\verb+@dollars+ preprocessor directive must be specified to activate +this delimiter (section \ref{dol}). + +The first delimiter is recommended especially for large blocks of +\devnag{} text. The second delimiter is useful when there is a need +to switch often between \devnag{} and roman text. Any text outside +of delimiters is not parsed by the preprocessor. + +There are very few restrictions on what may be placed between the +delimiters. The 7-bit Velthuis encoding shown in Table \ref{chars}, all +punctuation marks, and all \TeX{} macro commands are acceptable input. +The preprocessor will produce a warning for unrecognized input +characters and commands. + +\subsection{Example Input Files} + +Two sample \devnag{} documents are bundled with this distribution. +Please refer to the contents of these files for examples of producing a +\devnag{} document. The file \texttt{misspaal.dn} contains an excerpt +from the Hindi short story \textit{Miss Pal} by Mohan Rakesh. The file +\texttt{examples.dn} contains some advanced examples of \devnag{} +typesetting. Shown below are two small examples of Plain \TeX{} and +\LaTeX{} documents with \devnag{} text. + +\begin{multicols}{2} + +\begin{verbatim} + % Sample TeX input file + \input dnmacs + {\dn devaanaa.m priya.h} + \bye +\end{verbatim} + +\columnbreak + +\begin{verbatim} + % Sample LaTeX input file + \documentclass{article} + \usepackage{devanagari} + \begin{document} + {\dn devaanaa.m priya.h} + \end{document} +\end{verbatim} + +\end{multicols} + +The filename of the \TeX{} document that contains \devnag{} should +be given a \texttt{.dn} extension. The preprocessor will produce +a filename with a \texttt{.tex} extension after processing the +input file. + +\section{Input Encoding} +\label{trans} + +\devnag{} text is prepared using a 7-bit (ASCII-based) transliterated +input encoding in which \devnag{} characters are represented by Roman +characters. The input encoding for \textsf{devnag} was developed by +Frans Velthuis with the objective to keep the format of the input source +text as close as possible to the accepted scholarly practices for +transliteration of \devnag{}. The Velthuis encoding is widely used and +has been adapted by other Indic language \TeX{} packages, and also +serves as the basis of other Indic transliteration schemes. + +\subsection{Supplemental Notes} +Attention should be paid to the following points: +\begin{enumerate} +\item There are different ways to produce consonant conjuncts. For +example, the sequence \texttt{ktrya} can be represented as {\dn \3FCw} +and as {\dn ?\3ECwy}. The creation of conjuncts may be controlled +through the use of the preprocessor directives \verb+@sanskrit+, +\verb+@hindi+, and \verb+@modernhindi+, and more strictly through the +\verb+@lig+ directive. Please refer to Table \ref{ligs} for a list of +supported conjuncts. + +\item There are two different ways to produce long vowels: +typing the short vowel twice or by capitalizing the short vowel, eg. +\texttt{aa} or \texttt{A} for {\dn aA}. + +\item Aspirated consonants may be produced alternately by capitalizing +the voiceless counterpart. For example, the standard encoding for +{\dn B} is \texttt{bha}, but it may also be produced by \texttt{Ba}; +{\dn G} is \texttt{gha} or \texttt{Ga}; etc. + +\item For words which have two successive short vowels, a sequence of +brackets \verb+{}+ may be used to separate the vowels, eg. {\dn +\3FEw{}ug} \verb+pra{}uga+, as opposed to {\dn \3FEwOg} \verb+prauga+ . +This is required because the combinations \verb+ai+ and \verb+au+ +represent the dipthongs {\dn e\?} and {\dn aO}. + +\item The use of uppercase letters to indicate long vowels may be +preferred in cases where ambiguity might arise. When encoding a word +like {\dn kI}, the sequence \verb+kaii+ will produce the incorrect form +{\dn k\4i}, while \verb+kaI+ will yield the correct form {\dn kI}. A +sequence of brackets, as in the previous note, will also produce the +correct form, eg. \verb+ka{}ii+. + +\item The standard ligatures {\dn\symbol{34}}, {\dn \3E2w}, and {\dn /} +are produced by \verb+k.sa+, \verb+j~na+, and \verb+tra+. + +\item Candrabindu may be encoded either as a slash, as given in +Table~\ref{chars}, or by \verb+~m+. + +% \item \verb+~a+ produces an `English a' Marathi style. For example, +% Hindi {\dn V\4?sF} and Marathi {\dn V\+ +delimiters. In the example below, the font command between the angle brackets +will be ignored by the preprocessor, but will be removed from the +output file. + +For example, with \verb+{\dn dharmak.setre <\font\zzz=dvng10 at 18pt> kuruk.setre}+ +the preprocessor will operate on \texttt{dharmak.setre} and \texttt{kuruk.setre}, +but will ignore \verb+\font\zzz=dvng10 at 18pt+ because it occurs within the +\verb+<+ and \verb+>+ delimiters. + +\subsection{Breaking Pre-Defined Conjuncts} +The preprocessor will automatically produce predefined ligatures +from certain sequences of consonants. Placing the \texttt{+} character +between two consonants prevents any predefined ligature representing +those consonants from being produced. Instead a conjunct will be +created from half-forms, or, if half-forms do not exist, full forms +stopped with \textit{vir\=ama} will be used. + +For example, the sequence \texttt{kha} will produce {\dn K}. Using +\texttt{+} to break the sequence -- \texttt{k+ha} -- will create {\dn ?h}. + +The use of \texttt{+} is similar to the use of \verb+{}+. +For example, write \verb+t{}ha+ to produce {\dn \qq{t}{}h}, if +desired instead of \verb+tha+ {\dn T}. + +The \texttt{+} character can be used independently of the \verb+@lig+/\verb+@nolig+ +directives, and it can disable any conjunct. Note that the \texttt{+} character +only disables single occurrences of a conjunct. To disable all occurrence +of a conjunct use the \verb+@lig+ directive. + +\subsection{Supported \LaTeX{} Commands} +The preprocessor recognizes some \LaTeX{} macros with arguments. The +following command types are legal within delimiters. + +\begin{itemize} +\item Font commands: Standard \TeX{} size-changing commands, +eg. \verb+\small+, \verb+\large+, \verb+\huge+. + +\item Environments, including the three table environments: +\verb+tabular+, \verb+supertabular+, and \verb+longtable+. Note: To use +table environments within delimited text, the \verb+@tabs+ directive +must be specified in order to enable the use of the ampersand as a tab +marker instead of a marker for \textit{vir\=ama}. Refer to Section +\ref{directives} for more details on preprocessor directives. + +\item Spaces: \verb+\hspace+, \verb+\hspace*+, \verb+\vspace+, +\verb+\vspace*+, \verb+\addvspace+, \verb+\setlength+, \verb+\addtolength+, +\verb+\enlargethispage+, \verb+\enlargethispage*+, and +\verb+\\[+\textit{n}\verb+]+. Plain \TeX{} commands may also be used +when placed between brackets: \verb+{\hskip }+, \verb+{\vskip }+, +\verb+{\vadjust }+, and \verb+{\kern }+. + +\item Counters: \verb+\setcounter+, \verb+\stepcounter+, +\verb+\addtocounter+, and \verb+\refstepcounter+. Page numbering in +\devnag{} is also available through the \verb+dev+ counter. + +\item Boxes and rules: \verb+\parbox+, \verb+\makebox+, +\verb+\framebox+, \verb+raisebox+, and \verb+\rule+. + +\item References: \verb+\label+, \verb+\ref+, \verb+\pageref+, +\verb+\index+, \verb+\cite+, and \verb+\bibitem+. If the argument of the +\verb+\index+ command is in \devnag{}, it will appear in \devnag{} +in the index file. + +\item File commands: \verb+\input+ and \verb+\include+. + +\item Roman text may also be embedded within \devnag{} delimited text as +long as the Roman does not exceed the length of one line. Use +\verb+{\rm ... }+ to produce embedded Roman text. +\end{itemize} + +\subsection{Using Custom \LaTeX\ Commands} +\LaTeX\ users take advantage of numerous commands from various packages. All packages will never be +supported directly but solution is easy. As a matter of fact, all control sequences without +arguments or taking \devnag\ text as argument can be used without problem. Suppose the you want to +colorize text {\dn \textcolor{red}{: t(s\qq{t}}} using the \verb;\textcolor; command from the +\textsc{color} package. The bare word \textit{red} must not be converted. Conversion can be +suppressed by mechanism described in section~\ref{protecting}. One can write e.\,g.: + +\begin{verbatim} +{\dn \textcolor<{red}>{.o tatsat}} +\end{verbatim} + +It is, however, preferable to separate meaning and form. If a macro, e.\,g.\@ \verb;\myemph; is +defined, it is possible to decide later how the text will be emphasized. The text will then be +entered as follows: + +\begin{verbatim} +\def\myemph#{\textcolor{red}} +{\dn \myemph{.o tatsat}} +\end{verbatim} + +Using such an approach one does not need any escaping mechanism at all. + +\section{\devnag{} Fonts} + +The \textsf{devnag} package provides three font families in addition to +the Standard family: Bombay, Calcutta, and Nepali. All families are +available in regular, oblique, bold, bold oblique, and pen shapes +and weights. The Bombay, Calcutta, and Nepali families provide +variant glyphs which are predominant regional forms for certain +characters, as shown in Table \ref{diffs}. + +\begin{itemize} +\item \verb+\dnbombay+ switches to the Bombay family +\item \verb+\dncalcutta+ switches to the Calcutta family +\item \verb+\dnnepali+ switches to the Nepali family +\item \verb+\dnoriginal+ switches back to the default regular family +\item \verb+\dnpen+ switches to the Pen family +\item \verb+\dnpenbombay+ switches to the Bombay Pen family +\item \verb+\dnpencalcutta+ switches to the Calcutta Pen family +\item \verb+\dnpennepali+ switches to the Nepali Pen family +\end{itemize} + +The oblique, bold, and bold oblique shapes and weights are produced +using standard \LaTeX{} macros. Oblique is obtained with either of the +\verb+\textit{}+ or \verb+\itshape+ font-changing commands. Bold is +obtained with either \verb+\textbf{}+ or \verb+\bfseries+. Bold oblique +requires a combination of the bold and oblique commands, such as +\verb+\bfseries\itshape+. + +To use bold, oblique, and bold oblique varieties in Plain \TeX{}, use the macros +\verb+\dnbf+ and \verb+\dnit+. The regional families are accessed using the +macro commands described above. See \texttt{dnmacs.tex} for further information. + +Font size may be controlled in \LaTeX{} with the standard font sizing +commands. In Plain \TeX{}, font size may be controlled with the following +macros: \verb+\dnsmall+, \verb+\dnnine+, \verb+\dnnormal+, +\verb+\dnhalf+, \verb+\dnbig+, \verb+\dnlarge+, and \verb+\dnhuge+. See +\texttt{dnmacs.tex} for further information. + +\subsection{Bombay-Style Fonts} + +The family name for the Bombay \devnag{} fonts is \textsf{dnb}. To +access this family, use the command \verb+\dnbombay+ after the +\verb+\dn+ macro. Standard \LaTeX{} font commands like +\verb+\fontfamily{dnb}+ and \verb+\usefont{U}{dnb}{}{}+ may be used to +access the Bombay fonts, however, these commands conflict with the +preprocessor. Access to the Bombay family within \devnag{} +environments should be restricted to the \verb+\dnbombay+ macro. +Use the command \verb+\dnoriginal+ to return to the standard \devnag{} +font. + +\subsection{Calcutta-Style Fonts} + +The family name for the Calcutta \devnag{} fonts is \textsf{dnc}. In roder to +access this family, use the command \verb+\dncalcutta+ after the +\verb+\dn+ macro. Standard \LaTeX{} font commands like +\verb+\fontfamily{dnc}+ and \verb+\usefont{U}{dnb}{}{}+ may be used to +access the Calcutta fonts, however, these commands conflict with the +preprocessor. Access to the Calcutta family within \devnag{} +environments should be restricted to the \verb+\dncalcutta+ macro. +Use the command \verb+\dnoriginal+ to return to the standard \devnag{} +font. + +\subsection{Nepali-Style Fonts} + +The family name for the Nepali \devnag{} fonts is \textsf{dnn}. To +access this family, use the command \verb+\dnnepali+ after the +\verb+\dn+ macro. Standard \LaTeX{} font commands like +\verb+\fontfamily{dnn}+ and \verb+\usefont{U}{dnn}{}{}+ may be used to +access the Nepali fonts, however, these commands conflict with the +preprocessor. Access to the Nepali family within \devnag{} +environments should be restricted to the \verb+\dnnepali+ macro. +Use the command \verb+\dnoriginal+ to return to the standard \devnag{} +font. + + +\subsection{\devnag{} Pen Fonts} + +The \devnag{} Pen family is a simple modification of the Standard +face created by Tom Ridgeway, which resembles Devanagari written +with a pen. Standard Pen fonts are available as the family \textsf{dnp} and may be +accessed within \devnag{} environments with the command \verb+\dnpen+. The +Pen family for the Bombay style are available as the family \textsf{dnpb}, +and may be accessed with the command \verb+\dnpenbombay+. The Pen family for +the Calcutta style is called \textsf{dnpc} and may be accessed with the command +\verb+\dnpencalcutta+. The Pen family for the Nepali style is called \textsf{dnpn} +and may be accessed with the command \verb+\dnpennepali+. Use the command +\verb+\dnpen+ to return to the standard \devnag{} Pen font. + + +\subsection{Default \devnag{} Font (\LaTeX{} Only)} + +The \devnag{} package provides options \verb+bombay+, \verb+calcutta+, +\verb+nepali+, \verb+pen+, \verb+penbombay+, \verb+pencalcutta+, and +\verb+pennepali+ so as to set the corresponding font as the default one. It may +seem that using \verb+\dncalcutta+ at the beginning of the document is +sufficient. However, as we will show later in this document, the \devnag{} +package may create automatically some captions as well as a running head. When +producing such texts, \LaTeX{} is set to use Roman fonts and the automatic text +switches to \devnag{} just by \verb+\dn+. You would thus see {\dn\dncalcutta +a@yAy} in the normal text but {\dn a@yAy} in automatic captions which is +undesirable. The package options inform which font style should be used as +default. + +It is also possible to change the default font by defining macro +\verb+\dnfamilydefault+. + +The font switching commands described in the previous subsections can be used +for local changes of the style. + +\subsection{PostScript Type 1} + +The package now includes Type~1 fonts created by Karel P\'{\i}\v{s}ka using an +analytic fit. The fonts included here are a subset of his release of Indic +Type~1 fonts that are available from CTAN:fonts/ps-type1/indic and licensed +under GPL. + + An accurate analytic fit of outline contour curves taken from the \MP{} +output helps to avoid artifacts produced by an autotracing bitmap approach. +It allows to keep preciseness of calculations and to produce the outline +fonts faithful, optimal (to minimize their space amount) and hinted. +Therefore the results are not only more precise than fonts presented earlier +but also occupy a smaller place even if they include hinting additionally. +The distribution contains the PFB and TFM files both with accurate glyph +widths. The user UniqueID are present to distinguish fonts +during download process in PostScript printers and other RIP devices. + +The AFM files have be considered as derived files not usable for TFM creation, +because the \textsc{afm2tfm} program has a feature to round the glyph widths +and is not able to reproduce the original metrics. Use these files only with +tools that explicitly require AFM. + +To use the Type 1 fonts with \texttt{dvips} and pdf\TeX, it is in modern +\TeX{} distributions sufficient to run +\texttt{mktexlsr} or \texttt{texhash} and then issue: + +\begin{verbatim} +updmap --enable MixedMap=dvng.map +\end{verbatim} + +If you do not have \texttt{updmap}, you must +edit the local \textsf{dvips} \texttt{psfonts.map} +file to contain a reference to \texttt{dvng.map}; or copy the contents +of \texttt{dvng.map} into \texttt{config.ps}. + +Detailed installation instructions can be found in the README file in the root +directory of the CVS working copy or in the \texttt{doc/generic/velthuis/} +directory in the release package. + +% \subsection{Creating Custom Font Varieties} +% +% The \MF{} source files have been organized to make it easy to produce +% custom font varieties, such as larger point sizes, fonts that contain +% some alternate letters but not others, and non-standard bold and oblique +% fonts. For further information, see the comments in \texttt{dngen.mf}. +% If you are using \LaTeX{}, you may need to modify \texttt{devanagari.sty}, and +% add or modify \texttt{.fd} files. For Plain \TeX{}, you may want to +% modify \texttt{dnmacs.tex}. + +\section{Special Topics}\label{spec} + +\subsection{Delimiter Scope} +The \LaTeX{} font-size commands may be used within +\devnag{} delimited text, however, as a general rule, the font-size +command should follow the \verb+\dn+ delimiter, otherwise +the font definition commands of \verb+\dn+ will be overridden. For +example, items 1, 2, and 3 below produce the correct forms, but +4 does not: + +\begin{quote} +\begin{tabular}{llcl} +1. & \verb+{\dn \large acchaa}+ & $\rightarrow$ & {\dn aQCA} \\ +2. & \verb+{\dn {\large acchaa}}+ & $\rightarrow$ & {\dn aQCA} \\ +3. & \verb+{\large {\dn acchaa}}+ & $\rightarrow$ & {\dn aQCA} \\ +4. & \verb+{\large \dn acchaa}+ & $\rightarrow$ & {\dn acchaa} \\ +\end{tabular} +\end{quote} + +\subsection{Line Spacing} +Due to the super- and subscript characters of the \devnag{} script, the +default line spacing (leading) often needs to be increased to prevent +the crowding of lines. The parameter \verb+\baselineskip+ +(\verb+\linespread+ for \LaTeX{}) controls the line spacing. + +\TeX{} determines and adjusts the value of \verb+\baselineskip+ after it +finishes processing a paragraph. If a paragraph contains a mixture of +\devnag{} and Roman text, and ends with Roman text, then \TeX{} will set +the value of \verb+\baselineskip+ according to the Roman text. This may +result in crowding of \devnag{} text. + +There are, however, solutions to this. An explicit value can be assigned +to \verb+\baselineskip+ before the paragraph ends. The macro file +\texttt{dnmacs.tex} shows examples of the value of \verb+\baselineskip+ +at different font sizes. Default line spacing is also set in +\texttt{devanagari.sty}. Alternately, `dummy' \textsf{devnag} text containing +\verb+\par+ can be placed at the end of the paragraph, eg. +\verb+{\dn \par}+. + +Even when a paragraph has only \textsf{devnag} text, the paragraph-end +command must be included within \textsf{devnag} text, meaning that the +closing delimiter, which ends the \textsf{devnag} text, must follow +the empty line or the \verb+\par+ command that forces the paragraph to +end. + +\subsection{Hyphenation} +\label{hyphenation} + +The \texttt{devnag} package does more or less all that needs to be done +from the point of view of hyphenating Sanskrit in \devnag{} through the +\texttt{@hyphen} and \texttt{@nohyphen} directives, which are discussed in +section \ref{directives}. If hyphenation is off, then there are no hyphens, +and very stretchy inter-word space. This is acceptable for ragged-right +settings or for text in verse form, but may produce poor results +in right-justified prose text, especially if the given passage contains +long compound words. If hyphenation is on then discretionary hyphens are +set between all syllables. + +\subsection{Captions and Date Formats (\LaTeX{} only)} +The language modules of the \textsf{babel} package change captions texts and +date formats. Although \textsf{devanagari.sty} is not a \textsf{babel} module, similar +mechanism is implemented here. Macros \verb=\datehindi= and +\verb=\datemodernhindi= enable Europian style Hindi date generated by the +standard \verb=\today= command. The ``traditional'' and ``modern'' variants +comtain the same names of the months, they differ only in the ligatures used. +You should therefore use \verb=\datemodernhindi= in documents processed with +\verb=@modernhindi=. The names of the months used in the definition of +\verb=\datemodernhindi= are summarized in Table~\ref{months}. + +\begin{table}[bth] +\centering +\extrarowheight 2pt +\begin{tabular}{|rl|rl|}\hline +1 & {\dn jnvrF} & 7 & {\dn \7{j}lAI}\\ +2 & {\dn \327wrvrF} & 8 & {\dn ag-t}\\ +3 & {\dn mAc\0} & 9 & {\dn EstMbr}\\ +4 & {\dn a\3FEw\4l} & 10 & {\dn a?\8{t}br}\\ +5 & {\dn mI} & 11 & {\dn nvMbr}\\ +6 & {\dn \8{j}n} & 12 & {\dn EdsMbr}\\\hline +\end{tabular} + +\caption{Names of the months in the definition of +\texttt{\char92 datemodernhindi}}\label{months} +\end{table} + +The captions are similarly switched to Hindi by \verb=\captionshindi= or +\verb=\captionsmodernhindi=, respectively. Again the texts differ only in the +ligatures used. The captions for the modern Hindi variant are given in +Table~\ref{captions}. + +\begin{table}[bt] +\centering +\extrarowheight 2pt +\begin{tabular}{|>{\tt\char92 }l|l|}\hline +\multicolumn{1}{|l|}{\bfseries Macro} & \bfseries Caption \\\hline +abstractname & {\dn sArA\2f}\\ +appendixname & {\dn pErEf\309wV}\\ +bibname & {\dn s\2df\0 g\5\306wT}\\ +ccname & \\ +chaptername & {\dn a@yAy}\\ +contentsname & {\dn Evqy{\rs -\re}\8{s}cF}\\ +enclname & {\dn }\\ +figurename & {\dn Ec/}\\ +headpagename & {\dn \9{p}\309wW}\\ +headtoname & \\ +indexname & {\dn \8{s}cF}\\ +listfigurename & {\dn Ec/o{\qva} kF \8{s}cF}\\ +listtablename & {\dn tAElkAao\2 kF \8{s}cF}\\ +pagename & {\dn \9{p}\309wW}\\ +partname & {\dn K\317wX}\\ +prefacename & {\dn \3FEw-tAvnA}\\ +refname & {\dn hvAl\?}\\ +tablename & {\dn tAElkA}\\ +seename & {\dn d\?EKe}\\ +alsoname & {\dn aOr d\?EKe}\\ +alsoseename & {\dn aOr d\?EKe}\\\hline +\end{tabular} + +\caption{Modern Hindi captions}\label{captions} +\end{table} + +The macros for the \textsc{letter} class are left intentionally empty. The idea +of the \textsf{babel} package is to prepare a universal template for business +letters using a set of macros. The header of the letter would make use of the +\verb=\headtoname= macro which will produce ``To: Mr.\@ Kumar'' in English +letters and ``Komu: pan Kumar'' in Czech letters. If we simply defined +\verb=\headtoname= to {\dn ko}, the universal template would put it before the +name which would be wrong. Hindi requires different word order, namely {\dn +\399wF \7{k}mAr ko}. The universal templates are thus useless in Hindi and the +letter template must be redesigned almost from scratch. It therefore makes no +sense to define the letter macros. + +Two package options are provided: \verb=hindi= and \verb=modernhindi=. If used, +they cause the \verb=\dn= command to switch the caption text and date format as +well. The date format and captions may be switched back by macros +\verb=\dateenglish=, \verb=\dateUSenglish=, and \verb=\captionsenglish=. + +\subsection{Customizing the date and captions} +The user might prefer different caption texts. If just a few texts are to be +changed, they can simply be redefined in the main document, for instace by: + +\begin{verbatim} +\def\indexname{{\dn anukrama.nikaa}} +\end{verbatim} + +This redefinition must appear \textbf{after} \verb=\captionshindi= or +\verb=\captionsmodernhindi= was invoked. + +It is also possible to change all definitions. The source texts in the Velthuis +transliteration can be found in the \texttt{input} directory +(\verb=$TEXMF/tex/latex/devanagr=) in file +\texttt{captions.dn} with some suggested variants in comments. You can either +put modified definitions to your main document (after \textsf{devanagari.sty}) or to a +package of your own. Remember that the preprocessor will not see your package, +you must preprocess it separately. Your package must either reside in the same +directory as your document or in some directory which is searched by \LaTeX. In +the latter case you will have to rebuild the database by running +\textsf{mktexlsr} or \textsf{texhash} in many \TeX{} distributions. + +Do not put your packages to standard distribution directories. You may lose +them when upgrading your \TeX{} distribution. + +\renewcommand\thepage{{\dn\arabic{page}}} + +\subsection{Using \texorpdfstring{{\dn d\?vnAgrF}}{Devanagari} in Sections and References} +All macros necessary for typesetting \devnag{} text are robust. The +section/chapter titles as well as figure and table captions can contain +\devnag{} words. However, the font is changed to the standard document +font before the title is typeset. It is therefore mandatory to use +\verb+\dn+ even if the section title appears inside the \verb+\dn+ +environment. Thus, \verb+\chapter{{\dn mis paal}}+ will be printed +correctly while \verb+{\dn\chapter{mis paal}}+ will always +create garbage text. Section numbers as well as page numbers will be +printed in Roman numerals. + +\subsection{\devnag{} Page Numbers} +Changing page numbers to print \devnag{} numerals is possible by +redefining the \verb+\thepage+ macro. This redefinition places the +\verb+page+ counter in the scope of the \verb+\dn+ delimiter. However, +note that \verb+\arabic{page}+ is enclosed within angle brackets. This +is required because the preprocessor does not recognize the counter +as a command. The pagination for this page till the end of Chapter~\ref{spec} +occurs in \devnag{} through +the following redefintion of \verb+\thepage+: + +\begin{quote} +\verb+\renewcommand\thepage{{\dn<\arabic{page}>}}+ +\end{quote} + +Other counters can be printed in \devnag{} by redefinition macros. For +example, to change section numbering to \devnag{}, redefine +\verb+\thesection+ in a manner similar to \verb+\thepage+ above, using +the \verb+section+ counter instead of \verb+page+: + +\begin{quote} +\verb+\renewcommand\thesection{{\dn<\arabic{section}>}}+ +\end{quote} + +\subsection{Category Codes} +\label{catcodes} +\TeX{} assigns a category code (\verb+\catcode+) to each character. For +example, normal characters are assigned to category 11, and because the +backslash belongs to category 0, it is treated as the first character of +macro commands. + +The fonts in the \textsf{devnag} package use characters with codes below +32. In previous releases of the package the category of these characters was +to 11. However, these catcode assignments caused conflicts with some +packages and with tables where tab characters were used. +Most of these problems could be solved at the macro level, but +unfortunately not all of them. The most serious problem is that words +like {\dn v\char10 t} do not get correctly transfered from section +titles to the table-of-contents. + +A modification of the preprocessor was necessary to resolve this +issue. As a result, a change of character categories is no longer +needed. The output of the revised preprocessor is compatible with +previous releases of \texttt{devanagari.sty}. This fix solves the +table-of-contents problem, but not the conflicts. The new +\texttt{devanagari.sty} is still able to process files generated by the +previous versions of the preprocessor. + +To indicate which version of the preprocessor was used to process a +given \devnag{} file, a string is written to the beginning of the output +\TeX{} file. The macro definition \verb+\DevnagVersion+ is written to +the first line of the output file and indicates the preprocessor +version. If the whole document is present in a single file, the +definition will appear before reading the macro package. The package +then changes its behaviour according to the existence or non-existence +of the above mentioned macro. If the macro is defined, no categories are +changed. If the macro is undefined, the \textsf{devanagari} package assumes +that it is processing an output from an older version of the +preprocessor and the categories of the characters are changed. + +The \textsf{nocatcodes} option is intended for use with files produced +by the old preprocessor. This option changes the categories only within +the \verb+\dn+ environment, not globally for the document. The +\textsf{catcodes} option instructs the package to change the categories +globally. This does not, however, change the categories as a part of +the \verb+\dn+ command. If you assume that the categories can be changed +somewhere in the middle of the document and you wish to set them +properly by \verb+\dn+, you can use the \textsf{compat} option. The +macro \verb+\UnDevCatcodes+ changes catcodes back to the normal values +within the \verb+\dn+ environment. + +\clearpage % forced page break, remove it if the next section does not start + % at the same page as the previous subsection +\section{Vedic Macros} + +\renewcommand\thepage{{\arabic{page}}} + +These macros put Vedic intonation marks above and below individual +Devanagari letters and construct other characters generally used only in +Vedic text. + +There are two groups of these macros, one for Rig Veda, and one for Sama +Veda. To use the Rig Veda macros, you must first enter the command +\verb=\dnveda= +at some point after \verb=\input dnmacs= in plain \TeX\ or after \verb=\usepackage{devanagari}= in +\LaTeX , and to use the Sama Veda accents, you must first type \verb=\dnsamaveda=. + +Both of these modes redefine standard macro names already used in Plain \TeX{} +and \LaTeX. In Rig Veda mode the macros \verb=\_=, \verb+\=+, \verb=\|=, and +\verb=\~= are redefined, +while in Sama Veda mode, \verb=\^= and \verb=\@= are redefined. If your document already +uses these macros in their original sense, then use \verb=\dnveda= or +\verb=\dnsamaveda= only within \verb=\dn= mode. Otherwise, use \verb=\dnveda= +or \verb=\dnsamaveda= once +at the beginning of the document. + +This approach to macro names has been used because, when intonation marks +are needed, they are needed very frequently and are inserted into parts of +words, so the macro names should be very short and symbolic. + +\subsection{Rig Veda Macros} + +\subsubsection{Anudatta (low) tone macro\texorpdfstring{ \texttt{\char92\_}}{}, variable width} + +This macro takes one argument, the text letter. +Example: \verb=\dnveda ... {\dn \_{a}gnim}= + +This macro may be combined with \verb=\|= for a pluta mark: \verb=\_{\|{3}}=. + +The anudatta mark produced by this macro is nearly as wide as the letter and +thus varies in width from one letter to another. + + +\subsubsection{Anudatta (low) tone macro\texorpdfstring{ \texttt{\char92=}}{}, fixed width} + +This macro takes one argument, the text letter. +Example: \verb+\dnveda ... {\dn \={a}gnim}+ + +This macro may be combined with \verb=\|= for a pluta mark: \verb+\={\|{3}}+. + +The anudatta mark produced by this macro has a fixed width and is centered +under the letter. + + +\subsubsection{Svarita (rising) tone macro\texorpdfstring{ \texttt{\char92|}}{}} + +This macro takes one argument, the text letter. +Example: \verb=\dnveda ... {\dn \|{ii}Le}= + +This macro may be combined with \verb=\|= for a pluta mark: \verb=\|{\_{3}}=. + + +\subsubsection{Pada separator macro\texorpdfstring{ \texttt{\char92\char126}}{}} + +This macro inserts a pada separtor between two Devanagari letters. + +Example: \verb=\dnveda ... {\dn na\_{ra}\~maa}= + +\subsection{Usage Samples} +This subsection provides two small usage samples of Vedic macros. + + +{\dn\dnnum\Large\dncalcutta +{\dnveda + +\_{a}E`n\|{mF}\30Fw\? \_{\7{p}}ro\|{Eh}t\2 \_{y}\3E2w\|{-y} +\_{d\?}v\_{\9{m}}E(v\|{j}\qq{m} . \ +ho\|{tA}r\2 r\_{\3D7w}DA\|{t}m\qq{m} \quad \rn{1} + +}} + +The text above was typeset by: + +\begin{verbatim} +{\dn\dnnum\Large\dncalcutta +{\dnveda + +\_{a}gni\|{mii}Le \_{pu}ro\|{hi}ta.m \_{ya}j~na\|{sya} +\_{de}va\_{m.r}tvi\|{ja}m | \ +ho\|{taa}ra.m ra\_{tna}dhaa\|{ta}mam \quad 1 + +}} +\end{verbatim} + +\def\samaindent{\parindent=1.0in} +\def\dnitem#1{\noindent\llap{#1\space}\leftskip\parindent} +{\dn\dnnum\dncalcutta +{\dnsamaveda\samaindent +\dnitem{\rn{1}} \^{a}{\rn{2}}\^{`n}{\rn{3}} \^{aA}{\rn{1}} \^{yA}{\rn{2}}Eh +\^{vF}{\rn{3}}\^{t}{\rn{1}}\^{y\?}{\rn{2}} \9{g}\^{ZA}{\rn{3}}\^{no}{\rn{2}} +\^{h}{\rn{3}}\^{\326wy}{\rn{1}}\^{dA}{\rn{2}}ty\? \\ +\^{En}{\rn{1}} ho\^{tA}{\rn{2}r} sE(s \^{b}{\rn{3}}\^{Eh\0}{\rn{1}}\^{Eq}{\rn{2}} \quad \rn{1} + +}} + +The text above was typeset by: + +\begin{verbatim} +\def\samaindent{\parindent=1.0in} +\def\dnitem#1{\noindent\llap{#1\space}\leftskip\parindent} +{\dn\dnnum\dncalcutta +{\dnsamaveda\samaindent +\dnitem{1} \^{a}{2}\^{gna}{3} \^{aa}{1} \^{yaa}{2}hi +\^{vii}{3}\^{ta}{1}\^{ye}{2} g.r\^{.naa}{3}\^{no}{2} +\^{ha}{3}\^{vya}{1}\^{daa}{2}taye \\ +\^{ni}{1} ho\^{taa}{2ra} satsi \^{ba}{3}\^{rhi}{1}\^{.si}{2} \quad 1 + +}} +\end{verbatim} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\begin{table}[pt] +\begin{center} +\renewcommand{\arraystretch}{1.35} +\begin{tabular}{|l|c|c|c|c|} +\hline + & \textsc{original} & \textsc{bombay} & \textsc{calcutta} & \textsc{nepali} \\ +\hline +\textit{a} & {\dn a} & {\dn\dnbombay a} & {\dn\dncalcutta a} & \\ +\textit{\underrng{r}} & {\dn \31Bw} & {\dn\dnbombay \31Bw} & {\dn\dncalcutta \31Bw} & \\ +\textit{\diatop[\=|\underrng{r}]} & {\dn \311w} & {\dn\dnbombay \311w} & {\dn\dncalcutta \311w} & \\ +\textit{\underrng{l}} & {\dn \318w} & {\dn\dnbombay \318w} & {\dn\dncalcutta \318w} & \\ +\textit{\diatop[\=|\underrng{l}]} & {\dn \319w} & {\dn\dnbombay \319w} & {\dn\dncalcutta \319w} & \\ +\textit{cha} & {\dn C} & {\dn\dnbombay C} & {\dn\dncalcutta C} & \\ +\textit{jha} & {\dn J} & {\dn\dnbombay J} & {\dn\dncalcutta J} & {\dn\dnnepali J} \\ +\textit{\d{n}a} & {\dn Z} & {\dn\dnbombay Z} & {\dn\dncalcutta Z} & \\ +\textit{la} & {\dn l} & {\dn\dnbombay l} & {\dn\dncalcutta l} & \\ +\textit{\'sa} & {\dn f} & {\dn\dnbombay f} & {\dn\dncalcutta f} & \\ +\textit{1} & {\dn\dnnum 1} & {\dn\dnnum\dnbombay 1} & {\dn\dnnum\dncalcutta 1} & {\dn\dnnum\dnnepali 1}\\ +\textit{5} & {\dn\dnnum 5} & {\dn\dnnum\dnbombay 5} & {\dn\dnnum\dncalcutta 5} & \\ +\textit{8} & {\dn\dnnum 8} & {\dn\dnnum\dnbombay 8} & {\dn\dnnum\dncalcutta 8} & \\ +\textit{9} & {\dn\dnnum 9} & {\dn\dnnum\dnbombay 9} & {\dn\dnnum\dncalcutta 9} & {\dn\dnnum\dnnepali 9}\\ +\hline +\end{tabular} +\end{center} +\bigskip + +\begin{center} +\renewcommand{\arraystretch}{1.35} +\begin{tabular}{|l|c|c|c|c|} +\hline + & \textsc{original} & \textsc{bombay} & \textsc{calcutta} & \textsc{nepali} \\ +\hline +\textit{k\d{s}a} & {\dn "} & {\dn\dnbombay "} & {\dn\dncalcutta "} & \\ +\textit{k\d{s}}- & {\dn \symbol{'43}} & {\dn\dnbombay \symbol{'43}} & {\dn\dncalcutta \symbol{'43}} & \\ +\textit{\.nk\d{s}a} & {\dn \3B0w} & {\dn\dnbombay \3B0w} & {\dn\dncalcutta \3B0w} & \\ +\textit{\.nk\d{s}va} & {\dn \3B1w} & {\dn\dnbombay \3B1w} & {\dn\dncalcutta \3B1w} & \\ +\textit{chya} & {\dn \3D0w} & {\dn\dnbombay \3D0w} & {\dn\dncalcutta \3D0w} & \\ +\textit{j\~na} & {\dn \3E2w} & {\dn\dnbombay \3E2w} & {\dn\dncalcutta \3E2w} & \\ +\textit{j\~n}- & {\dn \symbol{'352}} & {\dn\dnbombay \symbol{'352}} & {\dn\dncalcutta \symbol{'352}} & \\ +\textit{jh}- & {\dn \324w} & {\dn\dnbombay \324w} & {\dn\dncalcutta \324w} & {\dn\dnnepali \324w} \\ +\textit{\d{n}}- & {\dn \symbol{'27}} & {\dn\dnbombay \symbol{'27}} & {\dn\dncalcutta \symbol{'27}} & \\ +\textit{\d{n}\d{n}a} & {\dn \symbol{'233}} & {\dn\dnbombay \symbol{'233}} & {\dn\dncalcutta \symbol{'233}} & \\ +\textit{lla} & {\dn \3A5w} & {\dn\dnbombay \3A5w} & {\dn\dncalcutta \3A5w} & \\ +\textit{\'{s}}- & {\dn \symbol{'133}} & {\dn\dnbombay \symbol{'133}} & {\dn\dncalcutta \symbol{'133}} & \\ +\textit{-ya} & {\dn \symbol{'053}} & {\dn\dnbombay \symbol{'053}} & {\dn\dncalcutta \symbol{'053}} & \\ +\textit{h\d{n}a} & {\dn \3A2w} & {\dn\dnbombay \3A2w} & {\dn\dncalcutta \3A2w} & \\ +\hline +\end{tabular} +\end{center} + +\caption{Standard and Variant \devnag{} Characters} +\label{diffs} +\end{table} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\begin{center} +\begin{table}[p] +\renewcommand{\arraystretch}{1.35} +\begin{tabular}{|lllll||lllll||lllll|} +\hline +\# & & \textsc{s} & \textsc{h} & \textsc{mh} & +\# & & \textsc{s} & \textsc{h} & \textsc{mh} & +\# & & \textsc{s} & \textsc{h} & \textsc{mh} \\ \hline +1 & {\dn k k} & {\dn\symbol{'303}} & {\dn \3C3w} & {\dn ?k} & +36 & {\dn\symbol{'32} c} & {\dn\symbol{'321}} & {\dn \316wc} & {\dn \316wc} & +71 & {\dn d r y} & {\dn\symbol{'357}} & {\dn \3EFw} & {\dn \qb{d}+}\\ +2 & {\dn k t } & {\dn\symbol{'304}} & {\dn \3C4w} & {\dn ?t} & +37 & {\dn\symbol{'32} j} & {\dn\symbol{'322}} & {\dn \316wj} & {\dn \316wj} & +72 & {\dn d v y} & {\dn\symbol{'225}} & {\dn \395w} & {\dn \392w+}\\ +3 & {\dn k n} & {\dn\symbol{'307}} & {\dn ?n} & {\dn ?n} & +38 & {\dn V k} & {\dn\symbol{'326}} & {\dn \3D6w} & {\dn \qq{V}k} & +73 & {\dn D n} & {\dn\symbol{'360}} & {\dn @n} & {\dn @n}\\ +4 & {\dn k m} & {\dn\symbol{'311}} & {\dn ?m} & {\dn ?m} & +39 & {\dn V V} & {\dn\symbol{'323}} & {\dn \3D3w} & {\dn \qq{V}V} & +74 & {\dn n n} & {\dn\symbol{'340}} & {\dn \3E0w} & {\dn \306wn}\\ +5 & {\dn k y} & {\dn\symbol{'310}} & {\dn \3C8w} & {\dn ?y} & +40 & {\dn V W} & {\dn\symbol{'341}} & {\dn \3E1w} & {\dn \qq{V}W} & +75 & {\dn p t} & {\dn\symbol{'330}} & {\dn =t} & {\dn =t}\\ +6 & {\dn k l} & {\dn\symbol{'312}} & {\dn ?l} & {\dn ?l} & +41 & {\dn V y} & {\dn\symbol{'324}} & {\dn \3D4w} & {\dn V+} & +76 & {\dn p n} & {\dn\symbol{'331}} & {\dn =n} & {\dn =n}\\ +7 & {\dn k v} & {\dn\symbol{'313}} & {\dn ?v} & {\dn ?v} & +42 & {\dn W y} & {\dn\symbol{'325}} & {\dn \3D5w} & {\dn W+} & +77 & {\dn p l} & {\dn\symbol{'332}} & {\dn =l} & {\dn =l}\\ +8 & {\dn k t y} & {\dn\symbol{'305}} & {\dn \3C5w} & {\dn ?(y} & +43 & {\dn X g} & {\dn\symbol{'263}} & {\dn \qq{X}g} & {\dn \qq{X}g} & +78 & {\dn b n} & {\dn\symbol{'247}} & {\dn Nn} & {\dn Nn}\\ +9 & {\dn k t v} & {\dn\symbol{'306}} & {\dn \3C6w} & {\dn ?(v} & +44 & {\dn X G} & {\dn\symbol{'264}} & {\dn \qq{X}G} & {\dn \qq{X}G} & +79 & {\dn b b} & {\dn\symbol{'251}} & {\dn Nb} & {\dn Nb}\\ +10 & {\dn k n y} & {\dn\symbol{'346}} & {\dn ?\306wy} & {\dn ?\306wy} & +45 & {\dn X X} & {\dn\symbol{'345}} & {\dn \3E5w} & {\dn \qq{X}X} & +80 & {\dn b v} & {\dn\symbol{'333}} & {\dn Nv} & {\dn Nv}\\ +11 & {\dn k r y} & {\dn\symbol{'347}} & {\dn \3E7w} & {\dn \3E7w} & +46 & {\dn X m} & {\dn\symbol{'273}} & {\dn \qq{X}m} & {\dn \qq{X}m} & +81 & {\dn B n} & {\dn\symbol{'336}} & {\dn