search

music-encoding / guidelines

:scroll: The Music Encoding Initiative Guidelines
Educational Community License v2.0
23 stars 29 forks source link

Chapter 05 (dev): MEI examples to be rendered in Verovio are not shown #175

Closed martha-thomae closed 4 years ago

martha-thomae commented 4 years ago

For some reason, in the development version of the guidelines, the MEI examples that I included in the "mei/dev/" folder are not showing. Just the first example is shown, the "notes_rests.mei", but all following are not displayed (neither the MEI encoding nor the Verovio rendition of it). In my local machine, all examples do render (see link).

I don't know why this is happening. I have cloned this exact same repo and while the examples are displayed on my local machine they are not displayed on the website.

martha-thomae commented 4 years ago

Also, the font for the examples is different, the one shown on my local machine makes the MEI encoding easier to read (see the text in bold and the different colors).

kepper commented 4 years ago

Without havind had a closer look at the problem itself: The CSS for the Guidelines is provided in the https://github.com/music-encoding/music-encoding.github.io repo, which admittedly is a nightmare to debug and should be changed asap. This probably doesn't explain why examples don't show up, but it could explain why things look different, assuming that you have a local copy of that other repo running locally…

lpugin commented 4 years ago

(@kepper I feel every day worse and worse about the guidelines setup which was my proposal. Please get rid of it as soon as you can.)

I'll have a look at the Verovio stuff. We can go back to static images if this is preferred.

martha-thomae commented 4 years ago

@kepper, that could be the case for the fonts since I do have the website's GitHub also cloned (well, a fork of it, but same thing).

Thanks, @lpugin for taking a look!

BTW, I love the Verovio stuff! I certainly do prefer this over static images because it is good to see that the encodings can actually be rendered somewhere (here, Verovio). It would also be good to have the same thing as the tutorials (or in the Verovio website) where you can click on "show full encoding" as well.

kepper commented 4 years ago

@lpugin, no worries. You had good arguments, which apparently convinced us all at some point ;-) But after a couple of years of operating this setup, we have a better picture now, and see that the benefits come at a cost we didn't foresee back then. We'll change that situation now, but it's already clear that every setup will have it's own issues…

lpugin commented 4 years ago

It should be fixed. The problem came from the capital letters in the file names. GitHub servers make the distinction be upper and lower case. Another reason to move away from the current setup ;-) Until then we need to use always lower case filenames.

martha-thomae commented 4 years ago

Thank you, Laurent!

bwbohl commented 4 years ago

It should be fixed. The problem came from the capital letters in the file names. GitHub servers make the distinction be upper and lower case. Another reason to move away from the current setup ;-) Until then we need to use always lower case filenames.

could you please document somewhere which files have to stick to lowercase naming scheme?