URL: <https://savannah.gnu.org/bugs/?67831>
Summary: Dragging text markup in Print View on Windows can
corrupt file
Group: Denemo
Submitter: rshann
Submitted: Sat 20 Dec 2025 11:51:16 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: Sat 20 Dec 2025 11:51:16 AM UTC By: Richard Shann <rshann>
The current windows build use the old guile 1.8 version.
If markup used for a rehearsal mark includes certain characters, e.g. the en
dash (–) the character will be transformed into an invalid encoding when it
is re-written in the course of using the "Offset Position" feature in the
Print View.
The consequence for the user is that when written to disk the file cannot be
read back in. The only fix at that stage is to edit the file in a text editor
to remove the invalid characters.
The problem seems to be caused by Guile's eval-string procedure which is used
to retrieve the markup from the data field of the directive: it detects a
newline character inside the encoded character and replaces it with carriage
return newline so breaking the encoding. Subsequent uses of the Offset
Position routine spreads the invalid encoding to other fields in the
directive.
Hopefully this can be fixed by building the Windows version against a more
modern Guile version.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67831>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
