EpiDoc Guidelines Preview Snapshot: 23 May 2013

This snapshot of the development status of the EpiDoc Guidelines is provided as a service to the EpiDoc community. Download and unzip epidoc-guidelines-preview-2013-05-23.zip. A "guidelines" folder and subordinate folders will be created. The README.txt explains how the contents are structured and how to generate your own HTML version of the guidelines; however the "output" subdirectory already contains a complete, generated version of the Guidelines. Just open guidelines/output/index.html with your favorite browser. Please note that the official HTML development version of the Guidelines is always to be found online at http://www.stoa.org/epidoc/gl/dev/.

This snapshot is current to SVN commit r1932.

Comments and corrections should be posted to the Markup List or reported as a bug via the EpiDoc Sourceforge Bug Tracker.

Release notes:

Please note that this is not a formal release; just a snapshot for convenience. There have been huge changes in the structure, layout, tooling and contents of the Guidelines since the last release, so it's really impossible to summarize them all here. In just the last month or so, we've trimmed a bunch of cruft from the table of contents and made some key updates including:

• fixed cross-references and external links that were failing
• added more guidance on encoding places and dates of finding and subsequent observation, as well as inventory numbers (with many new examples of each)
• added information on Petrae encoding
• added a stub page for interpuncts
• added introductory paragraphs to the top-level page and the introductory pages on transcription and supporting data
• highlighted the "structure of an edition" page via the "supporting data" page, with a link to a downloadable version of the example found there, suitable for use as a project template
• added a modest touch of CSS to improve readability and show off the new EpiDoc logo
• added a glossary
• added project links to the bibliography
• added many new examples throughout

It takes a village:

Kudos to everyone who's committed code or content to the Guidelines so far, including:

• asciva = Valentina Asciutti
• bealietz
• bryaxis = Pascal Lemaire'
• ctupman = Charlotte Tupman
• ellimylonas = Elli Mylonas
• gabrielbodard = Gabriel Bodard
• hcayless = Hugh Cayless
• paregorios = me
• rahtz = Sebastian Rahtz (special thanks for the TEI stylesheets that we use to help produce the guidelines!)
• rviglianti = Raffaelle Viglianti
• sarcanon = Scott Varnderbilt
• sbauman = Syd Bauman
• simonastoyanova = Simona Stoyanova
• zau = Zaneta Au

Other folks are credited in the authorial statements at the bottom of each page, especially when markup from their projects has been used in examples.