Re: guile-2.0 and debian

[Antonio Ospite]

Hi everyone,

On Mon, 14 Nov 2016 01:15:52 +0100
David Kastrup <address@hidden> wrote:

> Thomas Morley <address@hidden> writes:
> 
> > Short update:
> > I managed to get guile 2.0.13 and guile-2.0-dev for 2.0.13 (grabed it
> > from Zesty Zapus which will be Ubuntu 17.04)
> > Successful make with all of Antonios patches (didn't try make doc so far).
> >

In the latest version of my notes I forgot to mention that I am using
2.0.13 from Debian unstable. It was in the first draft.

> > Though, _every_ compilation of a .ly will cause a gs-error.
> >
> > Even for { c1 } I get:
> >
> > lilypond-git atest-40.ly
> > GNU LilyPond 2.19.51
> > Processing `atest-40.ly'
> > Parsing...
> > Interpreting music...
> > Preprocessing graphical objects...
> > Finding the ideal number of pages...
> > Fitting music on 1 page...
> > Drawing systems...
> > Layout output to `/tmp/lilypond-6s1XBB'...
> > Converting to `atest-40.pdf'...
> > warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595,28
> > -dDEVICEHEIGHTPOINTS=841,89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
> > -r1200 -sDEVICE=pdfwrite -sOutputFile=atest-40.pdf -c.setpdfwrite
> > -f/tmp/lilypond-6s1XBB)' failed (256)
> >
> > fatal error: failed files: "atest-40.ly"
> >
> > Will try to continue tomorrow, too late today.
> 
> That one is going to be another (re)encoding error, this time when
> writing PostScript.  It may or may not be a different problem than the
> ones I experienced: Masamichi-san fairly recently made some changes to
> font handling that also were concerned with byte transparency.
> 

Thomas what is your locale?

If run lilypond with my default locale (LANG=it_IT.utf8) I get this
error too; as I wrote somewhere, running the "gs" command on its own
showed that in my case this was due to the EPS file containing commas
as decimal separator instead of periods.

Running lilypond like this worked around the issue for me:

  $ LANG=C lilypond-git atest-40.ly

Does this work for you too?
BTW setting only LC_NUMERIC instead of LANG could be enough.

As happened often in my naive attempt to move things forward I could
spot where the problem was but due to my lack of knowledge about
lilypond and guile I am not always able to figure out what the correct
fix is.

For instance if David, or someone else, could confirm that patch 0005
[1] actually makes sense I would propose it for inclusion in lilypond.

Thanks,
   Antonio

[1]
https://ao2.it/tmp/lilypond-guile2/0005-Fix-ending-the-dynamic-extent-in-Text_interface-inte.patch

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?