Re: GUILE 2.2 progress

[David Kastrup]

Han-Wen Nienhuys <address@hidden> writes:

> On Sat, Jan 25, 2020 at 8:16 PM David Kastrup <address@hidden> wrote:
>> > $ gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89
>> > -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
>> > -dAutoRotatePages=/None -dPrinted=false -sOutputFile=mozart-hrn-3.pdf
>> > -c.setpdfwrite -f/tmp/lilypond-OCyOzh
>> > Error: /rangecheck in /--.parsecff--
>> > Operand stack:
>> >    false   --nostringval--
>>
>> Pretty sure this is an encoding problem.
>
> the question is how this managed to work on GUILE 2.0.

Which Guile 2.0?  The Guile developers changed the behavior several
times during the "stable release" series.

> We're embedding the OTF/CFF font (which is binary data) into a string
> without considering any encoding. The string then gets dumped onto the
> PS file.

I think there were a few changes.  We got it working a few times.

-- 
David Kastrup