Description of problem: Lilypond is not rendering non-ascii characters anymore, even though it has full unicode support. Besides authors having names with non-ascii characters, it's common to have French, German or Italian words in classical musical scores, which do require proper unicode support. Version-Release number of selected component (if applicable): lilypond-2.19.42-1 How reproducible: Any .ly input file with unicode characters will produce output with those characters replaced by "?". Steps to Reproduce: 1. Create a `test.ly' file with the contents: \version "2.19.42" { c'' ^ \markup{ "this is a test: ñ" } _ \markup{ "and this is another: " \char ##x00F1 } } 2. Run `lilypond test.ly' 3. Open the `test.pdf' file that was created. Instead of having two "ñ" characters, they'll be replaced by two "?".
CC: (none) => marja11Assignee: bugsquad => rverschelde
After a bit of investigation, it appears that Lilypond isn't compatible with guile 2.0. It claims "experimental" support, but it's clearly very incomplete. The main issue seems to be assumptions about the internal representation of strings, which changed between guile 1.8 and 2.0. There are comments in Lilypond's code about how it could be changed for the newest version; I tried doing the changes, but it still doesn't work. I suggest Lilypond to be built with guile 1.8 instead of leaving it broken.
Should be fixed in next lilypond update reverting back guile 1.8: - lilypond-2.19.44-2.mga6
CC: (none) => geiger.david68210