Home > Resources for Contributors > Interpreting Feedback

Interpreting Feedback

Generally, collaborators will receive feedback on their work in the form of a PDF of the current state of the XML file, as shown in the “intermediate” view. In some cases, I may also or alternatively provide a PDF of one of the other views.

That PDF will include highlighted text, with comments showing the abbreviations below. In all cases, refer to the editorial criteria for your project when interpreting this feedback.

You will need to open the file in Acrobat Reader in order to most easily see the comments. You can download Acrobat Reader for free or access it through the cloud. In Acrobat Reader, you can also mark off the items as complete as you finish them.

Abbreviations

a – abbreviation. There seems to be a problem related to the expansion of an abbreviation. 

t – transcription. There appears to be a problem with the transcription itself. Compare what you have to the document image. 

r – regularization. There is a problem related to regularization. 

s – space. You’re missing space between words, or have space where it isn’t needed. This generally doesn’t refer to an error in transcription, but rather the inadvertent placement without spacing of two XML elements that need to be separated.

In all cases, these abbreviations may be followed by an explanatory comment in parentheses.

Color Coding

In the “edited text showing changes” view, text encoded with the following elements is color-coded as indicated:

<unclear> red

<supplied> orange 

<reg> green

<expan> blue

<corr> purple