Werner LEMBERG wrote:
We're still working on formatting issues -- I tend to send one email
to Sebastiano each day; the latest issue was automatically escaping
@[EMAIL PROTECTED] for the texidoc strings.
Uh. Those braces are completely irritating!
The problem is this: in LSR, a user sees this:
----
The property @code{chordNameExceptions} can used to store a list of
special notations for specific chords.
----
and he wonders what on earth the @code means. Now, if we only use HTML
for the snippet description, we could standardize on
<texttt>chordNameExceptions</texttt>
to be @code{} in the texidoc. (err, I think \texttt is LaTeX.
Whatever the HTML equivalent is)
I thought that {chordNameExceptions} was an acceptable compromise for
the next couple of days until we figure out how to fix this. It'll
certainly be fixed before the next stable release!
although I'm not certain what to do about snippets that use HTML for
descriptions. (currently we strip away all the HTML tags)
They should be converted to texinfo format, probably manually.
No, no! Absolutely no manual stuff!
Sebastiano is very helpful (and amazingly fast) at adding extra
text-conversion rules. As long as we can give an exact formulation for
the conversion, he can add such a rule.
When I get a chance, I'll edit all those files in LSR to include the
fixes you've made.
I don't care. In case it's necessary, just drop or ignore them.
Cameron offered to do this, and it'll be good practice for him. :)
Cheers,
- Graham
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
