Re: guile-2.0 and debian
2016-11-20 23:23 GMT+01:00 Antonio Ospite :
> On Sun, 20 Nov 2016 22:07:39 +0100
> Antonio Ospite wrote:
>
>> On Sun, 20 Nov 2016 01:12:59 +0100
>> Thomas Morley wrote:
>>
> [...]
>> > Well, this example gives a gs-error again:
>> >
>> > \header { title = "ちりぬるを)" } \markup \null
>> >
>>
>> The problem here is that, when writing to the postscript file, the
>> escaping is (mistakenly) done before the encoding, so the escaped "\)"
>> gets represented in UTF-16 as "^@\^@)" which makes the ')' not really
>> escaped anymore and ghostscript fails.
>>
>> I'll try to come up with a better solution for this problem.
>>
>
> I think I got it this time. David?
>
> All the previous changes to scm/framework-ps.scm can be replaced by
> these:
>
> --
> diff --git a/scm/framework-ps.scm b/scm/framework-ps.scm
> index a404119..da341eb 100644
> --- a/scm/framework-ps.scm
> +++ b/scm/framework-ps.scm
> @@ -28,6 +28,10 @@
> (scm clip-region)
> (lily))
>
> +(if (guile-v2)
> + (use-modules (rnrs bytevectors)
> + (ice-9 iconv)))
> +
> (define format ergonomic-simple-format)
>
> (define framework-ps-module (current-module))
> @@ -518,9 +522,14 @@
>(define (metadata-encode val)
> ;; First, call ly:encode-string-for-pdf to encode the string (latin1 or
> ;; utf-16be), then escape all parentheses and backslashes
> -;; FIXME guile-2.0: use (string->utf16 str 'big) instead
> +;; With guile-2.0: use (string->utf16 str 'big) instead
> +(if (guile-v2)
> + (let* ((utf16be-bom #vu8(#xFE #xFF)))
> +(ps-quote
> + (string-append (bytevector->string utf16be-bom "ISO-8859-1")
> + (bytevector->string (string->utf16 val 'big)
> "ISO-8859-1"
> + (ps-quote (ly:encode-string-for-pdf val
>
> -(ps-quote (ly:encode-string-for-pdf val)))
>(define (metadata-lookup-output overridevar fallbackvar field)
> (let* ((overrideval (ly:modules-lookup (list header) overridevar))
> (fallbackval (ly:modules-lookup (list header) fallbackvar))
>
> --
>
> This looks a lot cleaner, no messing around with the file port encoding
> anymore, so now the "format" command down in the function does not need
> to be split.
>
> It looks like that no substitutions into '?' take place when
> bytevector->string is called with the "ISO-8859-1" encoding.
Hi Antonio,
at least I couldn't break it anymore. :)
Though, I noticed you didn't change the comment right at start of
framework-ps.scm:
;;; this is still too big a mess.
lol
Cheers,
Harm
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
2016-11-19 16:05 GMT+01:00 Antonio Ospite : > > I managed to have "make LANGS='' doc" succeed again, there was > a transient failure, but just rerunning the make command worked. > > This is with the patches at: > https://ao2.it/tmp/lilypond-guile2/patches_2016-11-19/ on top of the git > tag "release/2.19.50-1". > > With this setup your test file should work. The test-file indeed works, but not "make LANGS='' doc" Earlier every file in the regtests gave a gs-error, now it happens frequently, but not always. Here a cutoff from the log for two files: input/regression/center-title.ly worked input/regression/chord-name-minor.ly not I don't get the essential difference... Processing `./29/lily-e0ac5d9b.ly' Parsing... Renaming input to: `/home/hermann/lilypond-git/input/regression/center-title.ly' Interpreting music... Preprocessing graphical objects... Calculating line breaks... Drawing systems... Writing header field `texidoc' to `./29/lily-e0ac5d9b.texidoc'... Writing ./29/lily-e0ac5d9b-1.signature Writing ./29/lily-e0ac5d9b-2.signature Layout output to `./29/lily-e0ac5d9b.eps'... Converting to `./29/lily-e0ac5d9b.pdf'... Converting to PNG... Layout output to `./29/lily-e0ac5d9b-1.eps'... Layout output to `./29/lily-e0ac5d9b-2.eps'... Converting to `./29/lily-e0ac5d9b-1.pdf'... Converting to `./29/lily-e0ac5d9b-2.pdf'... Writing ./29/lily-e0ac5d9b-systems.texi... Writing ./29/lily-e0ac5d9b-systems.tex... Writing ./29/lily-e0ac5d9b-systems.count... Processing `./56/lily-44b4b5eb.ly' Parsing... Renaming input to: `/home/hermann/lilypond-git/input/regression/chord-name-minor.ly' Interpreting music... Preprocessing graphical objects... Calculating line breaks... Drawing systems... Writing header field `texidoc' to `./56/lily-44b4b5eb.texidoc'... Writing ./56/lily-44b4b5eb-1.signature Layout output to `./56/lily-44b4b5eb.eps'... Converting to `./56/lily-44b4b5eb.pdf'... warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./56/lily-44b4b5eb.pdf -c.setpdfwrite -f./56/lily-44b4b5eb.eps)' failed (256) As before compiling them as standalone files works without problems. Cheers, Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
Thomas Morley writes:
> 2016-11-20 23:23 GMT+01:00 Antonio Ospite :
>> On Sun, 20 Nov 2016 22:07:39 +0100
>> Antonio Ospite wrote:
>>
>>> On Sun, 20 Nov 2016 01:12:59 +0100
>>> Thomas Morley wrote:
>>>
>> [...]
>>> > Well, this example gives a gs-error again:
>>> >
>>> > \header { title = "ちりぬるを)" } \markup \null
>>> >
>>>
>>> The problem here is that, when writing to the postscript file, the
>>> escaping is (mistakenly) done before the encoding, so the escaped "\)"
>>> gets represented in UTF-16 as "^@\^@)" which makes the ')' not really
>>> escaped anymore and ghostscript fails.
>>>
>>> I'll try to come up with a better solution for this problem.
>>>
>>
>> I think I got it this time. David?
In general I think you are better off reverting to "bytevectors" for
most of our purposes since they don't result in unnecessary conversions.
But they really require at least Guile 2.0.12 in order to not have some
showstopper bugs interfering.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
On Mon, 21 Nov 2016 10:37:31 +0100 Thomas Morley wrote: > 2016-11-19 16:05 GMT+01:00 Antonio Ospite : > [...] > > With this setup your test file should work. > > > The test-file indeed works, but not "make LANGS='' doc" > > Earlier every file in the regtests gave a gs-error, now it happens > frequently, but not always. > > Here a cutoff from the log for two files: > input/regression/center-title.ly worked > input/regression/chord-name-minor.ly not > I don't get the essential difference... > [...] > Writing header field `texidoc' to `./56/lily-44b4b5eb.texidoc'... > Writing ./56/lily-44b4b5eb-1.signature > Layout output to `./56/lily-44b4b5eb.eps'... > Converting to `./56/lily-44b4b5eb.pdf'... > warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4 > -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite > -sOutputFile=./56/lily-44b4b5eb.pdf -c.setpdfwrite > -f./56/lily-44b4b5eb.eps)' failed (256) > > As before compiling them as standalone files works without problems. > Can I look at your ./56/lily-44b4b5eb.eps file? Ciao, Antonio -- 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? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
2016-11-21 10:49 GMT+01:00 Antonio Ospite : > Can I look at your ./56/lily-44b4b5eb.eps file? Here you are. Cheers, Harm lily-44b4b5eb.eps Description: PostScript document ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
On Mon, 21 Nov 2016 10:59:17 +0100 Thomas Morley wrote: > 2016-11-21 10:49 GMT+01:00 Antonio Ospite : > > > Can I look at your ./56/lily-44b4b5eb.eps file? > > Here you are. > The problem is that there are still some numbers formatted with commas as decimal points when producing EPS: it shows in the standalone command line too if you use '-dbackend=eps'. The following change fixes it: - diff --git a/ly/init.ly b/ly/init.ly index 58b2fac..8fdc6e2 100644 --- a/ly/init.ly +++ b/ly/init.ly @@ -9,7 +9,8 @@ #(if (guile-v2) (begin (use-modules (ice-9 curried-definitions)) - (setlocale LC_ALL ""))) + (setlocale LC_ALL "") + (setlocale LC_NUMERIC "C"))) #(session-initialize (lambda () - And this will also replace my previous ugly attempt of messing around with LC_NUMERIC in lily/general-scheme.cc. Ciao, Antonio -- 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? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCHES: Countdown for November 21st
Hello, Here is the current patch countdown list. The next countdown will be on November 24th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ __ Push: 4752 Add ly:one-page-breaking - Paul Morris https://sourceforge.net/p/testlilyissues/issues/4752 http://codereview.appspot.com/288910043 Countdown: 5000 Add using Extract PDFmark for document building - Masamichi Hosoda https://sourceforge.net/p/testlilyissues/issues/5000 http://codereview.appspot.com/314130043 4999 Synchronize \layout and \midi definitions - David Kastrup https://sourceforge.net/p/testlilyissues/issues/4999 http://codereview.appspot.com/316910043 Review: No patches in review at this time. New: No New patches at this time. Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: PATCHES: Countdown for November 21st
I just pushed the patches for issue 4752 (Add ly:one-page-breaking) to staging. Hopefully they don't break staging this time, and if they do we can capture the logs to find out what's not working. Thanks, -Paul On 11/21/2016 07:58 AM, James wrote: Hello, Here is the current patch countdown list. The next countdown will be on November 24th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ __ Push: 4752 Add ly:one-page-breaking - Paul Morris https://sourceforge.net/p/testlilyissues/issues/4752 http://codereview.appspot.com/288910043 Countdown: 5000 Add using Extract PDFmark for document building - Masamichi Hosoda https://sourceforge.net/p/testlilyissues/issues/5000 http://codereview.appspot.com/314130043 4999 Synchronize \layout and \midi definitions - David Kastrup https://sourceforge.net/p/testlilyissues/issues/4999 http://codereview.appspot.com/316910043 Review: No patches in review at this time. New: No New patches at this time. Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: PATCHES: Countdown for November 21st
Paul, On 21/11/16 14:56, Paul wrote: I just pushed the patches for issue 4752 (Add ly:one-page-breaking) to staging. Hopefully they don't break staging this time, and if they do we can capture the logs to find out what's not working. Thanks, -Paul This merged just fine. Thanks James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
MacUpdate - your app listing has been updated
[1][macupdate-logo.png] top background App Listing Updated Hi lilypond.org, We have updated your application listing for LilyPond 2.19.51-1 on [2]MacUpdate.com. Please take a moment to review your application's information to make sure that everything is correct. [3]View your updated app listing view your updated app You can [4]login to your Developer Account to reply to comments and view stats, or [5]submit new updates and changes to your app listing. [6]MacUpdate Desktop install compatibility Desktop Install Compatibility MacUpdate Desktop 6 is helping developers make it easier for users to fully install and use their apps. Download Desktop 6 and to ensure your app works with the “Install” link on our download pages. Advertise With MacUpdate The best Mac devs advertise their apps on MacUpdate.com because it’s the most targeted, highly performing Mac app advertising you can find on the web. Contact a...@macupdate.com to guarantee your annual ad campaigns get booked and expand your app’s audience. Learn more view your updated app MacUpdate Desktop install compatibility Questions? Contact our Content Update Team [7]upda...@macupdate.com. bottom background You are receiving this offer because you have an app listed on MacUpdate.com. Add us to your address book or white list to ensure reliable delivery. © 2014 MacUpdate LLC - All Rights Reserved 526 W. 14th St. #100 • Traverse City, MI 49684 [devemail-lilypond] References Visible links 1. https://www.macupdate.com/?utm_source=macupdate&utm_medium=email&utm_term=LilyPond&utm_content=appupdate&utm_campaign=dev_emails 2. https://www.macupdate.com/?utm_source=macupdate&utm_medium=email&utm_term=lilypond&utm_content=appupdate&utm_campaign=dev_emails 3. https://www.macupdate.com/app/mac/19024/lilypond?utm_source=macupdate&utm_medium=email&utm_term=lilypond&utm_content=appupdate&utm_campaign=dev_emails 4. https://www.macupdate.com/member/login?utm_source=macupdate&utm_medium=email&utm_term=lilypond&utm_content=appupdate&utm_campaign=dev_emails 5. https://www.macupdate.com/developers/update/?utm_source=macupdate&utm_medium=email&utm_term=lilypond&utm_content=appupdate&utm_campaign=dev_emails 6. https://www.macupdate.com/desktop?utm_source=macupdate&utm_medium=email&utm_term=lilypond&utm_content=appupdate&utm_campaign=dev_emails 7. mailto:upda...@macupdate.com Hidden links: 8. https://www.macupdate.com/advertise?utm_source=macupdate&utm_medium=email&utm_term=lilypond&utm_content=appupdate&utm_campaign=dev_emails ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: PATCHES: Countdown for November 21st
Great thanks! -Paul On 11/21/2016 11:15 AM, James wrote: Paul, On 21/11/16 14:56, Paul wrote: I just pushed the patches for issue 4752 (Add ly:one-page-breaking) to staging. Hopefully they don't break staging this time, and if they do we can capture the logs to find out what's not working. Thanks, -Paul This merged just fine. Thanks James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
2016-11-21 13:09 GMT+01:00 Antonio Ospite : > On Mon, 21 Nov 2016 10:59:17 +0100 > Thomas Morley wrote: > >> 2016-11-21 10:49 GMT+01:00 Antonio Ospite : >> >> > Can I look at your ./56/lily-44b4b5eb.eps file? >> >> Here you are. >> > > The problem is that there are still some numbers formatted with commas > as decimal points when producing EPS: it shows in the standalone > command line too if you use '-dbackend=eps'. > > The following change fixes it: > > - > diff --git a/ly/init.ly b/ly/init.ly > index 58b2fac..8fdc6e2 100644 > --- a/ly/init.ly > +++ b/ly/init.ly > @@ -9,7 +9,8 @@ > #(if (guile-v2) >(begin > (use-modules (ice-9 curried-definitions)) > - (setlocale LC_ALL ""))) > + (setlocale LC_ALL "") > + (setlocale LC_NUMERIC "C"))) > > #(session-initialize >(lambda () > - > > And this will also replace my previous ugly attempt of messing around > with LC_NUMERIC in lily/general-scheme.cc. I reverted locally "Print floating point variables using a period as the decimal separator" and applied your code above. I got a successful "make LANGS='' doc" That's great! Next would be a full "make doc" or at least with the Japanese docs to proof non latin. And I'd like to do a regtest-comparison, between builds with guile 1.8.8 and 2.0.13 Although, I currently don't know if this is possible at all with our "make test-baseline"/"make check"-procedures. Will try tomorrow. If all this only would not last ages on my weak laptop... Thanks, Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
