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
One of the MS73 folios I processed in November has a syllable that doesn't have a <facs> element, so it doesn't have a bounding box. It's the very first syllable: 141v-285.mei.zip
I made an issue about that in the MEI_encoding repo, but there's still the question of how Neon should deal with a syllable like that if it happens. At the moment, if I ungroup the syllable that has no <facs>, this happens:
The first resulting baby syllable also doesn't have a <facs>;
All of the other resulting baby syllables do have a <facs>, but all of their bounding boxes have both an lry and a uly of 0, so they're effectively invisible.
@yinanazhou would it be possible for Neon to assign a syllable a <facs> if it doesn't have one? I suppose another solution would be to delete the offending syllable, but in the case of the file I've uploaded here the bad syllable is huge, so deleting it would remove almost all the neumes on the first staff.
The text was updated successfully, but these errors were encountered:
I checked the files you provided. You are not seeing the bbox for the syllable text because the <zone> is invalid, all the coordinates are 0s. And Neon check and remove these invalid zones and its corresponding elements. I remember invalid all-zero zones have happened before, but I can't find the issue :(
One thing I could do in Neon is to generate a bbox based on the syllable position, like the default bbox when you insert a syllable. How does that sound to you?
And I will check the cause of these all-zero zones in MEI encoding.
One thing I could do in Neon is to generate a bbox based on the syllable position, like the default bbox when you insert a syllable. How does that sound to you?
That would be perfect, thank you! I'll put the files you asked for in the MEI encoding issue
One of the MS73 folios I processed in November has a syllable that doesn't have a
<facs>
element, so it doesn't have a bounding box. It's the very first syllable: 141v-285.mei.zipI made an issue about that in the MEI_encoding repo, but there's still the question of how Neon should deal with a syllable like that if it happens. At the moment, if I ungroup the syllable that has no
<facs>
, this happens:<facs>
;<facs>
, but all of their bounding boxes have both anlry
and auly
of 0, so they're effectively invisible.@yinanazhou would it be possible for Neon to assign a syllable a
<facs>
if it doesn't have one? I suppose another solution would be to delete the offending syllable, but in the case of the file I've uploaded here the bad syllable is huge, so deleting it would remove almost all the neumes on the first staff.The text was updated successfully, but these errors were encountered: