xml_jats_resolver 0.0.1

data/lib/dtd/atypon/2.2/dtd/section.ent

@@ -0,0 +1,327 @@
+<!-- ============================================================= -->
+<!--  MODULE:    Section Class Elements                            -->
+<!--  VERSION:   2.2                                               -->
+<!--  DATE:      March 2009                                        -->
+<!--                                                               -->
+<!-- ============================================================= -->
+
+<!-- ============================================================= -->
+<!--                    PUBLIC DOCUMENT TYPE DEFINITION            -->
+<!--                        TYPICAL INVOCATION                     -->
+<!--
+"-//Atypon//DTD Atypon Systems Archival NLM DTD Suite Section Class Elements v2.2.0 20090301//EN"
+     Delivered as file "section.ent"                               -->
+<!-- ============================================================= -->
+
+<!-- ============================================================= -->
+<!-- SYSTEM:     Archiving and Interchange DTD Suite               -->
+<!--                                                               -->
+<!-- PURPOSE:    Defines the member of the sec.class, that is,     -->
+<!--             names all section-level elements in the           -->
+<!--             Archiving and Interchange DTD Suite               -->
+<!--                                                               -->
+<!--             At the time of the initial DTD creation           -->
+<!--             there is only one such element, Section itself    -->
+<!--             <sec>, but future expansion to named sections     -->
+<!--             (such as <methodology> or <materials> or any      -->
+<!--             new section-level structures would be added here. -->
+<!--                                                               -->
+<!-- CONTAINS:   1) Default definition of the section class        -->
+<!--             2) Defaults for attribute lists                   -->
+<!--             3) Section <sec>                                  -->
+<!--                                                               -->
+<!-- CREATED FOR:                                                  -->
+<!--             Digital archives and publishers who wish to       -->
+<!--             create a custom XML DTD for original markup of    -->
+<!--             journal literature, books, and related material,  -->
+<!--             or for archiving and transferring such material   -->
+<!--             between archives.                                 -->
+<!--                                                               -->
+<!--             This DTD is in the public domain. An organization -->
+<!--             that wishes to create its own DTD from the suite  -->
+<!--             may do so without permission from NLM.            -->
+<!--                                                               -->
+<!--             The suite has been set up to be extended using a  -->
+<!--             new DTD file and a new DTD-specific customization -->
+<!--             module to redefine the many Parameter Entities.   -->
+<!--             Do not modify the suite directly or redistribute  -->
+<!--             modified versions of the suite.                   -->
+<!--                                                               -->
+<!--             In the interest of maintaining consistency and    -->
+<!--             clarity for potential users, NLM requests:        -->
+<!--                                                               -->
+<!--             1. If you create a DTD from the Archiving and     -->
+<!--                Interchange DTD Suite and intend to stay       -->
+<!--                compatible with the suite, then please include -->
+<!--                the following statement as a comment in all of -->
+<!--                your DTD modules:                              -->
+<!--                   "Created from, and fully compatible with,   -->
+<!--                    the Archiving and Interchange DTD Suite."  -->
+<!--                                                               -->
+<!--             2. If you alter one or more modules of the suite, -->
+<!--                then please rename your version and all its    -->
+<!--                modules to avoid any confusion with the        -->
+<!--                original suite. Also, please include the       -->
+<!--                following statement as a comment in all your   -->
+<!--                DTD modules:                                   -->
+<!--                   "Based in part on, but not fully compatible -->
+<!--                    with, the Archiving and Interchange DTD    --> 
+<!--                    Suite."                                    -->
+<!--                                                               -->
+<!--             Suggestions for refinements and enhancements to   -->
+<!--             the DTD suite should be sent in email to:         -->
+<!--                 archive-dtd@ncbi.nlm.nih.gov                  -->
+<!--                                                               -->
+<!-- ORIGINAL CREATION DATE:                                       -->
+<!--             December 2002                                     -->
+<!--                                                               -->
+<!-- CREATED BY: Jeff Beck       (NCBI)                            -->
+<!--             Deborah Lapeyre (Mulberry Technologies, Inc.)     -->
+<!--             Bruce Rosenblum (Inera Inc.)                      -->
+<!--                                                               -->
+<!--             NLM thanks the Harvard University Libraries, both -->
+<!--             for proposing that a draft archiving NLM DTD for  --> 
+<!--             life sciences journals be extended to accommodate -->
+<!--             journals in all disciplines and for sponsoring    -->
+<!--             Bruce Rosenblum's collaboration with other DTD    -->
+<!--             authors in completing Version 1.0. The Andrew W.  --> 
+<!--             Mellon Foundation provided support for these      --> 
+<!--             important contributions.                          -->
+<!--                                                               -->
+<!-- ============================================================= -->
+
+
+<!-- ============================================================= -->
+<!--                    DTD VERSION/CHANGE HISTORY                 -->
+<!-- ============================================================= -->
+<!--
+     =============================================================
+
+Version  Reason/Occasion                   (who) vx.x (yyyy-mm-dd)
+
+     =============================================================
+     Version 2.2                       (DAL/BTU) v2.2 (2006-04-30)
+     
+     Backwards-compatible changes to meet operational needs.
+     Typical changes include adding attribute values and making 
+     required elements optional.
+          
+  5. SECTION METADATA - Added new element <sec-meta>. There are 
+     sections that are authored independently, even in journal 
+     articles, and this is the start of allowing additional metadata 
+     for such sections.
+     
+  4. Updated public identifier to "v2.2 20060430//EN"          
+
+     =============================================================
+     Version 2.0                       (DAL/BTU) v2.0 (2004-08-30)
+     
+     Major requirement changes led to the new release, producing
+     DTD version "2.0":
+       a) The splitting of the Archival and Interchange Tag Set 
+          DTDs into three DTDs from two: an authoring DTD, an
+          archive regularization and interchange DTD (the
+          current Blue Publishing DTD), and a preservationist 
+          archive DTD (the current Green Archiving and Interchange 
+          DTD).
+       b) AIT Working Group suggestions from the June 04 meeting 
+          and June/July 2004 followup discussions
+       c) Suite remodularization to meet new (and newly articulated)
+          modularization requirements
+       d) New or renamed classes and mixes to make modifications
+          easier and more consistent
+
+  3. COMPLETE MODELS WHEN OVER-RIDING A MODEL 
+     (for all Parameter Entities suffixed "-model")
+     ### Customization Alert ###
+     Added internal parentheses to Parameter Entity and removed 
+     them from Element Declaration for:
+     - %sec-model;
+
+  2. DEFAULT CLASSES - Were moved from this module to 
+     %default-classes.ent;
+  
+  1. Updated public identifier to "v2.0 20040830"          
+                                                                   -->
+
+
+<!-- ============================================================= -->
+<!--                    PARAMETER ENTITY DEPENDENCIES             
+                        Requires the following parameter entities
+                        be defined before calling this module. 
+                        The content-model Parameter Entities are
+                        defined in %common.ent; but may be
+                        redefined in the Customization Module for
+                        the specific DTD:
+                          %sec-model; - Content model for section-like 
+                                        elements  
+                                                                   -->
+<!-- ============================================================= -->
+
+
+<!-- ============================================================= -->
+<!--                    DEFAULTS FOR ATTRIBUTE LISTS               -->
+<!-- ============================================================= -->
+
+
+<!--                    SECTION ATTRIBUTES                         -->
+<!--                    Attribute list for Section element         -->
+<!ENTITY % sec-atts   
+            "id         ID                                 #IMPLIED
+             xml:lang   NMTOKEN                            #IMPLIED
+             sec-type   CDATA                              #IMPLIED 
+             disp-level CDATA                              #IMPLIED" >
+
+
+<!-- ============================================================= -->
+<!--                    SECTION ELEMENTS                           -->
+<!-- ============================================================= -->
+
+
+<!--                    SECTION                                    -->
+<!--                    A headed group of material; the basic 
+                        structural unit of the article             -->
+<!ELEMENT  sec          %sec-model;                                  >
+<!--         id         Unique identifier, so the Section can be
+                        referenced                   
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiations such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English). 
+             sec-type   Conversion Note: This attribute may be used
+                        to retain information on the semantic
+                        content of a section where that is known.
+                        Authoring Note: Top-level sections (those 
+                        that are not nested inside other sections)
+                        may be assigned a "type" attribute for 
+                        indexing purposes. This attribute should be
+                        used only if the section is one of the listed
+                        types and should otherwise be omitted. A
+                        section that contains content of more than 
+                        one type should have the type IDs combined.
+                        (e.g., "Materials and Methods" would be
+                        type="materials|methods").  
+                        Types values are:         
+                          cases     Cases/Case Reports
+                          conclusions Conclusions/Comment
+                          discussion  Discussion/Interpretation
+                          intro     Introduction/Synopsis/Overview
+                          materials Materials
+                          methods   Methods/Methodology/Procedures
+                          results   Results/Statement of Findings
+                          subjects  Patients/Participants/Subjects
+                          supplementary-material
+                                    Supplementary Materials
+             disp-level Sometimes in print or on screen, the display
+                        or apparent hierarchical level of a section
+                        is not the same as its real position in the
+                        hierarchy.  For example, in some styles,
+                        the "Clinical Finding" Section or the 
+                        'Methodology" Section always looks like a 
+                        particular level heading (say a level 2 head),
+                        wherever it falls in the hierarchy (say a 
+                        level 1 head or a level 3 head). This
+                        attribute can be used to record the needed
+                        display level. (Rare)                      -->
+<!ATTLIST  sec
+             %sec-atts;                                              >
+
+
+<!--                    SECTION METADATA                           -->
+<!--                    In some articles, each section has a different
+                        author or some sections are authored by 
+                        different contributors from the enclosing
+                        article. This wrapper element for 
+                        section-level metadata is used to capture
+                        information concerning those contributors. -->
+<!ELEMENT  sec-meta     %sec-meta-model;                             >
+
+
+<!-- ============================================================= -->
+<!--                    EXAM ELEMENTS                              -->
+<!-- ============================================================= -->
+
+<!--                    QUESTION ATTRIBUTES                        -->
+<!--                    Attribute list for Question element        -->
+<!ENTITY % question-atts
+            "id         ID                                 #IMPLIED
+             xml:lang   NMTOKEN                            #IMPLIED">
+
+
+<!--                    QUESTION                                   -->
+<!--                    A question structure used in an exam       -->
+<!ELEMENT  question     (%sec-opt-title-model;, answer+, explanation?)         >
+<!--         id         Unique identifier, so the Question can be
+                        referenced                   
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiations such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English)                    -->
+<!ATTLIST  question
+             %question-atts;                                         >
+
+<!--                    ANSWER ATTRIBUTES                          -->
+<!--                    Attribute list for Answer element          -->
+<!ENTITY % answer-atts
+            "id         ID                                 #IMPLIED
+             xml:lang   NMTOKEN                            #IMPLIED
+             correct    (yes|no)                           #IMPLIED" >
+
+<!--                    ANSWER                                   -->
+<!--                    An answer element to an exam question    -->
+<!ELEMENT  answer  %sec-opt-title-model;                           >
+<!--         id         Unique identifier, so the Answer can be
+                        referenced                   
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiations such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English)
+	    correct     Indicates whether this answer is the correct
+	                one. The attribute has a default value of
+			"no"                                       -->
+<!ATTLIST  answer
+             %answer-atts;                                           >
+
+<!--                    EXPLANATION ATTRIBUTES                     -->
+<!--                    Attribute list for Explanation element     -->
+<!ENTITY % explanation-atts
+            "id         ID                                 #IMPLIED
+             xml:lang   NMTOKEN                            #IMPLIED" >
+
+<!--                    EXPLANATION                              -->
+<!--                    An explanation to an exam answer         -->
+<!ELEMENT  explanation  %sec-opt-title-model;                      >
+<!--         id         Unique identifier, so the Explanation can be
+                        referenced                   
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiations such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English)                   -->
+<!ATTLIST  explanation
+             %explanation-atts;                                           >
+
+<!-- ================== End Section Class Module ================= -->

