[MEI-L] Where to report customization service bugs?

Johannes Kepper kepper at edirom.de
Sun Aug 4 11:07:21 CEST 2013

Hi Thomas,

I admit that this is somewhat tricky. All references should be relative to the driver.xml file in the repository, but when checking the current situation, I just noticed that the CSS is not contained in the zip you get from custom.music-encoding.org. So the current behavior is definitely faulty, and you should report that an Google Code. However, we already planned to revise the service and integrate it better with the website itself. Looking at our current schedule, this won't happen before September, and even September is pretty dense already… You may have to be patient, or you could volunteer ;-)


Am 04.08.2013 um 07:11 schrieb TW:

> Hi all,
> would it make sense to report problems with the customization service
> via the Google Code issue tracker?
> The problem:  When generating guidelines, the CSS files are missing
> and the image links point to the wrong directory (or the images are in
> the wrong directory, depending on what perspective you take).
> Have a nice Sunday!
> Thomas
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l

More information about the mei-l mailing list