Copyright held by
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Further details of licences are available from our
Licences page. For more
information, contact the project director,
Born Digital
Most MoEML documents, or significant fragments with mol:
prefix and accessed through the web application
with their id + .xml
.
The molagas prefix points to the shape representation of a location on MoEML’s OpenLayers3-based rendering of the Agas Map.
Links to page-images in the Chadwyck-Healey
Links to page-images in the
The mdt (MoEML Document Type) prefix used on
The mdtlist (MoEML Document Type listing) prefix used in linking attributes points to a listings page constructed from a category in the central MDT taxonomy in the includes file. There are two variants, one with the plain _subcategories
, meaning all subcategories of the category.
The molgls (MoEML gloss) prefix used on
This molvariant prefix is used on
This molajax prefix is used on
The molstow prefix is used on
The molshows prefix is used on
The sb prefix is used on
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
PDF documents are created by transforming the html
source document to an XSL:FO
file that gets processed into a fixed (image-like) PDF document. In order to get to the final format that we want, the files are processed multiple times. Our main concern is to preserve as much of the theme and feel of Early Modern works in general, and MoEML works in particular, all the while conforming to the PDF (and XSL:FO
) requirements and restrictions. To this end, we carefully create attribute-sets documents that replicate the styling of the source file, within the limitations of FO. This means that we need to account for some inline attributes and values that we cannot know to generate globally for the project, along with the ones that we can generally retrieve from appropriate CSS
files. Thus, we parse the style element of each document (inside the
then parses the source file and assigns appropriate attribute sets to the corresponding FO elements.
The cover page is delicately designed to represent the feel of the project and the primary source MoEML works. The page has the MoEML decorative daisy and a snippet of the
PDFs have a hybrid metadata title page that contains the title of the work, author(s), compiler(s), editor(s), and the publication information, which basically indicates the version of MoEML with which this edition was published, and the corresponding date. The PDFs also list the credits, have a running head, and mostly conform to the layout of traditional books.
When building a PDF document, the build application first retrieves the source file from our Jenkins repository. The file gets processed to remove elements and details that are mainly for web purposes including (but not limited to) navigation, breadcrumbs, search, and send feedback. The build application then creates the special styles module, which is the one that contains the document specific styling attributes. This module gets included in the master file. Further, to create the PDF files, we need to copy images and fonts, which is achieved by the build application during the process. The process also checks for the latest version of the FOP
application, and downloads it if it is not available.
Note that a global file, named pdf_globals.xsl
, contains functions, variables, and parameters that are common to the entire build process and files.
In order to create the final file and document specific XSLT
code, we process multiple XSLT
s that write and override general PDF code. For example, add_special_styles_to_fo_master.xsl
allows us to include a special document styles module in the master XSLT
. The PDF global file also has functions that allow us to add specific classes and their attributes to the elements. It also creates a document that contains the classes and attributes, with the name of docID_styles_module.xsl
. The resulting XSLT
has a function—getAtts
—that overwrites attributes and values that would otherwise break the FO file.
The PDFs will be published on MoEML’s UVic libraries UVicSpace—UVic’s Research and Learning Repository (https://dspace.library.uvic.ca/handle/1828/10927). MoEML is part of the
For more detailed information about the PDF building process, please see the developers’ PDF documentation.