Hi everyone
Found a solution for my issue.
Just wrote a little bash-script which does the following:
- replace all spaces with underlines in the filenames of the current directory
- running the lilypond-book preprocessor
- running the latex processor
- replace all underlines with spaces in the fi
Hi André,
I'm not sure how it has been done but if you don't use lilypond-book but
the new lyluatex package (obviously requiring LuaLaTeX) you *can* use
spaces and special characters in file names.
lyluatex (https://github.com/jperon/lyluatex) is a package that does
everything lilypond-book
Hi
Thanks for your answers.
I'm not expert in the technical internals of LilyPond and/or LaTeX,
but I'm pretty sure the problem could be solved in LilyPond.
Why?
Let's have a look of how LilyPond-embedding in LaTeX works:
LaTeX itself knows nothing abount LilyPond and how to interpret *.ly files
On 13.02.2018 14:36, André Rohrbach wrote:
Just tried to use special characters (mostly spaces and single quotes)
in filenames while working with \lilypondfile.
I’m pretty sure this is an issue with LaTeX syntax, not with LilyPond.
Also, it’s good advice anyway to not use spaces in file names,
On 2/13/2018 7:36 AM, André Rohrbach wrote:
Sent this already as question to the lilypond-users mailing list, but
they told me to just prevent from using special characters in file
names.
I'm pretty sure that everyone who reads the bug-lilypond list also reads
the lilypond-user list. The quest
Hi :)
I use LilyPond in combination with LaTeX since a few weeks and I'm
very happy about this great piece of software!
A few days ago I came across an issue using lilypond-book:
Just tried to use special characters (mostly spaces and single quotes)
in filenames while working with \lilypondfile.
