doc/latex

git-svn-id: svn://tug.org/texlive/trunk@84 c570f23f-e606-0410-a88d-b1316a301751

4 files changed, 686 insertions, 0 deletions

diff --git a/Master/texmf-dist/doc/latex/cm-lgc/COPYING b/Master/texmf-dist/doc/latex/cm-lgc/COPYING
new file mode 100644
index 00000000000..d60c31a97a5
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/cm-lgc/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.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    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) year  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.
+
+  <signature of Ty Coon>, 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/latex/cm-lgc/HISTORY b/Master/texmf-dist/doc/latex/cm-lgc/HISTORY
new file mode 100644
index 00000000000..47ec363fb45
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/cm-lgc/HISTORY
@@ -0,0 +1,54 @@
+2004-10-06 Alexej Kryukov  <basileia@yandex.ru>
+
+	* Version 0.3.1. released.
+        
+        * Fixed problem with wrong kerning pairs (exported from the small
+        caps fonts) in Unicode virtual fonts. The problem was reported by
+        Alexander Lee <alexlee@uchicago.edu>.
+        
+        * The "angleleft" and "angleright" glyphs (present in Greek
+        and Cyrillic fonts) are now recognized as aliases for angbracketleft
+        (U+2329) and angbracketright (U+232A) while building Unicode
+        virtual fonts.
+
+2004-04-27 Alexej Kryukov  <basileia@yandex.ru>
+
+	* Version 0.3. released.
+
+        * The EC-styled germandbls glyph replaced with the glyph taken
+        from CM fonts.
+        
+        * Corrected position of the macron and breve accents (again, 
+        EC-styled glyphs replaced with CM versions).
+        
+        * Corrected ellipsis in the monospaced fonts (which was 3
+        characters width in previous versions).
+        
+        * Added ligatures allowing to obtain single quotes in Greek fonts.
+        
+        * Added *.inf files allowing to install fonts under MS Windows.
+        All fonts have been tested and found really installable.
+        
+        * Since Windows seems to have troubles when installing fonts
+        which have too many kerning pairs in afm files, I tried to reduce
+        the number of kerning pairs in Greek afm files by removing useless
+        autogenerated kerning pairs which never occur in real text.
+
+2003-08-31 Alexej Kryukov  <basileia@yandex.ru>
+
+	* Version 0.2.1. released.
+        
+        * Fixed bug with optional argument of \ProvidesFile in the style
+        packages.
+        
+        * Fixed bug with incomplete *.fd files for Computer Modern Sans
+        and Computer Modern Typewriter.
+        
+        * Fixed bug in UT1 encoding: wrongly positioned dagger and
+        double dagger.
+        
+        * Virtual fonts regenerated with Fontinst 1.926.
+
+2003-03-20 Alexej Kryukov  <basileia@yandex.ru>
+
+	* Version 0.2 released: first public release.
diff --git a/Master/texmf-dist/doc/latex/cm-lgc/INSTALL b/Master/texmf-dist/doc/latex/cm-lgc/INSTALL
new file mode 100644
index 00000000000..a4b09e196ed
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/cm-lgc/INSTALL
@@ -0,0 +1,72 @@
+========================================================================
+
+These are generic installation instructions for the CM-LGC font package.
+
+Below, we assume that your TeX system is compliant to the TDS (TeX
+Directory Structure) standard. If it is not so, refer to documentation of
+your TeX system for the proper locations of files of various types.
+
+To install the CM-Super font package in teTeX, fpTeX, TeX Live, MikTeX 
+or VTeX/Free systems:
+
+1. Copy all *.pfb, *.afm, *.tfm, *.vf, *.ofm and *.ovf files to
+the appropriate subdirectories in your .../texmf/fonts directory.
+
+2. Create a subdirectory called "cm-lgc" in your .../texmf/tex/latex 
+directory and put all *.fd files and the cmlgc.sty file here. Note that 
+all *.fd files having the `ut1' prefix in their names are needed only 
+for Omega, and so you can put them to .../texmf/omega/lambda/cm-lgc 
+instead.
+
+3. (a) [not for VTeX/Free] Put the dvips/config/cm-lgc.map file to your
+   .../texmf/dvips/config directory.
+
+   (b) [for VTeX/Free only] Copy the vtex/config/cm-lgc.ali file to 
+   your .../texmf/vtex/config/ directory.
+
+4. (a) [not for VTeX/Free] Put the dvips/base/8r-mod.enc file to your 
+   .../texmf/dvips/base directory.
+
+   (b) [for VTeX/Free only] Put the vtex/enc/8r-mod.enc file to your 
+   .../texmf/vtex/enc directory.
+
+5. Instruct your TeX (pdftex, vtex, etc.) or drivers (dvips, dvipdfm,
+etc.) to use your new fonts. To accomplish this, do one of the following
+points which corresponds to your TeX system (if it is not listed here,
+please refer to the documentation).
+
+(a) [for teTeX, fpTeX or MikTeX] Edit the file 
+    .../texmf/dvips/config/config.ps and add the following line:
+
+     p + cm-lgc.map
+
+(b) If you use pdftex, edit the file .../texmf/pdftex/pdftex.cfg and 
+    add the following line:
+
+    map +cm-lgc.map
+
+    Alternatively, you can edit your .../texmf/dvips/cunfig/updmap script 
+    and run it to update all necessary configuration files automatically.
+
+(c) [for VTeX/Free only] Edit the files .../texmf/vtex/config/ps.fm
+    and .../texmf/vtex/config/pdf.fm, and add the following line into the 
+    TYPE1 section:
+
+    cm-super.ali
+
+6. [not for VTeX/Free] Update the filename search database:
+run "mktexlsr" on teTeX, TeX Live, or fpTeX;
+run "initexmf.exe -u" on MikTeX (or do the same via a menu item).
+
+7. You can install the CM-LGC fonts as regular Windows fonts, if you
+wish to use them in non-TeX applications (e.g. packages for preparation 
+of graphics which are to be included into your TeX documents, or even 
+word processors, etc.)
+
+You will need Adobe Type Manager (either a regular version, or the
+Lite version, which is available for free from the Adobe web site).
+
+Place all corresponding PFB, AFM, and INF files which you need to
+install into the same directory, and feed it to ATM.
+
+========================================================================
diff --git a/Master/texmf-dist/doc/latex/cm-lgc/README b/Master/texmf-dist/doc/latex/cm-lgc/README
new file mode 100644
index 00000000000..3f5599e0b9f
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/cm-lgc/README
@@ -0,0 +1,220 @@
+=========================================================================
+CM-LGC font package
+version 0.3.1 (Oct 06, 2004)
+
+Copyright (c) 2003--2004 Alexej Kryukov <basileia@yandex.ru>.
+
+This package 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.
+
+As a special exception, permission is granted to include these font
+programs in a Postscript or PDF file that consists of a document that
+contains text to be displayed or printed using these fonts, regardless
+of the conditions or license applying to the document itself.
+
+This package 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
+
+Abstract
+~~~~~~~~
+
+The CM-LGC package contains Type 1 fonts converted from METAFONT
+sources of the Computer Modern font families. The following encodings
+are supported: T1, T2A (Cyrillic), LGR (Greek) and TS1. This package
+includes also Unicode virtual fonts for use with Omega/Lambda.
+
+See the file INSTALL for installation instructions for teTeX, TeX Live,
+MikTeX or VTeX/Free systems.
+
+PLEASE read the files README and INSTALL carefully before reporting 
+problems.
+
+The goal of the package
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Thanks to Peter Szabo's excellent TeXtrace program it is easy
+to convert METAFONT sources to the Type 1 format. There are some
+Type 1 font packages based on the Computer Modern font families 
+already available on the Web. I have to mention here excellent 
+CM-SUPER font package by Vladimir Volovich, which covers all
+European and Cyrillic writings. So you can ask me, why not to
+use already existing font packages instead of making new one.
+Here the reasons which made me to undertake this work one more
+time:
+
+1. All font packages designed as a replacement for METAFONT
+sources try to include a maximal possible number of fonts. Usually
+for each size of each family and shape different *.pfb files
+are provided. This increases the size of whole package enormously.
+For example, the CM-SUPER font package requires (with afm files) 
+more than 100 Mb free disk space.
+
+The CM-LGC package does *not* replace standard METAFONT files. 
+Although it is based on the Computer Modern font families,
+I renamed the font files in order to avoid name clashes. Since
+CM-LGC is designed as a separate package, it includes only
+minimal set of fonts, which, however, should be sufficient for 
+regular work.
+
+2. Until recently there were no publicly available font packages 
+including Type 1 versions of Claudio Beccari's Greek fonts. Now
+these versions (converted by Apostolos Syropoulos) are available
+on CTAN, but CM-LGC is the first Type 1 font package for LaTeX which 
+supports *all* European scripts (LGC means `Latin, Greek and Cyrillic').
+
+3. Since CM-LGC is not so huge as other CM-based font packages,
+it was easy to accomplish it with Unicode virtual fonts
+(*.ovf files) for Omega. CM-LGC is the first free alternative font
+package which may be used with Omega/Lambda.
+
+4. Type 1 fonts converted from the METAFONT sources are usually
+not suitable for use outside of TeX, since they preserve their 
+TeX-specific encodings. The only exception is CM-SUPER fonts
+by Vladimir Volovich, which use Unicode encoding. However,
+Unicode Type 1 fonts are hardly usable with some versions of
+ATM (which is designed mainly for 8-bit fonts), and using them
+may cause some problems even under XWindow system.
+
+CM-LGC is the first font package, which provides CM-like fonts
+with standard (not TeX-specific) 8-bit codepages. For each font
+family the following codepages are supported:
+
+-- Adobe Standard (which, of course, is never used by itself, but
+always reencoded to MICROSOFT-ANSI by ATM and to ISO8859-1 under
+XWindow system);
+
+-- WINDOWS-1251 (Cyrillic);
+
+-- PARATYPE-CP154 (Cyrilic Asian);
+
+-- UNITYPE WINLANGUAGE, also known as PARATYPE-CP122 (Polytonic 
+Greek).
+
+Glyphs from physical pfb files are combined to TeX-specific
+codepages with virtual fonts, which are prepared by the same 
+way, as, for example, virtual fonts from the psnfss collection.
+Of course, this means that CM-LGC lacks some rarely used glyphs,
+present in the original CM fonts. However, the following TeX
+codepages are fully covered: T1, T2A and LGR.
+
+Font Naming System
+~~~~~~~~~~~~~~~~~~
+
+Since the CM-LGC fonts are designed to be suitable for use in
+WYSIWYG applications under MS Windows (with ATM) or X-Window
+system, it was necessary to provide meaningful names for them.
+Here the elements used to build the PostScript font names for
+each font family and shape:
+
+-- the font family itself (CM Roman/CM Sans/CM Typewriter);
+
+-- the script name for non-Latin fonts (Cyrillic, Asian (for
+Asian Cyrillic) or Greek);
+
+-- the font weight and shape (Regular/Italic/Bold/BoldItalic).
+The CMSans font family includes "Slanted" shape instead of
+"Italic" and "BoldSlanted" instead of "BoldItalic";
+
+-- the last name element is the "SC" letters for small caps
+fonts or the "OsF" letters for italic fonts with old style 
+numerals.
+
+Font File Names
+~~~~~~~~~~~~~~~
+
+The font files are named according to Karl Berry's font naming 
+scheme, usually used in TeX for Type 1 fonts. The first
+letter, which should represent a font foundry, is always
+`f' (i. e. `free/public'). Next two letters are font family 
+codes. I used `cm' for "Computer Modern", `cs' for "Computer
+Modern Sans" and `ct' for "Computer Modern Typewriter".
+
+The fourth and fifth letters in the font name correspond to 
+font weight and shape. Here the list of font weights and shapes 
+available in the CM-LGC fonts:
+
+r	Regular;
+ri	Regular Italic;
+ro	Regular Slanted;
+rc	Regular Small Caps;
+b	Bold;
+bi	Bold Italic;
+bo	Bold Slanted;
+bc	Bold Small Caps.
+
+Next letter may represent a font variant. I used `j' for
+Italic fonts with Old Style digits.
+
+The last two letters in the font name represent font encodings.
+This part is the most problematic, since there are no standard 
+conventions determining which letters should be used for Cyrillic 
+or Greek encodings. Here the list of font encodings used in
+CM-LGC fonts:
+
+8a	Adobe Standard;
+8r	Latin raw font encoding (which, however, is slightly
+	different from standard 8r);
+8t	Latin TeX font encoding, i. e. T1;
+6z	Cyrillic raw font encoding (based on windows-1251);
+6y	Asian Cyrillic raw font encoding (based on paratype-cp1254);
+6a	Cyrillic TeX font encoding, i. e. T2A;
+pg	Greek raw font encoding (paratype-cp122);
+gr	Greek TeX font encoding (LGR);
+ut	Unicode-based encoding for Omega's ovf files (UT1).
+	
+For example, the font name `fctrijpg.pfb' means "Computer 
+Modern Typewriter font with regular weight and italic shape, 
+containing old style numerals and using the Greek 
+paratype-cp122 codepage".
+
+Installation
+~~~~~~~~~~~~
+
+See the INSTALL file for installation instrustions.
+
+Using CM-LGC with LaTeX
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Just put in your LaTeX preamble the following line:
+
+\usepackage{cmlgc}
+
+This will set your default Roman font to fcm, your Sans Serif
+font to fcs, and your Typewriter font to fct.
+
+Using CM-LGC with Omega/Lambda
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Unfortunately, last Omega releases doesn't provide any
+high-level commands for working with multilingual document.
+That's why I provided alternative language support package
+for Omega, called ANTOMEGA.
+
+Note that the Unicode virtual fonts, included in the CM-LGC
+package, are not fully compatible with Yannis Haralambous'
+omlgc font (which really uses a font-specific encoding).
+ANTOMEGA provides special features for handling strict Unicode
+fonts, and using it instead of the standard omega.sty file
+is strongly recommended.
+
+The CM-LGC package includes antcmlgc.sty file, designed 
+specially for ANTOMEGA. If you use both ANTOMEGA and CM-LGC,
+load it in your preamble instead of cmlgc.sty.
+
+Thanks
+~~~~~~
+
+I'd like to thank Peter Szabo for TeXtrace, Martin Weber for
+AutoTrace, and George Williams for his excellent pfaedit program,
+which I used for optimizing Type 1 font files.
+
+Happy TeXing!
+=========================================================================