Stylesheet Info While Building MEI Using Oxygen and Command Line

[yinanazhou]

Do the command line instructions for building the MEI guidelines use the same stylesheet as the instructions in Oxygen? Are they both using music-encoding/utils/guidelines_xslt/odd2html.xsl ? or is the command line method using something in music-encoding/submodules/Stylesheets ?

[ahankinson]

This would suggest that it uses the same one?

https://github.com/music-encoding/music-encoding/blob/develop/build.xml#L158

[yinanazhou]

Ohhhhhh! That's the bug! I got it! Thank you soooo much!
We did get that error!

[ahankinson]

What's the bug? Could you describe it so that others who might have the same problem will know how to fix it?

[yinanazhou]

Oh, sorry! The relative paths are what make the images not showing up when using Oxygen. When switching between different methods, the image paths should be adjusted accordingly.

[ahankinson]

Or you could write the output from Oxygen to a different place, presumably?

[yinanazhou]

Yes, if the output paths are the same, the relative path will work in both ways. I will try to change the output path from Oxygen.

[bwbohl]

Is there something missing from the build description for oXygen that would avoid the problem?

[yinanazhou]

Sorry, I was mixing things up. The relative path shouldn't be the problem. I checked it again with @martha-thomae today, and we found that when using Oxygen, the image folder was not copied into music-encoding\source\web. That is why all the images do not show up. After pasting the image folder manually into music-encoding\source\web, all the images do show up.

[martha-thomae]

Hi @bwbohl! So, the thing is:

When you use the command line instructions, you have all these files generated in music-encoding/dist/guidelines/dev/web:

You can see that it includes an images folder (which is probably copied from the music-encoding/source/images/ folder).

On the other hand, when you use the Oxygen building instructions, this is the file structure that you get in music-encoding/source/web:

It is missing the images folder. Therefore, the relative path to any image (../images/modules/<something>), which works perfectly on the folder generated by the command line instructions (first screenshot), doesn't work on the HTML file generated by Oxygen because there is no images folder in the first place (second screenshot).

(Thanks for the screenshots, @yinanazhou)

[bwbohl]

many thanks for the info

[musicEnfanthen]

Follow up question: Why is the command line building to music-encoding/dist/guidelines/dev/web, but Oxygen building to music-encoding/source/web?

[bwbohl]

Ok, apparently after checking music-encoding/build.xml the images folder is not being copied to destination by the XSLT but by Ant. Nevertheless you can run Ant based Transformation Scenarios from within oxygen XML Editor. We should update the build instructions for oXygen accordingly.

[bwbohl]

I hope to give it a try next week, but if anyone is faster, feel free to ;-)