Re: Two possible bugs bugging me

Thank you for this. It didn't occur to me there would be a new reference
manual for each new edition. Nor did it occur to me that there would be
such a thing as odd-numbered editions for developers. I am a musician, a
composer, one who has gotten quite a bit of really good use from
Lilipond. It fits my particular needs for vocal music much better than the
drag and drop programs. But I'm not a developer, and it's difficult for me
to parse a lot of the tech jargon. In fact, I'm leaving this group. It's
obviously not for me. I appreciate the help. I've compiled my own little
personal manual that works for a non-techy like myself, and this new piece
of code will be a useful addition to it.

Thanks again,

John Bari

On Tue, Jul 26, 2022 at 2:50 PM William Rehwinkel <
[email protected]> wrote:

> Hey Bari,
>
> For the first point...From looking at this page:
> https://lilypond.org/doc/v2.23/Documentation/notation/formatting-text ,
> the syntax for entering notes in markups is `\note {4} #1`. Does your
> syntax work in a previous version? If you are dealing with an older
> file, maybe running convert-ly will help alleviate this.
>
> best,
>
> -William
>
> On 7/26/22 14:32, John Ramsey wrote:
> > 1. I notice that the commands for showing musical notes within markups, {
> > \note #"8" #UP } and { \note #"2. " #DOWN } for instance, are not working
> > in version 22. Has this been changed to something else, or is it a bug?
> > It's still shown this way in the manual.
> >
> > 2. I do some of my rough drafts in MSWord and transfer the notations to
> > LilyPad. BUT as of version 22, I have a problem with quotation marks and
> > apostrophes. MSWord uses curly quote marks and curly apostrophes as a
> > default, which I would hate to change. And LilyPad is now only
> recognizing
> > straight ones. Curly commas are OK, but I have to manually change the
> > quotes and apostrophes after transferring the text to the .ly document,
> in
> > order to prevent strings of weird code. I always miss a couple, which
> > drives me nuts. (I'm halfway there as it is.) Can this be put back the
> way
> > it was?
> >
> > Respectfully submitted,
> > Bari Ramsey
> > _______________________________________________
> > bug-lilypond mailing list
> > [email protected]
> > https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
> --
> William Rehwinkel
>
> [email protected]
> https://williamrehwinkel.net
>
>
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond