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 (http://pelavicino.labcd.unipi.it/), 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 http://www.perseus.tufts.edu/hopper/.
- 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!
- 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.
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 email@example.com. Also, if you use EVT 1/2 for your work we would love to know about it.