EVT 1 version 1.3 released!

The Xmas 2019 release

Dear EVT users,
after a long wait, EVT version 1.3 is finally available! Besides new features and bug fixes, we moved the repository to GitHub to make it more accessible: this is going to be the last version of the 1.* series, so enjoy the goodies, but also have a look at EVT 2 because that’s where all future development is going to have place!

You can quickly download the archive here (and the manual here), but you can also browse the sample editions directly on the project home page:

New and improved features

These are the main features for this release, those added since the previous release are preceded by a [NEW] label:

  • [NEW] verse visualization: poetic texts written as prose in diplomatic editions are now viewable as verses in the same edition frame, numbering of verses is now present in the standard prose-like text;
  • [NEW] translations: support has been added for translations of the edited text in multiple languages;
Old English text and Italian translation

Old English text and Italian translation

  • [NEW] VisColl support: EVT has integrated the VisColl XSLT style sheets so that it is now possible to prepare a description of manuscript structure and have EVT automatically create SVG diagrams in a dedicated frame;
  • [NEW] chronological index: editions which are based on multiple s can now be indexed chronologically using ;
  • [NEW] navigation bar: a new navigation bar has been added, which will be particularly useful for big manuscripts counting many folios;
VisColl quire structure and the new navigation bar

VisColl quire structure and the new navigation bar

  • [NEW] comment and critical notes: now EVT distingueshes critical notes from general, comment notes thanks to different exponents (different background color, alphabetic vs. numerical exponents); this will make it easier to create critical editions of codex unicus texts, or even of works with a very small number of witnesses;
Verse numbering and critical / comment notes

Verse numbering and critical / comment notes

  • [NEW] A Web interface for easy configuration is available at this URL:;
  • [IMPROVED] named entities support: now there’s a simple and powerful method to handle named entities, also it is now possible to define custom interesting elements which are going to be highlighted in the text;
  • [IMPROVED] support for : now and its sub-elements are supported;
  • many bug fixes and minor enhancements.


Sample documents

In this release the default example document is the Old English poem The Dream of the Rood, one of the texts encoded for the Digital Vercelli Book project which has been adapted to show all the new features available in this release. To better understand how the named entities work, however, you are advised to look into the Codice Pelavicino Digitale sample document (ed. by Enrica Salvatori). Finally, besides the usual TEI-based examples, we added a new document which is a play from Gherardi’s work, Le Théâtre Italien collection of plays (ed. by Barbara Sommovigo).

End of development cycle for EVT 1

As mentioned above, please note that this is the final release for EVT 1.*: after a short period to gather feedback and fix possible bugs in this version, the source code – which has been moved to a public repository on GitHub – is now fully shared with the user community to be modified and/or enhanced as other developers may see fit. From now on, all development efforts will focus on EVT 2 to reach feature parity with EVT 1 (with regard to diplomatic editions) and to improve / develop new features, starting from support for critical editions.

In any case, EVT 1.3 is a mature, featureful product which can be used “as is” for diplomatic / single witness editions, or can be further customized by anyone who has good knowledge of XSLT 2 and HTML/CSS.

Important note about testing a local installation

In the past, we always suggested that you use Firefox to test an EVT-based edition on your computer, but during 2019 things have changed: starting from version 67 Firefox developers adopted the same security-conscious policy chosen by developers of Chrome and other Web browsers, that is forbidding loading local files (= documents available on the user’s computer drive) in the browser as a result of the execution of Javascript programs. The goal is to improve global security when browsing the Web, but the unpleasant collateral effect is that of preventing the loading of digital editions based on EVT, or similar software, from local folders. Fortunately there are several workarounds that can be used to test EVT editions that are located on your hard drive:

  • option no. 1: launch Chrome from the command line with the –allow-file-access-from-files parameter, after that you can press CTRL+O to open the index.html file, or you can just drag and drop it on Chrome’s window; this is probably the most simple way to do it;
  • option no. 2: download and install Firefox ESR v. 60: this version predates the new security policy adopted in FF v. 67 and, furthermore, it can be installed in parallel with any other version of Firefox;
  • option no. 3: install an extension providing a local web server on Firefox or Chrome, f.i. there is this one available for Chrome:

