This section is edited by Dott.ssa Susanne Müller and Dott.ssa Costanza Giannaccini for contents and structural aspects, by Dott.ssa Francesca Di Donato and Dott.ssa Chiara Aiola for formal syntax.

1. Introduction
2. Letter structure
   2.1 General indications
   2.2 Opener and Closer
   2.3 Semantic Units

   2.4 Regularisations
   2.5 Abbreviation with glyph
   2.6 Illegible characters conveyed with the symbol “%”
   2.7 Missing letters, gaps
   2.8 Unclear
   2.9 Catchwords
   2.10 Additions
   2.11 Postscript
   2.12 Page numbers and conventional signs for page endings
   2.13 Handshift
   2.14 Space
   2.15 Supplied

3. Letter graphic layout
   3.1 Attribute Rend: position and alignment
   3.2 Attribute Rend: graphic layout
4. Interface tools
   4.1 Dropdown menu for the letter structural elements
5. XML-HTML conversion through EVT
   5.1 Preliminary modifications of the XML file

   5.2 Modifications to the CSS
   5.3 XML-HTMLCorrespondence chart

1. Introduction

Purpose of this document is to clarify the essential steps that from a letter transcription in XML format lead to its transformation into the so-called “diplomatic” version, apt to reproduce the manuscript in the most accurate way.
The main steps are the following:

1. Definition of the XML encoding for every letter structure planned to be displayed
2. Transformation of the diplomatic XML into HTML via an appropriate XSLT stylesheet (profile OXGARAGE: burckhardt)
3. HTML display (using a modified version of the Vercelli Book) with an appropriate CSS

1. Letter structure

2.1 General indications

Paragraphs

Paragraphs default setting has left alignment. New paragraphs have a margin of about 10 pixels (this value is approximate and may be modified in the future). For the tag

, the attribute “rend” can have the following values in order to change paragraph alignment:

• Indented: paragraph first line is indented with a standard value of 35 pixels (this value is approximate and may be modified in the future).
• Right: the whole paragraph is right-aligned (see details below, 3.1).
• Centre: the whole paragraph is centered (see details below, 3.1).

Linebreak: Any corresponds to a new paragraph

2.2 Opener and Closer

In the diplomatic version, tags and will be treated as paragraphs:

• new paragraphs start before and after Opener and Closer
• a margin of around 10px is set (subject to change) and could be easily modified in the CSS.

2.3 Semantic Units

Semantic units possibly present in the text are not highlighted, they will follow the text flow set by existing line breaks and rends.

In the check phase of the diplomatic XML no tag will be therefore added to those already present for the definition of the semantic units:

• Date
• Salute
• Signed

2.4 Regularisations

Regularisations (tag … … ) include two types of interventions in the XML encoding:

• hyphenation
• corrections in the text, made by the letter author

The two cases are treated in a different way in the “Philological Version”:

1. the hyphenation appears as in the manuscript, without a regulation (in the “Semantic Edition” the word shows no hyphenation, i.e. in the regularised form)
2. Word correction is treated as follows:

the version shown in the text is the one contained in the .

any indications of deletions will be displayed graphically as follows:

• Strikethrough: the text crossed out with a line. Correction highlighted through coloured background. In the tooltip it only appears the regularised version
• Blackened: the text is obscured with a thick black line. Correction highlighted through coloured background.
• Overwritten: special characters reproducing an overwritten effect are superimposed on the text.

The different solutions proposed can be viewed at the following examples page:
http://jsfiddle.net/gandreini/8sutebma/

A pop-up shows the regularised version
A background highlight will show the regularisations present in the letter.

2.5 Abbreviation with glyph

Abbreviations with glyph are treated as follows:

• in the text the abbreviation appears in its extended version
• a pop-up indicates that it is a glyph

Special cases: ! and ? without full stop
Since the glyph is a graphic sign, a corresponding visualisation is not possible.
They appear as regular text characters, while the tooltip shows their description, eg: “question mark without full stop”
Example:

http://jsfiddle.net/gandreini/L1vsf26j/

2.6 Illegible characters conveyed with the symbol “%”

Illegible letters within a or an are conveyed with the symbol “%”.
One single % character is converted into [-]
A sequence of % (from two onwards) is converted into [–]
Illegible text portions are indicated with

• the tag is converted into [-]
• the tag with quantity higher than 1 [–]

2.7 Missing letters, gaps

2.7.1 A space replacing a letter within a word (peculiarity due to  the flow of the handwriting) is transcribed with the character ∩
2.7.2 A missing letter or word (due to damaged paper or unreadable passage) is transcribed with the symbol [-]. In case of more than one letter or word, the transcription is [–]
Both symbols are maintained in the XML and in the “Philological Version”

2.8 Unclear

Unclear words and/or text parts are highlighted with a different background colour (ffac4e).

2.9 Catchwords

