[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Parse inline scheme using per-expression port (issue 557330043 by ad
|
From: |
Han-Wen Nienhuys |
|
Subject: |
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden) |
|
Date: |
Mon, 10 Feb 2020 09:41:48 +0100 |
On Sun, Feb 9, 2020 at 7:00 PM <address@hidden> wrote:
> On 2020/02/09 17:18:19, hanwenn wrote:
> > David, please take another look.
>
> First, you are aware that the rationale for
>
> This commit fixes a problem with GUILE 2.2.6, where LilyPond
> calculates offsets in the source file as bytes, while GUILE
> interprets
> the source file as UTF-8 encoded Unicode. As a result, files with
> Unicode before embedded scheme break completely.
>
> is fixed in current master?
Yes. See also the list of commits that are effectively reverted by this
commit.
Note that there is still an off-by one error in the handling of closures
and parsing #{
which makes the satb template regtests fail, both in GUILE 1.8 and 2.x
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), dak, 2020/02/07
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/09
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), dak, 2020/02/09
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden),
Han-Wen Nienhuys <=
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), David Kastrup, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), David Kastrup, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/11
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), David Kastrup, 2020/02/10
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/11
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), lemzwerg, 2020/02/13
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), jonas . hahnfeld, 2020/02/13
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/13