This problem, however, only affects local testing, after the edition has been uploaded on a server there are no problems in accessing it with any of the major browsers.


As usual, user feedback is very much appreciated: please send all comments, suggestions, bug reports, etc. to Also, if you use EVT 1/2 for your work we would love to know about it!


The features in this release have been implemented by:

  • Chiara Di Pietro (general development lead, tireless bug fixing and improving of implemented features, new features such as named entities support)
  • Rocco Russo (verse numbering, visualization of poetic text as verses)
  • Greta Musso (VisColl support, navigation bar)
  • Chiara De Martin  (chronological index)
  • Federica Spinelli (support for translation, new exponents for critical/comment notes)
  • Giulia Cacioli (refinement of search engine, miscellaneous improvements, bug fixes)
  • Karel Pacovský (czech localization)
  • Roberto Rosselli Del Turco (general coordination, encoding of sample documents, documentation, testing, developer nagging)

Many thanks to all previous contributors (in particular: Raffaele Masotti, Julia Kenny and Jacopo Pugliese) and to all those who submitted bug reports and feature requests. Alberto Campagnolo helped us understand how VisColl works and helped Greta Musso while working on the EVT implementation and on her dissertation, thank you!


Lascia un commento

Pubblicato da su dicembre 20, 2019 in evt, release


Tag: , , ,

EVT 2 beta 1 available for download!

The Halloween release

It’s been more than a year after the initial release of the new version, but we think that it was worth waiting for it, just look at the new features! As usual the new release will be available from the SourceForge repository, but if you’re interested in the bleeding edge code it is all available on GitHub.

This release is the result of the hard work of Chiara Martignano (critical edition features), Maurizio Ricci (bibliographic entries handling), Roberto Rosselli Del Turco (documentation, testing), Chiara Di Pietro (general development overview, repository management, bug fixing).

Quite a number of new features

These are the main features available in EVT 2 beta, those added since the original alpha release are preceded by a [NEW] label:

  • Critical edition support: rich and expandable critical apparatus, variant heat map, witnesses collation and variant filtering are some of the main features developed for the critical edition.
  • Bookmark: direct reference to the current view of the web application, considering view mode, current document, page and edition level, eventual collated witnesses and selected apparatus entry.
  • High level of customization: the editor can customize both the user interface layout and the appearance of the graphical components.
  • [NEW] Critical edition features: support for critical apparatus, apparatus fontium and analogues in a dedicated text frame; support for multiple recensio editions; support for showing text sources in a parallel frame.
  • [NEW] Working area: now you can pin apparatus entries in a “pin frame” which will allow you to collect the most relevant ones for your research purposes, and to use them as bookmarks to quickly reach the desired parts of the critical text.
  • [NEW] Named entities support: basic support for named entities and lists, see the example from the Codice Pelavicino Digitale.
  • [NEW] Bibliography handling: bibliographic entries in a <listWit> can now be sorted by date, author or title, and they can be formatted in MLA or Chicago styles, ready to be copied and pasted in your working notes.

Available examples and configuration

