No, this is fine: Guile 1.8 stays the default for now and the compatibility
`define`s make sure that the change only affects Guile 2.x
---
** [issues:#5834] Fix most encoding problems with Guile 2.x**
**Status:** Started
**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
Individual commits:
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.
http://codereview.appspot.com/555420043
---
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.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
