You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In scores such as pl-wtm--r-248-n--002, the verse number is encoded in the text data rather than in an interpretation. This causes the verse number to be displayed as a syllabe which is elided to the next syllable for the notes (which is the true single syllable for the note):
In the Humdrum data:
Correct encoding:
Which produces the desired result:
where the 1. is placed before the note, and the real syllable is aligned with the note. Spine splits require care: the *v: interpretation should occur before the spine split (or should be placed in the left side split perhaps).
Detecting probable problems in a single file:
extractx -i text pl-wtm/kern/pl-wtm--r-248-n--002_noskowski-zygmunt--na-wodzie.krn | serialize | ridx -H | grep "[0-9].* "
1. Już
2. Nie-
3. My
This one is complicated since it also has **mod-text spines:
extractx -i mod-text pl-wtm/kern/pl-wtm--r-248-n--002_noskowski-zygmunt--na-wodzie.krn | serialize | ridx -H | grep "[0-9].* "
1. Już
2. Nie-
3. My
The first verse has a space after the number: *v:1 . This is fragile since spaces before or after a token are not generally used (and I may automatically remove them). So some other symbol should be invented to represent a space).
Other examples:
current
new
Nro.1. Un
*v:Nor.1.
Nro1. A-
*v:Noro1.
N.2 A-
*v:N.2
-7 Do-.
*v:-7 (strange sorts of cases need checking that this is a verse number)
V 1. ir-
*v:V 1.
Note that the script does not check when there is no space after the verse number (but this could be added).
The text was updated successfully, but these errors were encountered:
In scores such as pl-wtm--r-248-n--002, the verse number is encoded in the text data rather than in an interpretation. This causes the verse number to be displayed as a syllabe which is elided to the next syllable for the notes (which is the true single syllable for the note):
In the Humdrum data:
Correct encoding:
Which produces the desired result:
where the
1.
is placed before the note, and the real syllable is aligned with the note. Spine splits require care: the*v:
interpretation should occur before the spine split (or should be placed in the left side split perhaps).Detecting probable problems in a single file:
This one is complicated since it also has
**mod-text
spines:Commit 4a7c4c8 adds the script bin/verseCheck
This script can be run from the makefile target:
Here is the output of the script, which identies 141 files with verse problems in
**text
and 8 files where the verse problem is in**mod-text
.Click to view verse encoding problems.
Note that in cases where the style of the verse is other than ending in a
.
, you can use other characters in the*v:
token:View in VHV
The first verse has a space after the number:
*v:1
. This is fragile since spaces before or after a token are not generally used (and I may automatically remove them). So some other symbol should be invented to represent a space).Other examples:
Nro.1. Un
*v:Nor.1.
Nro1. A-
*v:Noro1.
N.2 A-
*v:N.2
-7 Do-
.*v:-7
(strange sorts of cases need checking that this is a verse number)V 1. ir-
*v:V 1.
Note that the script does not check when there is no space after the verse number (but this could be added).
The text was updated successfully, but these errors were encountered: