At the top of your Oxygen window, click File and then select New from the drop down menu.

In the window that pops up, scroll down to the Framework templates folder. Click on the LEMDO subfolder. This will show you a list of the templates that we have created.

Select the template that you wish to use.

At the bottom of the New file window, select Save as. If you know the pathway down which you wish to save your file, you can type it into the available field (i.e., lemdo/data/texts/{your edition abbreviation}/{the appropriate folder}). Otherwise, click on the folder to the right of the text field and browse for the correct directory. Name your file according to LEMDOʼs naming conventions.

Click Create.

Follow the instructions outlined in your newly created file. We use XML comments liberally in template files to provide you with instructions and helpful tips. You may delete comments as you complete the tasks therein.

The first step is to right click on the file in Oxygenʼs project view:

Here, we want to transform emd1H4_F1.xml, which lives in data/texts/1H4/main.

Next, hover over Transform and select Transform with…:

Note that we generally do not need to configure transformation scenarios for specific files. This will permanently associate a specific transformation with the file that you are working on. Most of the time, we only need to use a transformation once on a file and we do not want it to be associated with the file long-term as we do not want to repeatedly apply the same transformation.

When you click Transform with…, a window will open allowing you to select the appropriate transformation:

In this case, we want to number line beginnings in a semi-diplomatic transcription, so we will select lemdo_number_wlns_lb_in_semi-dip. If you are uncertain which transformation to use, or you want us to add a new transformation to our list, please email lemdotech@uvic.ca.

After clicking the Apply selected scenarios button, we open the file to check that the transformation has worked as expected:

The <lb> elements with @type="wln" now have consecutively numbered @n attributes. The transformation has successfully worked as expected.

As always, the last step in Oxygen is to validate the file.