data/lib/dtd/atypon/2.2/dtd/xmlchars/isogrk1.ent

@@ -0,0 +1,70 @@
+
+<!--
+     File isogrk1.ent produced by the XSL script characters.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to David Carlisle
+     via the public W3C list www-math@w3.org.
+
+     The numeric character values assigned to each entity
+     (should) match the Unicode assignments in Unicode 4.0.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY Agr              "&#x00391;" ><!--=capital Alpha, Greek -->
+<!ENTITY agr              "&#x003B1;" ><!--=small alpha, Greek -->
+<!ENTITY Bgr              "&#x00392;" ><!--=capital Beta, Greek -->
+<!ENTITY bgr              "&#x003B2;" ><!--=small beta, Greek -->
+<!ENTITY Dgr              "&#x00394;" ><!--=capital Delta, Greek -->
+<!ENTITY dgr              "&#x003B4;" ><!--=small delta, Greek -->
+<!ENTITY EEgr             "&#x00397;" ><!--=capital Eta, Greek -->
+<!ENTITY eegr             "&#x003B7;" ><!--=small eta, Greek -->
+<!ENTITY Egr              "&#x00395;" ><!--=capital Epsilon, Greek -->
+<!ENTITY egr              "&#x003B5;" ><!--=small epsilon, Greek -->
+<!ENTITY Ggr              "&#x00393;" ><!--=capital Gamma, Greek -->
+<!ENTITY ggr              "&#x003B3;" ><!--=small gamma, Greek -->
+<!ENTITY Igr              "&#x00399;" ><!--=capital Iota, Greek -->
+<!ENTITY igr              "&#x003B9;" ><!--=small iota, Greek -->
+<!ENTITY Kgr              "&#x0039A;" ><!--=capital Kappa, Greek -->
+<!ENTITY kgr              "&#x003BA;" ><!--=small kappa, Greek -->
+<!ENTITY KHgr             "&#x003A7;" ><!--=capital Chi, Greek -->
+<!ENTITY khgr             "&#x003C7;" ><!--=small chi, Greek -->
+<!ENTITY Lgr              "&#x0039B;" ><!--=capital Lambda, Greek -->
+<!ENTITY lgr              "&#x003BB;" ><!--=small lambda, Greek -->
+<!ENTITY Mgr              "&#x0039C;" ><!--=capital Mu, Greek -->
+<!ENTITY mgr              "&#x003BC;" ><!--=small mu, Greek -->
+<!ENTITY Ngr              "&#x0039D;" ><!--=capital Nu, Greek -->
+<!ENTITY ngr              "&#x003BD;" ><!--=small nu, Greek -->
+<!ENTITY Ogr              "&#x0039F;" ><!--=capital Omicron, Greek -->
+<!ENTITY ogr              "&#x003BF;" ><!--=small omicron, Greek -->
+<!ENTITY OHgr             "&#x003A9;" ><!--=capital Omega, Greek -->
+<!ENTITY ohgr             "&#x003C9;" ><!--=small omega, Greek -->
+<!ENTITY Pgr              "&#x003A0;" ><!--=capital Pi, Greek -->
+<!ENTITY pgr              "&#x003C0;" ><!--=small pi, Greek -->
+<!ENTITY PHgr             "&#x003A6;" ><!--=capital Phi, Greek -->
+<!ENTITY phgr             "&#x003C6;" ><!--=small phi, Greek -->
+<!ENTITY PSgr             "&#x003A8;" ><!--=capital Psi, Greek -->
+<!ENTITY psgr             "&#x003C8;" ><!--=small psi, Greek -->
+<!ENTITY Rgr              "&#x003A1;" ><!--=capital Rho, Greek -->
+<!ENTITY rgr              "&#x003C1;" ><!--=small rho, Greek -->
+<!ENTITY sfgr             "&#x003C2;" ><!--=final small sigma, Greek -->
+<!ENTITY Sgr              "&#x003A3;" ><!--=capital Sigma, Greek -->
+<!ENTITY sgr              "&#x003C3;" ><!--=small sigma, Greek -->
+<!ENTITY Tgr              "&#x003A4;" ><!--=capital Tau, Greek -->
+<!ENTITY tgr              "&#x003C4;" ><!--=small tau, Greek -->
+<!ENTITY THgr             "&#x00398;" ><!--=capital Theta, Greek -->
+<!ENTITY thgr             "&#x003B8;" ><!--=small theta, Greek -->
+<!ENTITY Ugr              "&#x003A5;" ><!--=capital Upsilon, Greek -->
+<!ENTITY ugr              "&#x003C5;" ><!--=small upsilon, Greek -->
+<!ENTITY Xgr              "&#x0039E;" ><!--=capital Xi, Greek -->
+<!ENTITY xgr              "&#x003BE;" ><!--=small xi, Greek -->
+<!ENTITY Zgr              "&#x00396;" ><!--=capital Zeta, Greek -->
+<!ENTITY zgr              "&#x003B6;" ><!--=small zeta, Greek -->

