URL: <https://savannah.gnu.org/bugs/?67917>
Summary: Lilypond export adds (invalid?) spaces in chorded
notes
Group: Denemo
Submitter: None
Submitted: Fri 16 Jan 2026 09:16:02 AM UTC
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Open/Closed: Open
Discussion Lock: Unlocked
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Fri 16 Jan 2026 09:16:02 AM UTC By: Anonymous
Chorded notes (polyphony), when exported as Lilypond, hvae spaces between the
note and the octave (apostrophe or comma), except for the last note, e.g.:
the output for the attached example is:
c'4 <e ' g'> <g ' b ' d''> <b ' d '' f '' a''>
^ ^ ^ ^ ^ ^
where I expect it to be:
c'4 <e' g'> <g' b' d''> <b' d'' f'' a''>
I stepped over this when writing a parser for a Lilypond converter.
The Lilypond application seems to tolerate this, but it seems unnecessary and
requires an additional rules for parsing the exported .ly file.
Denemo version is 2.6.10 (Windows)
_______________________________________________________
File Attachments:
Name: SpacesTest.ly Size: 1.1KiB
<https://file.savannah.gnu.org/file/SpacesTest.ly?file_id=58118>
Name: SpacesTest.denemo Size: 3.8KiB
<https://file.savannah.gnu.org/file/SpacesTest.denemo?file_id=58117>
AGPL NOTICE
These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://savannah.gnu.org/source/savane-c0e7328b0919e9b907c12a3a42c8f9bea29fbc0e.tar.gz
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67917>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
