<?xml version="1.0"?>

<!-- Start license statement: do not remove 

EpiDoc: Guidelines for Structured Markup of Epigraphic Texts in TEI
Copyright (C) 2000-2006 by all contributors listed in <div type="gl-responsibility">, below.
Additional contributors' copyright may be designated in individual source files.

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.

Information about the EpiDoc community can be obtained via 
http://epidoc.sf.net.

End license statement: do not remove -->
<!DOCTYPE div SYSTEM "../dtd/tei-epidoc.dtd">
<!-- Start CVS information: do not remove -->
<!-- $Header: /cvsroot/epidoc/guidelines/src/taggingtext.xml,v 1.11 2007/07/11 17:42:17 paregorios Exp $ -->
<!-- End CVS information: do not remove -->

<div xmlns="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XInclude" id="taggingtext"
    lang="en" rend="multipart">
    <head>Transcribing and Editing the Text</head>
    <p>The creation of epigraphic texts using XML is greatly facilitated by the
        traditional, scholarly techniques of editing epigraphic texts. Epigraphers are already
        accustomed to careful examination, analysis and description of letters, words, phrases and
        other aspects of texts. Communicating these aspects accurately and unambiguously is the
        central aim of scholarly epigraphic publication, and epigraphers have developed a highly
        technical and effective typographic vocabulary for achieving it (see further: "
        <xref href="introeps.xml">Introduction for Epigraphers</xref>").  Our goal in developing the guidelines in this section has been to render structurally distinct the semantic richness
        and rigor underlying the typographic vocabulary to permit computer software to distinguish all its elements reliably.
        This arrangement permits the use of xml-aware software 
        to increase scholarly productivity and reduce the manual tasks that slow scholarly
        inquiry. </p>
    <p>The use of sigla in traditional typographic
        editions that either bind to individual characters or that encompass a group of characters
        pair-wise provides a ready-made road map to the enumeration and application of XML tags. In
        formulating these recommendations, we have endeavored to provide
        unique combinations of elements and attributes for each and every distinction epigraphers
        attempt to draw with sigla in print editions. These element-attribute combinations are
        described in the following sections, arranged by broad classes of editorial activity.</p>
    <p>Note that this section focuses exclusively on the transcription and editing of the inscribed
        text, i.e., the specific activities in which an epigraphist engages to constitute a text and
        associated apparatus. Other aspects of epigraphic editions, reports and corpora are
        presented elsewhere in these <bibl>
            <title level="m">Guidelines</title>
        </bibl> (please see the <xref href="toc.xml">Table of Contents</xref> or <xref
            href="gl-organization.xml">Organization of the Guidelines: where to go from
            here</xref>).</p>
    <xi:include href="textparts.xml" />
    <xi:include href="transcription.xml" />
    <xi:include href="additionanddeletion.xml" />
    <xi:include href="formandappearance.xml" />
    <xi:include href="supplements.xml" />
    <xi:include href="corrections.xml" />
    <xi:include href="editorialother.xml" />
    <xi:include href="criticalapparatus.xml" />
    <div id="taggingtext-responsibility" type="gl-responsibility">
        <head>Responsibility for this section</head>
        <listBibl>
            <bibl>
                <respStmt>
                    <resp>author</resp>
                    <name>Tom Elliott</name>
                </respStmt>
            </bibl>
        </listBibl>
    </div>
    <div id="taggingtext-cvs" type="gl-cvs">
        <head><abbr expan="Concurrent Versioning System">CVS</abbr> Information</head>
        <p id="taggingtext-cvs-revision-number">Revision number: <seg n="cvs-revision-number"
                >$Revision: 1.11 $</seg></p>
        <p id="taggingtext-cvs-revision-name">Revision name (if any): <seg n="cvs-revision-name"
                >$Name: r-5 $</seg></p>
        <p id="taggingtext-cvs-revision-date">Revision date: <seg n="cvs-revision-date">$Date:
                2006/12/06 21:33:09 $</seg></p>
        <p id="taggingtext-cvs-revision-author">Revision committed by: <seg n="cvs-revision-author"
                >$Author: paregorios $</seg></p>
    </div>
</div>
