It sometimes happens that in the straight-outta-omr file, the coordinates of the bounding box of the first syllable are all 0. This is from folio 264r:
After uploading the file to Neon and adding text to the syllable, the syllable in the MEI has a syl with the input text, but the coordinates of the bounding box aren't listed at all. As a consequence, the syllable has no bounding box, no matter what I do.
This issue also happens in 264v and the MEI looks the same. Here are the files:
264r.mei.zip
264v.mei.zip
The only fix is to delete the neumes and input them back in. I'd estimate this issue occurs in one out of three folios, but it isn't super urgent, because it only applies to a single syllable per folio.
This issue was first mentioned in the Neon repo here DDMAL/Neon#790, but since the original problem is already present in the straight-outta-omr file, it's probably an mei encoding issue. The issue doesn't happen in every folio, but when it does it always affects only the very first syllable.
It sometimes happens that in the straight-outta-omr file, the coordinates of the bounding box of the first syllable are all 0. This is from folio 264r:
After uploading the file to Neon and adding text to the syllable, the syllable in the MEI has a
sylwith the input text, but the coordinates of the bounding box aren't listed at all. As a consequence, the syllable has no bounding box, no matter what I do.This issue also happens in 264v and the MEI looks the same. Here are the files:
264r.mei.zip
264v.mei.zip
The only fix is to delete the neumes and input them back in. I'd estimate this issue occurs in one out of three folios, but it isn't super urgent, because it only applies to a single syllable per folio.
This issue was first mentioned in the Neon repo here DDMAL/Neon#790, but since the original problem is already present in the straight-outta-omr file, it's probably an mei encoding issue. The issue doesn't happen in every folio, but when it does it always affects only the very first syllable.