diff --git a/www/contribute/how-tos/how-to-conquer-complex-drama-formatting.php b/www/contribute/how-tos/how-to-conquer-complex-drama-formatting.php index 4b683981..7a88fe53 100644 --- a/www/contribute/how-tos/how-to-conquer-complex-drama-formatting.php +++ b/www/contribute/how-tos/how-to-conquer-complex-drama-formatting.php @@ -27,6 +27,13 @@
  • Descriptions

  • Example

  • +
  • Bodymatter file semantics

  • +
      +
    1. Play without acts

    2. +
    3. Acts without scenes

    4. +
    5. Acts with scenes

    6. +
    7. Play in a collection

    8. +
  • Introductory scene descriptions

  • Personas

    1. @@ -38,14 +45,15 @@
      1. Multiple paragraphs

      2. Prose and verse

      3. -
      4. Stichomythia

      5. +
      6. Stichomythia

      7. +
      8. Ancient Greek choral sections

    2. Stage directions

      1. Right-aligned and brackets

      2. Interrupting dialog

      3. Attached to personas

      4. -
      5. Songs

      6. +
      7. “Song.”

      8. Parentheses

      9. Multiple paragraphs

      10. A stage direction for a stage direction

      11. @@ -68,7 +76,7 @@
      12. Make a template file

        -

        The se split-file tool defaults to a chapter template. To add the correct file semantics, we need to create the template file /src/epub/text/drama-template.xhtml. If you wish to split the work into acts or scenes, you can copy and paste the following code to your new file:

        +

        The se split-file tool defaults to a chapter template. To add the correct file semantics, we need to create the template file /src/epub/text/drama-template.xhtml. If you wish to split the work into acts, you can copy and paste the following code to your new file:

        <?xml version="1.0" encoding="utf-8"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" epub:prefix="z3998: http://www.daisy.org/z3998/2012/vocab/structure/, se: https://standardebooks.org/vocab/1.0" xml:lang="LANG"> @@ -126,8 +134,7 @@

        Any descriptions are placed in <p> elements after the list of speakers and end with periods.

        Example

        - -<body epub:type="frontmatter z3998:fiction z3998:drama"> +<body epub:type="frontmatter z3998:fiction z3998:drama"> <section id="dramatis-personae" epub:type="z3998:dramatis-personae"> <h2 epub:type="title">Dramatis Personae</h2> <ul> @@ -145,6 +152,62 @@ </ul> <p>Scene: Messina.</p> </section> +</body> +
        +
      13. +
      14. +

        Bodymatter file semantics

        +

        Plays can come in all shapes and sizes, and no two plays look alike. Figuring out where to place play semantics can be very confusing! Here are some basic play structures to show where play semantics go.

        +

        Play without acts

        +

        Some plays are not divided into acts. These plays are placed in a single file named after the play. z3998:drama and z3998:scene are located in the top-level section.

        +
        +<body epub:type="bodymatter z3998:fiction"> + <section id="ID" epub:type="z3998:drama z3998:scene"> + ... + </section> +</body> +
        +

        Some single-act plays do have scene sections, which are divided into section elements in the file with the z3998:scene semantic.

        +
        +<body epub:type="bodymatter z3998:fiction"> + <section id="ID" epub:type="z3998:drama"> + <section id="scene-1" epub:type="z3998:scene"> + ... + </section> + </section> +</body> +
        +

        Acts without scenes

        +

        Some plays are divided in to acts without scene sections. The body element contains the z3998:drama semantic; the top-level section element contains both chapter and z3998:scene semantics.

        +
        +<body epub:type="bodymatter z3998:fiction z3998:drama"> + <section id="act-1" epub:type="chapter z3998:scene"> + ... + </section> +</body> +
        +

        Acts with scenes

        +

        If a multi-act play has scene sections, the top-level section only has the chapter semantic, and the scene section elements are tagged with z3998:scene.

        +
        +<body epub:type="bodymatter z3998:fiction z3998:drama"> + <section id="act-1" epub:type="chapter"> + <h2> + <span epub:type="label">Act</span> + <span epub:type="ordinal z3998:roman">I</span> + </h2> + <section id="scene-1-1" epub:type="z3998:scene"> + ... + </section> + </section> +</body> +
        +

        Play in a collection

        +

        The rarest case encountered is a collection of short plays. Each play is in its own file, with article elements tagged with z3998:drama.

        +
        +<body epub:type="bodymatter z3998:fiction"> + <article id="ID" epub:type="z3998:drama"> + ... + </article> </body>
      15. @@ -221,17 +284,71 @@ </td> </tr>
        -

        Stichomythia

        +

        Stichomythia

        Stichomythia is a technique used in drama where two speakers engage in a rapid or intense exchange of alternating dialog. Here is an example found in William Shakespeare’s A Midsummer Night’s Dream.

        Five sections of dialog use stichomythia. The second section of dialog continues where the first section has left off. This pattern continues and creates a staircase effect.

        This highlights moments of conflict, urgency, or intense emotion and conveys dynamic interactions between characters. Unfortunately, there is no great way to format this technique with clear, predictable structuring. The text displayed has no additional indents or margins.

        +

        Ancient Greek choral sections

        +

        Ancient Greek drama can contain choral sections where each stanza is labeled as strophe, antistrophe, or epode. The sections are numbered if a chorus sings/chants a pattern of strophic, antistrophic, and epodic units. The labels are formatted with italics, parentheses around the label, and right-alignment.

        +
        +<tr> + <td epub:type="z3998:persona">Chorus</td> + <td epub:type="z3998:song"> + <div> + <header> + <p>Strophe 1</p> + </header> + <p> + <span>...</span> + </p> + </div> + <div> + <header> + <p>Antistrophe 1</p> + </header> + <p> + <span>...</span> + </p> + </div> + <div> + <header> + <p>Epode 1</p> + </header> + <p> + <span>...</span> + </p> + </div> + ... + </td> +</tr> +
        +
        +[epub|type~="z3998:song"] div + div{ + margin-top: 1em; +} + +[epub|type~="z3998:song"] header p{ + font-style: italic; + text-align: right; +} + +[epub|type~="z3998:song"] header p::before{ + content: "("; + font-style: normal; +} + +[epub|type~="z3998:song"] header p::after{ + content: ")"; + font-style: normal; +} +
      16. Stage directions

        Right-aligned and brackets

        -

        Exit or exeunt stage directions are traditionally shown right-aligned and bracketed. These are formatted like other inline stage directions and placed at the end of the preceding dialog. Compare how the following page scan source is structured in HTML.

        +

        Some stage direction have only an opening bracket and are right-aligned, like exit or exeunt stage directions. These are formatted like other inline stage directions and placed at the end of the preceding dialog. Compare how the following page scan source is structured in HTML.

        The stage direction “Goes.” is right-aligned and is preceded by a left bracket.
        @@ -295,8 +412,8 @@ </td> </tr>
        -

        Songs

        -

        Some songs are given a title or just labeled as “Song”. Treat these as stage direction rows.

        +

        “Song.”

        +

        Some songs are given a title or just labeled as “Song.” Treat these as stage direction rows.

        <tr> <td/>