new arkandis font romande(adf)

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

6 files changed, 786 insertions, 0 deletions

diff --git a/Master/texmf-dist/doc/fonts/romande/COPYING b/Master/texmf-dist/doc/fonts/romande/COPYING
new file mode 100644
index 00000000000..fbdd65f6f8b
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/romande/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/fonts/romande/NOTICE.txt b/Master/texmf-dist/doc/fonts/romande/NOTICE.txt
new file mode 100644
index 00000000000..bb9960e7abf
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/romande/NOTICE.txt
@@ -0,0 +1,39 @@
+    The Romande collection consists of fonts made by Arkandis Digital
+    Foundry (ADF), collectively known as the "Program"
+
+    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 any later 
+    version, with font exception.
+
+   As a special exception, if you create a document which uses Romande
+   font, and embed this font or unaltered portions of this font into the
+   document, this font does not by itself cause the resulting document to
+   be covered by the GNU General Public License. This exception does not
+   however invalidate any other reasons why the document might be covered
+   by the GNU General Public License. If you modify this font, you may
+   extend this exception to your version of the font, but you are not
+   obligated to do so. If you do not wish to do so, delete this exception
+   statement from your 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
+_____________________________________________________________________________________
+     RELEASE 
+	1.000 - Initial release
+	1.001 - New kerning table
+	1.002 - Modifications: S,s; Spacing corrections.
+	1.003 - Modifications: T,t
+	1.004 - Modifications: c,e
+	1.005 - Hinting correction, Addition liga
+	1.006 - Modifications: S,Z,T,s,z,t
+	1.007 - Modifications: A,R,V,W,c, numbers; addition of a new kerning table and
+		Ghyphes for Std. and addition of Romande ADF Sript font
+	1.008 - Minor corrections, zero.slash change
+
diff --git a/Master/texmf-dist/doc/fonts/romande/README b/Master/texmf-dist/doc/fonts/romande/README
new file mode 100644
index 00000000000..266e0fc0fee
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/romande/README
@@ -0,0 +1,35 @@
+romandeadf
+----------
+
+romandeadf consists of:
+1. the Romande ADF Std fonts developed by Hirwen Harendel, Arkandis Digital
+Foundry (ADF) and released under the terms set out in the files COPYING and
+NOTICE.txt in postscript type 1 format;
+2. (La)TeX support by Clea F. Rees released under the LPPL. All files covered
+by the LPPL are listed in the file manifest.txt.
+
+Information and resources concerning Romande ADF, including truetype and
+opentype versions of the fonts, and other ADF fonts can be found on the
+foundry's homepage:
+	http://arkandis.tuxfamily.org/
+
+(La)TeX Support
+---------------
+
+For details, please see romandeadf.pdf.
+
+The (La)TeX support requires nfssext-cfr and xkeyval. These packages are
+available from CTAN.
+
+The (La)TeX support should be considered somewhat experimental. If you find
+any problems, please let me know and I will try to correct them. If you can
+send a fix, so much the better.
+
+Contact Details
+---------------
+
+If you have comments about the fonts themselves, please contact Hirwen
+Harendal (harendalh <at> hotmail <dot> com). 
+
+Clea F. Rees (cfrees <at> imapmail <dot> org)
+2010/07/10
diff --git a/Master/texmf-dist/doc/fonts/romande/manifest.txt b/Master/texmf-dist/doc/fonts/romande/manifest.txt
new file mode 100644
index 00000000000..f5d646844e1
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/romande/manifest.txt
@@ -0,0 +1,95 @@
+Copyright 2010 Clea F. Rees
+
+This work may be distributed and/or modified under the conditions of the LaTeX Project Public License, either version 1.3 of this license or (at your option) any later version.  The latest version of this license is in http://www.latex-project.org/lppl.txt and version 1.3 or later is part of all distributions of LaTeX version 2005/12/01 or later.
+
+This work has the LPPL maintenance status `maintained'.
+
+The Current Maintainer of this work is Clea F. Rees.
+
+This work consists of all files listed in manifest.txt.
+
+This file lists all files released under the LPPL. It does *not* list all files included in the package. See README for further details.
+
+manifest.txt
+README
+reglyph-yrd.tex
+romande-supp.etx
+romande.sty
+romandeadf.tex
+t1-romandeadf-alt.etx
+t1-romandeadf.etx
+ts1-euro.etx
+yrd-drv.tex
+yrd-map.tex
+
+Derived files:
+romande-supp.enc
+romandeadf.pdf
+s-yrdd.tfm
+s-yrddi.tfm
+s-yrdr.tfm
+s-yrdri.tfm
+s-yrdriw.tfm
+t1-romandeadf-alt-yrdd.tfm
+t1-romandeadf-alt-yrddi.tfm
+t1-romandeadf-alt-yrdr.tfm
+t1-romandeadf-alt-yrdri.tfm
+t1-romandeadf-alt-yrdriw.tfm
+t1-romandeadf-alt.enc
+t1-romandeadf-yrdd.tfm
+t1-romandeadf-yrddc.tfm
+t1-romandeadf-yrddi.tfm
+t1-romandeadf-yrdr.tfm
+t1-romandeadf-yrdrc.tfm
+t1-romandeadf-yrdri.tfm
+t1-romandeadf-yrdriw.tfm
+t1-romandeadf.enc
+ts1-euro-yrd.enc
+t1yrd.fd
+t1yrda.fd
+t1yrdaw.fd
+t1yrdw.fd
+ts1-yrdd.tfm
+ts1-yrddi.tfm
+ts1-yrdr.tfm
+ts1-yrdri.tfm
+ts1-yrdriw.tfm
+ts1yrd.fd
+ts1yrda.fd
+ts1yrdaw.fd
+ts1yrdw.fd
+yrd.map
+yrdd8c.tfm
+yrdd8c.vf
+yrdd8t.tfm
+yrdd8t.vf
+yrdda8t.tfm
+yrdda8t.vf
+yrddai8t.tfm
+yrddai8t.vf
+yrddc8t.tfm
+yrddc8t.vf
+yrddi8c.tfm
+yrddi8c.vf
+yrddi8t.tfm
+yrddi8t.vf
+yrdr8c.tfm
+yrdr8c.vf
+yrdr8t.tfm
+yrdr8t.vf
+yrdra8t.tfm
+yrdra8t.vf
+yrdrai8t.tfm
+yrdrai8t.vf
+yrdraiw8t.tfm
+yrdraiw8t.vf
+yrdrc8t.tfm
+yrdrc8t.vf
+yrdri8c.tfm
+yrdri8c.vf
+yrdri8t.tfm
+yrdri8t.vf
+yrdriw8c.tfm
+yrdriw8c.vf
+yrdriw8t.tfm
+yrdriw8t.vf
diff --git a/Master/texmf-dist/doc/fonts/romande/romandeadf.pdf b/Master/texmf-dist/doc/fonts/romande/romandeadf.pdf
new file mode 100644
index 00000000000..f657a434d82
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/romande/romandeadf.pdf
diff --git a/Master/texmf-dist/doc/fonts/romande/romandeadf.tex b/Master/texmf-dist/doc/fonts/romande/romandeadf.tex
new file mode 100644
index 00000000000..ee98f30a74c
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/romande/romandeadf.tex
@@ -0,0 +1,277 @@
+% !TEX TS-program = pdflatex
+% !TEX encoding = UTF-8 Unicode
+%% romandeadf.tex
+%% Copyright 2010 Clea F. Rees
+%
+% This work may be distributed and/or modified under the
+% conditions of the LaTeX Project Public License, either version 1.3
+% of this license or (at your option) any later version.
+% The latest version of this license is in
+%   http://www.latex-project.org/lppl.txt
+% and version 1.3 or later is part of all distributions of LaTeX
+% version 2005/12/01 or later.
+%
+% This work has the LPPL maintenance status `maintained'.
+% 
+% The Current Maintainer of this work is Clea F. Rees.
+%
+% This work consists of all files listed in manifest.txt.
+\listfiles
+\documentclass[11pt,british]{article}
+\usepackage{babel}
+\usepackage[T1]{fontenc}
+\usepackage{textcomp}
+\usepackage{lmodern}
+\renewcommand{\ttdefault}{lmvtt}
+\let\origrmdefault\rmdefault
+\DeclareRobustCommand{\origrmfamily}{%
+	\fontencoding{T1}%
+	\fontfamily{\origrmdefault}%
+	\selectfont}
+\DeclareTextFontCommand{\textorigrm}{\origrmfamily}
+\usepackage{romande}
+	\pdfmapfile{+yrd.map}	% not necessary for installed package
+\usepackage{fancyhdr,lastpage,fancyref}
+\usepackage{array,longtable,verbatim}
+\usepackage{booktabs}
+\usepackage{url}
+	\urlstyle{tt}
+\usepackage{hyperref}
+\usepackage{microtype}
+\usepackage[a4paper,headheight=14pt]{geometry}	% use 14pt for 11pt text, 15pt for 12pt text
+
+\title{romandeadf}
+\author{Clea F.\ Rees\footnote{cfrees <at> imapmail <dot> org}}
+\newcommand*{\dyddiad}{10\textsuperscript{th} July, 2010}
+\date{\dyddiad}
+\pagestyle{fancy}
+	\fancyhf[lh]{\itshape romandeadf}
+	\fancyhf[rh]{\itshape\dyddiad}
+	\fancyhf[ch]{}
+	\fancyhf[lf]{}
+	\fancyhf[rf]{}
+	\fancyhf[cf]{\itshape --- \thepage~\ofname~\pageref{LastPage} ---}
+	
+
+\begin{document}
+\maketitle\thispagestyle{empty}
+\pdfinfo{%
+	/Creator		(TeX)
+	/Producer		(pdfTeX)
+	/Author			(Clea F.\ Rees)
+	/Title				(romandeadf)
+	/Subject		(TeX)
+	/Keywords		(TeX,LaTeX,font,fonts,tex,latex,Romande,romande,romandeadf,RomandeADF,ADF,adf,Arkandis,Digital,Foundry,arkandis,digital,foundry,Hirwen,Harendal,Clea,Rees)}
+\pdfcatalog{%
+	/URL				()
+	/PageMode	/UseOutlines}	% other values: /UseNone, /UseOutlines, /UseThumbs, /FullScreen
+	%[openaction <actionspec>]
+%	\pagestyle{empty}	% if you want this, you probably want to comment out \maketitle as well...?
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{0.5em}
+	
+	
+\newcommand*{\adf}{\textsc{adf}}
+\newcommand*{\lpack}[1]{\textsf{#1}}
+\newcommand*{\fgroup}[1]{\textsf{#1}}
+\newcommand*{\fname}[1]{\textsf{#1}}
+
+\begin{abstract}
+	\hspace*{-\parindent}Hirwen Harendal, Arkandis Digital Foundry (\adf) has produced the Romande \adf\ font collection. This guide outlines the \emph{experimental} \TeX/\LaTeX\ support provided by \lpack{romandeadf} for version 1.008 of the fonts.
+\end{abstract}
+
+\tableofcontents
+
+\section{Introduction}
+
+This document explains how to use the \TeX/\LaTeX\ support provided for version 1.008 of the Romande \adf\ font collection developed by Hirwen Harendal of the Arkandis Digital Foundry (\adf). \lpack{romandeadf} includes copies of the fonts in postscript type 1 format. Further  information about the fonts themselves and alternative font formats for use with other programmes can be found at \url{http://arkandis.tuxfamily.org/adffonts.html}. The fonts are released under the \textsc{gnu} General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version, with font exception. For details, see \textsc{notice}.txt and \textsc{copying}.
+
+The \TeX/\LaTeX\ support package consists of all files listed in \path{manifest.txt}\ and these files are released under the \LaTeX\ Project Public Licence as explained in the included licensing notices. Please let me know of any problems so that I can solve them if I can. If you can correct the problems and send me the fix, that would be even better. Unlike the fonts themselves, the \TeX/\LaTeX\ support is somewhat experimental.
+
+\section{The collection}
+
+Romande \adf\ is a serif family with oldstyle figures designed as a substitute for Times, Tiffany or Caslon. The family currently includes upright, italic and small-caps shapes in each of regular and demi-bold\footnote{As \fgroup{romande} does not include bold or bold extended fonts, \lpack{romadeadf} substitutes demi-bold so that the ordinary commands to select bold work as expected.} weights and an italic script in regular. The support package renames the fonts according to the Karl Berry fontname scheme and defines four families. Two of these primarily provide access to the ``standard'' or default characters while the ``alternate'' families support alternate characters, additional ligatures and the long s\footnote{\Fref{sec:encs} describes the encodings used to create these families. For further details see the encoding files \path{t1-romandeadf.etx} and \path{t1-romandeadf-alt.etx}.}. The included package files provide access to these features in \LaTeX\ as explained in \fref{sec:support} and \fref{sec:commands}.
+
+\clearpage
+
+\begin{longtable}{llll}
+	\toprule
+	\textbf{\TeX\ directory}	&	\textbf{font families}	&	\textbf{Original name}	& \textbf{\TeX\ name}\\\midrule\endhead
+		\bottomrule\endfoot
+	romande		&	yrdw, yrdaw	&	RomandeADFScriptStd-Italic			&	yrdriw8a\\\cline{2-4}
+						& yrd, yrda		&	RomandeADFStd-DemiBold				&	yrdd8a\\
+						& 							&	RomandeADFStd-DemiBoldItalic	&	yrddi8a\\
+						&							&	RomandeADFStd-Italic						&	yrdri8a\\
+						&							&	RomandeADFStd-Regular					&	yrdr8a\\
+						&							&	RomandeADFStyleStd-DemiBold	&	yrddc8a\\
+						&							&	RomandeADFStyleStd-Regular		&	yrdrc8a\\
+
+\end{longtable}
+
+\section{Requirements}
+
+Apart from such obvious requirements as \LaTeXe, the \LaTeX\ support provided by \path{romande.sty} requires \lpack{nfssext-cfr} and \lpack{xkeyval}. Without this, you will get errors complaining that the package cannot be found and you will not be able to use any of the additional font commands described in \fref{sec:commands}.
+
+The documentation requires in additional packages. These are all standard and available from \textsc{ctan} but you can always comment out the relevant lines in \path{romandeadf.tex} if you wish.
+
+\section{Installation}
+
+Installation varies with \TeX\ distribution so you should consult the documentation which came with your system for details. In most cases, you will need to perform three steps:
+		\begin{enumerate}
+			\item move or copy the package files to appropriate locations on your system;
+			\item refresh the \TeX\ database;
+			\item incorporate the included map file fragments for the different engines your distribution supports.
+		\end{enumerate}
+
+The following instructions assume you are using \TeX~Live\footnote{This includes Mac\TeX\ for OS X users.}. They should not be too difficult to adapt if you are using a different distribution.
+
+\subsection{Install the files}
+
+The files should be installed in one of two locations: \emph{either} the local system-wide \TeX\ tree \emph{or} your personal tree. If the package is installed system-wide, all users will have access to it. On the other hand, you may need privileges you do not have to do this in which case you must use your personal tree.
+
+For \TeX~Live, \verb|kpsewhich -var-value TEXMFLOCAL| will return the path to the local tree and \verb|kpsewhich -var-value TEXMFHOME| the path to your personal tree. The package already includes a hierarchy of files to help you install them correctly. Ignoring any symbolic link in the top directory, move or copy the files in \path{doc}, \path{fonts} and \path{tex} into the appropriate locations. If the tree is initially empty, you can simply move or copy the directories in as they are. If the tree already contains other packages, you may need to merge the package hierarchy with the pre-existing one. For example, if you already have a \path{doc/fonts} directory, move or copy \path{doc/fonts/romande} into \path{doc/fonts/}. If you have a \path{doc} directory but not a \path{doc/fonts}, move \path{doc/fonts} into \path{doc/}.
+
+\subsection{Refresh the database}
+
+Again, this depends on your distribution. For \TeX~Live, \verb|mktexlsr <path to directory>| for the directory you used in the first step should do the trick. Note that you \emph{may} be able to skip this step if you install into your personal tree. Whether this is so depends on the details of your set-up. As a test, move to a directory containing none of the package files and try \verb|kpsewhich romande.sty|. If the file is found, you don't need to refresh the database; otherwise use \verb|mktexlsr| and then try again.
+
+\subsection{Install the map fragments}
+
+For \TeX~Live, there are at least two ways of doing this. The second method varies according to the version of \TeX~Live and instructions are provided accordingly. Both methods depend on whether you installed into \verb|TEXMFLOCAL| or \verb|TEXMFHOME|. If you installed system-wide, the choice is relatively straightforward --- it obviously makes sense in that case to update the font maps system-wide as well. If, on the other hand, you installed into your personal tree, the matter is more complex. On the one hand, updating the system-wide maps may create difficulties or confusion for other users because while the map files will list the fonts as available, they will not be able to access them. On the other hand, maintaining personal font map files can produce difficulties and confusions of its own. Whether it is to be preferred or not is a complex issue and depends on the details of your \TeX\ distribution, local configuration and personal preference. The one clear case is that in which you install into your personal tree because you lack the privileges needed to install system-wide. In that case, you have no choice but to maintain personal font map files or forgo the use of all fonts not provided by your administrator. Other cases are thankfully beyond the scope of this document.
+
+\subsubsection{Method 1}
+
+If you installed the package system-wide, use the command:
+\begin{verbatim}
+	updmap-sys --enable Map=yrd.map
+\end{verbatim}
+If you installed the package in your personal tree, you \emph{may} prefer to use:
+\begin{verbatim}
+	updmap --enable Map=yrd.map
+\end{verbatim}
+
+Either way, \verb|updmap| will output a good deal of information after each incantation. This is normal. Just check that it does not end with an error and that it found the new map file.
+
+\subsubsection{Method 2: \TeX~Live 2008 (and probably earlier)}
+
+If you installed the package system-wide, use \verb|updmap-sys --edit|.
+
+If you installed into your personal tree, you \emph{may} prefer to use	\verb|updmap --edit|.
+
+Either way, a configuration file will be opened which you can edit. Move to the end of the file and add the following line:
+\begin{verbatim}
+	Map yrd.map
+\end{verbatim}
+When you are done, save the file. \verb|updmap| or \verb|updmap-sys| will produce a great deal of output if all is well. Just check that it does not end with an error and that \path{yrd.map} is found.
+
+\subsubsection{Method 2: \TeX~Live 2009 (and possibly later)}
+
+If you installed the package system-wide, edit or or create \path{TEXMFLOCAL/web2c/updmap-local.cfg} and add the following line to the end of the file:
+\begin{verbatim}
+	Map yrd.map
+\end{verbatim}
+Save the file and tell \verb|tlmgr| to merge in your addition using the command:
+\begin{verbatim}
+	tlmgr generate updmap
+\end{verbatim}
+\verb|tlmgr| will then tell you that you need to ensure the changes are propagated correctly by calling \verb|updmap-sys|. This should produce a great deal of output. Check that it finds the new map file and does not end with an error.
+
+If you installed into your personal tree, you \emph{may} prefer to use \verb|	updmap --edit| as described above for \TeX~Live 2008.
+
+To test your installation and that the package works on your system, latex this file (\path{romandeadf.tex}). The console output and/or log should tell you whether any fonts were not found. If you are careful not to overwrite it, you may also compare your output with \path{romandeadf.pdf}.
+
+\section{The support package}\label{sec:support}
+
+\subsection{Encodings}\label{sec:encs}
+
+The package supports modified \textsc{ec}/\textsc{t1} and Text Companion (\textsc{ts1}) encodings. Most characters in the \textsc{ec} encoding are available and the fonts provide a small number of characters from the \textsc{ts1} encoding as well, including the \texteuro. The regular version of the \textsc{ec}/\textsc{t1} encoding (\path{t1-romandeadf.enc}) reassigns one slot which would otherwise be empty due to missing glyphs which \path{fontinst} cannot fake. In the \textsc{t1} encoding, this slot is standardly used for the per thousand zero. \path{t1-romandeadf.enc} uses the slot for the slashed zero (0*). The fonts also lack the unfakable Sami Eng/eng characters (\textorigrm{\NG}/\textorigrm{\ng}). Although these slots remain in the regular version of the encoding, they are empty due to the lack of suitable glyphs.
+
+The ``alternative'' version of the \textsc{ec}/\textsc{t1} encoding (\path{t1-romandeadf-alt.enc}) provides access to the full range of ligatures available --- including `\textalt{ct}', `\textalt{sp}', `\textalt{st}' and `\textalt{s*t}' --- in addition to the alternate `Q' (\textalt{Q*}) and the long s (\textalt{s*}). The slots used by \textsc{t1} for the Sami characters and per thousand zero are reassigned first since these would otherwise be empty, but because further slots are required, a number of characters normally available in the \textsc{ec} encoding are unavailable. These are Ohungarumlaut (\u{O}), ohungarumlaut (\u{o}), Uhungarumlaut (\u{U}) and dbar (\dj). Attempting to access these characters while using the alternative versions of the fonts may result in errors of various kinds and will certainly produce unexpected output even though the characters are provided by the fonts, as the previous sentence demonstrates. To access these glyphs, ensure that the regular version of the fonts are active.
+
+\subsection{\LaTeX\ package}
+
+To use the fonts in a \LaTeX\ document, add \verb|\usepackage{romande}| to your document preamble. This will set the default serif/roman family to \fname{yrd} (\fgroup{romande}) and enable access to the various alternates and additional glyphs available in the other families. The package supports the single option \verb|alt|. Loading \lpack{romande} with this option will select the ``alternative'' version as the default serif/roman family. \textbf{\emph{This option is not recommended unless you are \emph{certain} you do not wish to access any of the characters described in \fref{sec:encs}.}} You should also note that this option will mean all of the additional ligatures will be active, which may not be what you want.
+
+Note that loading \path{romande.sty} will not affect the default sans-serif or typewriter families.
+	
+\section{Additional font selection commands}\label{sec:commands}
+
+	The \LaTeX\ package \lpack{romande}\ loads \lpack{nfssext-cfr}\ which is an extension of the package \lpack{nfssext}\ supplied by Philipp Lehman as part of The Font Installation Guide. The file extends the font selection commands to facilitate access to various font features. Both the original and the extension are designed for use with a wide range of fonts. For this reason, only a subset of the additional commands are relevant to any particular font support package. Those relevant to \lpack{romandeadf}\ are described below.
+	
+	I consider my additions to \lpack{nfssext-cfr}\ to be \emph{highly experimental}. If things don't work as advertised, apart from letting me know about the problem, you may be able to access the features you need by issuing a \verb|\normalfont| and then selecting features from there. This command will return you to the default document text font --- typically the relevant serif in regular weight, standard width and upright shape with oldstyle or lining figures etc.\ as determined by the packages and options loaded or your distribution's setup.
+	
+\subsection{nfssext-cfr}
+
+These commands are available when \lpack{romande} is loaded. If for some reason you wish to make them available when no relevant package is loaded, use \verb|\usepackage{nfssext-cfr}| in your document preamble.
+	
+\subsubsection{Styles}
+
+	\begin{longtable}{llll}
+		\toprule
+		\textbf{style}			&	\textbf{style command}	&	\textbf{text command}	&	\textbf{effect}\\\midrule\endhead
+		\bottomrule\endfoot
+		alternate					&	\verb|\altstyle|					&	\verb|\textalt{}|					&	``alternative''\\
+		script/swash				&	\verb|\swashstyle|				&	\verb|\textswash{}|			&	italic, regular script\\
+	\end{longtable}
+	
+	\verb|\swashstyle| and \verb|\textswash{}| switch to the script font (\fgroup{yrdw}/\fgroup{yrdaw}) regardless of the current shape and weight --- you do not need to select italic shape or regular weight.
+	
+	\verb|\altstyle| and \verb|\textalt{}| switch to the ``alternative'' families (\fgroup{yrda}/\fgroup{yrdaw}). Within the scope of these commands and except for small-caps:
+	\begin{itemize}
+		\item \verb|Q*| will typeset the alternate `Q' (\textalt{Q*});
+		\item \verb|s*| will typeset the long s (\textalt{s*});
+		\item \verb|ct|, \verb|sp|, \verb|st| and \verb|s*t| will typeset the corresponding ligature (\textalt{ct}/\textalt{sp}/\textalt{st}/\textalt{s*t});
+		\item attempting to typeset certain standard characters will produce unexpected results (see \fref{sec:encs}).
+	\end{itemize}
+	
+	To make things slightly more convenient, \verb|Q*| and \verb|s*| will not be typeset literally when the regular encoding (or small-caps) is active. Rather, these sequences will simply typeset the standard `Q' and `s'.
+	
+	For example, suppose that \lpack{romande}\ was loaded and the following commands set up:
+		\begin{verbatim}
+			\newcommand{\fytext}{%
+			Sphinx of black quartz, judge my vow.\\
+			Querulous sponges act last.\\
+			Q*uerulous s*ponges* act las*t.}
+			\newcommand{\fytest}{%
+			\fytext\\[1em]
+			\textit{\fytext}\\[1em]
+			\textsc{\fytext}\\[1em]
+			\textbf{\fytext\\[1em]
+			\textit{\fytext}\\[1em]
+			\textsc{\fytext}}\\[1em]
+			\textswash{\fytext}}
+		\end{verbatim}
+		\newcommand{\fytext}{%
+			Sphinx of black quartz, judge my vow.\\
+			Querulous sponges act last.\\
+			Q*uerulous s*ponges* act las*t.}
+		\newcommand{\fytest}{%
+			\fytext\\[1em]
+			\textit{\fytext}\\[1em]
+			\textsc{\fytext}\\[1em]
+			\textbf{\fytext\\[1em]
+			\textit{\fytext}\\[1em]
+			\textsc{\fytext}}\\[1em]
+			\textswash{\fytext}}
+		Then:
+		\begin{verbatim}
+			--- ``regular'' ---\\[1em]
+			\fytest\\\bigskip
+			--- ``alternate'' ---\\[1em]
+			\altstyle			
+			\fytest
+		\end{verbatim}
+		produces:
+		\begin{center}
+			--- ``regular'' ---\\[1em]
+			\fytest\\\bigskip
+			--- ``alternate'' ---\\[1em]
+			\altstyle			
+			\fytest
+		\end{center}
+		
+\subsubsection{The slashed zero (0*)}
+
+Both of the modified \textsc{t1} encodings used by \lpack{romandeadf} include a non-standard ligature to accommodate the slashed zero. Provided \lpack{romande} is loaded and the default serif/roman family is active, \verb|0*| will produce the slashed zero (0*). 
+	
+\end{document}  
\ No newline at end of file