What uses should one look at? For `raise` I’ve found `chord-name.scm` (this 
patch is an improvement, see [#5371]) `define-woodwinds-diagram.scm` and maybe 
`musicxml2ly.py`.

The latter seems to have to do with accordion symbols, I have no idea what’s 
going on there.
`define-woodwinds-diagram.scm` uses `raise` for accidentals too but in an 
absolute-fontsize context so I suppose one cannot change this from the outside 
→ no problem?

 The markup command `lower` doesn’t occur at all.


---

** [issues:#5375] Let \raise and \lower heed font-size**

**Status:** Started
**Created:** Sat Jul 07, 2018 05:08 PM UTC by David Kastrup
**Last Updated:** Sun Jul 29, 2018 11:47 AM UTC
**Owner:** David Kastrup
**Attachments:**

- [Screenshot 07-08 
.png](https://sourceforge.net/p/testlilyissues/issues/5375/attachment/Screenshot%2007-08%20.png)
 (468.3 kB; image/png)


Let \raise and \lower heed font-size

This is more in line with using them on text, their primary target.


This is actually an incompatible change in meaning but most uses
appear to be more correct afterwards than before, so no convert-ly
rule.  Warrants discussion.

http://codereview.appspot.com/343330043


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto

Reply via email to