|From:||Auto mailings of changes to Lily Issues via Testlilyissues-auto|
|Subject:||[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5834 Fix most encoding problems with Guile 2.x|
|Date:||Sun, 08 Mar 2020 09:35:02 -0000|
No, this is fine: Guile 1.8 stays the default for now and the compatibility
defines make sure that the change only affects Guile 2.x
[issues:#5834] Fix most encoding problems with Guile 2.x
Created: Sat Mar 07, 2020 06:46 PM UTC by Jonas Hahnfeld
Last Updated: Sat Mar 07, 2020 09:50 PM UTC
Owner: Jonas Hahnfeld
Fix most encoding problems with Guile 2.x
1) Treat possibly incomplete UTF-8 as binary
replace_special_characters checks that the substring doesn't start
mid-UTF-8, but it does not guarantee that it ends in a complete glyph.
So just explicitly treat it as binary when creating the SCM.
While modifying the function, avoid comparison of zero-length substrings.
2) Use UTF-8 for all conversions to / from Scheme
LilyPond really expects all input to be encoded in UTF-8, and we should
not let GUILE 2.x mangle with it.
Sent from sourceforge.net because address@hidden 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.
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
|[Prev in Thread]||Current Thread||[Next in Thread]|