https://wiki.tei-c.org/api.php?action=feedcontributions&feedformat=atom&user=MarcusTEIWiki - User contributions [en]2026-04-18T21:43:29ZUser contributionsMediaWiki 1.32.0https://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=16854Samples of TEI texts2021-07-12T17:14:06Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__<br />
The availability of texts enables others to learn by example; it fosters similar approaches to solving the same problems across the entire community of practice; and it gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Explicitly Pedagogical Samples ==<br />
<br />
* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]<br />
<br />
* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)<br />
<br />
* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)<br />
<br />
* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/BZA/bzaComCatWeb.html '''Shorter Saṃyukta Āgama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies 中國佛教傳記''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers 中國佛寺志''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* ''Four Early Chan Texts from Dunhuang - A TEI based Edition'' 早期禪宗文獻四部 —— 以TEI標記重訂敦煌寫卷：楞伽師資記，傳法寶紀，修心要論，觀心論. Densely marked-up texts from Dunhuang manuscripts, with special attention to Chinese character variants (異體字). [https://zenodo.org/record/1133490#.WkXojPYxUyc '''Texts, data, and documentation archived at Zenodo'''].<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)<br />
<br />
* The [http://sarit.indology.info SARIT] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.16 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.<br />
<br />
* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.<br />
<br />
* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup<br />
<br />
* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.<br />
<br />
* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].<br />
<br />
* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].<br />
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=16853Samples of TEI texts2021-07-12T14:14:12Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__<br />
The availability of texts enables others to learn by example; it fosters similar approaches to solving the same problems across the entire community of practice; and it gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Explicitly Pedagogical Samples ==<br />
<br />
* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]<br />
<br />
* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)<br />
<br />
* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)<br />
<br />
* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/BZA/bzaComCatWeb.html '''Shorter Saṃyukta Āgama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies 中國佛教傳記''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers 中國佛寺志''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* ''Four Early Chan Texts from Dunhuang - A TEI based Edition'' 早期禪宗文獻四部 —— 以TEI標記重訂敦煌寫卷：楞伽師資記，傳法寶紀，修心要論，觀心論. Densely marked-up Dunhuang manuscripts, with special attention to Chinese character variants (異體字). [https://zenodo.org/record/1133490#.WkXojPYxUyc '''Texts, data, and documentation archived at Zenodo'''].<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)<br />
<br />
* The [http://sarit.indology.info SARIT] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.16 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.<br />
<br />
* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.<br />
<br />
* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup<br />
<br />
* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.<br />
<br />
* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].<br />
<br />
* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].<br />
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=16852Samples of TEI texts2021-07-12T14:13:14Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__<br />
The availability of texts enables others to learn by example; it fosters similar approaches to solving the same problems across the entire community of practice; and it gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Explicitly Pedagogical Samples ==<br />
<br />
* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]<br />
<br />
* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)<br />
<br />
* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)<br />
<br />
* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/BZA/bzaComCatWeb.html '''Shorter Saṃyukta Āgama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies 中國佛教傳記''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers 中國佛寺志''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* ''Four Early Chan Texts from Dunhuang - A TEI based Edition''. Densely marked-up Dunhuang manuscripts, with special attention to Chinese character variants (異體字). [https://zenodo.org/record/1133490#.WkXojPYxUyc '''Texts, data, and documentation archived at Zenodo'''].<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)<br />
<br />
* The [http://sarit.indology.info SARIT] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.16 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.<br />
<br />
* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.<br />
<br />
* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup<br />
<br />
* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.<br />
<br />
* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].<br />
<br />
* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].<br />
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=16851Samples of TEI texts2021-07-12T14:12:28Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__<br />
The availability of texts enables others to learn by example; it fosters similar approaches to solving the same problems across the entire community of practice; and it gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Explicitly Pedagogical Samples ==<br />
<br />
* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]<br />
<br />
* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)<br />
<br />
* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)<br />
<br />
* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/BZA/bzaComCatWeb.html '''Shorter Saṃyukta Āgama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies 中國佛教傳記''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers 中國佛寺志''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* ''Four Early Chan Texts from Dunhuang - A TEI based Edition''. Densely marked-up texts of manuscripts, with special attention to Chinese character variants (異體字). [https://zenodo.org/record/1133490#.WkXojPYxUyc '''Texts, data, and documentation archived at Zenodo'''].<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)<br />
<br />
* The [http://sarit.indology.info SARIT] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.16 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.<br />
<br />
* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.<br />
<br />
* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup<br />
<br />
* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.<br />
<br />
* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].<br />
<br />
* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].<br />
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=16850Samples of TEI texts2021-07-12T14:11:31Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__<br />
The availability of texts enables others to learn by example; it fosters similar approaches to solving the same problems across the entire community of practice; and it gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Explicitly Pedagogical Samples ==<br />
<br />
* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]<br />
<br />
* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)<br />
<br />
* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)<br />
<br />
* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/BZA/bzaComCatWeb.html '''Shorter Saṃyukta Āgama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies 中國佛教傳記''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers 中國佛寺志''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* ''Four Early Chan Texts from Dunhuang - A TEI based Edition''. Densely marked-up texts of manuscripts, with special attention to Chinese character variants (異體字). [https://zenodo.org/record/1133490#.WkXojPYxUyc '''Texts, data, and documentation archived at Zenodo''']<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)<br />
<br />
* The [http://sarit.indology.info SARIT] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.16 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.<br />
<br />
* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.<br />
<br />
* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup<br />
<br />
* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.<br />
<br />
* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].<br />
<br />
* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].<br />
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=16849Samples of TEI texts2021-07-12T14:10:53Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__<br />
The availability of texts enables others to learn by example; it fosters similar approaches to solving the same problems across the entire community of practice; and it gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Explicitly Pedagogical Samples ==<br />
<br />
* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]<br />
<br />
* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)<br />
<br />
* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)<br />
<br />
* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/BZA/bzaComCatWeb.html '''Shorter Saṃyukta Āgama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies 中國佛教傳記''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers 中國佛寺志''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* Four Early Chan Texts from Dunhuang - A TEI based Edition. Densely marked-up texts of manuscripts, with special attention to Chinese character variants (異體字). [https://zenodo.org/record/1133490#.WkXojPYxUyc '''Texts, data, and documentation archived at Zenodo''']<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)<br />
<br />
* The [http://sarit.indology.info SARIT] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.16 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.<br />
<br />
* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.<br />
<br />
* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup<br />
<br />
* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.<br />
<br />
* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].<br />
<br />
* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].<br />
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=16848Samples of TEI texts2021-07-12T13:39:18Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__<br />
The availability of texts enables others to learn by example; it fosters similar approaches to solving the same problems across the entire community of practice; and it gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Explicitly Pedagogical Samples ==<br />
<br />
* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]<br />
<br />
* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)<br />
<br />
* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)<br />
<br />
* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/BZA/bzaComCatWeb.html '''Shorter Saṃyukta Āgama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies 中國佛教傳記''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.dila.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers 中國佛寺志''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)<br />
<br />
* The [http://sarit.indology.info SARIT] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.16 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.<br />
<br />
* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.<br />
<br />
* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup<br />
<br />
* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.<br />
<br />
* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].<br />
<br />
* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].<br />
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]</div>Marcushttps://wiki.tei-c.org/index.php?title=Geany&diff=13961Geany2014-11-10T15:53:35Z<p>Marcus: /* Current version number and date of release */</p>
<hr />
<div>[[Category:Tools]]<br />
<br />
[[Category:Development tools]]<br />
[[Category:Editing tools]]<br />
[[Category:Conversion and preprocessing tools]]<br />
[[Category:Testing and QA tools]]<br />
<br />
[[Category:Discovering]]<br />
[[Category:Annotating]]<br />
[[Category:Comparing]]<br />
[[Category:Referring]]<br />
[[Category:Sampling]]<br />
[[Category:Illustrating]]<br />
[[Category:Representing]]<br />
<br />
== Synopsis ==<br />
Geany is a cross-platform IDE suitable for XML and HTML, C, Java, PHP, HTML, Python, Perl and Pascal. More inforamtion at http://www.geany.org/ and at https://en.wikipedia.org/wiki/Geany.<br />
<br />
== Features ==<br />
* Windows, Linux, etc<br />
* small and fast<br />
* auto closing of XML tags<br />
<br />
== User commentary ==<br />
'''Please sign all comments.'''<br />
(please leave the above note about signing comments, and add signed comments here below it)<br />
<br />
== System requirements ==<br />
* GTK (cross platform windowing toolkit, which comes with the download)<br />
<br />
== Source code and licensing ==<br />
GNU General Public Licence. <br />
<br />
== Support for TEI ==<br />
Generic XML support<br />
<br />
== Language(s) ==<br />
Written in C / C++ ?<br />
Supports: de, es, fr, hu, it, ja, kk, lt, nl, pl, pt, pt_BR, sk, sl, sv, tr, zh_CN, zh_TW. <br />
<br />
<br />
== Documentation ==<br />
(link to or information about documentation available)<br />
<br />
== Tech support ==<br />
(What technical support is provided by the creators of the tool?)<br />
<br />
== User community ==<br />
(Are there any communities of users?)<br />
<br />
== Sample implementations ==<br />
(links to demo sites running the tool or successful implementations of it)<br />
<br />
== Current version number and date of release ==<br />
1.24.1 (Released April 16, 2014)<br />
<br />
== History of versions ==<br />
(type in that information here)<br />
<br />
== How to download or buy ==<br />
(type in that information here)<br />
<br />
== Additional notes ==<br />
(type in that information here)</div>Marcushttps://wiki.tei-c.org/index.php?title=Geany&diff=13960Geany2014-11-10T15:52:06Z<p>Marcus: /* Synopsis */</p>
<hr />
<div>[[Category:Tools]]<br />
<br />
[[Category:Development tools]]<br />
[[Category:Editing tools]]<br />
[[Category:Conversion and preprocessing tools]]<br />
[[Category:Testing and QA tools]]<br />
<br />
[[Category:Discovering]]<br />
[[Category:Annotating]]<br />
[[Category:Comparing]]<br />
[[Category:Referring]]<br />
[[Category:Sampling]]<br />
[[Category:Illustrating]]<br />
[[Category:Representing]]<br />
<br />
== Synopsis ==<br />
Geany is a cross-platform IDE suitable for XML and HTML, C, Java, PHP, HTML, Python, Perl and Pascal. More inforamtion at http://www.geany.org/ and at https://en.wikipedia.org/wiki/Geany.<br />
<br />
== Features ==<br />
* Windows, Linux, etc<br />
* small and fast<br />
* auto closing of XML tags<br />
<br />
== User commentary ==<br />
'''Please sign all comments.'''<br />
(please leave the above note about signing comments, and add signed comments here below it)<br />
<br />
== System requirements ==<br />
* GTK (cross platform windowing toolkit, which comes with the download)<br />
<br />
== Source code and licensing ==<br />
GNU General Public Licence. <br />
<br />
== Support for TEI ==<br />
Generic XML support<br />
<br />
== Language(s) ==<br />
Written in C / C++ ?<br />
Supports: de, es, fr, hu, it, ja, kk, lt, nl, pl, pt, pt_BR, sk, sl, sv, tr, zh_CN, zh_TW. <br />
<br />
<br />
== Documentation ==<br />
(link to or information about documentation available)<br />
<br />
== Tech support ==<br />
(What technical support is provided by the creators of the tool?)<br />
<br />
== User community ==<br />
(Are there any communities of users?)<br />
<br />
== Sample implementations ==<br />
(links to demo sites running the tool or successful implementations of it)<br />
<br />
== Current version number and date of release ==<br />
(type in that information here)<br />
<br />
== History of versions ==<br />
(type in that information here)<br />
<br />
== How to download or buy ==<br />
(type in that information here)<br />
<br />
== Additional notes ==<br />
(type in that information here)</div>Marcushttps://wiki.tei-c.org/index.php?title=XML_Copy_Editor&diff=13959XML Copy Editor2014-11-10T15:44:50Z<p>Marcus: /* Current version number and date of release */</p>
<hr />
<div>[[Category:Tools]]<br />
<br />
[[Category:Development tools]]<br />
[[Category:Editing tools]]<br />
[[Category:Conversion and preprocessing tools]]<br />
<br />
== Synopsis ==<br />
"XML Copy Editor is a fast, free, validating XML editor."<br />
<br />
== Features ==<br />
From http://xml-copy-editor.sourceforge.net/index.php?page=features :<br />
<br />
* DTD/XML Schema/RELAX NG validation (also in the background)<br />
* [[XSLT]]<br />
* XPath<br />
* Pretty-printing<br />
* Syntax highlighting<br />
* Folding<br />
* Tag completion<br />
* Tag locking<br />
* Tag-free editing<br />
* Spelling and style check<br />
* Built-in support for XHTML, XSL, [[DocBook]] and TEI<br />
* Lossless import and export of Microsoft Word documents (Windows only)<br />
* Full Aspell support and XML Schema-based element inspection<br />
<br />
== User commentary ==<br />
'''Please sign all comments.'''<br />
<br />
2007-2008: I have used XML Copy editor in classes teaching XML, TEI & XHTML and participated in the Chinese localization of the interface. Having much fewer functions than production line tools such as Oxygen actually helps beginners to get into the validate & transform routine on which much of XML-work is based.<br />
(M.Bingenheimer, May 2008)<br />
<br />
== System requirements ==<br />
Available for Windows and Linux.<br />
<br />
== Source code and licensing ==<br />
Open-source (GNU General Public License)<br />
<br />
== Support for TEI ==<br />
DTD/Schema for P4/5 are included.<br />
<br />
== Language(s) ==<br />
Interface in English.<br />
<br />
== Documentation ==<br />
See [http://xml-copy-editor.sourceforge.net/index.php?page=help Online Help].<br />
<br />
== Tech support ==<br />
<br />
== User community ==<br />
https://sourceforge.net/forum/forum.php?forum_id=475215<br />
<br />
<!-- inapplicable? <br />
== Sample implementations ==<br />
(links to demo sites running the tool or successful implementations of it)<br />
--><br />
== Current version number and date of release ==<br />
1.2.1.3 (2014-09-06)<br />
<br />
== History of versions ==<br />
http://sourceforge.net/news/?group_id=141776<br />
<br />
== How to download ==<br />
See http://xml-copy-editor.sourceforge.net/ .<br />
<br />
== Additional notes ==</div>Marcushttps://wiki.tei-c.org/index.php?title=Text_Directionality_Draft&diff=12739Text Directionality Draft2013-11-29T16:29:40Z<p>Marcus: /* Introduction */</p>
<hr />
<div>This is a preliminary draft of proposed sections for the TEI Guidelines, created by the [[Text Directionality Workgroup]]. Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions. There is also a [[Talk:Text_Directionality_Draft|talk page]] for more informal discussion.<br />
<br />
==Text directionality and transformation==<br />
<br />
===Introduction===<br />
<br />
Scripts used for writing human languages vary not only in the glyphs they use, but also in the direction in which these glyphs are to be read. The majority of modern languages are written from left to right within the line, and have their lines stacked from top to bottom vertically (English, Russian, Greek), but there are several widely-used scripts which run right-to-left (Arabic, Hebrew), while also stacking lines top-to-bottom. East Asian scripts (Sinitic characters, Japanese Kana, Korean Hangul, Vietnamese chữ nôm) were traditionally written from top to bottom within the line, with their lines sequenced from right to left.<ref>Today Chinese in China is printed with the same directionality as English, while printing in Taiwan and Hongkong uses both modes depending on taste and context. The vast majority of books and newpapers in Japanese are printed in the traditional vertical-rl mode, while the lay-out of Korean and Vietnamese is generally ltr / horizontal-tb.</ref> Ancient Uighur, classical Mongolian and Manchu too were written top to bottom, but with the lines stacked left to right. Cases of bottom-to-top writing are extremely rare, but there is Ancient Berber, and some Ogham inscriptions. There also are instances of writing which changes direction on alternate lines (boustrophedon, discussed in detail below). <br />
<br />
When a language or script can be arranged in two or more different directions, there are often other consequences arising out of the choice; for example, when Japanese is written horizontally, the Unicode character U+3001, the "ideographic comma", is used, whereas in vertical writing an alternative glyph, U+FE11, may be used to ensure that the comma appears in the correct position relative to the surrounding glyphs. In addition, scripts which normally have a single directionality (such as English) may be written in a different direction in the context of another language (English words inserted into vertical Chinese text, for example), or in response to layout constraints such as those imposed by a complex table, in which column or row labels may be written vertically to make the most effective use of available space.<br />
<br />
The directionality features of scripts, and the consequences arising out of them, are generally referred to as "writing modes". For many documents encoded in TEI, there may be no need to encode any information relating to writing mode, because it will be obvious. Modern printed texts in most European languages, for instance, may be expected to use left-to-right/top-to-bottom directionality; Arabic or Hebrew texts are expected to run right-to-left/top-to-bottom. It may appear that directionality can be reliably deduced from the language and script settings, and these are probably already encoded using the @xml:lang attribute in TEI documents (although the W3C i18n Working Group recommends against reliance on language tags for encoding directionality information [per Richard Ishida, W3C; I need to find a formal reference for this]). Even in the case of many "mixed mode" documents (documents in which languages or scripts with different writing modes are mixed together), it may not be necessary to be explicit about directionality. Consider the case of an English text containing a few Arabic words--what is termed a "bidirectional" text:<br />
<br />
<code>The Arabic term قلم رصاص means "pencil".</code><br />
<br />
Since Arabic is always written from right to left, we can assume that the Arabic glyphs are to be read in that direction, even if they are in the context of a left-to-right English sentence. In fact, most codepoints in the Unicode standard have a specific directionality setting which helps any rendering engine to determine how they should be ordered. The Latin glyph "a" has a bidirectionality setting of strong left-to-right; the Hebrew א (alef) is strongly right-to-left. Other glyphs have weak or neutral settings because of the contexts in which they may appear. The Unicode Bidirectional Algorithm (http://www.unicode.org/reports/tr9/) provides a complex series of rules enabling user agents to render most mixed-mode texts with predictable and reliable results, based on the bidirectionality class values of their glyphs.<br />
<br />
In some mixed-mode texts, though, the Bidirectional Algorithm may not give the desired results. To deal with this, Unicode provides a set of "directional formatting characters" (http://www.unicode.org/reports/tr9/#Directional_Formatting_Codes), also called "bidi formatting code characters", which are additional codepoints whose only function is to signal to a user-agent that a specific directionality setting should be turned on or off. These can be inserted into a text to influence the outcome of the bidirectional algorithm. However, in the case of documents encoded in XML, the W3C explicitly advises that markup rather than directional formatting characters should be used ("In (X)HTML and XML do not use the paired Unicode bidi formatting code characters where equivalent markup is available," http://www.w3.org/International/questions/qa-bidi-controls). We concur with this recommendation, and the remainder of this section and the next provide a set of encoding strategies for handling text directionality without the use of directional formatting characters. The approach we recommend is based on two external specifications, in line with our normal practice of incorporating existing standards where they are available and appropriate. Those specifications are the CSS Writing Modes module (http://dev.w3.org/csswg/css-writing-modes/) and the CSS Transforms module (http://www.w3.org/TR/css3-transforms/). Since (at the time of writing) neither of these modules has yet reached the stage of a Recommendation, the advice offered below should be regarded as provisional, and you should check your usage of the properties concerned against the current version of each specification where possible. <br />
<br />
The following sections will present a few simple examples of phenomena relating to text directionality and transformation, along with some suggested encoding strategies based on the following CSS properties from CSS Writing Modes:<br />
<br />
<code><br />
direction: ltr | rtl<br/><br />
writing-mode: horizontal-tb | vertical-rl | vertical-lr<br/><br />
text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation<ref>The value "use-glyph-orientation" may be dropped from the CSS Writing Modes specification.</ref><br/><br />
unicode-bidi: normal | embed | isolate | bidi-override | isolate-override | plaintext<br />
</code><br />
<br />
along with the <code>transform</code> property from CSS Transforms.<br />
<br />
In the following examples, CSS rules are encoded in the global TEI @style attribute, which applies them directly to the element on which they are specified (and in most cases, its descendants). It is also appropriate, and will often be more efficient, to express the rules in TEI <rendition> elements in the <teiHeader> and point to them using @rendition attributes. It should also be remembered that the CSS specifications are written primarily to guide users providing instructions for the rendering of digital texts, and implementers creating user-agents which will act on these instructions. However, our usage in the context of a TEI document is primarily ''descriptive'' rather than ''prescriptive''; we are typically describing the features of a text we are encoding, rather than providing instructions for rendering it. Our purpose below is not to enumerate an exhaustive set of strategies for encoding any writing mode feature you may encounter; rather we will show some simple examples which serve as an introduction to the topic.<br />
<br />
===Text directionality===<br />
<br />
====Horizontal directionality====<br />
<br />
Returning to our previous simple example<br />
<br />
<code>The Arabic term قلم رصاص means "pencil".</code><br />
<br />
we could use the <code>direction</code> property to make directionality explicit:<br />
<br />
<code>direction: ltr | rtl</code><br />
<br />
<syntaxhighlight lang="xml"><br />
<seg xml:lang="en" style="direction: ltr">The Arabic term </seg><br />
<seg xml:lang="ar" style="unicode-bidi: embed; direction: rtl">قلم رصاص</seg> <br />
<seg xml:lang="en" style="direction: ltr">means "pencil".</seg><br />
</syntaxhighlight><br />
<br />
The use of the <code>direction</code> property is straightforward, but the <code>unicode-bidi</code> property requires some explanation. These three segments are all inline; they form part of a single sentence, although they happen to be encoded on separate lines in this example. The default value for <code>unicode-bidi</code> is "normal", and the CSS Writing Modes specification stipulates that the <code>direction</code> property "has no effect on bidi reordering when specified on inline elements whose unicode-bidi property’s value is normal, because the element does not open an additional level of embedding with respect to the bidirectional algorithm." In other words, if we want to make it clear that the <code>direction</code> property is effective here, we must include a value for <code>unicode-bidi</code> which will make it so.<br />
<br />
However, as mentioned above, all of the directional encoding in this example is superfluous; ambiguity does not arise in this particular case. Moreover, "ltr" is the default value for the <code>direction</code> property, so we do not need to specify it for the English segments. However, consider the following example, contributed by Efraim Feinstein, in which Hebrew and English text are mixed. (This example is presented in the form of graphics, because we cannot rely on user agents that may be rendering or displaying these Guidelines to provide a consistent output.)<br />
<br />
[[File:En he embedding.png|800px]]<br />
<br />
Here, an English period appears in between two runs of Hebrew text. Should that period be interpreted as part of a single run of right-to-left text, or should it be deemed to terminate the first run and precede the second? For the Unicode Bidi Algorithm, punctuation is not strongly directional; it inherits directionality from the surrounding characters. Without further clues, therefore, it would interpret the example as a sequence of three runs (English, Hebrew, English), and arrive at an incorrect interpretation. A clear and correct interpretation requires that not only that the glyphs themselves be transcribed in the correct logical order, but that the encoding eliminate potential ambiguity by delimiting the two Hebrew runs separately, like this:<br />
<br />
<syntaxhighlight lang="xml"><br />
<p><br />
Here's a sentence that begins in English<br />
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ויש מלים בעברית והפסק</seg>.<br />
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ועוד מלים בעברית</seg><br />
and it continues in English.<br />
</p><br />
</syntaxhighlight><br />
<br />
Here the English is unmarked for directionality, but the period is clearly not included in either of the RTL runs, so the ambiguity inherent in the plain text is avoided. Once again, we might argue that the <code>@xml:lang</code> attribute should provide enough information; the important component here is the explicit delimitation of two distinct RTL runs. But additional clarity in the encoding certainly does no harm.<br />
<br />
[Would it be helpful to have another example presenting ambiguity arising out of the use of a g element at the end of a text run?]<br />
<br />
====Vertical writing modes====<br />
<br />
So far, we have looked only at left-to-right and right-to-left text running horizontally, using the <code>direction: ltr|rtl</code> property. However, there are many scripts and languages which are written vertically (mostly top-to-bottom, but with a few unusal examples running bottom-to-top, as we shall see below). Handling vertical directionality requires the use of another CSS property, the writing mode:<br />
<br />
<code>writing-mode: horizontal-tb | vertical-rl | vertical-lr</code><br />
<br />
The values for this property include two components: "horizontal" or "vertical" specifies the inline writing direction, while the second component specifies the direction in which lines in a block, and blocks in a sequence may be arranged: from top to bottom (as in most European languages, in which lines and paragraphs are arranged from top to bottom on a page), from right to left (as in the case of some East Asian languages such as Japanese, which we will see below), or left-to-right (e.g. Mongolian). This example shows a Japanese haiku poem transcribed first in Japanese, then in Romaji (Japanese in Latin script), and finally in an English translation. <br />
<br />
[[File:Basho_furu_ike_ya.png|thumb|left|alt=Basho poem|Taken from p.42 of ''Haiku: Japanese Art and Poetry''. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. Used with permission.]]<br />
<br />
<syntaxhighlight lang="xml"><br />
<div><br />
<ab xml:lang="ja" style="writing-mode: vertical-rl" <br />
xml:id="furu-ike-ya_jp" corresp="#furu-ike-ya_romaji #furu-ike-ya_en"><br />
古池や<lb/><br />
蛙<lb/><br />
飛び込む<lb/><br />
水の音<br />
</ab><br />
<br />
<lg xml:lang="ja-Latn" style="writing-mode: horizontal-tb" <br />
xml:id="furu-ike-ya_romaji" corresp="#furu-ike-ya_jp #furu-ike-ya_en"> <br />
<l>furu ike ya</l><br />
<l>kawazu tobikomu</l><br />
<l>mizu no oto</l><br />
</lg><br />
<br />
<lg xml:lang="en" <br />
xml:id="furu-ike-ya_en" corresp="#furu-ike-ya_jp #furu-ike-ya_romaji"><br />
<l>Old pond,</l><br />
<l>and a frog dives in—</l><br />
<l>"Splash"!</l><br />
</lg><br />
<br />
<bibl>—Bashō (1644–1694)</bibl><br />
</div><br />
</syntaxhighlight><br />
<br />
Note: for the sake of simplicity, the indenting of lines in the vertical Japanese and the central alignment of the other components have been ignored in this encoding, since this section focuses on language and writing mode issues. The Japanese transcription has <code>writing-mode: vertical-rl</code>, which is required because Japanese may be written either in this mode or horizontally. The transcription in Romaji has <code>@xml:lang="ja-Latn"</code> (Japanese written in Latin script) and has a horizontal writing mode; this may seem superfluous, but vertically-written romaji is not unknown.<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
====Vertical text with embedded horizontal text====<br />
<br />
When Japanese is written vertically, the glyph orientation remains the same as when it is written horizontally. In other words, glyphs are not rotated (although as noted above some different glyphs may be used for some characters the two orientations; punctuation for instance needs to be positioned differently in vertical versus horizontal text). However, it is very common for languages written vertically to have embedded runs of text from languages normally written horizontally. This raises the issue of the orientation of the glyphs from the horizontal language. Are they written upright, as they would normally appear in horizontal text runs, or are they rotated? Consider this fragment from a Japanese article about the Indonesian language, which takes the form of a glossary list:<br />
<br />
[[File:Ja vertical indonesian frag sm.jpg|thumb|left|alt=Glossary list|Taken from p.62 of "インドネシア語". 崎山理. 1985. ''外国語との対照II''. 講座日本語学 11.]]<br />
<br />
This might be transcribed as follows:<br />
<br />
<syntaxhighlight lang="xml"><br />
<list type="gloss" xml:lang="ja" <br />
style="writing-mode: vertical-rl; text-orientation: mixed"><br />
<br />
<label xml:lang="id">hampir</label> <br />
<item>「近い、ほとんど」</item><br />
<br />
<label xml:lang="id">baru</label><br />
<item>「新しい、ばかい」</item><br />
<br />
<!-- ... --><br />
</list><br />
</syntaxhighlight><br />
<br />
The rule <code>text-orientation: mixed</code> gives the expected orientation: "In vertical writing modes, characters from horizontal-only scripts are set sideways, i.e. 90° clockwise from their standard orientation in horizontal text. Characters from vertical scripts are set with their intrinsic orientation" ([http://www.w3.org/TR/2013/WD-css-writing-modes-3-20131024/#text-orientation CSS Writing Modes]). In actual fact, the default value for <code>text-orientation</code> is "mixed", so this rule is not strictly required, but if the Indonesian glyphs had been set vertically, like this:<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
[[File:Ja vertical indonesian frag rotated sm.jpg|50px|thumb|left|alt=Glossary list|Fragment of previous image with Indonesian glyphs upright.]]<br />
<br />
then the encoding would have to be explicit, and we could capture the orientation with <code>text-orientation: upright</code>.<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
====Vertical orientation in horizontal scripts====<br />
<br />
It is not unusual to see text from horizontal languages written vertically even where it is not embedded in a text run from a vertically-written script. This example is a fragment from a table of information about agricultural development on Vancouver Island, written in 1855:<br />
<br />
[[File:bcgenesis co 305 06 00131v table extract.jpg|thumb|center|600px|alt=Agricultural report table|Enclosure with 10048, CO 305/6, p. 109 http://bcgenesis.uvic.ca/getDoc.htm?id=V55116.scx]]<br />
<br />
Four subheading cells in this fragment contain English text, written vertically, bottom-to-top, to conserve space on the page. This is not a "native orientation" for English; readers would not find it easy to read this text, and might be inclined to rotate the page in order to read it in a more natural way. To describe this sort of phenomenon, we can use the text-orientation property again:<br />
<br />
<code>text-orientation: mixed|upright|sideways-right|sideways-left|sideways|use-glyph-orientation</code><br />
<br />
For full details on this property, we refer the reader to the CSS Writing Modes specification. For the present example, we will make use only of the "sideways-left" value, which "causes text to be set as if in a horizontal layout, but rotated 90° counter-clockwise." We might encode one of the four cells containing vertical text like this:<br />
<br />
<syntaxhighlight lang="xml"><br />
<cell style="writing-mode: vertical-lr; text-orientation: sideways-left"><br />
Cash Value<lb/><br />
of<lb/><br />
Farms<br />
</cell><br />
</syntaxhighlight><br />
<br />
The <code>writing-mode</code> captures the fact that the script is written vertically, and its line/block flow is from left to right (so "of" is to the right of "Cash value"), while the <code>text-orientation</code> value encodes the orientation (rotated 90° counter-clockwise). We might also add <code>text-align: center</code> to the style, to express the fact that the text is centrally-aligned; alignment properties are mapped relative to the line flow, so the word "of" is visibly centred relative to the physical top and bottom of the box, which are the left and right from the point of view of the line flow.<br />
<br />
====Bottom-to-top writing====<br />
<br />
There are a very small number of scripts which appear to be written bottom-to-top; perhaps the most well-known is Ogham, an alphabet used mainly to write Archaic Irish. The CSS Writing Modes specification does not explicitly provide for the distinction between top-to-bottom and bottom-to-top in vertically-written scripts; it is argued that all instances of bottom-to-top scripts are actually left-to-right horizontal scripts, oriented vertically because of the constraints of the medium on which they are inscribed (as in the case of Ogham inscriptions on tombstones). In other words, the case of scripts like this is analogous to the vertical English text-runs in the table cells in the example above, and can be handled in exactly the same manner (<code>writing-mode: vertical-lr; text-orientation: sideways-left</code>).<br />
<br />
====Summary====<br />
<br />
In this section, we have presented one approach to encoding text directionality features in TEI files, using the properties and values from the CSS Writing Modes module, encoded in the global TEI @style attribute (or in the TEI <code><rendition></code> element and linked with the @rendition attribute). For most texts, it will not be necessary to encode any information about text directionality, either because it follows unambiguously from <code>@xml:lang</code> values, or because it can be expected to be handled unequivocally by the Unicode Bidi Algorithm. Where it is important to encode text directionality, we believe that most phenomena can be well described through the use of the CSS Writing Modes features; of those which cannot, other approaches based on the CSS Transforms module are presented below.<br />
<br />
===Text transformation===<br />
<br />
====Rotation====<br />
<br />
In what follows, we examine a range of textual phenomena which in some ways appear very similar to those examined above, and even overlap with them. We can categorize these as text transformation features, and suggest some strategies for encoding them based on the properties detailed in the [http://www.w3.org/TR/css3-transforms/ CSS Transforms] specification. The CSS Transforms module provides a complex array of properties, values and functions which can be used to rotate, skew, translate and otherwise transform textual and graphical objects. We can borrow this vocabulary in order to describe textual phenomena in a precise manner.<br />
<br />
We begin with a simple example of a rotational transform:<br />
<br />
[[File:Rotation_on_z_axis.png|frame]]<br />
<br />
Here a block of text has been rotated around its z-axis. This is clearly not a "writing mode"; the writing mode for this text is horizontal, left to right. Furthermore, even if we wished to treat this as a writing mode, we could not do so, because there is no way to use writing modes properties to describe an text orientation which is angled at 45 degrees; no human languages are consistently written in this orientation. It is more appropriate to treat this as a rotational transformation. We can do this using two properties: <code>transform</code> and <code>transform-origin</code>. (Both of these properties have quite complex value sets, and we will not look at all of them here. See the [http://www.w3.org/TR/css3-transforms/ specification] for full details.)<br />
<br />
The <code>transform</code> property takes as its value one or more of the transform functions, one of which is the function <code>rotateZ</code>:<br />
<br />
<syntaxhighlight lang="xml"><br />
<br />
<ab style="transform:rotateZ(-45deg)">TEI-C.ORG</ab><br />
<br />
</syntaxhighlight><br />
<br />
Any rotation must take place around an axis positioned relative to the element being rotated, and the <code>transform-origin</code> property can be used to specify the pivot point. By default, the value of <code>transform-origin</code> is "50% 50%", the point at the centre of the element, but these values can be changed to reflect rotation around a different origin point. (The TEI [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone element] also bears an attribute @rotate which can specify rotation in degrees around the z-axis, but it is not available for any other element.)<br />
<br />
An element may also be rotated about either of its other axes. For example, this shows rotation around the Y (vertical) axis:<br />
<br />
[[File:Rotation_on_y_axis.png|frame]] <br />
<br />
<syntaxhighlight lang="xml"><br />
<br />
<ab style="transform:rotateY(45deg)">TEI-C.ORG</ab><br />
<br />
</syntaxhighlight><br />
<br />
These are obviously trivial examples, but similar features do appear in historical texts. George Herbert's ''The Temple'' includes two stanzas headed "Easter Wings" which are both normally printed in a rotated form so that they represent a pair of wings:<br />
<br />
[[File:Herbert church p35 sm.jpg|thumb|left|300px|Page 35 of Herbert's ''The Temple'', second stanza of Easter Wings (or second poem so named). Used with permission of the Folger Library.]]<br />
<br />
This could be encoded thus:<br />
<br />
<syntaxhighlight lang="xml"><br />
<lg style="transform:rotateX(90deg)"><br />
<l>My tender age in ſorrow did beginne:</l><br />
<l>And ſtill with ſickneſſes and ſhame</l><br />
<!-- ... --><br />
</lg><br />
</syntaxhighlight><br />
<br />
but we might also argue that this is in fact a vertical writing mode, and express it with <code>writing-mode: vertical-rl; text-orientation: sideways-right</code>.<br />
<br />
<div style="clear: both;">&#160;</div><br />
<br />
====Boustrophedon====<br />
<br />
We may also use rotation as a method of handling a true writing mode which is not covered by the CSS Writing Modes: boustrophedon. This is a writing mode common in inscriptions in Latin, Greek and other languages, in which alternate lines run from left to right and from right to left; its name derives from the path of an ox pulling a plough. Right-to-left lines in boustrophedon have another unexpected feature: their glyphs are reversed, so that these lines appear as "mirror writing". This example shows a transcription of a Greek inscription at Dodona:<br />
<br />
[[File:Boustrophedon small J.NW.Epeiros.13.p03.jpg|thumb|left|300px|Drawing of a leaden plaque bearing an inquiry by Hermon from the oracular precinct at Dodona. Image and transcription from http://poinikastas.csad.ox.ac.uk, used with permission.]]<br />
<br />
This might be transcribed as follows (ignoring word boundaries for the moment):<br />
<br />
<syntaxhighlight lang="xml"><br />
<ab><br />
ΗΕΡΜΟΝΤΙΝΑ <lb/><br />
<seg style="rotateY(180deg)">ΚΑΘΕΟΝΠΟΤΘΕΜ</seg> <lb/><br />
ΕΝΟΣΥΕΝΕΑϜ <lb/><br />
<seg style="rotateY(180deg)">ΟΙΥΕΝΟΙΤΙΕΚΚ</seg> <lb/><br />
ΡΕΤΑΙΑΣΟΝΑ <lb/><br />
<seg style="rotateY(180deg)">ΣΙΜΟΣΟΤΤΑΙΕ</seg> <lb/><br />
ΑΣΣΑΙ<br />
</ab><br />
</syntaxhighlight><br />
<br />
The 180-degree rotation around the Y (vertical) axis here gives us exactly the effect of the RTL line in boustrophedon; the order of glyphs is reversed, and so is their individual orientation (in fact, we see them "from the back", as it were). <code><seg></code> elements have been used here because these are clearly not "lines" in the sense of poetic lines; the text is continuous prose, and linebreaks are incidental.<br />
<br />
There are obviously some unsatisfactory aspects of this manner of encoding boustrophedon. In the inscription above, some words run across linebreaks, so if we wished to tag both words and the right-to-left phenomena, one hierarchy would have to be privileged over the other. By using a transform function rather than a writing mode property, we are apparently suggesting that boustrophedon is not in fact a writing mode, whereas it clearly is. But the CSS Writing Modes specification does not provide support for boustrophedon, because it is a rather obscure historical phenomenon; using a rotational transform is one practical alternative.<br />
<br />
<div style="clear: both;">&#160;</div><br />
<br />
====Caveats====<br />
<br />
The effect and behaviour of CSS Transforms properties and values according to the specification are highly dependent on the computed [http://www.w3.org/TR/CSS2/visuren.html Visual formatting model] of an HTML document. TEI currently does not have an explicit processing or formatting model. That is, it is by no means clear whether any given TEI element should be interpreted, for instance, as a block-level or inline-level element; for many elements we may think we can assume block-level (<code><ab></code>, "anonymous block") or inline-level (<code><w></code>, "word") from the semantics, but even this is risky. As long as the properties and values from the CSS Transforms module are used as a convenient, well-specified descriptive language to capture features of a text, without any expectation of using them directly and reliably for rendering, this is not problematic; we are simply borrowing a useful vocabulary from an external source, and benefiting from the clarity of definition provided by the specification. However, if there is any expectation of using this information to render a text in a predictable and accurate way, it will be essential to provide enough styling information throughout the document hierarchy to resolve all ambiguities with regard to size, positioning, block status, etc. before any element undergoes a transform operation.<br />
<br />
<references/><br />
<br />
<br />
<br />
<br />
[[Category:Council]]</div>Marcushttps://wiki.tei-c.org/index.php?title=Text_Directionality_Draft&diff=12738Text Directionality Draft2013-11-29T16:19:43Z<p>Marcus: /* Introduction */</p>
<hr />
<div>This is a preliminary draft of proposed sections for the TEI Guidelines, created by the [[Text Directionality Workgroup]]. Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions. There is also a [[Talk:Text_Directionality_Draft|talk page]] for more informal discussion.<br />
<br />
==Text directionality and transformation==<br />
<br />
===Introduction===<br />
<br />
Scripts used for writing human languages vary not only in the glyphs they use, but also in the direction in which these glyphs are to be read. The majority of modern languages are written from left to right within the line, and have their lines stacked from top to bottom vertically (English, Russian, Greek), but there are several widely-used scripts which run right-to-left (Arabic, Hebrew), while also stacking lines top-to-bottom. East Asian scripts (Sinitic characters, Japanese Kana, Korean Hangul, Vietnamese chữ nôm) were traditionally written from top to bottom within the line, with their lines sequenced from right to left.<ref>Today Chinese in China is printed with the same directionality as English, while printing in Taiwan and Hongkong uses both modes depending on taste and context. The vast majority of books and newpapers in Japanese are printed in the traditional vertical-rl mode, while the lay-out of Korean and Vietnamese is generally ltr / horizontal-tb.</ref> There are a few cases of bottom-to-top writing, such as Ancient Berber, and some Ogham inscriptions; there are even instances of writing which changes direction on alternate lines (boustrophedon, discussed in detail below). <br />
<br />
When a language or script can be arranged in two or more different directions, there are often other consequences arising out of the choice; for example, when Japanese is written horizontally, the Unicode character U+3001, the "ideographic comma", is used, whereas in vertical writing an alternative glyph, U+FE11, may be used to ensure that the comma appears in the correct position relative to the surrounding glyphs. In addition, scripts which normally have a single directionality (such as English) may be written in a different direction in the context of another language (English words inserted into vertical Chinese text, for example), or in response to layout constraints such as those imposed by a complex table, in which column or row labels may be written vertically to make the most effective use of available space.<br />
<br />
The directionality features of scripts, and the consequences arising out of them, are generally referred to as "writing modes". For many documents encoded in TEI, there may be no need to encode any information relating to writing mode, because it will be obvious. Modern printed texts in most European languages, for instance, may be expected to use left-to-right/top-to-bottom directionality; Arabic or Hebrew texts are expected to run right-to-left/top-to-bottom. It may appear that directionality can be reliably deduced from the language and script settings, and these are probably already encoded using the @xml:lang attribute in TEI documents (although the W3C i18n Working Group recommends against reliance on language tags for encoding directionality information [per Richard Ishida, W3C; I need to find a formal reference for this]). Even in the case of many "mixed mode" documents (documents in which languages or scripts with different writing modes are mixed together), it may not be necessary to be explicit about directionality. Consider the case of an English text containing a few Arabic words--what is termed a "bidirectional" text:<br />
<br />
<code>The Arabic term قلم رصاص means "pencil".</code><br />
<br />
Since Arabic is always written from right to left, we can assume that the Arabic glyphs are to be read in that direction, even if they are in the context of a left-to-right English sentence. In fact, most codepoints in the Unicode standard have a specific directionality setting which helps any rendering engine to determine how they should be ordered. The Latin glyph "a" has a bidirectionality setting of strong left-to-right; the Hebrew א (alef) is strongly right-to-left. Other glyphs have weak or neutral settings because of the contexts in which they may appear. The Unicode Bidirectional Algorithm (http://www.unicode.org/reports/tr9/) provides a complex series of rules enabling user agents to render most mixed-mode texts with predictable and reliable results, based on the bidirectionality class values of their glyphs.<br />
<br />
In some mixed-mode texts, though, the Bidirectional Algorithm may not give the desired results. To deal with this, Unicode provides a set of "directional formatting characters" (http://www.unicode.org/reports/tr9/#Directional_Formatting_Codes), also called "bidi formatting code characters", which are additional codepoints whose only function is to signal to a user-agent that a specific directionality setting should be turned on or off. These can be inserted into a text to influence the outcome of the bidirectional algorithm. However, in the case of documents encoded in XML, the W3C explicitly advises that markup rather than directional formatting characters should be used ("In (X)HTML and XML do not use the paired Unicode bidi formatting code characters where equivalent markup is available," http://www.w3.org/International/questions/qa-bidi-controls). We concur with this recommendation, and the remainder of this section and the next provide a set of encoding strategies for handling text directionality without the use of directional formatting characters. The approach we recommend is based on two external specifications, in line with our normal practice of incorporating existing standards where they are available and appropriate. Those specifications are the CSS Writing Modes module (http://dev.w3.org/csswg/css-writing-modes/) and the CSS Transforms module (http://www.w3.org/TR/css3-transforms/). Since (at the time of writing) neither of these modules has yet reached the stage of a Recommendation, the advice offered below should be regarded as provisional, and you should check your usage of the properties concerned against the current version of each specification where possible. <br />
<br />
The following sections will present a few simple examples of phenomena relating to text directionality and transformation, along with some suggested encoding strategies based on the following CSS properties from CSS Writing Modes:<br />
<br />
<code><br />
direction: ltr | rtl<br/><br />
writing-mode: horizontal-tb | vertical-rl | vertical-lr<br/><br />
text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation<ref>The value "use-glyph-orientation" may be dropped from the CSS Writing Modes specification.</ref><br/><br />
unicode-bidi: normal | embed | isolate | bidi-override | isolate-override | plaintext<br />
</code><br />
<br />
along with the <code>transform</code> property from CSS Transforms.<br />
<br />
In the following examples, CSS rules are encoded in the global TEI @style attribute, which applies them directly to the element on which they are specified (and in most cases, its descendants). It is also appropriate, and will often be more efficient, to express the rules in TEI <rendition> elements in the <teiHeader> and point to them using @rendition attributes. It should also be remembered that the CSS specifications are written primarily to guide users providing instructions for the rendering of digital texts, and implementers creating user-agents which will act on these instructions. However, our usage in the context of a TEI document is primarily ''descriptive'' rather than ''prescriptive''; we are typically describing the features of a text we are encoding, rather than providing instructions for rendering it. Our purpose below is not to enumerate an exhaustive set of strategies for encoding any writing mode feature you may encounter; rather we will show some simple examples which serve as an introduction to the topic.<br />
<br />
===Text directionality===<br />
<br />
====Horizontal directionality====<br />
<br />
Returning to our previous simple example<br />
<br />
<code>The Arabic term قلم رصاص means "pencil".</code><br />
<br />
we could use the <code>direction</code> property to make directionality explicit:<br />
<br />
<code>direction: ltr | rtl</code><br />
<br />
<syntaxhighlight lang="xml"><br />
<seg xml:lang="en" style="direction: ltr">The Arabic term </seg><br />
<seg xml:lang="ar" style="unicode-bidi: embed; direction: rtl">قلم رصاص</seg> <br />
<seg xml:lang="en" style="direction: ltr">means "pencil".</seg><br />
</syntaxhighlight><br />
<br />
The use of the <code>direction</code> property is straightforward, but the <code>unicode-bidi</code> property requires some explanation. These three segments are all inline; they form part of a single sentence, although they happen to be encoded on separate lines in this example. The default value for <code>unicode-bidi</code> is "normal", and the CSS Writing Modes specification stipulates that the <code>direction</code> property "has no effect on bidi reordering when specified on inline elements whose unicode-bidi property’s value is normal, because the element does not open an additional level of embedding with respect to the bidirectional algorithm." In other words, if we want to make it clear that the <code>direction</code> property is effective here, we must include a value for <code>unicode-bidi</code> which will make it so.<br />
<br />
However, as mentioned above, all of the directional encoding in this example is superfluous; ambiguity does not arise in this particular case. Moreover, "ltr" is the default value for the <code>direction</code> property, so we do not need to specify it for the English segments. However, consider the following example, contributed by Efraim Feinstein, in which Hebrew and English text are mixed. (This example is presented in the form of graphics, because we cannot rely on user agents that may be rendering or displaying these Guidelines to provide a consistent output.)<br />
<br />
[[File:En he embedding.png|800px]]<br />
<br />
Here, an English period appears in between two runs of Hebrew text. Should that period be interpreted as part of a single run of right-to-left text, or should it be deemed to terminate the first run and precede the second? For the Unicode Bidi Algorithm, punctuation is not strongly directional; it inherits directionality from the surrounding characters. Without further clues, therefore, it would interpret the example as a sequence of three runs (English, Hebrew, English), and arrive at an incorrect interpretation. A clear and correct interpretation requires that not only that the glyphs themselves be transcribed in the correct logical order, but that the encoding eliminate potential ambiguity by delimiting the two Hebrew runs separately, like this:<br />
<br />
<syntaxhighlight lang="xml"><br />
<p><br />
Here's a sentence that begins in English<br />
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ויש מלים בעברית והפסק</seg>.<br />
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ועוד מלים בעברית</seg><br />
and it continues in English.<br />
</p><br />
</syntaxhighlight><br />
<br />
Here the English is unmarked for directionality, but the period is clearly not included in either of the RTL runs, so the ambiguity inherent in the plain text is avoided. Once again, we might argue that the <code>@xml:lang</code> attribute should provide enough information; the important component here is the explicit delimitation of two distinct RTL runs. But additional clarity in the encoding certainly does no harm.<br />
<br />
[Would it be helpful to have another example presenting ambiguity arising out of the use of a g element at the end of a text run?]<br />
<br />
====Vertical writing modes====<br />
<br />
So far, we have looked only at left-to-right and right-to-left text running horizontally, using the <code>direction: ltr|rtl</code> property. However, there are many scripts and languages which are written vertically (mostly top-to-bottom, but with a few unusal examples running bottom-to-top, as we shall see below). Handling vertical directionality requires the use of another CSS property, the writing mode:<br />
<br />
<code>writing-mode: horizontal-tb | vertical-rl | vertical-lr</code><br />
<br />
The values for this property include two components: "horizontal" or "vertical" specifies the inline writing direction, while the second component specifies the direction in which lines in a block, and blocks in a sequence may be arranged: from top to bottom (as in most European languages, in which lines and paragraphs are arranged from top to bottom on a page), from right to left (as in the case of some East Asian languages such as Japanese, which we will see below), or left-to-right (e.g. Mongolian). This example shows a Japanese haiku poem transcribed first in Japanese, then in Romaji (Japanese in Latin script), and finally in an English translation. <br />
<br />
[[File:Basho_furu_ike_ya.png|thumb|left|alt=Basho poem|Taken from p.42 of ''Haiku: Japanese Art and Poetry''. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. Used with permission.]]<br />
<br />
<syntaxhighlight lang="xml"><br />
<div><br />
<ab xml:lang="ja" style="writing-mode: vertical-rl" <br />
xml:id="furu-ike-ya_jp" corresp="#furu-ike-ya_romaji #furu-ike-ya_en"><br />
古池や<lb/><br />
蛙<lb/><br />
飛び込む<lb/><br />
水の音<br />
</ab><br />
<br />
<lg xml:lang="ja-Latn" style="writing-mode: horizontal-tb" <br />
xml:id="furu-ike-ya_romaji" corresp="#furu-ike-ya_jp #furu-ike-ya_en"> <br />
<l>furu ike ya</l><br />
<l>kawazu tobikomu</l><br />
<l>mizu no oto</l><br />
</lg><br />
<br />
<lg xml:lang="en" <br />
xml:id="furu-ike-ya_en" corresp="#furu-ike-ya_jp #furu-ike-ya_romaji"><br />
<l>Old pond,</l><br />
<l>and a frog dives in—</l><br />
<l>"Splash"!</l><br />
</lg><br />
<br />
<bibl>—Bashō (1644–1694)</bibl><br />
</div><br />
</syntaxhighlight><br />
<br />
Note: for the sake of simplicity, the indenting of lines in the vertical Japanese and the central alignment of the other components have been ignored in this encoding, since this section focuses on language and writing mode issues. The Japanese transcription has <code>writing-mode: vertical-rl</code>, which is required because Japanese may be written either in this mode or horizontally. The transcription in Romaji has <code>@xml:lang="ja-Latn"</code> (Japanese written in Latin script) and has a horizontal writing mode; this may seem superfluous, but vertically-written romaji is not unknown.<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
====Vertical text with embedded horizontal text====<br />
<br />
When Japanese is written vertically, the glyph orientation remains the same as when it is written horizontally. In other words, glyphs are not rotated (although as noted above some different glyphs may be used for some characters the two orientations; punctuation for instance needs to be positioned differently in vertical versus horizontal text). However, it is very common for languages written vertically to have embedded runs of text from languages normally written horizontally. This raises the issue of the orientation of the glyphs from the horizontal language. Are they written upright, as they would normally appear in horizontal text runs, or are they rotated? Consider this fragment from a Japanese article about the Indonesian language, which takes the form of a glossary list:<br />
<br />
[[File:Ja vertical indonesian frag sm.jpg|thumb|left|alt=Glossary list|Taken from p.62 of "インドネシア語". 崎山理. 1985. ''外国語との対照II''. 講座日本語学 11.]]<br />
<br />
This might be transcribed as follows:<br />
<br />
<syntaxhighlight lang="xml"><br />
<list type="gloss" xml:lang="ja" <br />
style="writing-mode: vertical-rl; text-orientation: mixed"><br />
<br />
<label xml:lang="id">hampir</label> <br />
<item>「近い、ほとんど」</item><br />
<br />
<label xml:lang="id">baru</label><br />
<item>「新しい、ばかい」</item><br />
<br />
<!-- ... --><br />
</list><br />
</syntaxhighlight><br />
<br />
The rule <code>text-orientation: mixed</code> gives the expected orientation: "In vertical writing modes, characters from horizontal-only scripts are set sideways, i.e. 90° clockwise from their standard orientation in horizontal text. Characters from vertical scripts are set with their intrinsic orientation" ([http://www.w3.org/TR/2013/WD-css-writing-modes-3-20131024/#text-orientation CSS Writing Modes]). In actual fact, the default value for <code>text-orientation</code> is "mixed", so this rule is not strictly required, but if the Indonesian glyphs had been set vertically, like this:<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
[[File:Ja vertical indonesian frag rotated sm.jpg|50px|thumb|left|alt=Glossary list|Fragment of previous image with Indonesian glyphs upright.]]<br />
<br />
then the encoding would have to be explicit, and we could capture the orientation with <code>text-orientation: upright</code>.<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
====Vertical orientation in horizontal scripts====<br />
<br />
It is not unusual to see text from horizontal languages written vertically even where it is not embedded in a text run from a vertically-written script. This example is a fragment from a table of information about agricultural development on Vancouver Island, written in 1855:<br />
<br />
[[File:bcgenesis co 305 06 00131v table extract.jpg|thumb|center|600px|alt=Agricultural report table|Enclosure with 10048, CO 305/6, p. 109 http://bcgenesis.uvic.ca/getDoc.htm?id=V55116.scx]]<br />
<br />
Four subheading cells in this fragment contain English text, written vertically, bottom-to-top, to conserve space on the page. This is not a "native orientation" for English; readers would not find it easy to read this text, and might be inclined to rotate the page in order to read it in a more natural way. To describe this sort of phenomenon, we can use the text-orientation property again:<br />
<br />
<code>text-orientation: mixed|upright|sideways-right|sideways-left|sideways|use-glyph-orientation</code><br />
<br />
For full details on this property, we refer the reader to the CSS Writing Modes specification. For the present example, we will make use only of the "sideways-left" value, which "causes text to be set as if in a horizontal layout, but rotated 90° counter-clockwise." We might encode one of the four cells containing vertical text like this:<br />
<br />
<syntaxhighlight lang="xml"><br />
<cell style="writing-mode: vertical-lr; text-orientation: sideways-left"><br />
Cash Value<lb/><br />
of<lb/><br />
Farms<br />
</cell><br />
</syntaxhighlight><br />
<br />
The <code>writing-mode</code> captures the fact that the script is written vertically, and its line/block flow is from left to right (so "of" is to the right of "Cash value"), while the <code>text-orientation</code> value encodes the orientation (rotated 90° counter-clockwise). We might also add <code>text-align: center</code> to the style, to express the fact that the text is centrally-aligned; alignment properties are mapped relative to the line flow, so the word "of" is visibly centred relative to the physical top and bottom of the box, which are the left and right from the point of view of the line flow.<br />
<br />
====Bottom-to-top writing====<br />
<br />
There are a very small number of scripts which appear to be written bottom-to-top; perhaps the most well-known is Ogham, an alphabet used mainly to write Archaic Irish. The CSS Writing Modes specification does not explicitly provide for the distinction between top-to-bottom and bottom-to-top in vertically-written scripts; it is argued that all instances of bottom-to-top scripts are actually left-to-right horizontal scripts, oriented vertically because of the constraints of the medium on which they are inscribed (as in the case of Ogham inscriptions on tombstones). In other words, the case of scripts like this is analogous to the vertical English text-runs in the table cells in the example above, and can be handled in exactly the same manner (<code>writing-mode: vertical-lr; text-orientation: sideways-left</code>).<br />
<br />
====Summary====<br />
<br />
In this section, we have presented one approach to encoding text directionality features in TEI files, using the properties and values from the CSS Writing Modes module, encoded in the global TEI @style attribute (or in the TEI <code><rendition></code> element and linked with the @rendition attribute). For most texts, it will not be necessary to encode any information about text directionality, either because it follows unambiguously from <code>@xml:lang</code> values, or because it can be expected to be handled unequivocally by the Unicode Bidi Algorithm. Where it is important to encode text directionality, we believe that most phenomena can be well described through the use of the CSS Writing Modes features; of those which cannot, other approaches based on the CSS Transforms module are presented below.<br />
<br />
===Text transformation===<br />
<br />
====Rotation====<br />
<br />
In what follows, we examine a range of textual phenomena which in some ways appear very similar to those examined above, and even overlap with them. We can categorize these as text transformation features, and suggest some strategies for encoding them based on the properties detailed in the [http://www.w3.org/TR/css3-transforms/ CSS Transforms] specification. The CSS Transforms module provides a complex array of properties, values and functions which can be used to rotate, skew, translate and otherwise transform textual and graphical objects. We can borrow this vocabulary in order to describe textual phenomena in a precise manner.<br />
<br />
We begin with a simple example of a rotational transform:<br />
<br />
[[File:Rotation_on_z_axis.png|frame]]<br />
<br />
Here a block of text has been rotated around its z-axis. This is clearly not a "writing mode"; the writing mode for this text is horizontal, left to right. Furthermore, even if we wished to treat this as a writing mode, we could not do so, because there is no way to use writing modes properties to describe an text orientation which is angled at 45 degrees; no human languages are consistently written in this orientation. It is more appropriate to treat this as a rotational transformation. We can do this using two properties: <code>transform</code> and <code>transform-origin</code>. (Both of these properties have quite complex value sets, and we will not look at all of them here. See the [http://www.w3.org/TR/css3-transforms/ specification] for full details.)<br />
<br />
The <code>transform</code> property takes as its value one or more of the transform functions, one of which is the function <code>rotateZ</code>:<br />
<br />
<syntaxhighlight lang="xml"><br />
<br />
<ab style="transform:rotateZ(-45deg)">TEI-C.ORG</ab><br />
<br />
</syntaxhighlight><br />
<br />
Any rotation must take place around an axis positioned relative to the element being rotated, and the <code>transform-origin</code> property can be used to specify the pivot point. By default, the value of <code>transform-origin</code> is "50% 50%", the point at the centre of the element, but these values can be changed to reflect rotation around a different origin point. (The TEI [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone element] also bears an attribute @rotate which can specify rotation in degrees around the z-axis, but it is not available for any other element.)<br />
<br />
An element may also be rotated about either of its other axes. For example, this shows rotation around the Y (vertical) axis:<br />
<br />
[[File:Rotation_on_y_axis.png|frame]] <br />
<br />
<syntaxhighlight lang="xml"><br />
<br />
<ab style="transform:rotateY(45deg)">TEI-C.ORG</ab><br />
<br />
</syntaxhighlight><br />
<br />
These are obviously trivial examples, but similar features do appear in historical texts. George Herbert's ''The Temple'' includes two stanzas headed "Easter Wings" which are both normally printed in a rotated form so that they represent a pair of wings:<br />
<br />
[[File:Herbert church p35 sm.jpg|thumb|left|300px|Page 35 of Herbert's ''The Temple'', second stanza of Easter Wings (or second poem so named). Used with permission of the Folger Library.]]<br />
<br />
This could be encoded thus:<br />
<br />
<syntaxhighlight lang="xml"><br />
<lg style="transform:rotateX(90deg)"><br />
<l>My tender age in ſorrow did beginne:</l><br />
<l>And ſtill with ſickneſſes and ſhame</l><br />
<!-- ... --><br />
</lg><br />
</syntaxhighlight><br />
<br />
but we might also argue that this is in fact a vertical writing mode, and express it with <code>writing-mode: vertical-rl; text-orientation: sideways-right</code>.<br />
<br />
<div style="clear: both;">&#160;</div><br />
<br />
====Boustrophedon====<br />
<br />
We may also use rotation as a method of handling a true writing mode which is not covered by the CSS Writing Modes: boustrophedon. This is a writing mode common in inscriptions in Latin, Greek and other languages, in which alternate lines run from left to right and from right to left; its name derives from the path of an ox pulling a plough. Right-to-left lines in boustrophedon have another unexpected feature: their glyphs are reversed, so that these lines appear as "mirror writing". This example shows a transcription of a Greek inscription at Dodona:<br />
<br />
[[File:Boustrophedon small J.NW.Epeiros.13.p03.jpg|thumb|left|300px|Drawing of a leaden plaque bearing an inquiry by Hermon from the oracular precinct at Dodona. Image and transcription from http://poinikastas.csad.ox.ac.uk, used with permission.]]<br />
<br />
This might be transcribed as follows (ignoring word boundaries for the moment):<br />
<br />
<syntaxhighlight lang="xml"><br />
<ab><br />
ΗΕΡΜΟΝΤΙΝΑ <lb/><br />
<seg style="rotateY(180deg)">ΚΑΘΕΟΝΠΟΤΘΕΜ</seg> <lb/><br />
ΕΝΟΣΥΕΝΕΑϜ <lb/><br />
<seg style="rotateY(180deg)">ΟΙΥΕΝΟΙΤΙΕΚΚ</seg> <lb/><br />
ΡΕΤΑΙΑΣΟΝΑ <lb/><br />
<seg style="rotateY(180deg)">ΣΙΜΟΣΟΤΤΑΙΕ</seg> <lb/><br />
ΑΣΣΑΙ<br />
</ab><br />
</syntaxhighlight><br />
<br />
The 180-degree rotation around the Y (vertical) axis here gives us exactly the effect of the RTL line in boustrophedon; the order of glyphs is reversed, and so is their individual orientation (in fact, we see them "from the back", as it were). <code><seg></code> elements have been used here because these are clearly not "lines" in the sense of poetic lines; the text is continuous prose, and linebreaks are incidental.<br />
<br />
There are obviously some unsatisfactory aspects of this manner of encoding boustrophedon. In the inscription above, some words run across linebreaks, so if we wished to tag both words and the right-to-left phenomena, one hierarchy would have to be privileged over the other. By using a transform function rather than a writing mode property, we are apparently suggesting that boustrophedon is not in fact a writing mode, whereas it clearly is. But the CSS Writing Modes specification does not provide support for boustrophedon, because it is a rather obscure historical phenomenon; using a rotational transform is one practical alternative.<br />
<br />
<div style="clear: both;">&#160;</div><br />
<br />
====Caveats====<br />
<br />
The effect and behaviour of CSS Transforms properties and values according to the specification are highly dependent on the computed [http://www.w3.org/TR/CSS2/visuren.html Visual formatting model] of an HTML document. TEI currently does not have an explicit processing or formatting model. That is, it is by no means clear whether any given TEI element should be interpreted, for instance, as a block-level or inline-level element; for many elements we may think we can assume block-level (<code><ab></code>, "anonymous block") or inline-level (<code><w></code>, "word") from the semantics, but even this is risky. As long as the properties and values from the CSS Transforms module are used as a convenient, well-specified descriptive language to capture features of a text, without any expectation of using them directly and reliably for rendering, this is not problematic; we are simply borrowing a useful vocabulary from an external source, and benefiting from the clarity of definition provided by the specification. However, if there is any expectation of using this information to render a text in a predictable and accurate way, it will be essential to provide enough styling information throughout the document hierarchy to resolve all ambiguities with regard to size, positioning, block status, etc. before any element undergoes a transform operation.<br />
<br />
<references/><br />
<br />
<br />
<br />
<br />
[[Category:Council]]</div>Marcushttps://wiki.tei-c.org/index.php?title=Text_Directionality_Draft&diff=12737Text Directionality Draft2013-11-29T16:18:16Z<p>Marcus: /* Introduction */</p>
<hr />
<div>This is a preliminary draft of proposed sections for the TEI Guidelines, created by the [[Text Directionality Workgroup]]. Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions. There is also a [[Talk:Text_Directionality_Draft|talk page]] for more informal discussion.<br />
<br />
==Text directionality and transformation==<br />
<br />
===Introduction===<br />
<br />
Scripts used for writing human languages vary not only in the glyphs they use, but also in the direction in which these glyphs are to be read. The majority of modern languages are written from left to right within the line, and have their lines stacked from top to bottom vertically (English, Russian, Greek), but there are several widely-used scripts which run right-to-left (Arabic, Hebrew), while also stacking lines top-to-bottom. East Asian scripts (Sinitic characters, Japanese Kana, Korean Hangul, Vietnamese chữ nôm) were traditionally written from top to bottom within the line, with their lines sequenced from right to left. There are a few cases of bottom-to-top writing, such as Ancient Berber, and some Ogham inscriptions; there are even instances of writing which changes direction on alternate lines (boustrophedon, discussed in detail below). <br />
<br />
When a language or script can be arranged in two or more different directions, there are often other consequences arising out of the choice; for example, when Japanese is written horizontally, the Unicode character U+3001, the "ideographic comma", is used, whereas in vertical writing an alternative glyph, U+FE11, may be used to ensure that the comma appears in the correct position relative to the surrounding glyphs. In addition, scripts which normally have a single directionality (such as English) may be written in a different direction in the context of another language (English words inserted into vertical Chinese text, for example), or in response to layout constraints such as those imposed by a complex table, in which column or row labels may be written vertically to make the most effective use of available space.<br />
<br />
The directionality features of scripts, and the consequences arising out of them, are generally referred to as "writing modes". For many documents encoded in TEI, there may be no need to encode any information relating to writing mode, because it will be obvious. Modern printed texts in most European languages, for instance, may be expected to use left-to-right/top-to-bottom directionality; Arabic or Hebrew texts are expected to run right-to-left/top-to-bottom. It may appear that directionality can be reliably deduced from the language and script settings, and these are probably already encoded using the @xml:lang attribute in TEI documents (although the W3C i18n Working Group recommends against reliance on language tags for encoding directionality information [per Richard Ishida, W3C; I need to find a formal reference for this]). Even in the case of many "mixed mode" documents (documents in which languages or scripts with different writing modes are mixed together), it may not be necessary to be explicit about directionality. Consider the case of an English text containing a few Arabic words--what is termed a "bidirectional" text:<br />
<br />
<code>The Arabic term قلم رصاص means "pencil".</code><br />
<br />
Since Arabic is always written from right to left, we can assume that the Arabic glyphs are to be read in that direction, even if they are in the context of a left-to-right English sentence. In fact, most codepoints in the Unicode standard have a specific directionality setting which helps any rendering engine to determine how they should be ordered. The Latin glyph "a" has a bidirectionality setting of strong left-to-right; the Hebrew א (alef) is strongly right-to-left. Other glyphs have weak or neutral settings because of the contexts in which they may appear. The Unicode Bidirectional Algorithm (http://www.unicode.org/reports/tr9/) provides a complex series of rules enabling user agents to render most mixed-mode texts with predictable and reliable results, based on the bidirectionality class values of their glyphs.<br />
<br />
In some mixed-mode texts, though, the Bidirectional Algorithm may not give the desired results. To deal with this, Unicode provides a set of "directional formatting characters" (http://www.unicode.org/reports/tr9/#Directional_Formatting_Codes), also called "bidi formatting code characters", which are additional codepoints whose only function is to signal to a user-agent that a specific directionality setting should be turned on or off. These can be inserted into a text to influence the outcome of the bidirectional algorithm. However, in the case of documents encoded in XML, the W3C explicitly advises that markup rather than directional formatting characters should be used ("In (X)HTML and XML do not use the paired Unicode bidi formatting code characters where equivalent markup is available," http://www.w3.org/International/questions/qa-bidi-controls). We concur with this recommendation, and the remainder of this section and the next provide a set of encoding strategies for handling text directionality without the use of directional formatting characters. The approach we recommend is based on two external specifications, in line with our normal practice of incorporating existing standards where they are available and appropriate. Those specifications are the CSS Writing Modes module (http://dev.w3.org/csswg/css-writing-modes/) and the CSS Transforms module (http://www.w3.org/TR/css3-transforms/). Since (at the time of writing) neither of these modules has yet reached the stage of a Recommendation, the advice offered below should be regarded as provisional, and you should check your usage of the properties concerned against the current version of each specification where possible. <br />
<br />
The following sections will present a few simple examples of phenomena relating to text directionality and transformation, along with some suggested encoding strategies based on the following CSS properties from CSS Writing Modes:<br />
<br />
<code><br />
direction: ltr | rtl<br/><br />
writing-mode: horizontal-tb | vertical-rl | vertical-lr<br/><br />
text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation<ref>The value "use-glyph-orientation" may be dropped from the CSS Writing Modes specification.</ref><br/><br />
unicode-bidi: normal | embed | isolate | bidi-override | isolate-override | plaintext<br />
</code><br />
<br />
along with the <code>transform</code> property from CSS Transforms.<br />
<br />
In the following examples, CSS rules are encoded in the global TEI @style attribute, which applies them directly to the element on which they are specified (and in most cases, its descendants). It is also appropriate, and will often be more efficient, to express the rules in TEI <rendition> elements in the <teiHeader> and point to them using @rendition attributes. It should also be remembered that the CSS specifications are written primarily to guide users providing instructions for the rendering of digital texts, and implementers creating user-agents which will act on these instructions. However, our usage in the context of a TEI document is primarily ''descriptive'' rather than ''prescriptive''; we are typically describing the features of a text we are encoding, rather than providing instructions for rendering it. Our purpose below is not to enumerate an exhaustive set of strategies for encoding any writing mode feature you may encounter; rather we will show some simple examples which serve as an introduction to the topic.<br />
<br />
===Text directionality===<br />
<br />
====Horizontal directionality====<br />
<br />
Returning to our previous simple example<br />
<br />
<code>The Arabic term قلم رصاص means "pencil".</code><br />
<br />
we could use the <code>direction</code> property to make directionality explicit:<br />
<br />
<code>direction: ltr | rtl</code><br />
<br />
<syntaxhighlight lang="xml"><br />
<seg xml:lang="en" style="direction: ltr">The Arabic term </seg><br />
<seg xml:lang="ar" style="unicode-bidi: embed; direction: rtl">قلم رصاص</seg> <br />
<seg xml:lang="en" style="direction: ltr">means "pencil".</seg><br />
</syntaxhighlight><br />
<br />
The use of the <code>direction</code> property is straightforward, but the <code>unicode-bidi</code> property requires some explanation. These three segments are all inline; they form part of a single sentence, although they happen to be encoded on separate lines in this example. The default value for <code>unicode-bidi</code> is "normal", and the CSS Writing Modes specification stipulates that the <code>direction</code> property "has no effect on bidi reordering when specified on inline elements whose unicode-bidi property’s value is normal, because the element does not open an additional level of embedding with respect to the bidirectional algorithm." In other words, if we want to make it clear that the <code>direction</code> property is effective here, we must include a value for <code>unicode-bidi</code> which will make it so.<br />
<br />
However, as mentioned above, all of the directional encoding in this example is superfluous; ambiguity does not arise in this particular case. Moreover, "ltr" is the default value for the <code>direction</code> property, so we do not need to specify it for the English segments. However, consider the following example, contributed by Efraim Feinstein, in which Hebrew and English text are mixed. (This example is presented in the form of graphics, because we cannot rely on user agents that may be rendering or displaying these Guidelines to provide a consistent output.)<br />
<br />
[[File:En he embedding.png|800px]]<br />
<br />
Here, an English period appears in between two runs of Hebrew text. Should that period be interpreted as part of a single run of right-to-left text, or should it be deemed to terminate the first run and precede the second? For the Unicode Bidi Algorithm, punctuation is not strongly directional; it inherits directionality from the surrounding characters. Without further clues, therefore, it would interpret the example as a sequence of three runs (English, Hebrew, English), and arrive at an incorrect interpretation. A clear and correct interpretation requires that not only that the glyphs themselves be transcribed in the correct logical order, but that the encoding eliminate potential ambiguity by delimiting the two Hebrew runs separately, like this:<br />
<br />
<syntaxhighlight lang="xml"><br />
<p><br />
Here's a sentence that begins in English<br />
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ויש מלים בעברית והפסק</seg>.<br />
<seg xml:lang="he" style="unicode-bidi: isolate; direction: rtl">ועוד מלים בעברית</seg><br />
and it continues in English.<br />
</p><br />
</syntaxhighlight><br />
<br />
Here the English is unmarked for directionality, but the period is clearly not included in either of the RTL runs, so the ambiguity inherent in the plain text is avoided. Once again, we might argue that the <code>@xml:lang</code> attribute should provide enough information; the important component here is the explicit delimitation of two distinct RTL runs. But additional clarity in the encoding certainly does no harm.<br />
<br />
[Would it be helpful to have another example presenting ambiguity arising out of the use of a g element at the end of a text run?]<br />
<br />
====Vertical writing modes====<br />
<br />
So far, we have looked only at left-to-right and right-to-left text running horizontally, using the <code>direction: ltr|rtl</code> property. However, there are many scripts and languages which are written vertically (mostly top-to-bottom, but with a few unusal examples running bottom-to-top, as we shall see below). Handling vertical directionality requires the use of another CSS property, the writing mode:<br />
<br />
<code>writing-mode: horizontal-tb | vertical-rl | vertical-lr</code><br />
<br />
The values for this property include two components: "horizontal" or "vertical" specifies the inline writing direction, while the second component specifies the direction in which lines in a block, and blocks in a sequence may be arranged: from top to bottom (as in most European languages, in which lines and paragraphs are arranged from top to bottom on a page), from right to left (as in the case of some East Asian languages such as Japanese, which we will see below), or left-to-right (e.g. Mongolian). This example shows a Japanese haiku poem transcribed first in Japanese, then in Romaji (Japanese in Latin script), and finally in an English translation. <br />
<br />
[[File:Basho_furu_ike_ya.png|thumb|left|alt=Basho poem|Taken from p.42 of ''Haiku: Japanese Art and Poetry''. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. Used with permission.]]<br />
<br />
<syntaxhighlight lang="xml"><br />
<div><br />
<ab xml:lang="ja" style="writing-mode: vertical-rl" <br />
xml:id="furu-ike-ya_jp" corresp="#furu-ike-ya_romaji #furu-ike-ya_en"><br />
古池や<lb/><br />
蛙<lb/><br />
飛び込む<lb/><br />
水の音<br />
</ab><br />
<br />
<lg xml:lang="ja-Latn" style="writing-mode: horizontal-tb" <br />
xml:id="furu-ike-ya_romaji" corresp="#furu-ike-ya_jp #furu-ike-ya_en"> <br />
<l>furu ike ya</l><br />
<l>kawazu tobikomu</l><br />
<l>mizu no oto</l><br />
</lg><br />
<br />
<lg xml:lang="en" <br />
xml:id="furu-ike-ya_en" corresp="#furu-ike-ya_jp #furu-ike-ya_romaji"><br />
<l>Old pond,</l><br />
<l>and a frog dives in—</l><br />
<l>"Splash"!</l><br />
</lg><br />
<br />
<bibl>—Bashō (1644–1694)</bibl><br />
</div><br />
</syntaxhighlight><br />
<br />
Note: for the sake of simplicity, the indenting of lines in the vertical Japanese and the central alignment of the other components have been ignored in this encoding, since this section focuses on language and writing mode issues. The Japanese transcription has <code>writing-mode: vertical-rl</code>, which is required because Japanese may be written either in this mode or horizontally. The transcription in Romaji has <code>@xml:lang="ja-Latn"</code> (Japanese written in Latin script) and has a horizontal writing mode; this may seem superfluous, but vertically-written romaji is not unknown.<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
====Vertical text with embedded horizontal text====<br />
<br />
When Japanese is written vertically, the glyph orientation remains the same as when it is written horizontally. In other words, glyphs are not rotated (although as noted above some different glyphs may be used for some characters the two orientations; punctuation for instance needs to be positioned differently in vertical versus horizontal text). However, it is very common for languages written vertically to have embedded runs of text from languages normally written horizontally. This raises the issue of the orientation of the glyphs from the horizontal language. Are they written upright, as they would normally appear in horizontal text runs, or are they rotated? Consider this fragment from a Japanese article about the Indonesian language, which takes the form of a glossary list:<br />
<br />
[[File:Ja vertical indonesian frag sm.jpg|thumb|left|alt=Glossary list|Taken from p.62 of "インドネシア語". 崎山理. 1985. ''外国語との対照II''. 講座日本語学 11.]]<br />
<br />
This might be transcribed as follows:<br />
<br />
<syntaxhighlight lang="xml"><br />
<list type="gloss" xml:lang="ja" <br />
style="writing-mode: vertical-rl; text-orientation: mixed"><br />
<br />
<label xml:lang="id">hampir</label> <br />
<item>「近い、ほとんど」</item><br />
<br />
<label xml:lang="id">baru</label><br />
<item>「新しい、ばかい」</item><br />
<br />
<!-- ... --><br />
</list><br />
</syntaxhighlight><br />
<br />
The rule <code>text-orientation: mixed</code> gives the expected orientation: "In vertical writing modes, characters from horizontal-only scripts are set sideways, i.e. 90° clockwise from their standard orientation in horizontal text. Characters from vertical scripts are set with their intrinsic orientation" ([http://www.w3.org/TR/2013/WD-css-writing-modes-3-20131024/#text-orientation CSS Writing Modes]). In actual fact, the default value for <code>text-orientation</code> is "mixed", so this rule is not strictly required, but if the Indonesian glyphs had been set vertically, like this:<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
[[File:Ja vertical indonesian frag rotated sm.jpg|50px|thumb|left|alt=Glossary list|Fragment of previous image with Indonesian glyphs upright.]]<br />
<br />
then the encoding would have to be explicit, and we could capture the orientation with <code>text-orientation: upright</code>.<br />
<br />
<div style="clear: both">&#160;</div><br />
<br />
====Vertical orientation in horizontal scripts====<br />
<br />
It is not unusual to see text from horizontal languages written vertically even where it is not embedded in a text run from a vertically-written script. This example is a fragment from a table of information about agricultural development on Vancouver Island, written in 1855:<br />
<br />
[[File:bcgenesis co 305 06 00131v table extract.jpg|thumb|center|600px|alt=Agricultural report table|Enclosure with 10048, CO 305/6, p. 109 http://bcgenesis.uvic.ca/getDoc.htm?id=V55116.scx]]<br />
<br />
Four subheading cells in this fragment contain English text, written vertically, bottom-to-top, to conserve space on the page. This is not a "native orientation" for English; readers would not find it easy to read this text, and might be inclined to rotate the page in order to read it in a more natural way. To describe this sort of phenomenon, we can use the text-orientation property again:<br />
<br />
<code>text-orientation: mixed|upright|sideways-right|sideways-left|sideways|use-glyph-orientation</code><br />
<br />
For full details on this property, we refer the reader to the CSS Writing Modes specification. For the present example, we will make use only of the "sideways-left" value, which "causes text to be set as if in a horizontal layout, but rotated 90° counter-clockwise." We might encode one of the four cells containing vertical text like this:<br />
<br />
<syntaxhighlight lang="xml"><br />
<cell style="writing-mode: vertical-lr; text-orientation: sideways-left"><br />
Cash Value<lb/><br />
of<lb/><br />
Farms<br />
</cell><br />
</syntaxhighlight><br />
<br />
The <code>writing-mode</code> captures the fact that the script is written vertically, and its line/block flow is from left to right (so "of" is to the right of "Cash value"), while the <code>text-orientation</code> value encodes the orientation (rotated 90° counter-clockwise). We might also add <code>text-align: center</code> to the style, to express the fact that the text is centrally-aligned; alignment properties are mapped relative to the line flow, so the word "of" is visibly centred relative to the physical top and bottom of the box, which are the left and right from the point of view of the line flow.<br />
<br />
====Bottom-to-top writing====<br />
<br />
There are a very small number of scripts which appear to be written bottom-to-top; perhaps the most well-known is Ogham, an alphabet used mainly to write Archaic Irish. The CSS Writing Modes specification does not explicitly provide for the distinction between top-to-bottom and bottom-to-top in vertically-written scripts; it is argued that all instances of bottom-to-top scripts are actually left-to-right horizontal scripts, oriented vertically because of the constraints of the medium on which they are inscribed (as in the case of Ogham inscriptions on tombstones). In other words, the case of scripts like this is analogous to the vertical English text-runs in the table cells in the example above, and can be handled in exactly the same manner (<code>writing-mode: vertical-lr; text-orientation: sideways-left</code>).<br />
<br />
====Summary====<br />
<br />
In this section, we have presented one approach to encoding text directionality features in TEI files, using the properties and values from the CSS Writing Modes module, encoded in the global TEI @style attribute (or in the TEI <code><rendition></code> element and linked with the @rendition attribute). For most texts, it will not be necessary to encode any information about text directionality, either because it follows unambiguously from <code>@xml:lang</code> values, or because it can be expected to be handled unequivocally by the Unicode Bidi Algorithm. Where it is important to encode text directionality, we believe that most phenomena can be well described through the use of the CSS Writing Modes features; of those which cannot, other approaches based on the CSS Transforms module are presented below.<br />
<br />
===Text transformation===<br />
<br />
====Rotation====<br />
<br />
In what follows, we examine a range of textual phenomena which in some ways appear very similar to those examined above, and even overlap with them. We can categorize these as text transformation features, and suggest some strategies for encoding them based on the properties detailed in the [http://www.w3.org/TR/css3-transforms/ CSS Transforms] specification. The CSS Transforms module provides a complex array of properties, values and functions which can be used to rotate, skew, translate and otherwise transform textual and graphical objects. We can borrow this vocabulary in order to describe textual phenomena in a precise manner.<br />
<br />
We begin with a simple example of a rotational transform:<br />
<br />
[[File:Rotation_on_z_axis.png|frame]]<br />
<br />
Here a block of text has been rotated around its z-axis. This is clearly not a "writing mode"; the writing mode for this text is horizontal, left to right. Furthermore, even if we wished to treat this as a writing mode, we could not do so, because there is no way to use writing modes properties to describe an text orientation which is angled at 45 degrees; no human languages are consistently written in this orientation. It is more appropriate to treat this as a rotational transformation. We can do this using two properties: <code>transform</code> and <code>transform-origin</code>. (Both of these properties have quite complex value sets, and we will not look at all of them here. See the [http://www.w3.org/TR/css3-transforms/ specification] for full details.)<br />
<br />
The <code>transform</code> property takes as its value one or more of the transform functions, one of which is the function <code>rotateZ</code>:<br />
<br />
<syntaxhighlight lang="xml"><br />
<br />
<ab style="transform:rotateZ(-45deg)">TEI-C.ORG</ab><br />
<br />
</syntaxhighlight><br />
<br />
Any rotation must take place around an axis positioned relative to the element being rotated, and the <code>transform-origin</code> property can be used to specify the pivot point. By default, the value of <code>transform-origin</code> is "50% 50%", the point at the centre of the element, but these values can be changed to reflect rotation around a different origin point. (The TEI [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone element] also bears an attribute @rotate which can specify rotation in degrees around the z-axis, but it is not available for any other element.)<br />
<br />
An element may also be rotated about either of its other axes. For example, this shows rotation around the Y (vertical) axis:<br />
<br />
[[File:Rotation_on_y_axis.png|frame]] <br />
<br />
<syntaxhighlight lang="xml"><br />
<br />
<ab style="transform:rotateY(45deg)">TEI-C.ORG</ab><br />
<br />
</syntaxhighlight><br />
<br />
These are obviously trivial examples, but similar features do appear in historical texts. George Herbert's ''The Temple'' includes two stanzas headed "Easter Wings" which are both normally printed in a rotated form so that they represent a pair of wings:<br />
<br />
[[File:Herbert church p35 sm.jpg|thumb|left|300px|Page 35 of Herbert's ''The Temple'', second stanza of Easter Wings (or second poem so named). Used with permission of the Folger Library.]]<br />
<br />
This could be encoded thus:<br />
<br />
<syntaxhighlight lang="xml"><br />
<lg style="transform:rotateX(90deg)"><br />
<l>My tender age in ſorrow did beginne:</l><br />
<l>And ſtill with ſickneſſes and ſhame</l><br />
<!-- ... --><br />
</lg><br />
</syntaxhighlight><br />
<br />
but we might also argue that this is in fact a vertical writing mode, and express it with <code>writing-mode: vertical-rl; text-orientation: sideways-right</code>.<br />
<br />
<div style="clear: both;">&#160;</div><br />
<br />
====Boustrophedon====<br />
<br />
We may also use rotation as a method of handling a true writing mode which is not covered by the CSS Writing Modes: boustrophedon. This is a writing mode common in inscriptions in Latin, Greek and other languages, in which alternate lines run from left to right and from right to left; its name derives from the path of an ox pulling a plough. Right-to-left lines in boustrophedon have another unexpected feature: their glyphs are reversed, so that these lines appear as "mirror writing". This example shows a transcription of a Greek inscription at Dodona:<br />
<br />
[[File:Boustrophedon small J.NW.Epeiros.13.p03.jpg|thumb|left|300px|Drawing of a leaden plaque bearing an inquiry by Hermon from the oracular precinct at Dodona. Image and transcription from http://poinikastas.csad.ox.ac.uk, used with permission.]]<br />
<br />
This might be transcribed as follows (ignoring word boundaries for the moment):<br />
<br />
<syntaxhighlight lang="xml"><br />
<ab><br />
ΗΕΡΜΟΝΤΙΝΑ <lb/><br />
<seg style="rotateY(180deg)">ΚΑΘΕΟΝΠΟΤΘΕΜ</seg> <lb/><br />
ΕΝΟΣΥΕΝΕΑϜ <lb/><br />
<seg style="rotateY(180deg)">ΟΙΥΕΝΟΙΤΙΕΚΚ</seg> <lb/><br />
ΡΕΤΑΙΑΣΟΝΑ <lb/><br />
<seg style="rotateY(180deg)">ΣΙΜΟΣΟΤΤΑΙΕ</seg> <lb/><br />
ΑΣΣΑΙ<br />
</ab><br />
</syntaxhighlight><br />
<br />
The 180-degree rotation around the Y (vertical) axis here gives us exactly the effect of the RTL line in boustrophedon; the order of glyphs is reversed, and so is their individual orientation (in fact, we see them "from the back", as it were). <code><seg></code> elements have been used here because these are clearly not "lines" in the sense of poetic lines; the text is continuous prose, and linebreaks are incidental.<br />
<br />
There are obviously some unsatisfactory aspects of this manner of encoding boustrophedon. In the inscription above, some words run across linebreaks, so if we wished to tag both words and the right-to-left phenomena, one hierarchy would have to be privileged over the other. By using a transform function rather than a writing mode property, we are apparently suggesting that boustrophedon is not in fact a writing mode, whereas it clearly is. But the CSS Writing Modes specification does not provide support for boustrophedon, because it is a rather obscure historical phenomenon; using a rotational transform is one practical alternative.<br />
<br />
<div style="clear: both;">&#160;</div><br />
<br />
====Caveats====<br />
<br />
The effect and behaviour of CSS Transforms properties and values according to the specification are highly dependent on the computed [http://www.w3.org/TR/CSS2/visuren.html Visual formatting model] of an HTML document. TEI currently does not have an explicit processing or formatting model. That is, it is by no means clear whether any given TEI element should be interpreted, for instance, as a block-level or inline-level element; for many elements we may think we can assume block-level (<code><ab></code>, "anonymous block") or inline-level (<code><w></code>, "word") from the semantics, but even this is risky. As long as the properties and values from the CSS Transforms module are used as a convenient, well-specified descriptive language to capture features of a text, without any expectation of using them directly and reliably for rendering, this is not problematic; we are simply borrowing a useful vocabulary from an external source, and benefiting from the clarity of definition provided by the specification. However, if there is any expectation of using this information to render a text in a predictable and accurate way, it will be essential to provide enough styling information throughout the document hierarchy to resolve all ambiguities with regard to size, positioning, block status, etc. before any element undergoes a transform operation.<br />
<br />
<references/><br />
<br />
<br />
<br />
<br />
[[Category:Council]]</div>Marcushttps://wiki.tei-c.org/index.php?title=Talk:Text_Directionality_Draft&diff=12736Talk:Text Directionality Draft2013-11-29T15:52:57Z<p>Marcus: /* Attribution */</p>
<hr />
<div>Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions.<br />
<br />
== Attribution ==<br />
<br />
Sometimes one well-chosen example organizes an entire section, or even chapter, and is a guarantee of success. In cases where such an example comes from a helpful soul that is not automatically credited in the wiki article history, it's good to provide the attribution immediately, for fear that the contribution gets forgotten and some awkwardness may ensue, in the end. I'm sure the final version would mention Efraim Feinstein as the source of the Hebrew example, but we know how sometimes drafts get stalled and all. I suggest to go ahead and attribute at once, as a general principle. Great read, by the way, and very enlightening -- thanks! [[User:Piotr Banski|Piotr]] 13:17, 6 November 2013 (EST)<br />
<br />
Thanks Piotr -- I agree completely, and I've added the attribution. I'm not sure whether an attribution like this should make it into the final Guidelines prose, though -- I don't remember any examples of that in the existing prose, and even Guidelines sections are (correctly) not attributed to individual authors. Richard Ishida from the W3C has also provided some helpful guidance, as have the other members of the workgroup of course.<br />
:Hi Martin, good point about the Guidelines themselves, where maintaining attributions across the evolving text would lead to a mess and maybe bile as well. There's no good solution that comes to my mind apart from the admittedly meagre one to credit while inside wiki and "clean" the prose of attributions when ready to transfer, but that idea suffers from many problems. Possibly, the only useful outcome of our conversation is the justification for the lack of attribution... (sigh). [[User:Piotr Banski|Piotr]] 09:30, 7 November 2013 (EST)<br />
<br />
I second Martin's and Piotr's take on attribution. Contributing to the guidelines in progress is not something which generates (academic) credit. I therefore believe it is not necessary to include the origin of even the more interesting examples. Still we need to make sure all images, examples etc. are properly licensed.--[[User:Marcus|Marcus]] 10:51, 29 November 2013 (EST)</div>Marcushttps://wiki.tei-c.org/index.php?title=Talk:Text_Directionality_Draft&diff=12735Talk:Text Directionality Draft2013-11-29T15:52:22Z<p>Marcus: /* Attribution */</p>
<hr />
<div>Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions.<br />
<br />
== Attribution ==<br />
<br />
Sometimes one well-chosen example organizes an entire section, or even chapter, and is a guarantee of success. In cases where such an example comes from a helpful soul that is not automatically credited in the wiki article history, it's good to provide the attribution immediately, for fear that the contribution gets forgotten and some awkwardness may ensue, in the end. I'm sure the final version would mention Efraim Feinstein as the source of the Hebrew example, but we know how sometimes drafts get stalled and all. I suggest to go ahead and attribute at once, as a general principle. Great read, by the way, and very enlightening -- thanks! [[User:Piotr Banski|Piotr]] 13:17, 6 November 2013 (EST)<br />
<br />
Thanks Piotr -- I agree completely, and I've added the attribution. I'm not sure whether an attribution like this should make it into the final Guidelines prose, though -- I don't remember any examples of that in the existing prose, and even Guidelines sections are (correctly) not attributed to individual authors. Richard Ishida from the W3C has also provided some helpful guidance, as have the other members of the workgroup of course.<br />
:Hi Martin, good point about the Guidelines themselves, where maintaining attributions across the evolving text would lead to a mess and maybe bile as well. There's no good solution that comes to my mind apart from the admittedly meagre one to credit while inside wiki and "clean" the prose of attributions when ready to transfer, but that idea suffers from many problems. Possibly, the only useful outcome of our conversation is the justification for the lack of attribution... (sigh). [[User:Piotr Banski|Piotr]] 09:30, 7 November 2013 (EST)<br />
<br />
I second Martin's and Piotr's take on attribution. Contributing to the guidelines in progress is not something which generates (academic) credit. I therefore believe it is not necessary to include the origin of even the more interesting examples. Still we probably need to make sure all images etc. are properly licensed.--[[User:Marcus|Marcus]] 10:51, 29 November 2013 (EST)</div>Marcushttps://wiki.tei-c.org/index.php?title=Talk:Text_Directionality_Draft&diff=12734Talk:Text Directionality Draft2013-11-29T15:51:45Z<p>Marcus: /* Attribution */</p>
<hr />
<div>Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions.<br />
<br />
== Attribution ==<br />
<br />
Sometimes one well-chosen example organizes an entire section, or even chapter, and is a guarantee of success. In cases where such an example comes from a helpful soul that is not automatically credited in the wiki article history, it's good to provide the attribution immediately, for fear that the contribution gets forgotten and some awkwardness may ensue, in the end. I'm sure the final version would mention Efraim Feinstein as the source of the Hebrew example, but we know how sometimes drafts get stalled and all. I suggest to go ahead and attribute at once, as a general principle. Great read, by the way, and very enlightening -- thanks! [[User:Piotr Banski|Piotr]] 13:17, 6 November 2013 (EST)<br />
<br />
Thanks Piotr -- I agree completely, and I've added the attribution. I'm not sure whether an attribution like this should make it into the final Guidelines prose, though -- I don't remember any examples of that in the existing prose, and even Guidelines sections are (correctly) not attributed to individual authors. Richard Ishida from the W3C has also provided some helpful guidance, as have the other members of the workgroup of course.<br />
:Hi Martin, good point about the Guidelines themselves, where maintaining attributions across the evolving text would lead to a mess and maybe bile as well. There's no good solution that comes to my mind apart from the admittedly meagre one to credit while inside wiki and "clean" the prose of attributions when ready to transfer, but that idea suffers from many problems. Possibly, the only useful outcome of our conversation is the justification for the lack of attribution... (sigh). [[User:Piotr Banski|Piotr]] 09:30, 7 November 2013 (EST)<br />
<br />
I second Martin's and Piotr's take on attribution. Contributing to the guidelines guidelines in progress is not something which generates academic credit. I therefore believe it is not necessary to include the origin of even the more interesting examples. Still we probably need to make sure all images etc. are properly licensed.--[[User:Marcus|Marcus]] 10:51, 29 November 2013 (EST)</div>Marcushttps://wiki.tei-c.org/index.php?title=Talk:Text_Directionality_Draft&diff=12733Talk:Text Directionality Draft2013-11-29T15:50:26Z<p>Marcus: /* Attribution */</p>
<hr />
<div>Please see the associated [[Text Directionality Draft Questions]] document for some issues to think about before and after reading this draft, and feel free to respond there and to add new questions.<br />
<br />
== Attribution ==<br />
<br />
Sometimes one well-chosen example organizes an entire section, or even chapter, and is a guarantee of success. In cases where such an example comes from a helpful soul that is not automatically credited in the wiki article history, it's good to provide the attribution immediately, for fear that the contribution gets forgotten and some awkwardness may ensue, in the end. I'm sure the final version would mention Efraim Feinstein as the source of the Hebrew example, but we know how sometimes drafts get stalled and all. I suggest to go ahead and attribute at once, as a general principle. Great read, by the way, and very enlightening -- thanks! [[User:Piotr Banski|Piotr]] 13:17, 6 November 2013 (EST)<br />
<br />
Thanks Piotr -- I agree completely, and I've added the attribution. I'm not sure whether an attribution like this should make it into the final Guidelines prose, though -- I don't remember any examples of that in the existing prose, and even Guidelines sections are (correctly) not attributed to individual authors. Richard Ishida from the W3C has also provided some helpful guidance, as have the other members of the workgroup of course.<br />
:Hi Martin, good point about the Guidelines themselves, where maintaining attributions across the evolving text would lead to a mess and maybe bile as well. There's no good solution that comes to my mind apart from the admittedly meagre one to credit while inside wiki and "clean" the prose of attributions when ready to transfer, but that idea suffers from many problems. Possibly, the only useful outcome of our conversation is the justification for the lack of attribution... (sigh). [[User:Piotr Banski|Piotr]] 09:30, 7 November 2013 (EST)<br />
<br />
I second Martin's and Piotr's take on attribution. Contributing to the guidelines guidelines in progress is not something which generates academic credit. I therefore believe it is not necessary to include the origin of even the more interesting examples. Still we probably need to make sure all images etc. are properly licensed.</div>Marcushttps://wiki.tei-c.org/index.php?title=Text_Directionality_Workgroup&diff=11584Text Directionality Workgroup2013-01-10T14:20:58Z<p>Marcus: /* Rotation */</p>
<hr />
<div>== Text Directionality Workgroup ==<br />
<br />
This page will summarize the evolving work of the Text Directionality Workgroup, tasked by the TEI Council with developing a new section for the Guidelines on recommendations for encoding a variety of textual features related to text directionality and orientation. The related SourceForge ticket is http://purl.org/tei/fr/3475007.<br />
<br />
===Workgroup Members===<br />
<br />
*Martin Holmes (TEI Council)<br />
*Deborah W. Anderson (Unicode Consortium)<br />
*Robert Whalen (Northern Michigan University)<br />
*Marcus Bingenheimer (Temple University)<br />
*Stella Dee (King's College, London)<br />
<br />
===Order of Tasks===<br />
<br />
*Enumerate textual features to be covered<br />
*Collate existing standards and recommendations and relate them to features<br />
*Identify any gaps which might require new TEI elements or attributes<br />
*Outline the new section<br />
*Write the first draft for consideration by Council<br />
*Identify other places in the Guidelines where information or links need to be included<br />
<br />
===Mailing List===<br />
<br />
The group has a mailing list provided through Brown University at [http://listserv.brown.edu/archives/cgi-bin/wa?A0=TEI-DIR-WG http://listserv.brown.edu/archives/cgi-bin/wa?A0=TEI-DIR-WG].<br />
<br />
===Notes from initial discussions===<br />
<br />
*We agree (so far) that we would like to distinguish between two distinct types of phenomena: "true" text directionality (such as that found in language such as Japanese written vertically ttb with lines sequence rtl -- and "rotational" features, in which text written in any direction is rotated or written along a path. Our proposal will have to cover both of these phenomena, and provide for cases in which they interact, but they will probably be handled by different mechanisms.<br />
<br />
*We agree that the ITS specification is rather a red herring. Its primary concern is translation rather than text representation, and its provisions for directionality are sparse.<br />
<br />
*We agree that the [http://dev.w3.org/csswg/css3-writing-modes/ CSS Writing Modes] draft provides the best descriptive introduction to directional phenomena.<br />
<br />
===Examples, constructed and from primary sources===<br />
<br />
This section collects together some examples which our discussion can reference. We aim to collect useful examples of some straightforward cases, but also of some edge cases which our proposal must be able to handle. Some of these may be used as examples in a final draft of the new section of the Guidelines. These are listed in no particular order.<br />
<br />
====Text directionality====<br />
<br />
*[http://en.wikipedia.org/wiki/Boustrophedon Wikipedia] has some good examples of Boustrophedon (alternate lines running in different directions, with glyphs also flipped horizontally for rtl lines).<br />
*[http://lbi-project.org/inscr_data.php?site=CHEN1&inscr=28 Ancient Berber] is an example of a script written bottom-to-top, with lines right-to-left.<br />
*[http://lbi-project.org/inscr_data.php?site=BOUK2&inscr=1 This Berber inscription] also incorporates rotation, so we could demonstrate the combination.<br />
<br />
<br />
====Rotation====<br />
<br />
*Rotation along X axis: [[File:Rotation_on_x_axis.png]] "tei-c.org" 180 deg: "ʇǝı-ɔ˙oɹƃ"<br />
*Rotation along Y axis: [[File:Rotation_on_y_axis.png]] <br />
*Rotation along Z axis: [[File:Rotation_on_z_axis.png]]<br />
<br />
*[http://www.ccel.org/h/herbert/temple/EasterWings.jpg Easter Wings] is a good real-world example of rotation along the z axis.<br />
*[http://www.metmuseum.org/toah/works-of-art/1985.240.1 Arabic text] written along a circular path (a roundel).<br />
<br />
===Useful documents===<br />
<br />
*[http://www.unicode.org/reports/tr50/ Unicode Properties for Horizontal and Vertical Text Layout]<br />
*[http://www.unicode.org/reports/tr9/ Unicode Bidirectional Algorithm] (to be revised soon, in the light of TR50 above)<br />
*[http://www.unicode.org/review/pri232/ proposed review of TR9]<br />
*[http://people.w3.org/rishida/scripts/bidi/ what you need to know about the bidi algorithm and inline markup]<br />
*[http://www.w3.org/International/questions/qa-bidi-controls.en.php Unicode controls vs markup for bidi support]<br />
*[http://dev.w3.org/csswg/css3-writing-modes/ CSS Writing Modes]<br />
*[http://www.w3.org/International/questions/qa-bidi-css-markup CSS vs Markup in XHTML]<br />
<br />
[[Category:Council]]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=10760Samples of TEI texts2012-04-18T13:33:04Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]]<br />
[[Category: TEI:P4]]<br />
[[Category: TEI:P5]]<br />
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.ddbc.edu.tw/BZA/bzaComCatWeb.html '''Samyukta Agama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.ddbc.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.ddbc.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?)<br />
<br />
* The [[http://sarit.indology.info SARIT]] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.6 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/txm/ '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://ducange.enc.sorbonne.fr/src/, the TEI choices are [http://ducange.enc.sorbonne.fr/src/schema.htm documented] (in french).<br />
<br />
== See also ==<br />
* [[TEI by example]]</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=10759Samples of TEI texts2012-04-18T13:31:12Z<p>Marcus: </p>
<hr />
<div>[[Category: Markup]]<br />
[[Category: TEI:P4]]<br />
[[Category: TEI:P5]]<br />
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Texts == <br />
<br />
* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)<br />
<br />
* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5<br />
<br />
* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* [https://github.com/papyri/idp.data '''Duke Databank'''/Heidelberg/APIS] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata), and the Advanced Papyrological Information System. Approx 145,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.<br />
<br />
* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)<br />
<br />
* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.<br />
<br />
* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)<br />
<br />
* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)<br />
<br />
* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:<br />
** Use of <revisionDesc> and <change> tags to implement workflow<br />
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])<br />
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)<br />
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])<br />
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).<br />
<br />
* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.<br />
<br />
* The [http://buddhistinformatics.ddbc.edu.tw/BZA/bzaComCatWeb.html '''Samyukta Agama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.<br />
<br />
* The [http://buddhistinformatics.ddbc.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese. The data is linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. Data is published under a CC licence.<br />
<br />
* The [http://buddhistinformatics.ddbc.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr:8080/xtf/search?title=&creator=&year=&keyword=&type=tei Epistemon]. These files are licenced under Creative Commons Attribution.<br />
<br />
* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]<br />
<br />
* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?)<br />
<br />
* The [[http://sarit.indology.info SARIT]] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.6 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.<br />
<br />
* [http://txm.bfm-corpus.org/txm/ '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.<br />
<br />
== Dictionaries ==<br />
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.<br />
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://ducange.enc.sorbonne.fr/src/, the TEI choices are [http://ducange.enc.sorbonne.fr/src/schema.htm documented] (in french).<br />
<br />
== See also ==<br />
* [[TEI by example]]</div>Marcushttps://wiki.tei-c.org/index.php?title=EXist&diff=7011EXist2009-11-18T05:26:34Z<p>Marcus: /* Sample implementations */</p>
<hr />
<div>[[Category:Tools]]<br />
<br />
[[Category:Querying tools]]<br />
[[Category:Publishing and delivery tools]]<br />
[[Category:XQuery]]<br />
<br />
== Synopsis ==<br />
[http://exist.sourceforge.net/ eXist] is a Native XML Database, used for storing and querying XML files. Since the first versions, made available between 2000 and 2001, eXist has considerably evolved, thanks also to an active community of developers and users, and in its latest releases, it has several functions, such as support for [http://www.w3.org/TR/xquery/ XQuery], [http://www.w3.org/2001/XInclude XInclude] and [http://xmldb-org.sourceforge.net/xupdate/ XUpdate]. Through an integration with [[ApacheCocoon]], [http://www.w3.org/TR/xslt XSLT] processing can be added to the whole workflow, using the pipeline concept of the [http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html Sitemap]. In this way data and documents can be queried and transformed using together, in the same process, [http://www.w3.org/TR/xquery/ XQuery] and [http://www.w3.org/TR/xslt XSLT]. Moreover [http://exist.sourceforge.net/ eXist] can be integrated as a block in [[ApacheCocoon]], so to use all the modules of this framework, and not the limited version shipped with this database. Recently, starting from version 1.1, [http://exist.sourceforge.net/ eXist] has changed the indexing core, becoming more efficient in being used with complex document-centric files, such as TEI encoded texts.<br />
<br />
== Features ==<br />
* Persistent storing and indexing of the XML documents<br />
* Database administration functions (data management, backup, recoveries) <br />
* Management of the stored documents in collections<br />
* XQuery engine with extentions for full-text search<br />
* Support for XQuery, XSLT, XInclude and XPointer (partial), XUpdate<br />
* [http://xmldb-org.sourceforge.net/xapi/ XMLDB Api]<br />
* Use of network protocols (HTTP/REST, XML-RPC, SOAP, WebDAV)<br />
* Integration with [[ApacheCocoon]] <br />
<br />
== User commentary ==<br />
'''Please sign all comments.'''<br />
<br />
<br />
== System requirements ==<br />
eXist is written in Java, and therefore requires a [http://java.sun.com/javase/downloads/index.jsp JDK] > 1.4. Being a Java application it can be used on most operating systems, from Windows 2000/XP to Linux or MacOs X, and it can be deployed in several ways, as a standalone application, as a web application inside a servlet container (such as [http://tomcat.apache.org/ Apache Tomcat] or [http://www.mortbay.org/ Jetty]) or as a Java library in a larger application.<br />
<br />
== Source code and licensing ==<br />
eXist is open-source, released under the [http://www.gnu.org/copyleft/lesser.html GNU LGPL] license.<br />
<br />
== Support for TEI ==<br />
Support for TEI is not out of the box, meaning that in the standard distribution there are not ready to use XQuery or XSLT files for TEI documents, even as examples. Notwithstanding implementation with TEI is really straightforward and there are several applications based on this software. In particular the development of the new indexing core, for a better management of complex document-centric file, such as TEI documents, has been supported by the TAPoR node of [http://tapor.uvic.ca/home.php University of Victoria]. <br />
<br />
== Language(s) ==<br />
As wrote before, eXist is a Java application. Anyway, whole applications can be created without writing any line of programming code, but using only XQuery, XSLT, (X)HTML, CSS and Javascript. Using the available network interfaces is possible to query eXist not only with Java, and there are already available several modules for other languages ([http://www.bmuskalla.de/DB_eXist/ PHP], [http://query-exist.sourceforge.net/ Perl]) and frameworks ([http://sourceforge.net/projects/springxmldb/ Spring], [http://www.throwingbeans.org/tech/xml_databases_with_exist_and_coldfusion.html ColdFusion], [http://www.zope.org/Members/spilloz/existda Zope]).<br />
The [http://exist-db.org/documentation.html documentation] is available only in english.<br />
<br />
== Documentation ==<br />
http://exist-db.org/documentation.html<br />
<br />
== Tech support ==<br />
Technical support is provived mainly throught the [http://sourceforge.net/mail/?group_id=17691 mailing list]. Being eXist open-source all kind of support and help is made voluntarily and with no obligations. Anyway the support it is very efficient, and almost all the requests are answered in a complete and qualified way.<br />
<br />
== User community ==<br />
The user community is very active and, as for the technical support, the main way of communication is the [http://sourceforge.net/mail/?group_id=17691 mailing list]. Many participants of this list are also part of the TEI Community. There is also a [http://wiki.exist-db.org wiki] and an IRC channel: #existdb at irc.freenode.net. <br />
<br />
== Sample implementations ==<br />
* [http://demo.exist-db.org/examples.xml official demo] (without TEI related examples) <br />
* [http://web.uvic.ca/hrd/achallc2005/abstracts.htm ACH/ALLC 2005: Conference Program and Abstracts]<br />
* [http://www.tapor.uvic.ca:8080/cocoon/graves/ Diary of Robert Graves]<br />
* [http://193.204.255.27/operaliber/index.php?page=/operaLiber/home OperaLiber]<br />
* [http://www.anglo-norman.net/ The Anglo-Norman Dictionary]<br />
* [http://mith2.umd.edu/eada/ Early Americas Digital Archive]<br />
* [http://buddhistinformatics.ddbc.edu.tw/BZA/ A Digital Comparative Edition and Translation of the Shorter Chinese Saṃyukta Āgama]<br />
<br />
== Current version number and date of release ==<br />
New Indexing Core: eXist 1.2 - 2008-01-16<br />
<br />
Old Indexing Core: eXist 1.0.2 - 2007-02-25<br />
<br />
== How to download ==<br />
[http://exist-db.org/index.html#download http://exist-db.org/index.html#download].<br />
<br />
== See also ==<br />
* [[Berkeley DB XML]]</div>Marcushttps://wiki.tei-c.org/index.php?title=OXygen&diff=5033OXygen2009-01-24T18:57:35Z<p>Marcus: /* Additional notes */</p>
<hr />
<div>[[Category:Tools]]<br />
<br />
[[Category:All-in-one Tools]]<br />
[[Category:Development tools]]<br />
[[Category:Editing tools]]<br />
[[Category:Conversion and preprocessing tools]]<br />
<br />
== Synopsis ==<br />
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.<br />
<br />
== Features ==<br />
Supports most features typical of a high-end XML editor, including:<br />
* syntax coloring<br />
* context-sensitive content assistant<br />
* built-in validation and well-formedness checking<br />
* built-in XSLT engines<br />
* Unicode support<br />
* formatting and indentation<br />
* folding<br />
* outline view (shows document structure)<br />
* model view (shows element content model)<br />
* XPath support<br />
* XSLT debugger<br />
* DTD/schema editor<br />
* Text, Grid, and Author (tagless) editing modes<br />
<br />
See also http://www.oxygenxml.com/features.html .<br />
<br />
== User commentary ==<br />
'''Please sign all comments.'''<br />
<br />
I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)<br />
<br />
== System requirements ==<br />
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).<br />
<br />
(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)<br />
<br />
For detailed requirements, see http://www.oxygenxml.com/download.html .<br />
<br />
== Source code and licensing ==<br />
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. Discount available for TEI subscribers and individuals from TEI member institutions: contact [mailto:info@tei-c.org info@tei-c.org] for information. Free 30-day trial license available.<br />
<br />
== Support for TEI ==<br />
As of Version 9.0 build 2007110615, oXygen has TEI P5 1.0 schemas and the TEI XSL 5.7 stylesheets included in the installation kit.<br />
<br />
Comes with TEI schemas and [http://www.tei-c.org/Tools/Stylesheets/ Sebastian Rahtz's stylesheet library], ready to work out of the box.<br />
<br />
== Language(s) ==<br />
Interface available in English, French, German, Italian, Japanese and Dutch.<br />
<br />
Documentation available in English.<br />
<br />
== Documentation ==<br />
http://www.oxygenxml.com/documentation.html<br />
<br />
== Tech support ==<br />
http://www.oxygenxml.com/techSupport.html<br />
<br />
Can buy maintenance and support pack, providing free upgrades and tech support.<br />
<br />
== User community ==<br />
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/<br />
* http://www.oxygenxml.com/forum/<br />
<br />
== Current version number and date of release ==<br />
9.2 (2008-05-09)<br />
<br />
== History of versions ==<br />
See http://www.oxygenxml.com/software_archive.html .<br />
<br />
== How to download or buy ==<br />
http://www.oxygenxml.com/download.html<br />
<br />
== Additional notes ==<br />
<br />
David Sewell wrote ( http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0804&L=TEI-L&T=0&O=D&P=4227 ):<br />
<br />
<blockquote><br />
Because the schema files distributed with oXygen sometimes lag behind<br />
the latest TEI releases, kind souls like Syd Bauman have from time to<br />
time packaged new schema files so that they can be unpacked to replace<br />
part of the oXygen frameworks hierarchy. You could also go to<br />
<br />
http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/<br />
<br />
and grab the files there to replace the ones in a local oXygen<br />
directory.<br />
</blockquote><br />
<br />
Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at tei.oucs.ox.ac.uk/teideb/ .<br />
<br />
<br />
Marcus Bingenheimer:<br />
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and gives and error whenever elements in the RNG or other namespaces are used within <datatype>. <br />
As usual you can associate the tei_odds with a oxygen specific processing command similar to this:<br />
<?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></div>Marcushttps://wiki.tei-c.org/index.php?title=OXygen&diff=5032OXygen2009-01-24T18:29:34Z<p>Marcus: /* Additional notes */</p>
<hr />
<div>[[Category:Tools]]<br />
<br />
[[Category:All-in-one Tools]]<br />
[[Category:Development tools]]<br />
[[Category:Editing tools]]<br />
[[Category:Conversion and preprocessing tools]]<br />
<br />
== Synopsis ==<br />
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.<br />
<br />
== Features ==<br />
Supports most features typical of a high-end XML editor, including:<br />
* syntax coloring<br />
* context-sensitive content assistant<br />
* built-in validation and well-formedness checking<br />
* built-in XSLT engines<br />
* Unicode support<br />
* formatting and indentation<br />
* folding<br />
* outline view (shows document structure)<br />
* model view (shows element content model)<br />
* XPath support<br />
* XSLT debugger<br />
* DTD/schema editor<br />
* Text, Grid, and Author (tagless) editing modes<br />
<br />
See also http://www.oxygenxml.com/features.html .<br />
<br />
== User commentary ==<br />
'''Please sign all comments.'''<br />
<br />
I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)<br />
<br />
== System requirements ==<br />
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).<br />
<br />
(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)<br />
<br />
For detailed requirements, see http://www.oxygenxml.com/download.html .<br />
<br />
== Source code and licensing ==<br />
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. Discount available for TEI subscribers and individuals from TEI member institutions: contact [mailto:info@tei-c.org info@tei-c.org] for information. Free 30-day trial license available.<br />
<br />
== Support for TEI ==<br />
As of Version 9.0 build 2007110615, oXygen has TEI P5 1.0 schemas and the TEI XSL 5.7 stylesheets included in the installation kit.<br />
<br />
Comes with TEI schemas and [http://www.tei-c.org/Tools/Stylesheets/ Sebastian Rahtz's stylesheet library], ready to work out of the box.<br />
<br />
== Language(s) ==<br />
Interface available in English, French, German, Italian, Japanese and Dutch.<br />
<br />
Documentation available in English.<br />
<br />
== Documentation ==<br />
http://www.oxygenxml.com/documentation.html<br />
<br />
== Tech support ==<br />
http://www.oxygenxml.com/techSupport.html<br />
<br />
Can buy maintenance and support pack, providing free upgrades and tech support.<br />
<br />
== User community ==<br />
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/<br />
* http://www.oxygenxml.com/forum/<br />
<br />
== Current version number and date of release ==<br />
9.2 (2008-05-09)<br />
<br />
== History of versions ==<br />
See http://www.oxygenxml.com/software_archive.html .<br />
<br />
== How to download or buy ==<br />
http://www.oxygenxml.com/download.html<br />
<br />
== Additional notes ==<br />
<br />
David Sewell wrote ( http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0804&L=TEI-L&T=0&O=D&P=4227 ):<br />
<br />
<blockquote><br />
Because the schema files distributed with oXygen sometimes lag behind<br />
the latest TEI releases, kind souls like Syd Bauman have from time to<br />
time packaged new schema files so that they can be unpacked to replace<br />
part of the oXygen frameworks hierarchy. You could also go to<br />
<br />
http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/<br />
<br />
and grab the files there to replace the ones in a local oXygen<br />
directory.<br />
</blockquote><br />
<br />
Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at tei.oucs.ox.ac.uk/teideb/ .<br />
<br />
<br />
Marcus Bingenheimer:<br />
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and give errors whenever elements from other namespaces are involved. As usual you can associate the tei_odds with a oxygen specific processing command similar to this:<br />
<?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></div>Marcushttps://wiki.tei-c.org/index.php?title=XML_Copy_Editor&diff=4446XML Copy Editor2008-05-15T11:28:46Z<p>Marcus: /* User commentary */</p>
<hr />
<div>[[Category:Tools]]<br />
<br />
[[Category:Development tools]]<br />
[[Category:Editing tools]]<br />
[[Category:Conversion and preprocessing tools]]<br />
<br />
== Synopsis ==<br />
"XML Copy Editor is a fast, free, validating XML editor."<br />
<br />
== Features ==<br />
From http://xml-copy-editor.sourceforge.net/index.php?page=features :<br />
<br />
* DTD/XML Schema/RELAX NG validation<br />
* [[XSLT]]<br />
* XPath<br />
* Pretty-printing<br />
* Syntax highlighting<br />
* Folding<br />
* Tag completion<br />
* Tag locking<br />
* Tag-free editing<br />
* Spelling and style check<br />
* Built-in support for XHTML, XSL, [[DocBook]] and TEI<br />
* Lossless import and export of Microsoft Word documents (Windows only)<br />
* Version 1.1.0.6 introduces full Aspell support and XML Schema-based element inspection.<br />
<br />
== User commentary ==<br />
'''Please sign all comments.'''<br />
<br />
2007-2008: I have used XML Copy editor in classes teaching XML, TEI & XHTML and participated in the Chinese localization of the interface. Having much fewer functions than production line tools such as Oxygen actually helps beginners to get into the validate & transform routine on which much of XML-work is based.<br />
(M.Bingenheimer, May 2008)<br />
<br />
== System requirements ==<br />
Available for Windows and Linux.<br />
<br />
== Source code and licensing ==<br />
Open-source (GNU General Public License)<br />
<br />
== Support for TEI ==<br />
DTD/Schema for P4/5 are included.<br />
<br />
== Language(s) ==<br />
Interface in English.<br />
<br />
== Documentation ==<br />
See [http://xml-copy-editor.sourceforge.net/index.php?page=help Online Help].<br />
<br />
== Tech support ==<br />
<br />
== User community ==<br />
https://sourceforge.net/forum/forum.php?forum_id=475215<br />
<br />
<!-- inapplicable? <br />
== Sample implementations ==<br />
(links to demo sites running the tool or successful implementations of it)<br />
--><br />
== Current version number and date of release ==<br />
1.1.0.6 (2008-01-21)<br />
<br />
== History of versions ==<br />
http://sourceforge.net/news/?group_id=141776<br />
<br />
== How to download ==<br />
See http://xml-copy-editor.sourceforge.net/ .<br />
<br />
== Additional notes ==</div>Marcushttps://wiki.tei-c.org/index.php?title=Samples_of_TEI_texts&diff=3547Samples of TEI texts2007-09-26T07:50:35Z<p>Marcus: /* Texts */</p>
<hr />
<div>[[Category: Markup]]<br />
[[Category: TEI:P4]]<br />
[[Category: TEI:P5]]<br />
= Samples of TEI Texts =<br />
<br />
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.<br />
<br />
== Texts == <br />
<br />
* [http://www.ota.ox.ac.uk/texts/2493.html The Auchinleck Manuscript], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.<br />
<br />
* The [http://www.tei-c.org/Activities/MI/Samples/ Migration Samples] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.<br />
<br />
* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "Manuscript Markup," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform.<br />
<br />
* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html Samyukta Agama Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.</div>Marcus