This release comes with a few examples to show the new features and different use cases:

  • Example 1: A short extract of Edizione Logica Avicennae, changed by CM for EVT testing purposes. It presents multiple levels of apparatuses (critical entries, sources and analogues), displayed in a separate dedicated frame.
    • Filename: avicenna.xml
    • Configuration file: config_avicenna.json


  • Example 2: Pseudo edition for demonstration and testing purposes only, originally encoded by Marjorie Burghart for her TEI Critical Toolbox software, and modified in order to cover the highest number of possible use cases. It presents just the critical apparatus entry, displayed inline, within the main text.
    • Filename: pseudoEdition.xml
    • Configuration file: config_pseudoEdition.json


  • Example 3: Short extract of the Codice Pelavicino Digitale edition (, which presents the encoding of named entities, in particular person, place and organization names.
    • Filename: pelavicino.xml
    • Configuration file: config_pelavicino.json


  • Example 4: Short extract of The Tragedie of Doctor Faustus (B text) by Christopher Marlowe. Text provided by Perseus Digital Library, with funding from Tufts University. Original version available for viewing and download at
    • Filename: marlowe.xml
    • Configuration file: config_marlowe.json


The first example (Logica Avicennae) is by far the most complete and complex example with regard to critical edition support, but the pseudo-edition file is also a good way to check how how the TEI XML encoding of a critical edition works with EVT.


The third example, on the other hand, has been included to show that the porting of EVT 1 features is under way: at the moment you can see basic support for a diplomatic / interpretative edition and for named entities, but of course this is just the beginning. During next year a new image viewer will be implemented in EVT 2, so that it will be possible to add full support for diplomatic editions accompanied by digitized manuscript images.

Note that these are good starting point to start editing the config file for your edition, we advise that you keep the original example files for future reference, though.

Finally, we are also working on a web-based front-end for the configuration file, you can see and test a first version here:

Let us know how this tool worked for you!

Known issues

  • There may be some small glitches in text formatting, such as an extra white space before punctuation marks.
  • Similar errors in text formatting are present in the bibliographic entries.
  • When a version text is selected by clicking on the link inside of the entry panel (i.e. “Version B”), the view mode switches to the versions view and the selected version opens next to the main text box, but the two texts don’t scroll to the selected version entry.

Future development

Work has already started on the pre-1.0 version of EVT 2: this will be the first version to include all the features currently available in EVT 1 but not in the new Angular-based version, first and foremost a new powerful image viewer and a brand new search engine! Stay tuned for further announcements next year.


The announcement says it all: this is a beta release, i.e. while reasonably working and stable it surely isn’t bug-free, and it hasn’t been optimized yet, so you may experience slow-downs and the occasional freeze. If you find a bug please let us know! Also please remember that Chrome and Chrome-based browsers need to be launched with the –allow-file-access-from-files parameter to let them open the edition file(s) in EVT. If you want to save this hassle just install Firefox.

Another important caveat is the one about the User Interface: many new features have been added, but the UI has not yet been refined, so it may look a bit unfriendly right now. There will be a global UI redesign when we will merge all EVT 1 features in the new version, so stay tuned for a second beta announcement in 2018.


As usual, user feedback is very much appreciated: please send all comments, suggestions, bug reports, etc. to Also, if you use EVT 1/2 for your work we would love to know about it.


Lascia un commento

Pubblicato da su ottobre 31, 2017 in Uncategorized


EVT version 1.1.1 and version 2.0 alpha released!

Hello everybody,
we are back at you with what may be called a “double feature” release: two new versions of EVT at the same time! Here are the details.

EVT 1.1.1

This version is a follow-up to v. 1.1, which was released for the DH2016 conference, and adds support for yet another specific list (<listOrg>) besides a little refining. The 1.1 and following version was supposed to be a bug fix release, but we actually managed to include new features in it: EVT 1 is going to stay with us for a long time, which means that we definitely want to support it not only with bug fixes, but also with improvements when possible. Do not expect radical changes or brand new features in this version, however.

Here are the most important changes, please read the first item carefully:

  • changed the starting point of the transformation which is now based on <text> (also when using a <group> element): this is the most important difference compared to EVT 1.0, in fact note that the old method based on <div> does not work anymore, so please make sure to read the EVT 1.1.1 manual on this point;
  • added support for image formats other than JPEG;
  • added German language support thanks to Christian Schuster from Transylvania Digital Humanities Centre (DigiHUBB: who actually translated the English localization file;
  • added a template to rend italicized <title>s in <note>s;
  • added files for custom XSLT templates (evt_builder-custom-templates.xsl) and CSS rules (evt_builder-custom-styles.css), check section 3 of the manual;
  • added a distinction between critical <note>s and comment <note>s;
  • renamed evt_builder-miscellaneous.xsl into evt_builder-general.xsl;
  • added initial support for original content encoded into a <front>;
  • added support for <listOrg>;
  • many bug fixes!

Download it from the usual place and please report to us any problem that it may present. Your feedback is very much appreciated, as usual.

EVT 2.0 alpha

As the “alpha” tag suggests, this is not even a beta version of the new EVT 2 version. Actually it is very stable and does what it was created to do (support for critical editions in TEI XML format) quite well, but still has to be refined and, most of all, it lacks many important features available in EVT 1, the most critical one being support for digitized manuscript images.

EVT2 - Testimone frammentario

This is a very important release, however, because it is the first one based on the Angular.js framework and on the MVC design pattern, chosen because it allows to separate the logics of data presentation from the core of their processing. We needed more flexibility and modularity in order to make the development of new features easier and faster, and this has led to a completely new infrastructure: the XSLT stylesheets have been abandoned in favor of a set of JavaScript parsers specifically written to retrieve edition content directly from the XML file. Edition data is then saved in a JSON structure, organized in such a way that it can be easily and rapidly accessed when needed. The final styling of documents is entrusted to CSS style­sheets and is easily customizable.

EVT2 - Filtri

EVT2 - Heat map

Note that the current Javascript parser can only process TEI XML documents, but it is possible to add new parsers for different formats so that they are converted to the intermediate JSON structure, e.g. it is possible to add a custom XML (non­-TEI) parser, a LaTeX parser, etc.

These are the main features available in EVT 2.0 alpha:

  • Critical Edition support: rich and expandable critical apparatus, variant heat map, witnesses collation and variant filtering are some of the main features developed for the critical edition.
  • Bookmark: direct reference to the current view of the web application, considering view mode, current document, page and edition level, eventual collated witnesses and selected apparatus entry.
  • High level of customization: the editor can customize both the user interface layout and the appearance of the graphical components.

EVT2 - Varianti e note critiche

You can go straight to the online test site, but if you want to experiment with it you only have to download the archive from SourceForge and unpack it on your hard drive, after that you click on the index.html file and you are ready to go. If you want to try one of your documents you can do this by simply copying your file in the data folder and then editing the config.json file in the config folder: make sure that the dataUrl variable points to your file, e.g.

"dataUrl"          : "data/my_critical_edition.xml",

This version is the focus of all new development, so please let us know what you think of it writing at the usual contact email. Your feedback is even more appreciated for EVT 2 because this is the first public version and we definitely need to know if the path we have chosen is appropriate.

Many thanks to Marjorie Burghart for the TEI Critical Apparatus Toolbox which allowed us to perform a preliminary test of the TEI Parallel Segmentation method. A modified version of its sample file is the default pseudo-edition text showed in EVT 2.0 alpha.


1 Commento

Pubblicato da su luglio 28, 2016 in articles, evt, release


Tag: , , , ,

Second beta of the Digital Vercelli Book available!

As hinted in my previous post, a second beta of the Digital Vercelli Book published using EVT 1.0 is now available here:




Full announcement available here:

Lascia un commento

Pubblicato da su marzo 23, 2016 in Uncategorized


EVT version 1.0 has been released!

After a couple of intermediate releases, EVT version 1.0 is finally available! There are many new features in this version:

  • a full text search engine, with result highlighting in the text frame;
  • support for named entities: name highlighting in the edition text, browsable full lists with links to single documents;
  • support for <listPlace> and <listPerson> elements;
  • support for diplomatic documents (regesto) and for general information about specific texts;
  • support for bibliography, manuscript and project information;
  • User Interface localization;
  • lots of bugs fixed!

Go download it and check for yourself on the SourceForge site. For more information about how to use and/or customize EVT please refer to the EVT Manual included in the archive you downloaded, just look in the “doc” folder.

Please send all feedback to[1], we would love to hear from you: bug reports, suggestions, even your general impressions about how EVT has worked for you are more than welcome. If you want to check an actual edition made with EVT, possibly showing all the latest features, the excellent Codice Pelavicino Digitale [2] is just what you want to browse.


Named entities highlighting in the Codice Pelavicino Digitale

Also watch this space for an announcement about the Digital Vercelli Book 😉

EVT version 1.0 is the result of months of hard work by our development team:

  • Chiara Di Pietro
  • Raffaele Masotti
  • Julia Kenny
  • Ilaria Tiezzi
  • Chiara Alzetta
  • Jacopo Pugliese

Thank you all and congratulations for this achievement!


[1] You can also drop me a line at If for any particular reason you would prefer to send feedback anonymously, you can do it using this form; note, however, that it may take a little longer before one member of the development team checks it.

[2] The default EVT example in the 1.0 archive is in fact a single document from the Codice Pelavicino manuscript.


Lascia un commento

Pubblicato da su marzo 7, 2016 in evt, Uncategorized


Tag: , , , ,

SDE design: The agony and the ecstasy I

During all phases of EVT development the team members have had quite a number of lively discussions about the many topics and problems that such a (relatively) complex project entails: which programming and markup languages to use, basic features to implement in the beta version, the license to adopt when releasing EVT as open source software, the roadmap leading to its first release and subsequent ones, and more. Even considering roadmap-related issues, strictly linked to the financial and human resources available (hint: never enough of both!), the most heated debates revolve about one fundamental issue: which User Interface design for Scholarly Digital Editions should be implemented in EVT. This is easily explained if you think that we share basic ideas about most, if not all, of the technical aspects of software development, and that in any case I can only listen and then give green light on most of those issues, since Chiara, Julia and Raffaele have a competence in strictly technical aspects far exceeding mine; furthermore, roadmap-related issues usually fall in a sort of “external agents” category, be they impending university exams, a deadline for external projects or papers to be delivered, or quite simply a lack of adequate funding for all the nice things we have in mind.

UI (and UX: User Experience) design, on the other hand, is both an aspect of development we all believe to be fundamental for the success of EVT, and an area where every team member has her/his own specific sensitivity/orientation, therefore each of us has her/his own vision with regard how to make EVT “right“. A UI/UX done “right” makes a difference between a research tool that can prove useful to get stuff done, and a way to enjoy exploring and reading a digital edition besides that. Everyone in the team aims at this second goal besides the first one, and everyone has his/her own ideas about how to reach it. UI/UX development for EVT, therefore, is more a bumpy country road, where sometimes you get to regret how slowly you have to walk, than a speedy motorway leading you to the final, commonly shared destination. Also, there are lots of detours, dead-end streets and, of course, suffering and whining because of all the bumps 😉


“Getting the UI/UX right” for a software such as EVT is of primary importance for a number of reasons:

  • first of all, what is visible and actionable on the screen is “the edition” for our perspective users: at a markup level the edition is already there, but of course it is “invisible” for the intended public since without a tool such as EVT it wouldn’t be possible to access it, browse it, use it for research purposes or to simply enjoy viewing the manuscript images, reading the texts, and more; “getting the UI/UX right” means “getting the edition right” for all EVT users, and thence it is as important as “getting the edition right” at the markup and editorial level; note that, conversely, the marked up text is invisible to users once the edition has been published with EVT;
  • as noted by several researchers (see for instance Porter 2013 and my own 2011 article), a digital edition is still at disadvantage when compared with traditional printed editions because 1. digital editions are in small or big ways all different 2. you have to learn how to use them, both because of 1 and because they often include tools, such as text search/analysis tools, that are simply not available for printed editions (and, again, are all different in some way while sharing some common UI features); “getting the UI/UX right” also means lowering the learning curve as much as possible, with the ideal goal of making the digital edition as intuitive to use as a printed one;
  • last but not least, on the strictly technical level some aspects of the UI/UX are firmly connected with the internal workings of the software: a convoluted navigation system, for instance, would probably cause unnecessary stress on the software layer devoted to that specific purpose; vice versa, an elegant internal architecture would make it easier to devise an effective navigation method.

The first two points should be clear to everybody involved in the critical digital editing field, both creators and users of electronic editions. Indeed, we have received a good feedback about EVT by users of the Digital Vercelli Book beta, and generally appreciative remarks for its simple and elegant UI. Things are going to get more complicated soon (see below), but it never fails to surprise me how people may not be able to describe exactly what they what, but invariably recognize it when they’re presented with it. This is the general feeling with EVT and the VBD beta, even considering all its limitations, and it was a good one.


There’s another aspect to feedback, however, and it’s a darker, more troubling one: often the same people who appreciate a well done digital edition, and who are interested in using such resources on the Web, are not interested in taking part, if not in the actual design of such resources, in theoretical discourse about how to improve general usability and effectiveness of Scholarly Digital Editions. There is a general feeling that somehow, somewhere, somebody will come up with exactly the kind of resources that they need; not only that, but also the deeply ingrained conviction that an editor should do just that, prepare critical editions of his/her texts, and avoid at all costs getting involved with how these texts may be displayed and used in a digital edition: after all, this is why we have IT departments and technical personnel, right? not real “textual criticism” in action, is it? I will not surprise anyone by writing that I couldn’t disagree more with this line of thinking: it really is hard for me to imagine how an ICT professional, however excellent in his area of expertise, could design (not implement!) the perfect digital edition tool. Think of the “different layers …” of a critical edition, or even just the complexity of a full critical apparatus: who, if not a textual criticism scholar, is going to “get it right” when it comes to how and where the information is organized and showed to the user? Explaining to a programmer what we have done so far with printed editions, the rationale for critical apparatus etc. is not enough, since it’s the reason why so many first-generation digital editions resemble printed editions so closely, with a fixed layout similar to how the space is used on a printed page for the edition text, the critical apparatus, commentary notes etc.

For real innovation to happen in the SDE area with regard to their UI/UX component we all need to get our hands “dirty” with User Interface design: which doesn’t mean that anyone researching or studying textual criticism has to go out and buy the latest publications in HCI studies, of course, just sending detailed feedback to those creating digital editions and online resources would be a great start and a very appreciated help.

Those actually working on UI design for digital editions, on the other hand, need not only to listen to their own current and prospective users: they also need to put in place an effective way to share, discuss, accept and test UI design proposals. This is not a simple task in any research team, a fact of life that we discovered early during EVT development. The next post will be devoted to the work flow we are currently using and improving (or trying to) to design the next EVT version.


Porter, Dorothy C., ‘Medievalists and the Scholarly Digital Edition’, Scholarly Editing: The Annual of the Association for Documentary Editing, Volume 34 (2013) < > [accessed 20 April 2015].

Rosselli Del Turco, Roberto, ‘After the editing is done: designing a Graphic User Interface for Digital Editions’, Digital Medievalist Journal, 7 (2011). < > [accessed 20 April 2015].

Lascia un commento

Pubblicato da su aprile 20, 2015 in articles, evt, UI/UX


Tag: , , ,

TEI Embedded Transcription support in EVT

Since it was originally born as part of the Digital Vercelli Book project (, EVT was developed to deal with the XML encoding of texts which had been prepared for that project, namely making use of the XML TEI P5 parallel transcription method ( When using this method, information about the scan and possibly the coordinates of sensible areas are separated from the transcription and aligned with it thanks to linking attributes.

EVT-0.1.48-02The Vercelli Book Digital beta version using EVT

But, as it is possible to read in the TEI Guidelines, the scholar can choose to emphasize the importance of the physical surface and to encode words and other written traces as subcomponents of the XML elements representing the physical surface carrying them, rather than independently of them. This kind of encoding scheme is known as embedded transcription (, and thanks to support from EADH (see EADH Small Grant: Call for Proposals at this feature was added to the EVT software. The development took place in the period between May and July 2014.

Main changes to the original software

The main changes we implemented are mainly related to the identification and split of the text into different folios and the creation of the structure for the image-text linking tool.

Since the Vercelli Book transcription was completely encoded according to the parallel transcription method, we used different texts in order to have proper examples of embedded transcription; in particular, we used the TEI examples available in the Guidelines ( and the encoded text of the Slovenian «Tri Pridige O Jeziku (three sermons on language)» (

EVT-Slomsek-diplomaticThe Tri Pridige O Jeziku edition, an ET transcription, using EVT

First of all, we added an automatic detection of the encoded scheme used in the text that is being transformed (Parallel Transcription or Embedded Transcription): this identification is based on the absence/presence of the <sourceDoc> element, which is only used in ET.

If the system finds at least one <sourceDoc> element, the text will be treated as being encoded in ET: thus, each <sourceDoc> will be handled as a different document and each <surface> element, both when child of <sourceDoc> and when child of a <surfaceGrp> element, will be used to generate a single textual fragment.

We decided to consider the <surfaceGrp> element just as a mere generic division inside the code that does not produce any particular output in the interface. Moreover, even if the possible nestings of <surfaceGrp> are infinite, at the present moment the software is only able to support two levels.

The most important element after <sourceDoc> and <surface> is the <zone> element. This will be used to create the elements required for the activation of the image-text linking tool and of the hotspot tool.

A <zone> can be an empty node linked to one or more textual nodes, making use of the <line> element, or it can contain the text directly, without any further sub-elements. We considered both cases, therefore the XSLT transformation for the image-text linking tool will be activated with:

  • a <zone> element that contains some text and has the spatial coordinates attributes @ulx, @uly, @lrx and @lry. In this case, each sensitive area of the image identified by the previous coordinates will highlight all the text that was nested in the <zone>, even if it is distributed on more lines.



  • an empty <zone> element that has the spatial coordinates attributes and a reference to the particular <line> element it is linked to. Similarly to the previous case, each sensitive area of the image identified by the coordinates will highlight the text inside the element linked to the particular <zone>.

When the <zone> is missing the spatial coordinates attributes, the text-linking tool will not work, but the corresponding text (both if it is inside or outside the <zone> itself) will be rendered in the interface and nested in a particular HTML container (<div class=” *edition_level*–Zone “>), in such a way that the user can visually distinguish the separation between the different <zone> elements; the specific class (one for each edition level configured) allows to easily customize the visualization of the <zone> on the browser.

Instead, if the <zone> element is an empty node and the reference between it and the textual node is missing or broken, the text will properly appear on the page, but the image-text linking tool will not work for it, even if the <zone> had the spatial coordinates attributes.

As said before, in some cases the <zone> element will be used to generate an HotSpot, that is a sensible area on the image directly linked to a HTML pop-up window. We have decided to consider as a hotspot:

  • every <zone> that has the spatial coordinates attributes and is nested inside another <zone>; in this case the textual box will contain the text of the innermost zone;


  • every <zone> (even if a direct child of <surface>) that contains a <graphic> element with a @url attribute; in this case the textual box will contain the image referenced by the <graphic> element and the text inside the <zone> itself (if present).


All hotspots that were handled by means of the @rendition attribute in texts encoded in PT, will likewise work fine with texts encoded in ET.

Future developments

The remarkable variety of possible encodings available when using the Embedded Transcription method has made the task of supporting it more complicated than we expected. As it is clear from the section above, at least in this phase of development our support is somewhat “prescriptive”, in the sense that not every possible encoding is supported. This means that text encoded according to “reasonable” principles will very likely work, while in other cases it may or may not work and thence require some modifications to the encoded text. Since this is the first version of EVT supporting the Embedded Transcription method, we expect further improvements on the basis of users’ feedback: as always, feel free to contact us with your remarks, suggestions and feature requests. We have contacted the authors of the «Tri Pridige O Jeziku (three sermons on language)» edition mentioned above, and will experiment together with them with the goal of fine tuning ET support in EVT.


EVT Project
Roberto Rosselli Del Turco

List of participants

Chiara Di Pietro (
Julia Kenny (
Raffaele Masotti (


Digital Vercelli Book project:
EADH Supported activities and reports: [full report submitted to EADH].
Edition Visualization Technology:
Digital Vercelli Book beta version using EVT:
TEI P5 Parallel Transcription:
TEI P5 Embedded Transcription:
Tri Pridige O Jeziku (three sermons on language),

Post based on the final report by Chiara Di Pietro and Julia Kenny, revised and modified by R. Rosselli Del Turco.

2 commenti

Pubblicato da su novembre 11, 2014 in articles, evt


Tag: , , ,