search

openlilylib / scholarly

ScholarLY, a library for annotating LilyPond scores
GNU General Public License v3.0
24 stars 6 forks source link

Object representation in LaTeX output #11

Open uliska opened 8 years ago

uliska commented 8 years ago

When exporting annotations to the .inp LaTeX input file there are a number of properties that are exported in Schemes #< > "object" representation, e.g. #<Grob NoteHead >, which LaTeX doesn't like at all. So this has to be a way to change that (that's why it has the "bug" label).

The question is whether to tackle that on the LilyPond/Scheme or the LaTeX side.

My suggestion is to "sanitize" this during the export to LaTeX code, similar to the approach taken in dc2c2082. This has the advantage that at this stage we're still in LilyPond and can access arbitrary information about the object to be displayed. That is we can select the behaviour according to the object at hand and generate suitable code for the LaTeX export.

jefferyshivers commented 8 years ago

5a53ebbaedc8c2c25d15089b7ed4d07375e200f3 lets grob location filter back through, though I'm not sure if it's the most efficient approach.

uliska commented 8 years ago

That looks like a good fallback solution for object types that haven't been treated explicitly yet.

jefferyshivers commented 8 years ago

Is the aim to reformat those separately in the key list?