data/lib/dtd/atypon/2.2/dtd/xmlchars/isogrk2.ent

@@ -0,0 +1,41 @@
+
+<!--
+     File isogrk2.ent produced by the XSL script characters.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to David Carlisle
+     via the public W3C list www-math@w3.org.
+
+     The numeric character values assigned to each entity
+     (should) match the Unicode assignments in Unicode 4.0.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY Aacgr            "&#x00386;" ><!--=capital Alpha, accent, Greek -->
+<!ENTITY aacgr            "&#x003AC;" ><!--=small alpha, accent, Greek -->
+<!ENTITY Eacgr            "&#x00388;" ><!--=capital Epsilon, accent, Greek -->
+<!ENTITY eacgr            "&#x003AD;" ><!--=small epsilon, accent, Greek -->
+<!ENTITY EEacgr           "&#x00389;" ><!--=capital Eta, accent, Greek -->
+<!ENTITY eeacgr           "&#x003AE;" ><!--=small eta, accent, Greek -->
+<!ENTITY Iacgr            "&#x0038A;" ><!--=capital Iota, accent, Greek -->
+<!ENTITY iacgr            "&#x003AF;" ><!--=small iota, accent, Greek -->
+<!ENTITY idiagr           "&#x00390;" ><!--=small iota, dieresis, accent, Greek -->
+<!ENTITY Idigr            "&#x003AA;" ><!--=capital Iota, dieresis, Greek -->
+<!ENTITY idigr            "&#x003CA;" ><!--=small iota, dieresis, Greek -->
+<!ENTITY Oacgr            "&#x0038C;" ><!--=capital Omicron, accent, Greek -->
+<!ENTITY oacgr            "&#x003CC;" ><!--=small omicron, accent, Greek -->
+<!ENTITY OHacgr           "&#x0038F;" ><!--=capital Omega, accent, Greek -->
+<!ENTITY ohacgr           "&#x003CE;" ><!--=small omega, accent, Greek -->
+<!ENTITY Uacgr            "&#x0038E;" ><!--=capital Upsilon, accent, Greek -->
+<!ENTITY uacgr            "&#x003CD;" ><!--=small upsilon, accent, Greek -->
+<!ENTITY udiagr           "&#x003B0;" ><!--=small upsilon, dieresis, accent, Greek -->
+<!ENTITY Udigr            "&#x003AB;" ><!--=capital Upsilon, dieresis, Greek -->
+<!ENTITY udigr            "&#x003CB;" ><!--=small upsilon, dieresis, Greek -->