No special handling, only the indications in any possible “rend” are taken into account. Both occurrences are displayed.

2.10 Additions

Additions are arranged where they are in the XML. They have:

• a background colour: 69d0ef
• a pop-up specifying the exact location and the possible presence of the sign √

Special cases:
Additions located marginally (also vertical) and at page top/bottom.
a) Graphic signs for reference (cross, asterisk or similar): additions are inserted in the corresponding page, at page bottom. The location of the addition in the manuscript is indicated in the pop-up (Add place: “inter”, “bottom”, “Margin right_ Written vertically”). Graphic signs are kept.
b) No graphic signs: additions are inserted in the corresponding page, at page bottom. The location of the addition in the manuscript is indicated in the pop-up (Add place: “inter”, “bottom”, “Margin right_ Written vertically”). No graphic signs is needed.
c) When the letter continues backwards on previous sheets (eg. Bode), the addition is located at the end of the letter with an appropriate indication of its original place (eg. Add place p.1, Written Vertically)
Example:

http://jsfiddle.net/gandreini/gd09z2kd/

2.11 Postscript

The postscript is included in the Closer, whether text or addition. s and rends will indicate the correct placement.

2.12 Page numbers and conventional signs for page endings

They are shown in the Philological Version and they follow the directions present in any rend. No need to add a specific tag.

2.13 Handshift

Handshifts are indicated with the tag (type “milestone”). The beginning of a handshift is indicated with where the attribute “new” contains the author of the text from the tag onwards. The return to the main hand of the letter is indicated with and no attributes. In order to limit potential tag conversion errors, in the xst it is important:

• to always specify the return to the main hand, even if it is at the end of the letter, so to easily find both beginning and end of a and include the text in a tag html.
• not to break elements with handShifts, eg:

Dr Kern

and not

Dr Kern

Handshifts regarding only underlinings will be visible and will receive an appropriate description only in the Philological Version, while on the Semantic Edition they are not visible.

2.14 Space

Wider spaces are marked with . Convert tags in the & nbsp;

2.15 Supplied

The tag Supplied is used in those cases in which a part of the letter is illegible, but the solution is obvious (e.g. margin of the page): the editor integrates the missing text part.
A pop-up indicates that the text is supplied and explains the reason.

3. Letter graphic layout

3.1 Attribute Rend: position and alignment

The attribute “Rend” can contain information about position and alignment of the letter element. Possible values of the attribute:

• Right: it indicates a right alignment.
• Left: it indicates a protrusion of the item towards left, produced with a negative margin on the left side.
• Indented: the indented element is reproduced with the indention of the paragraph first line.
• Centre: the centered element is reproduced through center alignment, and margins on both right and left sides in order to make clearer the centrality in the page.
• Superscript: the element is superscribed.

3.2 Attribute Rend: graphic layout

The attribute “Rend” can contain values related to the layout of an element within the manuscript. Possible values:

• underline: the text is underlined
• double_underline: double underline. The text is underlined with a double line
• colour_ink: different values based on the colour type, eg red_ink, brown_ink, violet_ink. A specific css can be defined for the most frequent, while other specific cases could be integrated.
• pencil: light gray with tooltip indicating pencil as writing tool
• left_margin: TBD
• vertical: TBD

As a general the rule, at every rend value must correspond a style reproducing as trustworthy as possible the original appearance of the manuscript.
Examples:

http://jsfiddle.net/gandreini/a6fyp2c0/

For “strikethrough”, “blackened”, “overwritten” Rend, refer to the Regularisations section.

4. Interface tools

4.1 Dropdown menu for the letter structural elements

Abbreviations (including Abbreviations, Abbreviations brevigraph, Exclamation and questions marks, Hyphenation) Colour: 89e872

• Additions colour: 69d0ef
• Corrections colour: cccccc
• Uncertain readings colour: ffac4e
• Handshift colour: f8f4a2
• Next Page colour: NO colour
• Catchwords colour: NO colour
• Alignment colour: NO colour

The last option of the dropdown is:

• Show all/hide all (Option to show or hide all Structural annotations)

Each type of Structural annotations has a custom colour which will be used to highlight the text.

5. XML-HTML conversion through EVT

5.1 Preliminary modifications of the XML file

In order to use the conversion tool evt, the following preliminary changes to the  diplomatic XML must be completed:

• add to the
  container transcription the following attributes: subtype = “edition_text” type = “verse” xml: id = “DOTR”
• give an xml: id to the tags

5.2 Modifications to the CSS

• Handling of the two blocks Opener and Closer: currently the blocks Opener and Closer are not converted into HTML elements. They are instead transformed into
  , so that the text before and after start as a new paragraph
• Handling of the : What has to be shown is the expan and not abbr
• Handling of the : is not converted to html element. It should be converted into div and there should be added also « » if the type is “angle”.

5.3 XML-HTML Correspondence chart

Last updated 2015-09-03