diff options
Diffstat (limited to 'Master')
20 files changed, 2075 insertions, 1 deletions
diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/GPL.txt b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/GPL.txt new file mode 100644 index 00000000000..a3bd60912a4 --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/GPL.txt @@ -0,0 +1,697 @@ +Church Slavonic fonts Copyright (C) 2010-2016 Aleksandr Andreev and Yuri Shardt +Portions Copyright (C) 2010-2016 Nikita Simmons + +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 3 of the License, or +(at your option) any later version. + +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. + +A copy of the GNU General Public License is reproduced below. +You may also find it at http://www.gnu.org/licenses/. + +As a special exception, if you create a document which uses this 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. + + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. 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 +them 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 prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. 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. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey 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; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If 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 convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU 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 that a certain numbered version of the GNU General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + 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. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +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. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + 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 +state 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 3 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, see <http://www.gnu.org/licenses/>. + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + <program> Copyright (C) <year> <name of author> + This program 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, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +<http://www.gnu.org/licenses/>. + + The GNU 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 Lesser General +Public License instead of this License. But first, please read +<http://www.gnu.org/philosophy/why-not-lgpl.html>. + diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/LICENSE b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/LICENSE new file mode 100644 index 00000000000..4800a194285 --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/LICENSE @@ -0,0 +1,12 @@ +All fonts are dual-licensed EITHER: + * under the SIL Open Font License version 1.1, + a copy of which is reproduced in OFL.txt; OR + * under the GNU General Public License, v. 3 (or any later version) + with the font exception (see GPL.txt for details) +AT YOUR CHOOSING. + +Regardless of the license, it is understood that all of these fonts are free software. +As such, they come with ABSOLUTELY NO WARRANTY; +without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/OFL.txt b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/OFL.txt new file mode 100644 index 00000000000..ad14102b281 --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/OFL.txt @@ -0,0 +1,96 @@ +Copyright (c) 2013-2016, Aleksandr Andreev, Yuri Shardt, Nikita Simmons +(<http://www.ponomar.net/|aleksandr.andreev@gmail.com>), +without reserved font names. + +This Font Software is licensed under the SIL Open Font License, Version 1.1. +This license is copied below, and is also available with a FAQ at: +http://scripts.sil.org/OFL + + +----------------------------------------------------------- +SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 +----------------------------------------------------------- + +PREAMBLE +The goals of the Open Font License (OFL) are to stimulate worldwide +development of collaborative font projects, to support the font creation +efforts of academic and linguistic communities, and to provide a free and +open framework in which fonts may be shared and improved in partnership +with others. + +The OFL allows the licensed fonts to be used, studied, modified and +redistributed freely as long as they are not sold by themselves. The +fonts, including any derivative works, can be bundled, embedded, +redistributed and/or sold with any software provided that any reserved +names are not used by derivative works. The fonts and derivatives, +however, cannot be released under any other type of license. The +requirement for fonts to remain under this license does not apply +to any document created using the fonts or their derivatives. + +DEFINITIONS +"Font Software" refers to the set of files released by the Copyright +Holder(s) under this license and clearly marked as such. This may +include source files, build scripts and documentation. + +"Reserved Font Name" refers to any names specified as such after the +copyright statement(s). + +"Original Version" refers to the collection of Font Software components as +distributed by the Copyright Holder(s). + +"Modified Version" refers to any derivative made by adding to, deleting, +or substituting -- in part or in whole -- any of the components of the +Original Version, by changing formats or by porting the Font Software to a +new environment. + +"Author" refers to any designer, engineer, programmer, technical +writer or other person who contributed to the Font Software. + +PERMISSION & CONDITIONS +Permission is hereby granted, free of charge, to any person obtaining +a copy of the Font Software, to use, study, copy, merge, embed, modify, +redistribute, and sell modified and unmodified copies of the Font +Software, subject to the following conditions: + +1) Neither the Font Software nor any of its individual components, +in Original or Modified Versions, may be sold by itself. + +2) Original or Modified Versions of the Font Software may be bundled, +redistributed and/or sold with any software, provided that each copy +contains the above copyright notice and this license. These can be +included either as stand-alone text files, human-readable headers or +in the appropriate machine-readable metadata fields within text or +binary files as long as those fields can be easily viewed by the user. + +3) No Modified Version of the Font Software may use the Reserved Font +Name(s) unless explicit written permission is granted by the corresponding +Copyright Holder. This restriction only applies to the primary font name as +presented to the users. + +4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font +Software shall not be used to promote, endorse or advertise any +Modified Version, except to acknowledge the contribution(s) of the +Copyright Holder(s) and the Author(s) or with their explicit written +permission. + +5) The Font Software, modified or unmodified, in part or in whole, +must be distributed entirely under this license, and must not be +distributed under any other license. The requirement for fonts to +remain under this license does not apply to any document created +using the Font Software. + +TERMINATION +This license becomes null and void if any of the above conditions are +not met. + +DISCLAIMER +THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE +COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL +DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM +OTHER DEALINGS IN THE FONT SOFTWARE. + diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/README b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/README new file mode 100644 index 00000000000..f429a9b21f1 --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/README @@ -0,0 +1,49 @@ +fonts-churchslavonic +===================== + +Collection of free fonts for Church Slavonic language (also known as Church Slavic +and Old Church Slavonic), ISO 639-1 code "cu". + +All fonts use Unicode character encoding and are intended for Unicode TeX engines +only. + + +Installation: +------------- + + tlmgr install fonts-churchslavonic + + +Using fonts +----------- + +Use "fontspec" LaTeX package to load any of the installed fonts. For example: + + \newfontfamily\ponomar[Script=Cyrillic,HyphenChar=_]{PonomarUnicode.otf} + + +Support +------- + +For bug reports and support questions, please use GitHub issue tracker: + + https://github.com/typiconman/fonts-cu/issues + + +Authors +------- + +Fonts are maintained by the Slavonic Computing Initiative. Please see documentation +for more information about the authors of individual fonts. + +Maintainers +----------- + +Mike Kroutikov <pgmmpk@gmail.com>. +Aleksandr Andreev <aleksandr.andreev@gmail.com>. + +License +------- + +SIL Open Font License version 1.1 + diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/fonts-churchslavonic.pdf b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/fonts-churchslavonic.pdf Binary files differnew file mode 100644 index 00000000000..943c35b5263 --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/fonts-churchslavonic.pdf diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/fonts-churchslavonic.tex b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/fonts-churchslavonic.tex new file mode 100644 index 00000000000..c3f3759658a --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/fonts-churchslavonic.tex @@ -0,0 +1,1218 @@ +\documentclass[11pt]{ltxdoc} +\usepackage[usenames,dvipsnames,svgnames,table]{xcolor} +\usepackage{fontspec} +\usepackage{xltxtra} +% code borrowed from Polyglossia documentation — Thanks! +\definecolor{myblue}{rgb}{0.02,0.04,0.48} +\definecolor{lightblue}{rgb}{0.61,.8,.8} +\definecolor{myred}{rgb}{0.65,0.04,0.07} +\usepackage[ + bookmarks=true, + colorlinks=true, + linkcolor=myblue, + urlcolor=myblue, + citecolor=myblue, + hyperindex=false, + hyperfootnotes=false, + pdftitle={Church Slavonic fonts}, + pdfauthor={Aleksandr Andreev}, + pdfkeywords={Church Slavic, Church Slavonic, Old Church Slavonic, Old Slavonic, fonts, Unicode} + ]{hyperref} +\usepackage{polyglossia} +\setmainlanguage[variant=american]{english} +\setotherlanguages{russian,churchslavonic} + +%% KEYBOARD DRIVER VERSION AND RELEASE DATES +\def\filedate{April 26, 2016} +\def\fileversion{version 1.0} + +%% fontspec declarations: +\setmainfont[Ligatures = TeX]{Linux Libertine O} +\setsansfont{DejaVu Sans} +\setmonofont[Scale=MatchLowercase]{DejaVu Sans Mono} +\newfontfamily{\slv}[Scale=MatchLowercase]{Ponomar Unicode} +\newfontfamily{\ust}[Scale=MatchLowercase]{Menaion Unicode} + +\linespread{1.05} +\lineskiplimit=-1em +\frenchspacing +\EnableCrossrefs +\CodelineIndex +\RecordChanges +% COMMENT THE NEXT LINE TO INCLUDE THE CODE +\AtBeginDocument{\OnlyDescription} + +% FOR DRAWING KEY CAPS +\begin{document} + +\title{Church Slavonic Fonts} +\author{Aleksandr Andreev \and Yuri Shardt \and Nikita Simmons\thanks{Comments may be directed to \href{mailto:aleksandr.andreev@gmail.com}{aleksandr.andreev@gmail.com}.}} +\date{\filedate \qquad \fileversion\\ +\footnotesize (\textsc{pdf} file generated on \today)} + +\maketitle +\tableofcontents + +\section{Introduction} + +Church Slavonic (also called Church Slavic, Old Church Slavonic +or Old Slavonic; ISO 639-2 code |cu|) is a literary language used by +the Slavic peoples; presently it is used as a liturgical language by the +Russian Orthodox Church, other local Orthodox Churches, as well +as various Byzantine-Rite Catholic and Old Ritualist communities. +The package \texttt{fonts-churchslavonic} provides fonts for +representing Church Slavonic text. + +The fonts are designed to work with Unicode text encoded in UTF-8. +Texts encoded in legacy codepages (such as HIP and UCS) may be +converted to Unicode using a separate bundle of utilities. +See the \href{http://sci.ponomar.net/} +{Slavonic Computing Initiative website} for more information. + +\section{License} + +The fonts distributed in this package are dual-licensed under the GNU General Public License +(version 3 or later) and the SIL Open Font License (version 1.1 or later). The SIL +Open Font License is preferred, since this is a FLOSS license intended for fonts. +Dual licensing under GNU GPL is maintained to allow embedding of these +fonts into GPL-licensed applications and for compatibility with other projects. + +\subsection{The Legal Text} + +The fonts distributed in this package are free software: you can redistribute them and/or modify +them, in whole or in part, EITHER under the terms of the GNU General Public License as published by +the Free Software Foundation, either version 3 of the License, or +(at your option) any later version OR under the terms of the SIL Open Font License, +version 1.1, or (at your option) any later version, without reserved font names. + +As a special exception, if you create a document which uses any of these fonts, and embed the font or unaltered portions of the font +into the document, the 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 any of these fonts, you may extend this exception to your version of the fonts, but you are not obligated to do so. +If you do not wish to do so, delete this exception statement from your version. + +As free software, these fonts are distributed in the hope that they 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 or the SIL Open Font License for more details. + +This document is licensed under the Creative Commons Attribution-ShareAlike 4.0 +International License. To view a copy of this license, visit the \href{http://creativecommons.org/licenses/by-sa/4.0/}{CreativeCommons website}. + +\section{Introduction} + +The package provides several fonts that are intended for working with Church Slavonic text +of various recensions and other texts related to Church Slavonic: +modern Church Slavonic text (“Synodal Slavonic”), historical printed Church Slavonic text +and manuscript uncial (ustav) Church Slavonic text (in either Cyrillic or Glagolitic), +as well as text in Sakha (Yakut), Aleut (Fox Island dialect), and Romanian (Moldovan) +Cyrillic, all written in the ecclesiastical script. The coverage of the various fonts agrees +with the guidelines for font coverage specified in +\href{http://www.unicode.org/notes/tn41/} +{Unicode Technical Note \#41: Church Slavonic Typography in Unicode}. +Generally speaking, it includes most (but not all) characters in the Cyrillic, +Cyrillic Supplement, Cyrillic Extended-A, Cyrillic Extended-B, Cyrillic Extended-C +(as of Unicode 9.0), Glagolitic, and Glagolitic Supplement blocks of Unicode. +Characters not used in Church Slavonic, however, are not included (except for some +characters used in modern Russian, Ukrainian, Belorussian, Serbian and +Macedonian for purposes of compatibility with some applications). + +\section{Installation and Usage} + +If you are reading this document, then you probably have already downloaded +the font package. You may check if you have the most recent version by visiting +the \href{http://sci.ponomar.net/}{Slavonic Computing Initiative website}. + +\subsection{Font Formats} + +All fonts are currently available in two formats: + +\begin{description} +\item[\XeTeXpicfile "truetype.png" width 4mm] TrueType fonts, or, more precisely, +\hyperlink{OT}{OpenType} fonts with TrueType outlines; + +\item[\XeTeXpicfile "opentype.png" width 4mm] \hyperlink{OT}{OpenType} fonts with +PostScript outlines (also called OpenType-CFF fonts). +\end{description} + +\noindent Note that fonts in these two formats have different file extensions: +\texttt{*.ttf} for TrueType, \texttt{*.otf} for OpenType-CFF fonts. +Both the TrueType version and the OpenType-CFF version support +the same set of advanced \hyperlink{OT}{OpenType} features. + +The OpenType-CFF fonts use PostScript outlines, based +on third-order (cubic) Bézier curves, while the TrueType fonts +use second-order (quadratic) curves. There is also a significant difference in +hinting (grid fitting): TrueType instructions theoretically allow to +achieve much better quality of screen rendering than PostScript hinting. +However, since quality hinting is a very difficult and time-consuming process, +both the PostScript hinting and TrueType instructing of the fonts +has been done automatically, so high quality grid fitting is not available. + +Note that it is possible to install both the TrueType and OpenType-CFF versions +simultaneously. For this purpose, the TrueType fonts contain a “TT” suffix in their +font name/family name fields. Since all of the fonts have been drawn in cubic splines +(and then converted to quadratic for the TTF version), and since the TrueType instructions +have been automatically generated, the OpenType-CFF format may +theoretically give you better screen rendering quality, though in most situations +this will not be noticeable. Furthermore, note that only the TTF version supports +\hyperlink{Graphite}{SIL Graphite}, so you will need to use the TrueType fonts +if Graphite support is desired. The following considerations are also in order: + +\begin{itemize} + +\item In older versions of OpenOffice.org, OpenType-CFF fonts +were not properly embedded into PDF files. Moreover, under Unix-based +systems, OpenOffice.org could not access such fonts at all, so using TTF +versions was the only option. This was fixed in OpenOffice.org 3.2 and LibreOffice. + +\item OpenOffice.org and LibreOffice, however, still have no mechanism to +turn off and on advanced OpenType features, so if you plan to use optional typographic +features, you will need to use SIL Graphite, which is only available in the TTF version. + +\item OpenType-CFF fonts are poorly supported in the Sun Java Development Kit, +so we recommend use of the TTF versions in Java programming situations and +on Android devices. + +\item On Microsoft Windows, OpenType glyph positioning is not supported for glyphs +in the Private Use Area or characters outside of the Unicode 7.0 range. You will +need to rely on \hyperlink{Graphite}{SIL Graphite} (only available in the TTF versions) +for positioning of combining Glagolitic characters and various glyphs in the PUA. + +\end{itemize} + +Note that Microsoft Windows checks the presence of +a digital signature in a TrueType font, considering this would allow to distinguish +“old” TrueType fonts from “modern” OpenType fonts with TrueType outlines. +The fonts in this package contain a dummy digital signature +in order to fool Microsoft products into allowing use of additional TrueType features. + +\subsection{Source Packages} + +You can also download the FontForge sources for all of the fonts +from the \href{https://github.com/typiconman/fonts-cu/}{GitHub repository}. +This is only useful if you are planning on editing the fonts in the +\href{http://fontforge.sourceforge.net}{FontForge} font editor. In general, +you will not gain any productivity improvements from rebuilding the font files, +so rebuilding from source is not recommended, unless you have a real need +to modify the fonts, for example, to add your own additional glyphs to the Private Use Area. + +\section{System Requirements} + +All of these fonts are large Unicode fonts and require a Unicode-aware operating +system and software environment. Outside of a Unicode-aware environment, +you will only be able, at most, to access the first 256 glyphs of a font. + +\subsection{Microsoft Windows} + +Unicode has been supported since Windows 95, however to use the +OpenType-CFF version of the fonts, you need at least Windows 2000. +You will need a word processor that can handle +Unicode-based documents, such as Microsoft Word 97 and above, +or \href{http://www.libreoffice.org}{LibreOffice}. +Please note that maintenance of OpenOffice.org has been discontinued, +so we recommend using LibreOffice instead. If using \TeX{}, +you will need a Unicode-aware \TeX{} engine, such as +\XeTeX{} or \LuaTeX. + +You will also need a way to enter the Unicode characters that are not +directly accessible from standard keyboards. We recommend +installing a Church Slavonic or Russian-Extended keyboard layout, +available from the \href{http://www.ponomar.net/cu_support/keyboard.html} +{Slavonic Computing Initiative website}. It is also possible to enter +characters using the Windows Character Map utility or by codepoint, +but this is not recommended. + +\subsection{GNU/Linux} + +In order to be able to handle TrueType or OpenType fonts, your system should +have the \href{http://freetype.sourceforge.net}{freetype} library installed +and enabled; this is normally done by default in all modern distributions. +You will need a Unicode-aware word processor, such +as \href{http://www.libreoffice.org}{LibreOffice}. +Please note that OpenOffice.org is no longer maintained, +so we recommend using LibreOffice instead. If using \TeX, +you will need a Unicode-aware \TeX{} engine, such as +\XeTeX{} or \LuaTeX. + +You will need a keyboard driver to input Unicode characters. +Under GNU/Linux, this is handled by the |m17n| library and database. See the \href{http://www.ponomar.net/cu_support/keyboard.html} +{Slavonic Computing Initiative website} for more details. + +\subsection{OS X} + +Not sure. + +\section{Private Use Area} + +The Unicode Private Use Area (PUA) is a set of three ranges of codepoints +(U+E000 to U+F8FF, Plane 15 and Plane 16) that are guaranteed to never +be assigned to characters by the Unicode Consortium and can be used by third parties +to allocate their own characters. The Slavonic Computing Initiative has established an +industry standard for character allocation in the PUA, which is described in full +in the \href{http://www.ponomar.net/files/pua_policy.pdf}{PUA Allocation Policy}. + +The PUA in these fonts contains various additional glyphs: contextual alternatives, +stylistic alternatives, ligatures, hypothetical and nonce glyphs, various glyphs +not yet encoded in Unicode and various technical symbols. Most of these glyphs +(the alternative glyphs and ligatures) are accessible via +\hyperlink{OT}{OpenType} and \hyperlink{Graphite}{SIL Graphite} features. +Thus, you generally do not need to access glyphs in the PUA directly. There +may be some exceptions: + +\begin{itemize} + +\item If you need to access characters not yet encoded in Unicode and nonce glyphs. + +\item If you need to access alternative glyphs and ligatures on legacy systems that +do not support OpenType or Graphite features. + +\item If you are a computer programmer and need to work with glyphs +on a low level without relying on OpenType: having all alternatives +mapped to the PUA allows for a simple way to access glyphs by codepoint +instead of working with glyph indexes, which can change between versions +of a font. + +\end{itemize} + +\noindent For the characters mapped in the PUA and other technical considerations, +please see the \href{http://www.ponomar.net/files/pua_policy.pdf} +{PUA Allocation Policy}. + +\section{OpenType Technology} +\hypertarget{OT}{}\label{OT} + +OpenType is a “smart font” technology for advanced typography +developed by Microsoft Corporation and Adobe Systems and based on +the TrueType font format. It allows for correct typography in +complex scripts as well as providing advanced typographic effects. +This is achieved by applying various \textit{features}, or \textit{tags}, +described in the OpenType specification. Some of these features are supposed +to be enabled by default, while others are considered optional, and may be +turned on and off by the user when desired. + +\subsection{On Microsoft Windows} + +In order to use these advanced typographic features, +in addition to a “smart” font (like the fonts in this package), you need +an OpenType-aware application. Not all applications currently support OpenType, +and not all applications that claim to support OpenType actually support +all features or provide an interface to access features. Older versions of +Microsoft's Uniscribe library did not support OpenType features for +Cyrillic and Glagolitic, but beginning with Windows 7, this has been resolved. + +Generally speaking, you will get best results in \XeTeX{} or \LuaTeX{} +using the \texttt{fontspec} package or using advanced desktop publishing software +such as Adobe InDesign. Most OpenType features are also accessible +in Microsoft Office 2010 and later (but see below for details). +LibreOffice also supports OpenType features starting with version 4.1, +however provides no method to turn on optional features. Please +see the section on \hyperlink{Graphite}{SIL Graphite}, below. + +\subsection{On GNU/Linux} + +OpenType support is provided by the HarfBuzz shaping library, which is +accessible through FreeType, part of most standard distributions of the X Window +System. Thus, OpenType will be available in any application that uses FreeType, +though many applications lack an interface to turn on and off optional features. +Generally speaking, you will get best results in \XeTeX{} or \LuaTeX{} +using the \texttt{fontspec} package. LibreOffice also supports +OpenType features starting with version 4.1, +however provides no method to turn on optional features. Please +see the section on \hyperlink{Graphite}{SIL Graphite}, below. + +\subsection{OpenType Features} + +\subsubsection{Combining Mark Positioning} +\hypertarget{mark}{} + +OpenType allows smart diacritic positioning: if you type a letter followed by +a diacritic, the diacritic will be placed exactly above or below the letter; this +is provided by the \texttt{mark} feature. In addition, the \texttt{mkmk} feature +is used to position two marks with respect to each other, so that an additional +diacritic can be stacked properly above the first. This behavior is demonstrated +below: + +\begin{figure}[h] +\centering +\begin{tabular}{ll} +\large{ {\slv а} + {\slv ◌́} → {\slv а́ } } & \\ +\large{ {\slv А} + {\slv ◌́} → {\slv А́ } } & (glyph positioning via \emph{mark} feature) \\ +\large{ {\slv ◌ⷭ} + {\slv ◌҇} → {\slv ◌ⷭ҇ } } & (glyph positioning via \emph{mkmk} feature) \\ +\end{tabular} +\end{figure} + +The fonts provide proper \texttt{mark} and \texttt{mkmk} anchor points +for all Cyrillic and Glagolitic letters and combining marks, allowing you to enter them in +almost any combination (even those that are implausible). Most OpenType renderers +(except older versions of Adobe’s Cooltype library) support these features, +so you should be able to achieve correct positioning in most OpenType-aware +applications (for example, in MS Word 2010 or newer, LibreOffice 4.1 or newer, +and \XeTeX{}). + +\subsubsection{Glyph Composition and Decomposition} +\hypertarget{ccmp}{} + +The Glyph Composition / Decomposition (\texttt{ccmp}) feature is used +to compose two characters into a single glyph for better glyph processing. +This feature is also used to create precomposed forms of a base glyph with +diacritical marks when use of only \texttt{mark} and \texttt{mkmk} cannot achieve +the necessary positioning. It is also used to create alternative glyph shapes, +such as the alternative version of the Psili used over capital letters and +the truncated forms of the letter Uk used with accent marks, as is +demonstrated in the examples below: + +\begin{figure}[h] +\centering +\begin{tabular}{ll} +\large{ {\slv ◌҆} } $\rightarrow$ \large { {\slv ◌ } } & (glyph substitution using \emph{ccmp} feature) \\ +\large{ {\slv ◌҆} + {\slv ◌̀} $\rightarrow$ {\slv ◌҆̀} } & (ligature substitution using \emph{ccmp} feature) \\ +\large{ {\slv т} + {\slv } + {\slv в} $\rightarrow$ {\slv тв } } & (ligature substitution using \emph{ccmp} feature) \\ +\large{ {\slv ꙋ} + {\slv ◌ⷯ} $\rightarrow$ {\slv ꙋⷯ } } & (contextual substitution using \emph{ccmp} feature) \\ +\end{tabular} +\end{figure} + +Generally speaking, the \emph{ccmp} feature is not supposed to +(and often just cannot) be turned off, and thus this functionality +should work properly in any OpenType-aware application. For more details +on ligatures, see \href{http://www.unicode.org/notes/tn41/}{Unicode +Technical Note \#41: Church Slavonic Typography in Unicode}. + +\subsubsection{Language-based Features} + +Language-based features such as the \texttt{loca} (localized forms) feature +provide access to language-specific alternate glyph forms, such as the +alternate forms of the Cyrillic Letter I used in Ukrainian and Belorussian: + +\begin{figure}[h] +\centering +\begin{tabular}{ll} +\large{ {\slv і } } & (Church Slavonic text) \\ +\large{ {\slv і̇ } } & (Ukrainian text) \\ +\end{tabular} +\end{figure} + +To make use of these features, you need an OpenType-aware application +that supports specifying the language of text, for example \XeTeX{} or +\LuaTeX{} using the \texttt{fontspec} or \texttt{polyglossia} packages. +Since many software applications do not allow you to specify Church Slavonic +as a language of text, it is assumed by default that the font is being +used to represent Church Slavonic text, and thus all glyphs have +Church Slavonic appearances unless another language is specified. + +LibreOffice allows you to specify that text is in Church Slavonic +starting with version 5.0. This will allow you to take advantage of other +features, such as Church Slavonic hyphenation (see the +\href{http://sci.ponomar.net/}{Slavonic Computing Initiative website} +for more information). Microsoft Corporation does not recognize +Church Slavonic as a valid language, so you will not be able to set +the language of text to Church Slavonic in any Microsoft +product.\footnote{Please do not contact the font maintainers about this issue. +Instead, complain to Microsoft Customer Service in the USA at 1-800-642-7676 +or in Canada at +1 (877) 568-2495.} + +\subsubsection{Stylistic Alternatives and Stylistic Sets} + +Stylistic Alternatives (\texttt{salt} feature) provide variant glyph shapes +that may be selected by the user at will. Typically, these are glyphs that differ +from the base glyph only in graphical appearance where the use of these glyphs +does not follow any language-based or typography-based rules, but rather is +just an embellishment. For example, the following variant forms of U+1F545 +Symbol for Marks Chapter are provided: + +\begin{center} +\begin{tabular}{ccccc} +U+1F545 & \multicolumn{4}{c}{Alternative Glyphs} \\ +\hline +{\slv \Huge 🕅} & \textcolor{gray}{\slv \Huge } & \textcolor{gray}{\slv \Huge } & \textcolor{gray}{\slv \Huge } & \textcolor{gray}{\slv \Huge } \\ +\hline +\end{tabular} +\end{center} + +Stylistic sets are used to enable a group of stylistic variant glyphs, +designed to harmonize visually, and make them automatically substituted +instead of the default forms. OpenType allows to specify up to 20 stylistic +sets, marking them features \texttt{ss01}, \texttt{ss02}, \ldots{} \texttt{ss20}. + +Use of Stylistic Alternatives and Stylistic Sets requires an OpenType-aware +application that provides an interface to turn off and on advanced features +(since by default these features are turned off). This is possible in \XeTeX{} +or \LuaTeX{} using the \texttt{fontspec} package and in advanced desktop +publishing software such as Adobe InDesign. Microsoft Office and LibreOffice +currently have no way to access Stylistic Alternatives and Stylistic Sets. +If necessary, you may access these glyphs by codepoint from the Private +Use Area, though this is not recommended. + +\section{SIL Graphite Technology} + +\hypertarget{Graphite}{}\label{Graphite} + +\href{http://scripts.sil.org/Graphite}{Graphite} is a “smart font” technology +developed by \href{http://www.sil.org}{SIL International}. Since, unlike OpenType, +Graphite does not have predefined features, it provides the developer with an ability +to control subtle typographic features that may be difficult or impossible to handle +with OpenType. In fact, Graphite is in some respects more powerful than OpenType, +though this additional power is not necessary for standard Church Slavonic typography. +In addition, while support of OpenType features often varies from application to application, +Graphite relies on a single engine, and thus all Graphite features are supported +whenever an application supports Graphite. However, Graphite is not supported widely: +in addition to SIL's own \href{http://scripts.sil.org/WorldPadDownload}{WorldPad} +editor (a Windows-only application that requires a .NET runtime), Graphite is +supported in LibreOffice (starting with OpenOffice.org version 3.2), Mozilla Firefox (starting with +version 11), and \XeTeX{} (starting with version 0.997). Graphite support is not +available in Microsoft Office. + +Note that it is currently not possible to add Graphite tables to OpenType-CFF fonts. +Therefore Graphite is only supported in the TrueType versions of fonts. Mostly +Graphite will be of interest to LibreOffice users, since LibreOffice does not provide +any interface to turn off and on OpenType features. + +\subsection{Graphite in LibreOffice} + +LibreOffice (and all OpenOffice.org derivatives starting with version 3.2) +automatically recognizes fonts which contain Graphite tables. +For such fonts Graphite rendering is enabled by default. +Correct positioning, attachment and substitutions will work automatically. +However, there is currently no graphical interface that can be used +to turn additional features on and off. Instead, a special extended font name +syntax has been developed: in order to activate an optional feature, its ID, +followed by an equals sign and the ID of the desired setting, are appended +directly to the font name string. An ampersand is used to separate +different feature/settings pairs. + +For example, the following “font” should be used in order to get +alternative glyphs for U+1F545 Symbol for Marks Chapter: + +\begin{verbatim} +Ponomar Unicode TT:mark=1 +\end{verbatim} + +\noindent for the first alternate glyph, \texttt{mark=2} for the second alternate +glyph, and so forth. + +Of course modifying the font name directly is very inconvenient, since +it is difficult to remember short tags and numerical values used for +feature/setting IDs in different fonts. You may try to +install the \href{https://github.com/thanlwinsoft/groooext} +{Graphite Font Extension}, which provides a dialog for easier feature selection. +However, this extension has not been maintained since the passing of its +developer in 2011, and so may not work correctly in later versions of LibreOffice. +If you experience problems with Graphite features, you may get better +results accessing glyphs directly by codepoint from the Private Use Area, +though this is not recommended. + +\subsection{Graphite in \XeTeX} + +Graphite support is available in \XeTeX, which means Graphite +features are now accessible from \TeX{} documents. Moreover, it is possible +to enable the Graphite font renderer with the \texttt{fontspec} package, +which greatly simplifies selecting system-installed fonts in \XeTeX{} and \LuaTeX. +This functionality requires at least \TeX{} Live 2010 or Mik\TeX 2.9. + +You can activate the Graphite rendering mode for a particular font via the +the \texttt{Renderer} option (its value should be set to \texttt{Graphite}) +in the argument list of a font selection command. Since there are no standard +feature tags in Graphite, the feature identifiers and their settings are +passed to the \texttt{RawFeature} option as follows: + +\begin{verbatim} +\newfontfamily{\graphA} + [Renderer=Graphite, RawFeature= + {Symbol for Mark's Chapter=Alternative 1}] +{Ponomar Unicode TT} +\end{verbatim} + +\noindent Please consult the \texttt{fontspec} documentation for more information. + +\section{Ponomar Unicode} + +Ponomar Unicode is a font that reproduces the typeface of Synodal Church Slavonic +editions from the beginning of the 20th Century. It is intended for working with +modern Church Slavonic texts (Synodal Slavonic). Ponomar Unicode is based on +the Hirmos UCS font designed by Vlad Dorosh, but has been modified by the authors +of this package. Examples of text set in Ponomar Unicode are presented below. + +%\lineskip=0pt +%\lineskiplimit=-5em + +\subsection{Synodal Church Slavonic} + +\begin{churchslavonic} +{\slv \large +Бл҃же́нъ мꙋ́жъ, и҆́же не и҆́де на совѣ́тъ нечести́выхъ, и҆ на пꙋтѝ грѣ́шныхъ не ста̀, и҆ на сѣда́лищи гꙋби́телей не сѣ́де: но въ зако́нѣ гдⷭ҇ни во́лѧ є҆гѡ̀, и҆ въ зако́нѣ є҆гѡ̀ поꙋчи́тсѧ де́нь и҆ но́щь. И҆ бꙋ́детъ ꙗ҆́кѡ дре́во насажде́ное при и҆схо́дищихъ во́дъ, є҆́же пло́дъ сво́й да́стъ во вре́мѧ своѐ, и҆ ли́стъ є҆гѡ̀ не ѿпаде́тъ: и҆ всѧ̑, є҆ли̑ка а҆́ще твори́тъ, ᲂу҆спѣ́етъ. Не та́кѡ нечести́вїи, не та́кѡ: но ꙗ҆́кѡ пра́хъ, є҆го́же возмета́етъ вѣ́тръ ѿ лица̀ землѝ. Сегѡ̀ ра́ди не воскре́снꙋтъ нечести́вїи на сꙋ́дъ, нижѐ грѣ̑шницы въ совѣ́тъ првⷣныхъ. Ꙗ҆́кѡ вѣ́сть гдⷭ҇ь пꙋ́ть првⷣныхъ, и҆ пꙋ́ть нечести́выхъ поги́бнетъ. +} +\end{churchslavonic} + +\subsection{Kievan Church Slavonic} + +Kievan Church Slavonic uses a number of variant glyph forms, such as U+1C81 Long-Legged De ({\slv ᲁ}) and U+A641 Variant Ze ({\slv ꙁ}): + +\begin{churchslavonic} +{\slv \large +Бл҃же́нъ мꙋ́жъ, и҆́же не и҆́ᲁе на совѣ́тъ нечести́выхъ, и҆ на пꙋтѝ грѣ́шныхъ не ста̀, и҆ на сѣᲁа́лищи гꙋби́телей не сѣ́ᲁе: но въ зако́нѣ гᲁⷭ҇ни во́лѧ є҆гѡ̀, и҆ въ зако́нѣ є҆гѡ̀ поꙋчи́тсѧ де́нь и҆ но́щь. И҆ бꙋ́ᲁетъ ꙗ҆́кѡ дре́во насажᲁе́ное при и҆схо́ᲁищихъ во́ᲁъ, є҆́же плоᲁъ сво́й да́стъ во вре́мѧ своѐ, и҆ ли́стъ є҆гѡ̀ не ѿпаᲁе́тъ: и҆ всѧ̑, є҆ли̑ка а҆́ще твори́тъ, ᲂу҆спѣ́етъ. Не та́кѡ нечести́вїи, не та́кѡ: но ꙗ҆́кѡ пра́хъ, є҆го́же воꙁмета́етъ вѣ́тръ ѿ лица̀ землѝ. Сегѡ̀ ра́ᲁи не воскре́снꙋтъ нечести́вїи на сꙋ́ᲁъ, нижѐ грѣ̑шницы въ совѣ́тъ првⷣныхъ. Ꙗ҆́кѡ вѣ́сть гᲁⷭ҇ь пꙋ́ть првⷣныхъ, и҆ пꙋ́ть нечести́выхъ поги́бнетъ. +} +\end{churchslavonic} + +\subsection{Other Languages} + +The Ponomar Unicode font may also be used to typeset liturgical texts in other languages that use the ecclesiastic Cyrillic alphabet. Three such examples +are fully supported by the font: Romanian (Moldovan) in its Cyrillic alphabet, Aleut (Fox Island or Eastern dialect) in its Cyrillic alphabet, and Yakut (Sakha) as written in the alphabet created by Bishop Dionysius (Khitrov). + +\noindent Here is an example of the Lord's Prayer in Romanian (Moldovan) Cyrillic: \\ + +\begin{churchslavonic} +{\slv \large +Та́тъль но́стрꙋ ка́реле є҆́щй ꙟ҆ Че́рюрй: ᲃ︀фн҃цѣ́скъсе Нꙋ́меле тъ́ꙋ: ві́е ꙟ҆пъръці́ѧ та̀: фі́е во́ѧ та̀, прекꙋ́мь ꙟ҆ Че́рю̆ шѝ пре пъмѫ́нть. Пѫ́йнѣ но́астръ чѣ̀ ᲁепꙋ́рꙋрѣ ᲁъ́не но́аѡ а҆́стъꙁй. Шѝ не ꙗ҆́ртъ но́аѡ греша́леле но́астре, прекꙋ́мь шѝ но́й є҆ртъ́мь греши́цилѡрь но́щри. Ши́ нꙋ́не ᲁꙋ́че пре но́й ꙟ҆ и҆спи́тъ. Чѝ не и҆ꙁбъвѣ́ще ᲁе че́ль ръ́ꙋ. +} \\ +\end{churchslavonic} + +\noindent And here is an example of the Lord's Prayer in Aleut Cyrillic: \\ + +\begin{churchslavonic} +{\slv \large +Тꙋмани́нъ А́даԟъ! А҆́манъ акꙋ́х̑тхинъ и́нинъ кꙋ́ҥинъ, А́са́нъ амчꙋг̑а́сѧ́да́г̑та, Аҥали́нъ а҆ԟа́г̑та, Анꙋхтана́тхинъ малга́г̑танъ и́нимъ кꙋ́ганъ ка́юхъ та́намъ кꙋ́ганъ. Ԟалга́дамъ анꙋхтана̀ ҥи̑нъ аԟача́ ꙋ̆а҆ѧ́мъ: ка́юхъ тꙋма́нинъ а́д̑ꙋнъ ҥи̑нъ игни́да, а҆ма́кꙋнъ тꙋ́манъ ка́юхъ малгалиги́нъ ҥи̑нъ ад̑ꙋг̑и́нанъ игнида́кꙋнъ: ка́юхъ тꙋ́манъ сꙋглатачх̑и́г̑анах̑тхинъ, та́г̑а ад̑алю́дамъ илѧ́нъ тꙋ́манъ аг̑г̑ича. +} \\ +\end{churchslavonic} + +\noindent And here is an example of the Lord's Prayer in Yakut (Sakha): \\ + +\begin{churchslavonic} +{\slv \large +Халланнаръ юрдюлѧригѧрь баръ агабытъ бисенѧ ! Свѧтейдѧннинь а̄тыҥъ эенѧ ; кѧллинь царстваҥъ эенѧ ; сирь юрдюгѧрь кёҥюлюҥь эенѧ , халланъ юрдюгѧрь курдукъ боллунъ ; бюгюҥю кюннѧги асыръ аспытынъ бисенинь кулу бисеха бюгюнь ; бисиги да естѧрбитинь халларъ бисеха , хайтахъ бисиги да халларабытъ беэбить естѧхтѧрбитигѧрь ; килѧримѧ да бисигини альԫархайга ; хата быса бисигини албынтанъ . +} \\ +\end{churchslavonic} + +\noindent Here is an example using the Typicon symbols from Nikita Syrnikov's book {\slv Клю́чъ къ церко́вномꙋ ᲂу҆ста́вꙋ}: + +\begin{churchslavonic} +{\slv \large +і\textcolor{red}{і}꙼̇ ⧟̇҃ іѡа́ннꙋ і̲꙼ на лиⷮ бл҃жеⷩ҇, па́влꙋ пѣⷭ҇ г҃. а і҆оа́ннꙋ ѕ҃. + +и᷷͏҃і і\textcolor{red}{і}꙼̇ ⧟̲̇҃ кири́лꙋ і̲꙼ коⷣ и҆ и҆́коⷭ҇ о҆́бщїй и҆ коⷣ а҆фана́сїю. + +д҃ 🤉 іі̲ и҆си́дорꙋ ⹇ гео́ргїю кири́лѣ ⹉ + +} +\end{churchslavonic} + +\subsection{Font Features} + +Ponomar Unicode places some characters in the Private Use Area (PUA). +For the general PUA mappings, please see the +\href{http://www.ponomar.net/files/pua_policy.pdf}{PUA Allocation Policy}. + +In addition to the general PUA mappings, some characters have been +allocated the open range section of the PUA. These are: + +\begin{itemize} +\item U+F400 \textendash{} Alternatives of SMP glyphs: This section contains copies in the BMP of SMP glyphs for support in legacy applications. Currently, the following are available: U+F400 - U+F405 \textendash{} Typicon symbols (copies of U+1F540 through U+1F545) +\item U+F410 \textendash{} Presentation forms: Contains various presentation forms and ligatures used internally by the font. Generally, these are not intended to be called by users or external applications. +\item U+F420 \textendash{} Linguistic alternatives: Contains alternative shapes of glyphs that are language specific. Right now, these are modern punctuation shapes for use with Latin characters. These are not intended to be called externally. +\item U+F441 and on \textendash{} stylistic alternatives of Latin characters (Blackletter forms). These can be called via the Stylistic Set 2, but, if necessary, they may be called from the PUA directly. They are mapped to in the same order as in the Basic Latin block, beginning with U+F441 (for U+0041 Latin Capital Letter A). In addition to the Basic Latin repertoire, we also have: U+F4DE \textendash{} Blackletter Thorn; U+F4FE \textendash{} Lowercase Blackletter Thorn; and U+F575 \textendash{} Blackletter Long S +\end{itemize} + +The font provides a number of ligatures, which are made by inserting the Zero Width Joiner (U+200D) between two characters. A list of ligatures is provided in Table~\ref{ligs1}. + +\begin{table}[htbp] +\centering +\caption{Ligatures available in Ponomar Unicode \label{ligs1}} +\begin{tabular}{lcc} +Name & Sequence & Appearance \\ +\hline +Ligature A-U & U+0430 U+200D U+0443 & {\slv{\large ау}} \\ +Ligature El-U & U+043B U+200D U+0443 & {\slv{\large лу}} \\ +Ligature Te-Ve & U+0442 U+200D U+0432 & {\slv{\large тв}} \\ +\hline +\end{tabular} +\end{table} + +\noindent In OpenType, a number of Stylistic Alternatives are defined. They are listed in Table~\ref{salt1}. +In addition to additional decorative glyphs for the Symbol for Mark's Chapter, +the feature provides the alternate forms of the letter U+0423 U that look +exactly like U+A64A Uk (this usage is found in some publications), +and an alternative form for the U+0404 Wide Ye for use in contexts +where it needs to be distinguished from U+0415 Ye (mostly in Ukrainian text +stylized in a Church Slavonic font). + +\newfontfamily{\salt}[Alternate=0]{Ponomar Unicode} +\newfontfamily{\salta}[Alternate=1]{Ponomar Unicode} +\newfontfamily{\saltb}[Alternate=2]{Ponomar Unicode} +\newfontfamily{\saltc}[Alternate=3]{Ponomar Unicode} +\newfontfamily{\saltd}[Alternate=4]{Ponomar Unicode} +\newfontfamily{\salte}[Alternate=5]{Ponomar Unicode} +\newfontfamily{\saltf}[Alternate=6]{Ponomar Unicode} +\newfontfamily{\saltg}[Alternate=7]{Ponomar Unicode} + +\begin{table}[htbp] +\centering +\caption{Stylistic Alternatives in Ponomar Unicode \label{salt1}} +\begin{tabular}{lccccc} + & Base Form & \multicolumn{4}{c}{Alternate Forms} \\ +\hline +U+1F545 & {\slv{\large 🕅 }} & {\salt\large 🕅} & {\salta\large 🕅} & {\saltb\large 🕅} & {\saltc\large 🕅} \\ + & & {\saltd\large 🕅} & {\salte\large 🕅} & {\saltf\large 🕅} & {\saltg\large 🕅} \\ +U+0423 & {\slv\large У} & {\salt\large У} \\ +U+040E & {\slv\large Ў} & {\salt\large Ў} \\ +U+0404 & {\slv\large Є} & {\salt\large Є} \\ +\hline +\end{tabular} +\end{table} + +For the Cyrillic letters, the stylistic alternatives feature also allows access +to truncated letter forms; the order of the alternate forms is always: lower truncation, +upper truncation, left truncation, right truncation. Table~\ref{trunc} demonstrates +which truncated forms are available. Generally speaking, truncation should +be handled automatically by desktop publishing software and \TeX{}, though +this is difficult to accomplish. + +\begin{table}[htbp] +\centering +\caption{Truncated Forms Accessible via Stylistic Alternatives Feature +in Ponomar Unicode \label{trunc}} +\begin{tabular}{lccccc} + & Base Form & \multicolumn{4}{c}{Truncated Forms} \\ +\hline +U+0440 & {\slv{\large р }} & {\salt\large р} & \\ +U+0443 & {\slv{\large у }} & {\salt\large у} & \\ +U+0444 & {\slv{\large ф }} & {\salt\large ф} & {\salta\large ф} \\ +U+0445 & {\slv{\large х}} & {\salt\large х} & {\salta\large х} & {\saltb\large х} \\ +U+0446 & {\slv{\large ц }} & {\salt\large ц} & \\ +U+0449 & {\slv{\large щ }} & {\salt\large щ} & \\ +U+0471 & {\slv{\large ѱ }} & {\salt\large ѱ} & {\salta\large ѱ}\\ +U+A641 & {\slv{\large ꙁ }} & {\salt\large ꙁ} & \\ +U+A64B & {\slv{\large ꙋ }} & {\salt\large ꙋ} & {\salta\large ꙋ} & {\saltb\large ꙋ} \\ +\hline +\end{tabular} +\end{table} + +\noindent There is also defined Stylistic Set 2 (``ss02''), Blackletter forms. +When this stylistic set is turned on, +Latin letters appear in blackletter as opposed to their modern forms. +This is useful for setting Latin text side-by-side with Slavonic in +some contexts. See the following example: + +\newfontfamily{\blackletter}[StylisticSet=2]{Ponomar Unicode} + +\begin{figure}[h] +\centering +\begin{tabular}{ll} +Regular & +{\slv \large The quick brown fox. 1234567890. А҆ сїѐ по слове́нски. } \\ +Blackletter & +{\blackletter \large The quick brown fox. 1234567890. А҆ сїѐ по слове́нски. } \\ +\end{tabular} +\end{figure} + +\noindent Note that as of version 2.0 of the font, the ASCII digits (commonly called +``Arabic numerals'') are provided in roman form. Use Stylistic Set 2 to access +the blackletter forms, if necessary. + +\subsection{SIL Graphite Features} + +\newfontfamily{\graph}[Renderer=Graphite]{Ponomar Unicode TT} + +The SIL Graphite features in the font provide the same functionality +as the OpenType features. This is mostly of interest to users of +LibreOffice, which lacks support for stylistic alternatives and +stylistic sets but can access Graphite features (see above). + +The ``Symbol for Mark's Chapter'' (``mark'') feature provides alternatives +for the U+1F545 Symbol for Marks Chapter, much like the salt feature in OpenType. +The following values produce the results given in Table~\ref{ponograph}. + +\newfontfamily{\graphA}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 1}]{Ponomar Unicode TT} +\newfontfamily{\graphB}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 2}]{Ponomar Unicode TT} +\newfontfamily{\graphC}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 3}]{Ponomar Unicode TT} +\newfontfamily{\graphD}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 4}]{Ponomar Unicode TT} +\newfontfamily{\graphE}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 5}]{Ponomar Unicode TT} +\newfontfamily{\graphF}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 6}]{Ponomar Unicode TT} +\newfontfamily{\graphG}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 7}]{Ponomar Unicode TT} +\newfontfamily{\graphH}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 8}]{Ponomar Unicode TT} + +\begin{table}[htbp] +\centering +\caption{Values of the Symbol for Mark's Chapter (``mark'') Feature in Ponomar Unicode \label{ponograph}} +\begin{tabular}{lcccc} +\hline + & Base form & Alternative 1 & Alternative 2 & Alternative 3 \\ +U+1F545 & {\graph{\large 🕅 }} & {\graphA{\large 🕅}} & {\graphB{\large 🕅}} & {\graphC{\large 🕅}} \\ +& Alternative 4 & Alternative 5 & Alternative 6 & Alternative 7 \\ +& {\graphD{\large 🕅}} & {\graphE{\large 🕅}} & {\graphF{\large 🕅}} & {\graphG{\large 🕅}} \\ + & Alternative 8 \\ +& {\graphH{\large 🕅}} \\ +\hline +\end{tabular} +\end{table} + +\noindent The following additional Graphite features are provided (with +the exception of the ``hyph'' feature, they duplicate the functionality +of OpenType features): + +\begin{itemize} +\item The ``Truncation'' feature (``trnc'') provides the same functionality +as stylistic alternatives (for truncation) above. The possible values are: +\verb+1+ (lower truncation), \verb+2+ (upper truncation), +\verb+3+ (left truncation) and \verb+4+ (right truncation). + +\item The ``Use blackletter characters for Latin'' feature (``blck'') +provides the same functionality as Stylistic Set 2 in OpenType (see above). +Possible values are |0| (no) and |1| (yes). + +\item The ``Use alternative form of U'' feature (``altu'') +provides the alternative forms of the letter U+0423 U that look +exactly like U+A64A Uk. Possible values are |0| (no) and |1| (yes). + +\item The ``Cyrillic i has dot'' feature (``doti'') +provides a localized form of U+0456 Cyrillic I for use in Ukrainian +text. Possible values are |0| (no) and |1| (yes). + +\item The ``Use underscore for hyphenation'' feature (``hyph'') +replaces all instances of U+002D Hyphen-Minus and U+2010 Hyphen +with U+005F Low Line (underscore) for use as a hyphenation +character. This is meant as a workaround to +\href{https://bugs.documentfoundation.org/show_bug.cgi?id=85731} +{LibreOffice Bug 85731}, which does not allow you to specify +the hyphenation character in LibreOffice. +Possible values are |0| (no) and |1| (yes). Please note that this +feature will be deprecated once the necessary functionality is +added to LibreOffice. +\end{itemize} + +\section{Fedorovsk Unicode} + +Fedorovsk Unicode is based on the Fedorovsk font designed by Nikita Simmons. +It has been re-encoded for Unicode, with added OpenType and Graphite features +by Aleksandr Andreev. The Fedorovsk typeface is supposed to reproduce the typeface +of the printed editions of Ivan Fedorov produced in Moscow, for example, the +Apostol of 1564. The font is intended primarily for typesetting pre-Nikonian (Old Rite) +liturgical texts or for working with such texts in an academic context. + +\subsection{Sample Texts} +\newfontfamily{\right}[StylisticSet=1]{Fedorovsk Unicode} + +\subsubsection{Apostol of Ivan Fedorov} + +\begin{churchslavonic} +{\Large \right +\textcolor{red}{П}е́рвᲂе ᲂу҆́бо︀ сло́во︀ сᲂтвᲂри́хъ о҆ всѣ́хъ , ѽ , ѳео҆́филе , о҆ ниⷯже начѧ́тъ і︮с︯ , твᲂри́тиже и҆ ᲂу҆чи́ти . д︀о︀ него́же дн҃е , запᲂвѣ́д︀авъ а҆пⷭ҇лᲂмъ дх҃ᲂмъ ст҃ыⷨ , и҆́хже и҆ꙁбра̀ вᲂзнесе́сѧ . преⷣ ни́миже и҆ пᲂста́ви себѐ жи́ва по страд︀а́нїи свᲂе҆́мъ . во︀ мно́зехъ и҆́стинныхъ зна́менїи҆хъ . дн҃ьми четы́ридесѧтьми ꙗ҆влѧ́ꙗсѧ и҆́мъ и҆ гл҃ѧ ꙗ҆́же о҆ црⷭ҇твїи бж҃їи . сни́миже и҆ ꙗ҆д︀ы̀ , пᲂвелѣва́ше и҆́мъ ѿ і҆е҆рᲂсали́ма не ѿлꙋча́тисѧ . но̑ жда́ти о҆бѣтᲂва́нїе ѿч︮е︯е , е҆́же слы́шасте ѿ́ менѐ . ꙗ҆́кѡ і҆ѡ҃а́ннъ ᲂу҆́бо︀ крⷭ҇ти́лъ е҆́сть вᲂдо́ю . вы́же и҆́мате крести́тисѧ дх҃ᲂмъ ст҃ы́мъ , не по мно́ꙁѣхъ си́хъ д︀︮н︯еⷯ . +} +\end{churchslavonic} + +\subsubsection{Flowery Triodion} +\newfontfamily{\left}[StylisticSet=2]{Fedorovsk Unicode} + +\begin{churchslavonic} +{\Large \left +\textcolor{red}{стⷯры па́сцѣ . гла́съ , є҃ .} Д\textcolor{red}{а вᲂскрⷭ҇нетъ бг҃ъ ,꙳ и҆ разы́дꙋтсѧ вразѝ є҆гѡ̀ .} +Па́сха сщ҃е́ннаѧ на́мъ дне́сь пᲂказа́сѧ , па́сха но́ва ст҃а́ѧ , па́сха таи́нственнаѧ , па́сха всечестна́ѧ , па́сха хрⷭ҇та̀ и҆зба́вителѧ , па́сха непᲂро́чнаѧ , па́сха вели́каѧ , па́сха вѣ́рнымъ , па́сха двѣ́ри ра́йскїѧ на́мъ ѿверза́ющаѧ , па́сха всѣ́хъ ѡ҆сщ҃а́ющаѧ вѣ́рныхъ . +} +\end{churchslavonic} + +\subsection{OpenType Features} + +The font provides a number of ligatures, which are made by inserting the Zero Width Joiner (U+200D) between two characters. A list of ligatures is provided in Table~\ref{ligs2}. + +\begin{table}[htbp] +\centering +\caption{Ligatures available in Fedorovsk Unicode \label{ligs2}} +\begin{tabular}{lcc} +Name & Sequence & Appearance \\ +\hline +Ligature A-U & U+0430 U+200D U+0443 & {\left{\large ау}} \\ +Ligature El-U & U+043B U+200D U+0443 & {\left{\large лу}} \\ +Ligature A-Izhitsa & U+0430 U+200D U+0475 & {\left{\large аѵ}} \\ +Ligature El-Izhitsa & U+043B U+200D U+075 & {\left{\large лѵ}} \\ +Ligature Te-Ve & U+0442 U+200D U+0432 & {\left{\large тв}} \\ +Ligature Er-Yat & U+0440 U+200D U+0463 & {\left{\large рѣ}} \\ +\hline +\end{tabular} +\end{table} + +\noindent In OpenType, a number of Stylistic Alternatives are defined. +They are listed in Table~\ref{salt2}. In addition to providing alternative +glyph shapes for U+1F545 Symbol for Mark's Chapter, they allow you +to control the positioning of diacritical marks over certain letters. + +\newfontfamily{\glyphfont}{Fedorovsk Unicode} +\newfontfamily{\salt}[Alternate=0]{Fedorovsk Unicode} +\newfontfamily{\salta}[Alternate=1]{Fedorovsk Unicode} +\newfontfamily{\saltb}[Alternate=2]{Fedorovsk Unicode} +\newfontfamily{\saltc}[Alternate=3]{Fedorovsk Unicode} +\newfontfamily{\saltd}[Alternate=4]{Fedorovsk Unicode} +\newfontfamily{\salte}[Alternate=5]{Fedorovsk Unicode} +\newfontfamily{\saltf}[Alternate=6]{Fedorovsk Unicode} + +\begin{table}[htbp] +\centering +\caption{Stylistic Alternatives in Fedorovsk Unicode \label{salt2}} +\begin{tabular}{lcccccccc} + & Base Form & \multicolumn{7}{c}{Alternate Forms} \\ +\hline +U+0404 & {\glyphfont{\large Є}} & {\salt\large Є} \\ +U+0426 & {\glyphfont{\large Ц}} & {\salt\large Ц} \\ +U+0491 & {\glyphfont{\large ґ}} & {\salt\large ґ} \\ +U+A64C & {\glyphfont{\large Ꙍ}} & {\salt\large Ꙍ} \\ +U+047C & {\glyphfont{\large Ѽ}} & {\salt\large Ѽ} \\ +U+047E & {\glyphfont{\large Ѿ}} & {\salt\large Ѿ} \\ +U+047F & {\glyphfont{\large ѿ}} & {\salt\large ѿ} \\ +U+1F545 & {\glyphfont{\large 🕅 }} & {\salt\large 🕅} & {\salta\large 🕅} & {\saltb\large 🕅} & {\saltc\large 🕅} & {\saltd\large 🕅} & {\salte\large 🕅} & {\saltf\large 🕅} \\ +U+0463 U+0486 & {\glyphfont{\large ѣ҆}} & {\salt\large ѣ҆} \\ +U+0463 U+0300 & {\glyphfont{\large ѣ̀}} & {\salt\large ѣ̀} & {\salta\large ѣ̀} \\ +U+0463 U+0301 & {\glyphfont{\large ѣ́}} & {\salt\large ѣ́} & {\salta\large ѣ́} \\ +U+0463 U+0311 & {\glyphfont{\large ѣ̑}} & {\salt\large ѣ̑} & {\salta\large ѣ̑} \\ +U+0463 U+0486 U+0301 & {\glyphfont{\large ѣ҆́}} & {\salt\large ѣ҆́} \\ +U+A64B U+0486 & {\glyphfont{\large ꙋ҆}} & {\salt\large ꙋ҆} \\ +U+A64B U+0300 & {\glyphfont{\large ꙋ̀}} & {\salt\large ꙋ̀} & {\salta\large ꙋ̀} \\ +U+A64B U+0301 & {\glyphfont{\large ꙋ́}} & {\salt\large ꙋ́} & {\salta\large ꙋ́} \\ +U+A64B U+0311 & {\glyphfont{\large ꙋ̑}} & {\salt\large ꙋ̑} & {\salta\large ꙋ̑} & {\saltb\large ꙋ̑} \\ +U+A64B U+0486 U+0301 & {\glyphfont{\large ꙋ҆́}} & {\salt\large ꙋ҆́} \\ +\hline +\end{tabular} +\end{table} + +Additionally, three stylistic sets have been defined in the font. +Stylistic set 1 (``Right-side accents'') positions the accents over the Yat +and the Uk on the right side and Stylistic set 2 (``Left-side accents'') +positions the accents over the Yat and the Uk on the left side. +These stylistic sets are useful when a text uses one of +these positionings throughout. Stylistic set 10 (``Equal Baseline Variants'') +sets the capital letters on the same baseline as the +lowercase letters (useful for working with the font +in an academic context where the traditionally lowered +baseline of uppercase letters can cause vertical spacing +issues when working with text that is both in Latin and +Cyrillic scripts). Here is an example: + +\newfontfamily{\base}[StylisticSet=10]{Fedorovsk Unicode} + +\begin{figure}[h] +\centering +\begin{tabular}{ll} +{\large \glyphfont Хрⷭ҇то́съ вᲂскр҃се и҆з̾ ме́ртвыхъ} & (regular text) \\ +{\large \base Хрⷭ҇то́съ вᲂскр҃се и҆з̾ ме́ртвыхъ} & (Stylistic Set 10 enabled) \\ +\end{tabular} +\end{figure} + +\subsection{Graphite Features} + +The stylistic alternatives of the Mark's Chapter symbol, +the Letter Ge with Upturn, and the letters Ye, Tse, +and Omega have been duplicated as Graphite features in +the TTF version of the font, with names ``Symbol for Mark's Chapter'', +``Ye'', ``Tse'', ``Ghe'', and ``Omega'' respectively. +For the alternatives of the Mark's Chapter symbol, the values of the +property are assigned to correspond with the +\href{http://www.ponomar.net/files/pua_policy.pdf} +{Private Use Area Allocation Policy} and other fonts. The Graphite +features are demonstrated in Table~\ref{fedorgraph}. + +\newfontfamily{\graph}[Renderer=Graphite]{Fedorovsk Unicode TT} +\newfontfamily{\graphA}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 1}]{Fedorovsk Unicode TT} +\newfontfamily{\graphB}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 2}]{Fedorovsk Unicode TT} +\newfontfamily{\graphC}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 3}]{Fedorovsk Unicode TT} +\newfontfamily{\graphD}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 4}]{Fedorovsk Unicode TT} +\newfontfamily{\graphE}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 7}]{Fedorovsk Unicode TT} +\newfontfamily{\graphF}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 8}]{Fedorovsk Unicode TT} +\newfontfamily{\graphG}[Renderer=Graphite, RawFeature={Symbol for Mark's Chapter=Alternative 9}]{Fedorovsk Unicode TT} +\newfontfamily{\graphYe}[Renderer=Graphite, RawFeature={Ye=Alternative 1}]{Fedorovsk Unicode TT} +\newfontfamily{\graphTse}[Renderer=Graphite, RawFeature={Tse=Alternative 1}]{Fedorovsk Unicode TT} +\newfontfamily{\graphGhe}[Renderer=Graphite, RawFeature={Ghe=Alternative 1}]{Fedorovsk Unicode TT} +\newfontfamily{\graphOmega}[Renderer=Graphite, RawFeature={Omeg=Alternative 1}]{Fedorovsk Unicode TT} +\newfontfamily{\graphOt}[Renderer=Graphite, RawFeature={Ot=Alternative 1}]{Fedorovsk Unicode TT} + +\begin{table}[htbp] +\centering +\caption{Alternatives via Graphite Features in Fedorovsk Unicode \label{fedorgraph}} +\begin{tabular}{lcccc} +\hline + & Base form & Alternative 1 & Alternative 2 & Alternative 3 \\ +U+0404 & {\graph{\large Є }} & {\graphYe\large Є} \\ +U+0426 & {\graph{\large Ц}} & {\graphTse\large Ц} \\ +U+0491 & {\graph{\large ґ}} & {\graphGhe\large ґ} \\ +U+A64C & {\graph{\large Ꙍ}} & {\graphOmega\large Ꙍ} \\ +U+047C & {\graph{\large Ѽ}} & {\graphOmega\large Ѽ} \\ +U+047E & {\graph{\large Ѿ}} & {\graphOt\large Ѿ} \\ +U+047F & {\graph{\large ѿ}} & {\graphOt\large ѿ} \\ +U+1F545 & {\graph{\large 🕅 }} & {\graphA{\large 🕅}} & {\graphB{\large 🕅}} & {\graphC{\large 🕅}} \\ + & & Alternative 4 & Alternative 7 & Alternative 8 \\ + & & {\graphD{\large 🕅}} & {\graphE{\large 🕅}} & {\graphF{\large 🕅}} \\ + & & Alternative 9 \\ + & & {\graphG{\large 🕅}} \\ +\hline +\end{tabular} +\end{table} + +\noindent Two additional Graphite features are defined: ``Accent Positions'', +with values ``left'' and ``right'', which mimics the behavior +of stylistic sets 1 and 2; and ``Equal Baseline'' (with value ``yes''), +which mimics the behavior of Stylistic Set 10. + +\section{Menaion Unicode} + +The Menaion typeface is supposed to be used for working with text +of Ustav-era manuscripts. It contains the full repertoire of necessary +Cyrillic and Glagolitic glyphs as well as glyphs of Byzantine Ecphonetic +notation of the kind used in Cyrillic or Glagolitic manuscripts. + +The Menaion font was originally designed by Victor A. Baranov at +\href{http://www.manuscripts.ru/}{the Manuscript Project}. It was +re-encoded for Unicode by Aleksandr Andreev with permission of the original author. + +\newfontfamily{\glyphfont}{Menaion Unicode} + +\subsection{Sample Texts} + +Samples of text in Menaion Unicode are presented in Figures~\ref{men1} +and \ref{men2}. Please note that combining Glagolitic letters +(Glagolitic Supplement) +will become available in Unicode 9.0. In Microsoft products, correct +glyph positioning for these characters using OpenType features is +currently not possible. To achieve the desired output, you will need +to use LibreOffice, \XeTeX{}, \LuaTeX{}, or advanced desktop +publishing software such as Adobe InDesign. + +\begin{figure}[htbp] +\centering +\caption{Cyrillic text from the Ostromir Gospels (11th century) \label{men1}} +\begin{tabular}{lr} + 1& {\Large \glyphfont Искони бѣ слово } \\ + 2& {\Large \glyphfont и слово бѣ отъ } \\ + 3& {\Large \glyphfont б҃а и б҃ъ бѣ} \\ + 4& {\Large \glyphfont слово 𝀏̃ се бѣ} \\ + 5& {\Large \glyphfont искони оу} \\ + 6& {\Large \glyphfont б҃а ⁘ и тѣмь в̇са бꙑ-} \\ + 7& {\Large \glyphfont шѧ 𝀏̃ и беꙁ него ни-} \\ + 8& {\Large \glyphfont чьтоже не бꙑсть ·} \\ + 9& {\Large \glyphfont ѥже бꙑсть 𝀏̃ въ то-} \\ +10& {\Large \glyphfont мь животъ бѣ · и} \\ + 1& {\Large \glyphfont животъ бѣ свѣтъ} \\ + 2& {\Large \glyphfont чловѣкомъ 𝀏̃ и свѣ-} \\ + 3& {\Large \glyphfont тъ въ тьмѣ свьти-} \\ + 4& {\Large \glyphfont тьсѧ · и тьма ѥго} \\ + 5& {\Large \glyphfont не обѧтъ 𝀏̃ бꙑсть} \\ + 6& {\Large \glyphfont члв҃къ посъланъ} \\ + 7& {\Large \glyphfont отъ б҃а · имѧ ѥмоу} \\ + 8& {\Large \glyphfont иоанъ 𝀏̃ тъ приде} \\ + 9& {\Large \glyphfont въ съвѣдѣтель-} \\ +10& {\Large \glyphfont ство · да съвѣдѣте-} \\ +2.2 1& {\Large \glyphfont льствоуѥть о свѣ-} \\ + 2& {\Large \glyphfont тѣ 𝀏̃ да вьси вѣрѫ} \\ + 3& {\Large \glyphfont имѫть имь ⁘ не бѣ} \\ + 4& {\Large \glyphfont тъ свѣтъ ⁘ нъ да} \\ + 5& {\Large \glyphfont съвѣдѣтельствоу-} \\ + 6& {\Large \glyphfont ѥть о свѣтѣ 𝀏̃̑ бѣ} \\ + 7& {\Large \glyphfont свѣтъ истиньнꙑ-} \\ + 8& {\Large \glyphfont и · иже просвѣщаѥ-} \\ + 9& {\Large \glyphfont ть в́сꙗкого чл҃ка ⸴} \\ +10& {\Large \glyphfont грѧдѫща въ миръ 𝀏̃̑} \\ +\end{tabular} +\end{figure} + +\begin{figure}[htbp] +\centering +\caption{Glagolitic text from Codex Assemanius (11th century) \label{men2}} +\begin{tabular}{lr} +1 & {\Large \glyphfont ⁘ ⰅⰂⰀ𞀌҇ ⰙⰕ҇ ⰋⰉ҇Ⱁ } \\ + 2 & {\Large \glyphfont Ⰻⱄⰽⱁⱀⰹ ⰱⱑ } \\ + 3 & {\Large \glyphfont ⱄⰾⱁⰲⱁ · } \\ + 4 & {\Large \glyphfont ⰻ ⱄⰾⱁⰲⱁ } \\ + 5 & {\Large \glyphfont ⰱⱑ ⱋ̔ ⰱⰰ · } \\ + 6 & {\Large \glyphfont ⰻ ⰱ͞ⱏ ⰱⱑ } \\ + 7 & {\Large \glyphfont ⱄⰾⱁⰲⱁ · } \\ + 8 & {\Large \glyphfont Ⱄⰵ ⰱⱑ ⰻ̔ⱄⰽⱁ- } \\ + 9 & {\Large \glyphfont ⱀⰻ · ⱋ̔ ⰱ꙯ⰰ · ⰲⱐ- } \\ +10 & {\Large \glyphfont ⱄⱑ ⱅⱑⰿⱏ ⰱⱏⰻ- } \\ +11 & {\Large \glyphfont ⱎⱔ · Ⰻ̔ ⰱⰵⰶ ⱀⰵⰳⱁ } \\ +12 & {\Large \glyphfont ⱀⰹⱍⰵⱄⱁⰶⰵ } \\ +13 & {\Large \glyphfont ⱀⰵ ⰱⱏⰻⱄⱅⱏ · ⰵ̔- } \\ +14 & {\Large \glyphfont ⰶⰵ ⰱⱏⱄⱅⱏ · } \\ +15 & {\Large \glyphfont Ⰲⱏ ⱅⱁⰿⱏ ⰶⰹⰲⱁ- } \\ +16 & {\Large \glyphfont ⱅⱏ ⰱⱑ · ⰻ ⰶⰹⰲⱁ- } \\ +17 & {\Large \glyphfont ⱅⱏ ⰱⱑ ⱄⰲⱑⱅⱏ } \\ +18 & {\Large \glyphfont ⱍⰾ҃ⰽⰿⱏ · ⰻ̔ ⱄⰲⱁⱑ } \\ +19 & {\Large \glyphfont ⰲⱏ ⱅⱐⰿⱑ ⱄⰲⱏ- } \\ +20 & {\Large \glyphfont ⱅⰹⱅⱏ ⱄⱔ · ⰻ ⱅⱐ- } \\ +21 & {\Large \glyphfont ⰿⰰ ⰵ̔ⰳⱁ ⱀⰵ ⱁ̔ⰱⱔⱅ } \\ +\end{tabular} +\end{figure} + +\subsection{Provided Ligatures} + +The font provides a number of ligatures, which are made +by inserting the Zero Width Joiner (U+200D) between two +characters. The list of ligatures is provided in Table~\ref{menligs}. +The ligatures may be processed using either OpenType or +SIL Graphite. + +\newfontfamily{\graph}[Renderer=Graphite]{Menaion Unicode TT} + +\begin{table}[htbp] +\centering +\caption{Ligatures available in the Menaion Unicode font \label{menligs}} +\begin{tabular}{lcc} +Name & Sequence & Appearance \\ +\hline +Small Ligature I-Ye & U+0438 U+200D U+0435 & {\glyphfont{\large ие }} \\ +Small Ligature En-I & U+043d U+200D U+0438 & {\graph{\large ни }} \\ +Small Ligature En-Small Yus & U+043d U+200D U+0467 & {\glyphfont{\large нѧ }} \\ +Small Ligature Es-Ve & U+0441 U+200D U+0432 & {\glyphfont{\large св }} \\ +Small Ligature Te-Er & U+0442 U+200D U+0440 & {\glyphfont{\large тр }} \\ +Capital Litagure A-U & U+0410 U+200D U+0423 & {\glyphfont{\large АУ }} \\ +Small Ligature A-U & U+0430 U+200D U+0443 & {\glyphfont{\large ау }} \\ +Small Ligature A-Te & U+0430 U+200D U+0442 & {\glyphfont{\large ат }} \\ +Capital Ligature I-Ye & U+0418 U+200D U+0415 & {\glyphfont{\large ИЕ }} \\ +Capital Ligature El-Ge & U+041b U+200D U+0413 & {\glyphfont{\large ЛГ }} \\ +Small Ligature El-Ge & U+043b U+200D U+0433 & {\glyphfont{\large лг }} \\ +Capital Ligature En-I & U+041d U+200D U+0418 & {\glyphfont{\large НИ }} \\ +Capital Ligature En-Small Yus & U+041d U+200D U+0466 & {\graph{\large НѦ }} \\ +Capital Ligature Es-Ve & U+0421 U+200D U+0412 & {\glyphfont{\large СВ }} \\ +Small Ligature Te-Yat & U+0442 U+200D U+0463 & {\glyphfont{\large тѣ }} \\ +Capital Ligature Te-Ve & U+0422 U+200D U+0412 & {\glyphfont{\large ТВ }} \\ +Small Ligature Te-Ve & U+0442 U+200D U+0432 & {\glyphfont{\large тв }} \\ +Capital Ligature Te-I & U+0422 U+200D U+0418 & {\glyphfont{\large ТИ }} \\ +Small Ligature Te-I & U+0442 U+200D U+0438 & {\glyphfont{\large ти }} \\ +Capital Ligature Te-Er & U+0422 U+200D U+0420 & {\glyphfont{\large ТР }} \\ +Ligature Capital A-Small Te & U+0410 U+200D U+0442 & {\glyphfont{\large Ат }} \\ +Capital Ligature Te-Soft Sign & U+0422 U+200D U+042c & {\glyphfont{\large ТЬ }} \\ +Small Ligature Te-Soft Sign & U+0442 U+200D U+044c & {\graph{\large ть }} \\ +Small Ligature Te-A & U+0442 U+200D U+0430 & {\glyphfont{\large та }} \\ +\hline +\end{tabular} +\end{table} + +\section{Pomorsky Unicode} + +The Pomorsky Unicode font is a close (idealized) +reproduction of the decorative calligraphic style of book and chapter titles, +which was most likely developed in the 1700's by the scribes of the Old Ritualist +Vyg River Hermitage (Выговская пустынь). +It is seen extensively in the chant manuscripts, liturgical manuscripts, +hagiographic and polemical works of the Pomortsy and Fedoseyevtsy communities, +and is a traditional and ``organic'' style of lettering lacking any obvious influence +from western European and Latin typography. +The Pomorsky typeface was originally designed by Nikita Simmons. +It was edited and re-encoded for Unicode by Aleksandr Andreev. +It is intended for use with +\emph{bukvitsi} (drop caps) and decorative titling. + +Several versions of many glyphs are provided in the font. +The ornate forms of the letters are default and provided at the uppercase +Cyrillic codepoints; they should be used as much as possible. +Simpler forms can be used whenever the letters need a less ornate appearance, +or when diacritics might conflict with the ornamentation +(or when the ornamentation of one character will conflict with +the ornamentation of another); these simple forms are available as +\verb+Stylistic Set 1+ or as the Graphite feature ``Use simple forms'' +(\verb+smpl+). There are a few additional characters that are stylistic +variants, which are provided as Stylistic Alternatives (\verb+salt+) +or as the Graphite feature ``Alternates'' (\verb+salt+). +Since the font is intended for drop caps and titling, lowercase +characters are not available. + +\newfontfamily{\glyphfont}{Pomorsky Unicode} +\newfontfamily{\simple}[StylisticSet=1]{Pomorsky Unicode} +\newfontfamily{\salt}[Alternate=0]{Pomorsky Unicode} +\newfontfamily{\salta}[Alternate=1]{Pomorsky Unicode} +\newfontfamily{\saltb}[Alternate=2]{Pomorsky Unicode} +\newfontfamily{\saltc}[Alternate=3]{Pomorsky Unicode} + +The base form, the ``simple'' form, and any stylistic alternatives of +a character are demonstrated in Table~\ref{pomor}. + +\begin{table}[htbp] +\centering +\caption{Character shapes provided by Pomorsky Unicode \label{pomor}} +{\fontsize{38pt}{1.5em} +\begin{tabular}{cccc} + {\glyphfont А}{\simple А}{\salt А} & {\glyphfont Б}{\simple Б} & {\glyphfont В}{\simple В} & {\glyphfont Г}{\simple Г} \\ + + {\glyphfont Е}{\simple Е} & {\glyphfont Ж}{\simple Ж} & {\glyphfont Ѕ}{\simple Ѕ} & {\glyphfont З}{\simple З} \\ + + {\glyphfont И}{\simple И} & {\glyphfont Й}{\simple Й} & {\glyphfont І}{\simple І} & {\glyphfont Ї}{\simple Ї} \\ + + {\glyphfont К}{\simple К}{\salt К} & {\glyphfont Л}{\simple Л} & {\glyphfont М}{\simple М} & {\glyphfont Н}{\simple Н} \\ + + {\glyphfont О}{\simple О} & {\glyphfont Ѻ}{\simple Ѻ} & {\glyphfont П}{\simple П} & {\glyphfont Р}{\simple Р}{\salt Р} \\ + + {\glyphfont С}{\simple С} & {\glyphfont Т}{\simple Т} & {\glyphfont ОУ}{\simple ОУ} & {\glyphfont Ꙋ}{\simple Ꙋ} \\ + + {\glyphfont Ф}{\simple Ф} & {\glyphfont Х}{\simple Х} & {\glyphfont Ѡ}{\simple Ѡ} & {\glyphfont Ѽ}{\simple Ѽ} \\ + + {\glyphfont Ѿ}{\simple Ѿ} & {\glyphfont Ц}{\simple Ц} & {\glyphfont Ч}{\simple Ч} & {\glyphfont Ш}{\simple Ш} \\ + + {\glyphfont Щ}{\simple Щ} & {\glyphfont Ъ}{\simple Ъ} & {\glyphfont Ы}{\simple Ы} & {\glyphfont Ь}{\simple Ь} \\ + + {\glyphfont Ѣ}{\simple Ѣ} & {\glyphfont Ю}{\simple Ю} & {\glyphfont Ꙗ}{\simple Ꙗ}{\salt Ꙗ} & {\glyphfont Ѧ}{\simple Ѧ} \\ + + {\glyphfont Ѯ}{\simple Ѯ} & {\glyphfont Ѱ}{\simple Ѱ} & {\glyphfont Ѳ}{\simple Ѳ} & {\glyphfont Ѵ}{\simple Ѵ} \\ +\end{tabular} +} +\end{table} + +\subsection{Sample Texts} + +\begin{center} +\begin{tabular}{c} +{\fontsize{48pt}{2em} \glyphfont ЧИ́НЪ ВЕЧЕ́РНИ.} \\ +{\fontsize{48pt}{2em} \simple ЧИ́НЪ ВЕЧЕ́РНИ.} \\ +{\fontsize{48pt}{2em} \glyphfont СѶНѠ́ДИКЪ.} \\ +{\fontsize{48pt}{2em} \simple СѶНѠ́ДИКЪ.} \\ +{\fontsize{48pt}{2em} \simple\salt СѶНѠ́ДИКЪ.} \\ +\end{tabular} +\end{center} + +\section{Known Issues} + +Here are some known issues: + +\begin{itemize} + +\item Kerning is not available for Latin characters in any of the fonts. +Since it is not expected for these fonts to be heavily used to typeset Latin +text, this issue is not a very high priority for resolution. + +\item Ponomar Unicode has Graphite-based kerning for Cyrillic +characters starting in version 2.0, but it is defective. In particular, +inserting a diacritical mark will break the kerning between two letters. +This will be fixed in version 2.1. + +\item Kerning is not available in the Graphite version of +Pomorsky Unicode. + +\end{itemize} + +\noindent There may be other issues, but before reporting such issues, +please check that your software properly supports OpenType and / or +SIL Graphite. We suggest checking for expected behavior in \XeTeX{} +or \LuaTeX{}. + +\section{Credits} + +The authors would like to thank the following people: + +\begin{itemize} + +\item Vladislav Dorosh, who allowed his +\href{http://irmologion.ru/fonts.html}{Hirmos} font to be re-encoded +in Unicode and modified, leading to the creation of the Ponomar font. + +\item Viktor Baranov of the \href{http://www.manuscripts.ru/}{Manuscripts} +project, who allowed the re-encoding and modification of his Menaion font. + +\item Michael Ivanovich for help in designing the characters for Sakha +(Yakut), partially taken from his Sakha UCS font. + +\item Alexey Kryukov, who answered various questions about FontForge +and whose extensive documentation for the +\href{https://github.com/akryukov/oldstand/}{Old Standard} font was +consulted and partially reused. + +\item Mike Kroutikov, who put together the \TeX{} package of the fonts. +\end{itemize} + + +%% PLACE SAMPLE AND CODECHARTS HERE + + +\end{document} + diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/opentype.png b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/opentype.png Binary files differnew file mode 100644 index 00000000000..ea138301406 --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/opentype.png diff --git a/Master/texmf-dist/doc/fonts/fonts-churchslavonic/truetype.png b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/truetype.png Binary files differnew file mode 100644 index 00000000000..e2540aeb1a3 --- /dev/null +++ b/Master/texmf-dist/doc/fonts/fonts-churchslavonic/truetype.png diff --git a/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/FedorovskUnicode.otf b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/FedorovskUnicode.otf Binary files differnew file mode 100644 index 00000000000..540effe6c09 --- /dev/null +++ b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/FedorovskUnicode.otf diff --git a/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/MenaionUnicode.otf b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/MenaionUnicode.otf Binary files differnew file mode 100644 index 00000000000..20b8249ad66 --- /dev/null +++ b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/MenaionUnicode.otf diff --git a/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/PomorskyUnicode.otf b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/PomorskyUnicode.otf Binary files differnew file mode 100644 index 00000000000..708763a3d0f --- /dev/null +++ b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/PomorskyUnicode.otf diff --git a/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/PonomarUnicode.otf b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/PonomarUnicode.otf Binary files differnew file mode 100644 index 00000000000..a4e7a2125fa --- /dev/null +++ b/Master/texmf-dist/fonts/opentype/public/fonts-churchslavonic/PonomarUnicode.otf diff --git a/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/FedorovskUnicode.ttf b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/FedorovskUnicode.ttf Binary files differnew file mode 100644 index 00000000000..2db6f5963b9 --- /dev/null +++ b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/FedorovskUnicode.ttf diff --git a/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/MenaionUnicode.ttf b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/MenaionUnicode.ttf Binary files differnew file mode 100644 index 00000000000..9789768ad38 --- /dev/null +++ b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/MenaionUnicode.ttf diff --git a/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/PomorskyUnicode.ttf b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/PomorskyUnicode.ttf Binary files differnew file mode 100644 index 00000000000..ea46c8d724a --- /dev/null +++ b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/PomorskyUnicode.ttf diff --git a/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/PonomarUnicode.ttf b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/PonomarUnicode.ttf Binary files differnew file mode 100644 index 00000000000..5c7e1a1b55a --- /dev/null +++ b/Master/texmf-dist/fonts/truetype/public/fonts-churchslavonic/PonomarUnicode.ttf diff --git a/Master/tlpkg/bin/tlpkg-ctan-check b/Master/tlpkg/bin/tlpkg-ctan-check index a7c994ef3e2..c64ecb82ea5 100755 --- a/Master/tlpkg/bin/tlpkg-ctan-check +++ b/Master/tlpkg/bin/tlpkg-ctan-check @@ -257,7 +257,7 @@ my @TLP_working = qw( foekfont foilhtml fonetika fontawesome font-change font-change-xetex fontaxes fontbook fontch fontinst fontmfizz fontools - fonts-tlwg fontspec fonttable fontwrap + fonts-churchslavonic fonts-tlwg fontspec fonttable fontwrap footbib footmisc footnotebackref footnotehyper footnoterange footnpag forarray foreign forest forloop formlett formation-latex-ul formular fouridx fourier fouriernc diff --git a/Master/tlpkg/libexec/ctan2tds b/Master/tlpkg/libexec/ctan2tds index 309c8cf6773..e970f30e811 100755 --- a/Master/tlpkg/libexec/ctan2tds +++ b/Master/tlpkg/libexec/ctan2tds @@ -433,6 +433,7 @@ chomp ($Build = `cd $Master/../Build/source && pwd`); 'fontinstallationguide', "die 'skipping, use Type1fonts'", 'fontname', "die 'skipping, done through tl-update-auto'", 'fontools', "&MAKEflatten", + 'fonts-churchslavonic', "&MAKEflatten", 'footnpag', "&MAKEfootnpag", 'formula', "die 'skipping, requires scripts, very old'", 'fourier', "&MAKEflatten", diff --git a/Master/tlpkg/tlpsrc/collection-fontsextra.tlpsrc b/Master/tlpkg/tlpsrc/collection-fontsextra.tlpsrc index 139ebf69eb9..9aac07b3a5a 100644 --- a/Master/tlpkg/tlpsrc/collection-fontsextra.tlpsrc +++ b/Master/tlpkg/tlpsrc/collection-fontsextra.tlpsrc @@ -114,6 +114,7 @@ depend foekfont depend fonetika depend fontawesome depend fontmfizz +depend fonts-churchslavonic depend old-arrows depend fourier depend fouriernc diff --git a/Master/tlpkg/tlpsrc/fonts-churchslavonic.tlpsrc b/Master/tlpkg/tlpsrc/fonts-churchslavonic.tlpsrc new file mode 100644 index 00000000000..e69de29bb2d --- /dev/null +++ b/Master/tlpkg/tlpsrc/fonts-churchslavonic.tlpsrc |