data/lib/dtd/atypon/2.2/dtd/xmlchars/isogrk4.ent

@@ -0,0 +1,66 @@
+
+<!--
+     File isogrk4.ent produced by the XSL script characters.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to David Carlisle
+     via the public W3C list www-math@w3.org.
+
+     The numeric character values assigned to each entity
+     (should) match the Unicode assignments in Unicode 4.0.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY % plane1D  "&#38;#38;#x1D">
+
+<!ENTITY b.alpha          "%plane1D;6C2;" ><!--small alpha, Greek -->
+<!ENTITY b.beta           "%plane1D;6C3;" ><!--small beta, Greek -->
+<!ENTITY b.chi            "%plane1D;6D8;" ><!--small chi, Greek -->
+<!ENTITY b.Delta          "%plane1D;6AB;" ><!--capital delta, Greek -->
+<!ENTITY b.delta          "%plane1D;6C5;" ><!--small delta, Greek -->
+<!ENTITY b.epsi           "%plane1D;6C6;" ><!--small epsilon, Greek -->
+<!ENTITY b.epsiv          "%plane1D;6DC;" ><!--variant epsilon -->
+<!ENTITY b.eta            "%plane1D;6C8;" ><!--small eta, Greek -->
+<!ENTITY b.Gamma          "%plane1D;6AA;" ><!--capital gamma, Greek -->
+<!ENTITY b.gamma          "%plane1D;6C4;" ><!--small gamma, Greek -->
+<!ENTITY b.Gammad         "&#x003DC;" ><!--capital Digamma -->
+<!ENTITY b.gammad         "&#x003DD;" ><!--digamma -->
+<!ENTITY b.iota           "%plane1D;6CA;" ><!--small iota, Greek -->
+<!ENTITY b.kappa          "%plane1D;6CB;" ><!--small kappa, Greek -->
+<!ENTITY b.kappav         "%plane1D;6DE;" ><!--variant kappa -->
+<!ENTITY b.Lambda         "%plane1D;6B2;" ><!--capital Lambda, Greek -->
+<!ENTITY b.lambda         "%plane1D;6CC;" ><!--small lambda, Greek -->
+<!ENTITY b.mu             "%plane1D;6CD;" ><!--small mu, Greek -->
+<!ENTITY b.nu             "%plane1D;6CE;" ><!--small nu, Greek -->
+<!ENTITY b.Omega          "%plane1D;6C0;" ><!--capital Omega, Greek -->
+<!ENTITY b.omega          "%plane1D;6DA;" ><!--small omega, Greek -->
+<!ENTITY b.Phi            "%plane1D;6BD;" ><!--capital Phi, Greek -->
+<!ENTITY b.phi            "%plane1D;6D7;" ><!--small phi, Greek -->
+<!ENTITY b.phiv           "%plane1D;6DF;" ><!--variant phi -->
+<!ENTITY b.Pi             "%plane1D;6B7;" ><!--capital Pi, Greek -->
+<!ENTITY b.pi             "%plane1D;6D1;" ><!--small pi, Greek -->
+<!ENTITY b.piv            "%plane1D;6E1;" ><!--variant pi -->
+<!ENTITY b.Psi            "%plane1D;6BF;" ><!--capital Psi, Greek -->
+<!ENTITY b.psi            "%plane1D;6D9;" ><!--small psi, Greek -->
+<!ENTITY b.rho            "%plane1D;6D2;" ><!--small rho, Greek -->
+<!ENTITY b.rhov           "%plane1D;6E0;" ><!--variant rho -->
+<!ENTITY b.Sigma          "%plane1D;6BA;" ><!--capital Sigma, Greek -->
+<!ENTITY b.sigma          "%plane1D;6D4;" ><!--small sigma, Greek -->
+<!ENTITY b.sigmav         "%plane1D;6D3;" ><!--variant sigma -->
+<!ENTITY b.tau            "%plane1D;6D5;" ><!--small tau, Greek -->
+<!ENTITY b.Theta          "%plane1D;6AF;" ><!--capital Theta, Greek -->
+<!ENTITY b.thetas         "%plane1D;6C9;" ><!--straight theta, Greek -->
+<!ENTITY b.thetav         "%plane1D;6DD;" ><!--variant theta -->
+<!ENTITY b.Upsi           "%plane1D;6BC;" ><!--capital Upsilon, Greek -->
+<!ENTITY b.upsi           "%plane1D;6D6;" ><!--small upsilon, Greek -->
+<!ENTITY b.Xi             "%plane1D;6B5;" ><!--capital Xi, Greek -->
+<!ENTITY b.xi             "%plane1D;6CF;" ><!--small xi, Greek -->
+<!ENTITY b.zeta           "%plane1D;6C7;" ><!--small zeta, Greek -->