Here are some things I tried to make breve and longer rests hang both in 
RhythmicStaff (different line count) and in TabStaff (different staff-space):

* translate up by (staff-space - 1) → works for TabStaff (staff-space = 1.5) 
and Staff (staff-space = 1, so no visible change) but fails for different 
fontsize
* translate by (staff-space - fontsize) in brew_internal_stencil → dots are 
offset
* translate by (staff-space - fontsize) in y_offset_callback → 
Staff_symbol_referencer::get_position gives non-integer values → computing 
whether ledgered breve should be chosen in TabStaff fails, breve dots are offset
* change the font so that the glyphs hang from the base-line → not SMuFL 
compliant (according to [this part of the 
specification](https://w3c.github.io/smufl/gitbook/specification/scoring-metrics-glyph-registration.html)
 only semibreve rests should hang), would need a change in all other fonts made 
for LilyPond

And one thing I didn’t try:

* don’t use glyphs from the font but draw rectangles and ledger lines with 
Lookup::round_filled_box or similar commands → fonts cannot specify width of 
the rests, widths would only come from Rest.style or another grob property.

Are there other ideas how to use the glyphs from the font?


---

** [issues:#5258] Vertical breve rest position in TabStaff/RhythmicStaff**

**Status:** Started
**Created:** Sat Jan 13, 2018 04:47 PM UTC by Malte Meyn
**Last Updated:** Mon Jan 15, 2018 07:25 AM UTC
**Owner:** Malte Meyn
**Attachments:**

- 
[breve_rests.png](https://sourceforge.net/p/testlilyissues/issues/5258/attachment/breve_rests.png)
 (26.0 kB; image/png)
- 
[gould_breve_rests_oneline.png](https://sourceforge.net/p/testlilyissues/issues/5258/attachment/gould_breve_rests_oneline.png)
 (27.9 kB; image/png)


According to Gould breve rests should hang from a one line staff 
(RhythmicStaff) as semibreve rests do. Also, there is a comment in 
multi-measure-rest.cc saying
```
// Staff position is somewhat icky regarding its definition for
// compatibility reasons.  It is intended to be the baseline of
// a breve rest.  However, when the staff space is more than
// single space (like with tablature), it looks better if all
// rests are actually hanging.  So staff position, in reality,
// is the semi-breve position - 2.  Everything else is
// calculated from there.
```
This confirms what Gould writes. But the code applies only to MMRs with a 
measure-count > 1.

That leads to inconsistent behaviour: MultiMeasureRest breve glyphs hang, but 
not for single measures. Rest breve glyphs don’t hang. Instead, all breve rests 
should hang.
```
\version "2.19.80"

music = {
  \compressFullBarRests
  r1 R1 R\breve
  \time 4/2
  r\breve R\breve R\longa
  \time 8/2
  r\longa R\longa
}

\new TabStaff \with { \tabFullNotation } \music

\new RhythmicStaff \music

\new Staff \music
```


---

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
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... 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