<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE subtitle-script
   SYSTEM "http://www.instrumentality.org/dtd/subtitle-script-0.6.dtd">

<!--

   * * * * *
   WARNING:  IF YOU ARE VIEWING THIS IN A WEB BROWSER, IT MAY
   NOT BE DISPLAYING THE ACTUAL XML SOURCE.  Some browsers
   perform odd parsing and "pretty-printing" in order to make
   the XML look nicer, but this results in you not seeing the
   actual file.  Try downloading the file to disk and viewing
   it in a text editor or XML application.
   * * * * *

   This is a sample EVA script.  It was generated by hand (not
   by the Eva software) and contains numerous comments which
   will hopefully be helpful to the reader.  (A real Eva-
   generated script would not contain these comments.)

   For more information on the Eva subtitling software and the
   EVA script format, see:  http://www.instrumentality.org/eva/

   Note that this file is encoded in UTF-8 format, and contains
   some non-English text (Japanese, in this case) to demonstrate
   the multi-language features of the script format.  If you are
   viewing this file in an editor that does not support UTF-8
   (or if you do not have any Japanese fonts installed), some
   portions of this file may appear as "garbage" characters.

   Last modified 2004-03-04 by dev@instrumentality.org

-->

<!-- The top-level element is the "subtitle-script" -->
<subtitle-script version="0.6">

   <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
      The "script-info" element contains information such
      as the title, translator credits, etc..
    - - - - - - - - - - - - - - - - - - - - - - - - - -->
   <script-info>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The optional "generator" tag specifies the program
         that was used to create the script file.  It may
         also include a URI that points to the program's
         official home page.  The generator tag below is
         the format that is generated by Eva.
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <generator name="EVA Subtitling System"
         href="http://www.instrumentality.org/eva/" />

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The "title" element contains the title of the
         program being subtitled.  Multiple title elements
         may be present, as long as each has a different
         "xml:lang" value.  The original (native language)
         title should be marked as being the "canonical"
         title.  In the example below, the Japanese version
         is marked as being the canonical title.  Note that
         at least one title must be present.
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <title xml:lang="ja" canonical="true">台本の見本</title>
      <title xml:lang="en">A Sample Script</title>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The "episode-number" contains the number of this
         episode (for a TV series, OAV, or other program
         that has numbered episodes; it can be omitted if
         not applicable).
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <episode-number>1</episode-number>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The "episode-title" contains the title of this
         particular episode (again, only if applicable to
         the program).  The "official" (native language)
         title should be marked as canonical.
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <episode-title xml:lang="ja" canonical="true">この番組</episode-title>
      <episode-title xml:lang="en">This Episode</episode-title>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         A credit block is optional, but should usually be
         present.  It contains elements specifying copyright
         information, translators, editors, etc..

         The following items may appear in a credit block:

         "group"
            Name of a subtitling group (fansub circle, commercial
            translation bureau, etc.), with optional web site
            and contact email.
         "copyright"
            A copyright notice.
         "translator"
            A translator's name.
         "editor"
            An editor's name.
         "other"
            Some other credit.  May contain a "meta"
            attribute that is intended to clarify the
            meaning of the element's contents.  For
            example, below we added an "other" element
            to add a "Timer" credit.

         Note that these elements may repeat (for example,
         there can be any number of copyright notices,
         translators, etc.), but they must be presented
         in the order shown above (and specified explicitly
         in the DTD).  For example, all of the group elements
         must come first, then the copyright elements, then
         all of the translator elements, etc..
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <credits>
         <group href="http://www.example.com/"
            email="example@example.com">Some Fansub Group</group>
         <copyright>Copyright (c) 2002 by Some Fansub Group</copyright>
         <copyright>Song lyrics Copyrignt (c) 2002 by Someone Else</copyright>
         <translator>John Doe</translator>
         <editor>Jane Doe</editor>
         <other xml:lang="en" meta="Timer">Bob the Timer</other>
      </credits>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The "source" element contains information on the
         source material used (the original DVD, etc.).
         Note that, unlike the main script title area
         above, only one title may appear here.  It should
         be the actual (original language) title of the
         source DVD, etc..

         The "program" element specifies the program type,
         which is one of:  TV, OAV, movie, other.  It may
         also contain episode, chapter, or other numbers,
         if relevant.  (The "number" attribute should be
         omitted if not appropriate; for example, when
         referencing a standalone movie or unnumbered OAV.)

         The "product" element specifies the medium type,
         which is one of:  DVD, LD, VCD, tape, other.  It
         may also include an "id" attribute, which should
         contain the product code, ISBN, etc. of the
         actual source.

         The source element must contain exactly one each
         of title, program, and product (in that order).
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <source>
         <title xml:lang="ja">元のタイトル</title>
         <program type="TV" number="1 - 4" />
         <product type="DVD" id="ABCD-12345" />
      </source>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The optional "revision" element is used to indicate
         the script version or revision number.  (See the
         DTD for details on the recommended format.)
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <revision>1.0.5 (2004-02-01)</revision>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The "other" element (which may appear zero or more
         times at the end of the script-info block) is used
         to store generic information that does not fit in
         elsewhere.  (See also the "other" element in the
         "credits" element, above.)
       - - - - - - - - - - - - - - - - - - - - - - - - - -->

      <other xml:lang="en" meta="Example comment">
         This is just an example of how to use an "other" element here.
      </other>
      <other xml:lang="en" meta="Timing notes">
         You could put information on timing synchronization here, for
         example.  You can have as many of these elements as you want
         (including none at all, if you don't need any of them).
      </other>
      <other xml:lang="ja" meta="Another example">
         日本語もＯＫです！
      </other>

   </script-info>

   <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
      The "script-data" element contains information on
      the names of the speakers; the styles used; and
      the text of the script itself.
    - - - - - - - - - - - - - - - - - - - - - - - - - -->
   <script-data>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         First comes the "name-list" element.  This element
         contains zero or more "name-entry" elements.  A
         name-entry element is a means of associating
         multiple names, for facilitating a multi-language
         script.  For example, when translating a Japanese
         program into English, it allows the original
         (Japanese) name of a character to be associated
         with the official English spelling.

         Every name that appears as a speaker in the script
         must have a corresponding name-entry element here.

         Each name-entry element has an "id" attribute that
         specifies a unique tag that will be used when
         referencing that name (in any language).  The tag
         can be any valid identifier, as long as it is
         unique within the script.

         A name-entry element contains one or more
         "name-text" elements.  Each name-text element
         contains a name (for a given language).  The
         original (native language) name of a given
         character should be marked as the "canonical"
         name.  For example, in a Japanese program, the
         Japanese names would be the canonical names.
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <name-list>

         <name-entry id="name_000">
            <name-text xml:lang="ja" canonical="true">レイ</name-text>
            <name-text xml:lang="en">Rei</name-text>
         </name-entry>

         <name-entry id="name_001">
            <name-text xml:lang="ja" canonical="true">しんじ</name-text>
            <name-text xml:lang="en">Shinji</name-text>
         </name-entry>

      </name-list>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The "style-list" element contains a list of
         "style-entry" elements.  Each "style-entry"
         element provides information on a given text
         style.  It is up to a subtitle/overlay generator
         program to decide how to use the styles.  (The
         Eva editor is not a subtitling program; it is
         only a script editor.  For example, when a line
         is being "thought" (rather than spoken) by a
         character, you could apply a "Thought" style,
         which will probably be rendered in italics
         when the subtitles are applied.  However, as
         far as the Eva editor is concerned, the only
         important thing is the style identifier.)

         Each style-entry element has a unique "id"
         attribute and a "style-text" element which
         contains the human-readable name of the style.
         It must also contain one or more "style-data"
         elements.

         Each style-data element contains information on
         the style.  If no "agent" attribute is provided,
         then the contents are assumed to be a human-
         readable description of the style.  If an "agent"
         attribute is provided, it should identify a
         particular subtitle rendering program.  In this
         case, the style-data's contents should be some
         data that the specified agent can use to render
         text of the given style.  In the examples below,
         we have given a human-readable style-data element
         and a style-data element containing rendering
         information to be used by the popular SubStation
         Alpha program.  (The sample texts in the example
         entries below are in SubStation Alpha's style
         data format.)

         Note that Eva will not generate style-data tags.
         The only way that these will appear is if a script
         was originally in another format (for example, if
         a SubStation Alpha script is imported and then
         saved as an Eva script).

         Note also that, unlike most other elements in a
         script, the contents of a style-data element are
         preserved exactly, including whitespace, in case
         the spacing is important to the agent.
       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <style-list>

         <style-entry id="style_000">
            <style-text>Default</style-text>
            <style-data>The default style</style-data>
            <style-data agent="SubStation Alpha">Default,Arial,26,4259839,4259584,16760960,4210752,-1,0,1,2,2,2,0,0,26,0,0</style-data>
         </style-entry>

         <style-entry id="style_001">
            <style-text>Thoughts</style-text>
            <style-data>Style for lines that are thought (not spoken)</style-data>
            <style-data agent="SubStation Alpha">Thoughts,Arial,26,4259839,4259584,16760960,4210752,-1,-1,1,2,2,2,0,0,26,0,0</style-data>
         </style-entry>

      </style-list>

      <!-- - - - - - - - - - - - - - -  - - - - - - - - - -
         The "event-list" element is the "main" part of a
         script.  It contains zero or more (usually more)
         "event" elements.  It has two attributes, one of
         which ("timebase") is required, and one of which
         ("ntsc") is optional (but should generally be
         included anyway).  There is a fairly lengthy
         comment block in the DTD that lists all of the
         possible valid combinations.  Most likely, you
         will use one of the following:

            timebase 24, ntsc true
               This is the frame rate (23.976) that a
               film-based movie usually has when transferred
               to an NTSC DVD.

            timebase 30, ntsc true
               This is the frame rate (29.97) that a TV
               program aired in NTSC-based countries
               (including USA and Japan) will have.  Some
               movies will also have this frame rate when
               transferred to DVD.

            timebase 25, ntsc false
               This is the frame rate (25) that a TV
               program aired in a PAL-based country will
               have.

         Note that a "30/true" (29.97 fps) script should
         (but is not required to) use drop-frame notation
         in its timestamps; see the DTD for more details.

         Each event element represents a line of dialogue,
         on-screen text, a translator's comment, or another
         event that occurs at a specivic point in the script.
         The Eva script editor only knows and cares about
         dialogue events and comments (types "dialogue" and
         "comment").  Any agent-specific events (such as
         graphical overlay cues, etc.) may be stored as
         "generic" events.  The Eva editor will not display
         or edit "generic" type events, but it will preserve
         them if present in a script file.

         Every event has some associated text (which may
         be empty) and an in/out time pair.  Only dialogue
         events have a name and style; any name or style
         attributes in non-dialogue elements are ignored
         (and probably discarded upon next save).  The
         "text" element of a "generic" event should be in
         a format that is understood by the agent specified
         in the event's "agent" tag.  (Note that the agent
         tag is ignored in non-generic events.)

         By default, the exact spacing (including whitespace)
         is preserved in "text" elements.

         A text element's text may contain several markup
         tags, some of them similar to HTML markup tags:

            <i>       </i>        Italics
            <b>       </b>        Bold
            <u>       </u>        Underline
            <sup>     </sup>      Superscript
            <sub>     </sub>      Subscript
            <size>    </size>     Change the font size
            <special> </special>  Special tag (see below)
            <br />                Manual line break

         See the DTD for details on nesting behavior, etc..
         Note also that these tags are only included for
         the convenience of subtitle generators; Eva itself
         does not care about such things as text formatting.

         The "special" tag is used to include text format
         information beyond that covered by the other tags.
         For example, karaoke timing information, etc. may
         be included in "special" tags.  Eva ignores these
         tags (but preserves them if found in a file).  If
         no agent is specified, then the tag simply acts
         as an in-line comment.

         An event may also contain one (optional) annotation
         (typically a temporary translator's note or quotation
         citation) and any number of agent-specific flags.
         (For example, a user of the Eva editor may flag a line
         as "uncertain translation" ("U" flag), or may bookmark
         a line ("B" flag).  User agents are not required to
         follow this "one character per flag" convention, and
         must always preserve any unknown agents' flags that
         they may encounter.)

         The in/out timecodes ("time-in" and "time-out"
         elements) contain text that is formatted as a
         timecode in the notation specified in the timebase
         attribute of the event-list element.

            TIMEBASE/NTSC   ENCODING FORMAT   EXAMPLE
             1000s/false    HH:MM:SS.ttt      01:23:45.353
             30/true        HH:MM:SS;ff       01:23:45;12
             Others*        HH:MM:SS:ff       01:23:45:12
                (* or non-drop-frame 30fps)

       - - - - - - - - - - - - - - - - - - - - - - - - - -->
      <event-list timebase="30" ntsc="true">

         <event type="dialogue" time-in="00:00:00;00" time-out="00:00:02;00"
            name="name_000" style="style_000">
            <text xml:lang="en">This is an example.</text>
            <text xml:lang="ja">これは実例です。</text>
         </event>

         <event type="dialogue" time-in="00:00:03;10" time-out="00:00:04;22"
            name="name_001" style="style_000">
            <annotation>There is at most one annotation per line.</annotation>
            <text xml:lang="en">This is <i>another</i> example.</text>
            <text xml:lang="ja">これは<i>もう一つ</i>の実例です。</text>
         </event>

         <event type="comment" time-in="00:00:03;10" time-out="00:00:04;22">
            <text xml:lang="en">This is a sample comment.</text>
         </event>

         <event type="dialogue" time-in="00:00:05;00" time-out="00:00:07;00"
            name="name_000" style="style_000">
            <annotation>This line has an Eva "bookmark" flag set.</annotation>
            <flags agent="Eva" data="B" />
            <text>This shows how to use the <special agent="SubStation Alpha" data="{\c&amp;HFFE090&amp;}">special</special> tag (in this case, to embed a SubStation Alpha color command).</text>
         </event>

         <event type="generic" agent="SubStation Alpha"
            time-in="00:00:10;00" time-out="00:00:14;00">
            <text>An event code or something would go here</text>
         </event>

         <event type="dialogue" time-in="00:00:15;00" time-out="00:00:17;00"
            name="name_001" style="style_001">
            <text>This is an example<br />of text with a manual line break.</text>
         </event>

      </event-list>

   </script-data>

</subtitle-script>
<!-- End of file -->
