Bill Mitchell writes:
|> > > The same problem happens if you write, for example,
|> > > title = "The \\textit{ABC} of Music";
|> > >
|> >
|> > What is the difficulty about writing regular expressions to match
|> > everything from one double quote to the next unescaped double quote.
|>
|> The problem is to parse the TeX code which may contain nested
|> curly braces of any depth. The example above would result in:
|>
|> \def\mudelatitle{The \textit{ABC}%
|> of Music}%
|>
|
|An obvious fix for this example, at least, is to change the formatter
|so that it doesn't add a '%' when it breaks a line at a place that had
|white space in the original input.
I disagree, ly2dvi parses the TeX output of lilypond a line at a
time. Therefore we need lilypond output to look like:
\def\mudelatitle{The \textit{ABC} of Music}%
Maybe lilypond could use a different output formatter while outputting
header information?
Jeff
--
Jeffrey B. Reed
[EMAIL PROTECTED]
