|
|
 |
Transcriptions / Test |
 |
||||||||||
| § 1. Instructions / Commentary for viewing transcriptions online | ||||||||||
| § 2. NEUMES transcriptions online: Western manuscript sources | ||||||||||
| § 3. NEUMES transcriptions online: Eastern manuscript sources | ||||||||||
| § 4.
Roadmap of NEUMES transcriptions planned
A.
Sarum antiphoner, nocturns of Trinity Sunday
|
||||||||||
| § 5. Utilities | ||||||||||
| • See also, the NEUMES Data-Entry Applet | ||||||||||
|
||||||||||
A. Instructions for viewing a transcription in beta-test visualization: |
 |
||
 |
To have the NeumesXML document transformed on the Project Server (best choice):
Click  on the Siglum.[A siglum is the common abbreviation for the manuscript source.] |
||
| ~ Or ~ | |||
 |
To try having your browser transform the NeumesXML document:
Click the icon
 (left of Chant ID).
[Remark: Today's browsers generally do not correctly handle XSL Transformations.
We expect this situation will improve with the next generation of Web browsers.] |
||
B. Current problem with Western heighted sources |
|||
 A known problem in the beta-test visualization program
is that the offset (viz., the vertical position) of the first tone in multi-tone glyphs is unknown.
Images of heighted glyphs are positioned vertically according to a calculation that involves:
(a) the vertical position of the preceding glyph;
(b) internal Tonal Movement within the preceding glyph; and
(c) Tonal Movement from the last tone of the preceding glyph to the first tone of this glyph.
The problem, however, is that it is unkown where the first tone is located in this image.
In the case of a glyph with descending tone (such as the torculus shown here),
the image gets vertically aligned by the bottom tone instead of by the first tone, resulting in the glyph
being placed too high.
Unfortunately, this error also affects the placements of all subsequent glyphs, since the ending position
of the last tone in this glyph is incorrect. The short-term solution to this problem
is that we will create a manifest file for each glyph image set,
giving the dimensions of each image and the offset of the first tone in the glyph.
We call this the "baseline" of the glyph (see, illustration at right).
Glyph Manifest XML files have been created for several families of Western neume notation
(see, the 'Glyph Image Sets' section from the left-hand menu).In the long-term, however, our solution will be to enable transcribers to position glyphs exactly, in order to record more accurately the prima facie content of source manuscripts. We call this the "absolute position" of a glyph, and it will be part of the NEUMES character data as optional information about each transcribed symbol. Entering such information by-hand, however, would be impossibly tedious. The only feasible ways of doing this would be in conjunction with a graphical data-entry program or OCR (optical character recognition) from a source photograph. |
|||
C. Current problem with Eastern sources |
|||
Another known problem in the beta-test visualization program
is that the capability for 'stacking' glyphs of Eastern neume notations is quite limited. We have identified
twenty distinct positions in which glyphs can appear around the 'base glyph', as shown in the following diagram.
<- - - - - 1 - - - - -> ....................... 2 3 4 ....................... 5 6 7 ....................... ________ 8 / \ 11 | base | 9 | glyph | 12 \ / 10 \______/ 13 ....................... 14 15 16 ....................... 17 18 19 ....................... <- - - - - 20- - - - ->Unlike the substantial difficulty of problem 'B' regarding Western notations, the 'stacking' problem is fairly straightforward to solve: it just requires programming time that has not yet been available. |
|||
| Transcriptions: 3 | ||||||||||||||
|
Instance #1: heighted, unpitched source Remark: See, "Problem with Western heighted sources" (above). |
||||||||||||||
|
||||||||||||||
|
Instance #2: unheighted, unpitched source Remarks: This transcription is currently incomplete. No implementation problems. |
||||||||||||||
|
||||||||||||||
|
Instance #3: cleffed (pitched) source Remark: See, "Problem with Western heighted sources" (above). |
||||||||||||||
|
||||||||||||||
| Transcriptions: 1 | ||||||||||||||
|
Instance #1: square-neumed source Remark: Transcription currently online for testing. |
||||||||||||||
|
||||||||||||||
| Transcriptions: 1 | ||||||||||||||
|
Instance #1: square-neumed source Remark: Currently online for testing. |
||||||||||||||
|
||||||||||||||
| Transcriptions: 1 | ||||||||||||||
|
Instance #1: unheighted, unpitched source Remark: This transcription is being used for testing of software. |
||||||||||||||
|
||||||||||||||
|
Experiment #1 [approximate pitches by deduction]:
unheighted, unpitched source Remarks: Pitches were transcribed on the basis of the martyria and approximate Tonal Movements of the Neumatic Glyphs. A facility in NeumesXML that will allow transcribers to record deduced (non-prima facie) pitches is currently under development. |
||||||||||||||
|
||||||||||||||
|
Experiment #2 [stacked glyphs]: unheighted,
unpitched source Remarks: Compound glyphs in the Source are shown in the visualization by "stacking" of glyph images. The implementation in the visualization script is only a temporary solution, because the correct sequence of components in a compound glyph (viz., bottom-to-top) had to be reversed (top-to-bottom) in transcription so that the visualization would look correct. An implementation currently is being designed whereby complicated spatial relationships between component glyphs can be represented in the data. |
||||||||||||||
|
||||||||||||||
| Transcriptions: 1 | ||||||||||||||
|
Instance #1: post-Byzantine ('exegematic') source Remarks: New notation family. Online for software testing. Notice: This test transcription does not apply the necessary positioning. |
||||||||||||||
|
||||||||||||||
Sarum antiphoner; chants of the Matins Office for Trinity Sunday • Enumeration: 19 chants • Neume notation: Latin, pitched source on a four-line staff. •
Manuscript source for this set of transcriptions: Cambridge University Library, 
Cf., Roman ordo:
Invitatorium.
Cf., Roman ordo:
Officium lectionis.Remarks:
• The NEUMES Project is undertaking to digitally transcribe the full set of nocturns {def.} of the feast of Trinity Sunday from the Sarum antiphoner {def.}. • Motivation: There are no modern transcriptions at all of this section of the MS, by whatever method, as far as we know. Once numerous sources of the same music are digitally transcribed, it will become possible to identify variant readings and also to estimate the degree to which non-pitched sources are ambiguous. •
"Plate" refers to the facsimile print-edition, Antiphonale Sarisburiense, copyright 1901-1924;
{ • "CAO" refers to René-Jean Hesbert's index, Corpus Antiphonalium Officii. It is an index of chant texts, not melodies. • Notice: Viewing of full-page plate images requires that you disable 'Automatic Image Resizing' in your browser (cf., 'Internet Options/Advanced' in Internet Explorer). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
If you have a NeumesXML transcription on your computer's hard drive, you can view it in your browser by having the visualization transform done on the Scribe server. To do this, press the 'Browse' button (below) to locate the transcription on your hard disk, then press the 'Upload File' button.
|
|
Currently, the visualization transform (whether done on the Scribe server or by your browser) does not 'validate' transcription documents. (In other words, a visualization transform does not check that the transcription is grammatically correct against the NeumesXML Schema.) Until XSLT validating parsers are widely available, 'validation' must be done as a separate step. 1. You can Schema-validate a NeumesXML transcription that is under development. If the NeumesXML transcription is on your computer's hard drive, you can upload it to the W3C® Validator for XML Schema. You will see any syntax problems found in your NeumesXML file. To do this, press the 'Browse' button (below) to locate the transcription on your hard disk, and then press the 'Upload File' button.
2. You can Schema-Validate a NeumesXML transcription that exists on the Web by using the W3C® Validator for XML Schema. Type or paste the transcription file's URL into the box below, then click 'Submit URL'. • To use this Validator option, the transcription must exist on a server somewhere on the Web. • If you just wish to see what the Schema-Validator does, then highlight-and-copy the following URL of NeumesExample.xml into the lower box.
|
Help resources:
