>>> So do we need any warnings or notes to be added to here:
>>>
>>> http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond
>>>
>>> and/or here:
>>>
>>> http://lilypond.org/doc/v2.19/Documentation/notation-big-page#entire-document-fonts
>>>
>>> ?
>> In
Hosoda-san,
On 07/06/16 13:54, Masamichi Hosoda wrote:
So do we need any warnings or notes to be added to here:
http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond
and/or here:
http://lilypond.org/doc/v2.19/Documentation/notation-big-page#enti
>>> Any idea why this is so? Could you contact the gs people by filing
>>> a bug report so that we get an explanation?
>>
>> If I understand correctly, there is four issues at least. [...]
>
> Thanks for your analysis.
There is ghostscript developers reply.
http://bugs.ghostscript.com/show_bug
> So do we need any warnings or notes to be added to here:
>
> http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond
>
> and/or here:
>
> http://lilypond.org/doc/v2.19/Documentation/notation-big-page#entire-document-fonts
>
> ?
In my humble opini
Hosoda-san,
On 06/06/16 14:44, Masamichi Hosoda wrote:
I've tried some Japanese fonts with `-dgs-load-fonts' option. [...]
So most Japanese fonts can not be used with `-dgs-load-fonts'
option.
Any idea why this is so? Could you contact the gs people by filing a
bug report so that we get an e
>> Any idea why this is so? Could you contact the gs people by filing
>> a bug report so that we get an explanation?
>
> If I understand correctly, there is four issues at least. [...]
Thanks for your analysis.
Werner
___
lilypond-devel mailin
>> I've tried some Japanese fonts with `-dgs-load-fonts' option. [...]
>>
>> So most Japanese fonts can not be used with `-dgs-load-fonts'
>> option.
>
> Any idea why this is so? Could you contact the gs people by filing a
> bug report so that we get an explanation?
If I understand correctly,
> I've tried some Japanese fonts with `-dgs-load-fonts' option. [...]
>
> So most Japanese fonts can not be used with `-dgs-load-fonts'
> option.
Any idea why this is so? Could you contact the gs people by filing a
bug report so that we get an explanation?
Werner
___
>>> In addition, all fonts of the above without `-dgs-load-fonts' option are
>>> fine.
>>> I suggest removing `-dgs-load-fonts' option from lilypond-book.
>>> I think that `--bigpdfs' option is more suitable than
>>> `-dgs-load-fonts'.
>>
>> Either make for particularly large PDF files, don't the
>> In addition, all fonts of the above without `-dgs-load-fonts' option are
>> fine.
>> I suggest removing `-dgs-load-fonts' option from lilypond-book.
>> I think that `--bigpdfs' option is more suitable than
>> `-dgs-load-fonts'.
>
> Either make for particularly large PDF files, don't they?
If
Masamichi Hosoda writes:
> In addition, all fonts of the above without `-dgs-load-fonts' option are fine.
> I suggest removing `-dgs-load-fonts' option from lilypond-book.
> I think that `--bigpdfs' option is more suitable than
> `-dgs-load-fonts'.
Either make for particularly large PDF files, d
> As of
> http://www.mail-archive.com/bug-lilypond@gnu.org/msg40846.html
> I had uninstalled Noto and instead installed IPA fonts _and_ IPAex fonts.
> After uninstalling IPAex fonts - first the test-case worked and now I
> have success on a full `make doc'.
It seems that fonts-ipaexfont-{mincho|go
2016-06-04 15:12 GMT+02:00 Masamichi Hosoda :
>> In addition, the following command sequence succeeds:
>>
>> lilypond-book aaa-lilybook-test.lytex
>> latex aaa-lilybook-test.tex
>> dvips aaa-lilybook-test.dvi
>> ps2pdf aaa-lilybook-test.ps
>> evince aaa-lilybook-test.pdf
>>
>> aaa-lilybook-test.ps
> In addition, the following command sequence succeeds:
>
> lilypond-book aaa-lilybook-test.lytex
> latex aaa-lilybook-test.tex
> dvips aaa-lilybook-test.dvi
> ps2pdf aaa-lilybook-test.ps
> evince aaa-lilybook-test.pdf
>
> aaa-lilybook-test.ps is >16MB again, though.
Thank you for your results.
2016-06-03 23:57 GMT+02:00 Thomas Morley :
> 2016-06-03 14:02 GMT+02:00 Masamichi Hosoda :
>>> %%% start of aaa-lilybook.lytex
>>>
>>> \documentclass[a4paper]{article}
>>>
>>> \begin{document}
>>>
>>> \begin{lilypond}
>>> \markup {
>>> %foo bar buzz
>>> いろはにほへど ちりぬるを
>>> }
>>>
>>> \end{lily
2016-06-03 14:02 GMT+02:00 Masamichi Hosoda :
>> %%% start of aaa-lilybook.lytex
>>
>> \documentclass[a4paper]{article}
>>
>> \begin{document}
>>
>> \begin{lilypond}
>> \markup {
>> %foo bar buzz
>> いろはにほへど ちりぬるを
>> }
>>
>> \end{lilypond}
>>
>> \end{document}
>>
>> %%% end of aaa-lilybo
> %%% start of aaa-lilybook.lytex
>
> \documentclass[a4paper]{article}
>
> \begin{document}
>
> \begin{lilypond}
> \markup {
> %foo bar buzz
> いろはにほへど ちりぬるを
> }
>
> \end{lilypond}
>
> \end{document}
>
> %%% end of aaa-lilybook.lytex
>
> always fails with:
>
> $ lilypond-book --o
Thomas Morley writes:
> First the good news.
> With a build from a checkout of recent staging, I can successfully run
> make LANGS='' doc
> without any failure for orchestra.ly
> ... as soon as I comment/delete all japanese !!
Yes, it was pretty obvious that we are talking about two separate
pro
>> Hmm, pdflatex... What happens if you enforce xelatex?
>
> $ lilypond-book --latex-program=xelatex --output=out --pdf \
>aaa-lilybook.lytex
> [...]
> fatal error: failed files: "28/lily-a7047c84.ly"
OK. What Japanese font is used in the lilypond-book example? Is it
the same
2016-06-02 23:19 GMT+02:00 Werner LEMBERG :
>
>> Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default
>> page settings.
>
> Hmm, pdflatex... What happens if you enforce xelatex?
$ lilypond-book --latex-program=xelatex --output=out --pdf aaa-lilybook.lytex
lilypond-book (GNU LilyPond
> Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default
> page settings.
Hmm, pdflatex... What happens if you enforce xelatex?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilyp
First the good news.
With a build from a checkout of recent staging, I can successfully run
make LANGS='' doc
without any failure for orchestra.ly
... as soon as I comment/delete all japanese !!
But it allways fails for any japanese in the doc.
I spent some time to boil it down to a minmal example
James writes:
> Oh Well, Lilydev complains about the same make doc error when (I use
> -j5) - I am 99% sure, I haven't time now to look at the full output,
> but the messages generated on the console are so familiar that I am
> almost sure it is the same thing.
>
> I have to leave now for Home.
On 16-05-30 01:31 AM, Knut Petersen wrote:
Is there anybody out there who succeeds to build the current lilypond
documentation on a 64 bit linux machine with a 64 bit toolchain?
Please report cpu as well as versions of gcc and guile.
Linux Sherlock 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu
James writes:
> David if you need anything from any of these outputs on my machines
> here at work, let me know and I'll do whatever tests or output that
> you think might be helpful.
>
> Hope the Nettle-reaping was successful.
Scything. There is nothing to reap, they just have to be kept from
On 30/05/16 16:59, David Kastrup wrote:
James writes:
Hello
On 30/05/16 15:06, David Kastrup wrote:
James writes:
Zipped Valgrind output of both OSes is attached to this email or can
be obtained here:
https://drive.google.com/file/d/0B9nZ5LHV2Ds6dGU5VTJjOGNlSm8/view?usp=sharing
By far
James writes:
> Hello
>
> On 30/05/16 15:06, David Kastrup wrote:
>> James writes:
>>
>>> Zipped Valgrind output of both OSes is attached to this email or can
>>> be obtained here:
>>>
>>> https://drive.google.com/file/d/0B9nZ5LHV2Ds6dGU5VTJjOGNlSm8/view?usp=sharing
>> By far most complaints are
Hello
On 30/05/16 15:06, David Kastrup wrote:
James writes:
Zipped Valgrind output of both OSes is attached to this email or can
be obtained here:
https://drive.google.com/file/d/0B9nZ5LHV2Ds6dGU5VTJjOGNlSm8/view?usp=sharing
By far most complaints are in the GC marking phase and complain ab
James writes:
> Zipped Valgrind output of both OSes is attached to this email or can
> be obtained here:
>
> https://drive.google.com/file/d/0B9nZ5LHV2Ds6dGU5VTJjOGNlSm8/view?usp=sharing
By far most complaints are in the GC marking phase and complain about
uninitialized values in stack allocatio
David Kastrup writes:
> Thomas Morley writes:
>
>> 2016-05-29 21:03 GMT+02:00 Thomas Morley :
>>
>>> I'll now checkout a fresh branch from master, apply Hosoda-san's patch from
>>> https://codereview.appspot.com/298320043/
>>> change orchestra.ly as before.
>>> Try a full `make doc' and report b
> Is there anybody out there who succeeds to build the current lilypond
> documentation on a 64 bit linux machine with a 64 bit toolchain?
> Please report cpu as well as versions of gcc and guile.
Although my environment is not linux,
I've succeeded `make doc' by HEAD of master branch.
Of course,
Thomas Morley writes:
> 2016-05-29 21:03 GMT+02:00 Thomas Morley :
>
>> I'll now checkout a fresh branch from master, apply Hosoda-san's patch from
>> https://codereview.appspot.com/298320043/
>> change orchestra.ly as before.
>> Try a full `make doc' and report back later.
>
>
> This failed quit
2016-05-29 21:03 GMT+02:00 Thomas Morley :
> I'll now checkout a fresh branch from master, apply Hosoda-san's patch from
> https://codereview.appspot.com/298320043/
> change orchestra.ly as before.
> Try a full `make doc' and report back later.
This failed quite early in the regtest with the alr
Knut Petersen writes:
> Am 29.05.2016 um 13:52 schrieb David Kastrup:
>> I have to see whether I have a chance to run a 64 bit kernel on my
>> system: I used to for a few years (and consequently was able to look
>> at 64 bit code), but the current laptop has an Nvidia card and
>> Ubuntu's kernel/
Am 29.05.2016 um 13:52 schrieb David Kastrup:
I have to see whether I have a chance to run a 64 bit kernel on my system: I used to for a few years (and consequently was able to look at 64 bit code), but the current laptop has an Nvidia card and Ubuntu's kernel/library setup did not manage to integ
> I think make doc uses --bigpdf and some sort of PDF postprocessing.
> Maybe one needs that to reproduce?
Here's a more detailed analysis of the problem regarding OpenType
collections.
I've just tried to compile this snippet
\version "2.19.40"
\markup {
\override #'(font-name . "Noto S
David Kastrup writes:
> Thomas Morley writes:
>
>>> Processing `./c0/lily-c236818d.ly'
>>> Parsing...
>>> Renaming input to: `/home/hermann/lilypond-git/input/regression/utf-8.ly'
>>> Interpreting music...
>>> Preprocessing graphical objects...
>>> Calculating line breaks...
>>> Drawing systems.
Thomas Morley writes:
>> Processing `./c0/lily-c236818d.ly'
>> Parsing...
>> Renaming input to: `/home/hermann/lilypond-git/input/regression/utf-8.ly'
>> Interpreting music...
>> Preprocessing graphical objects...
>> Calculating line breaks...
>> Drawing systems...
>> Writing header field `texido
Thomas Morley writes:
> James,
>
> 2016-05-29 13:15 GMT+02:00 James Lowe :
>> Thomas,
>
>> I think this a a completely different issue that you have, perhaps,
>> self-inflicted here and this is just adding noise to the thread.
>>
>> Knut and I do not get these same errors as you and also note tha
; only purpose is to generate a png file for an examples display (i.e. it
> isn't a snippet that I can see used in any other part of the doc).
>
> Finally, as I cannot make doc still, I cannot test patches, am not really
> checking my emails as much as I normally do, other than
David Kastrup writes:
> David Kastrup writes:
>
>> I have to see whether I have a chance to run a 64 bit kernel on my
>> system: I used to for a few years (and consequently was able to look
>> at 64 bit code), but the current laptop has an Nvidia card and
>> Ubuntu's kernel/library setup did not
2016-05-29 14:44 GMT+02:00 David Kastrup :
> David Kastrup writes:
>
>> I have to see whether I have a chance to run a 64 bit kernel on my
>> system: I used to for a few years (and consequently was able to look
>> at 64 bit code), but the current laptop has an Nvidia card and
>> Ubuntu's kernel/li
David Kastrup writes:
> I have to see whether I have a chance to run a 64 bit kernel on my
> system: I used to for a few years (and consequently was able to look
> at 64 bit code), but the current laptop has an Nvidia card and
> Ubuntu's kernel/library setup did not manage to integrate the Nvidia
erning
architecture: having a different problem responsible there is clarifying
things.
> Finally, as I cannot make doc still, I cannot test patches, am not
> really checking my emails as much as I normally do, other than to drop
> by for the patch countdown - which doesn't need me to compile
> warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
> -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
> -sOutputFile=./55/lily-c61e089a.pdf -c.setpdfwrite
> -f./55/lily-c61e089a.eps)' failed (256)
Is there any possibility to increase the verbosity
ints. As soon as I rebase master with current and
try the same patch, I go back to the same old 'orchestra.ly' failure -
note also that he failure seems to occur at the 'website' making stage
where this ly file's only purpose is to generate a png file for an
examples d
2016-05-29 12:29 GMT+02:00 Thomas Morley :
> 2016-05-29 1:14 GMT+02:00 Thomas Morley :
>> 2016-05-28 12:27 GMT+02:00 Thomas Morley :
>>
>>>
>>> FWIW, I checked out staging with your recent patch, i.e.:
>>> $ git log
>>> commit 193369dddc8adc492d3d98b6f1d00de11a31e9c4
>>> Author: David Kastrup
>>>
2016-05-29 1:14 GMT+02:00 Thomas Morley :
> 2016-05-28 12:27 GMT+02:00 Thomas Morley :
>
>>
>> FWIW, I checked out staging with your recent patch, i.e.:
>> $ git log
>> commit 193369dddc8adc492d3d98b6f1d00de11a31e9c4
>> Author: David Kastrup
>> Date: Fri May 27 10:20:18 2016 +0200
>>
>> Issu
2016-05-28 12:27 GMT+02:00 Thomas Morley :
>
> FWIW, I checked out staging with your recent patch, i.e.:
> $ git log
> commit 193369dddc8adc492d3d98b6f1d00de11a31e9c4
> Author: David Kastrup
> Date: Fri May 27 10:20:18 2016 +0200
>
> Issue 4863: Protect Grob_interface<>::interface_symbol_
>
>> On my host system Ubuntu 16.04 64-bit
>> make doc
>> fails with orchestra.ly as before
>
> Yes, I reckoned so after James' report. Without some backtrace or
> core dump or recipe other than "run make doc" I cannot really track
> this down. It would not be feasible to look at the assembly code
Thomas Morley writes:
> 2016-05-27 16:22 GMT+02:00 David Kastrup :
>> James writes:
>>
>>> Hello,
>>>
>>> I still cannot make doc and so cannot merge staging - and for those
>>> waiting on me to test new patches, I cannot do that with any great
2016-05-27 16:22 GMT+02:00 David Kastrup :
> James writes:
>
>> Hello,
>>
>> I still cannot make doc and so cannot merge staging - and for those
>> waiting on me to test new patches, I cannot do that with any great
>> reliability either.
>
> Fiddlesticks.
- Original Message -
From: "David Kastrup"
To: "James"
Cc: "lilypond-devel"
Sent: Friday, May 27, 2016 3:36 PM
Subject: Re: Still cannot make doc :(
James writes:
Hello,
I still cannot make doc and so cannot merge staging - and for those
waitin
James writes:
> Hello,
>
> I still cannot make doc and so cannot merge staging - and for those
> waiting on me to test new patches, I cannot do that with any great
> reliability either.
>
> I am sorry this is incredibly frustrating.
>
> @Phil would it be possible for
Hello,
I still cannot make doc and so cannot merge staging - and for those
waiting on me to test new patches, I cannot do that with any great
reliability either.
I am sorry this is incredibly frustrating.
@Phil would it be possible for you to run Patchy Merge on your system
and see if you
James writes:
> Hello,
>
> I still cannot make doc and so cannot merge staging - and for those
> waiting on me to test new patches, I cannot do that with any great
> reliability either.
Fiddlesticks. I was afraid that this would be the case but it was worth
a try.
>
Le mercredi 09 décembre 2009 à 20:19 +0100, Francisco Vila a écrit :
> Thank you, now I have upgraded texi2html to v1.82 and have been able
> to complete the process.
Ah, if you used a version older than 1.82, it probably doesn't normalize
the node names the same way.
> I uncompressed it from
2009/12/9 John Mandereau :
> Le samedi 05 décembre 2009 à 11:18 +, Graham Percival a écrit :
>> I've seen similar messages when attempting to build it on GUB,
>> although they specify /contributor/ instead.
>
> Please send me the same info I asked in my reply to Francisco, otherwise
> there is
Le samedi 05 décembre 2009 à 11:18 +, Graham Percival a écrit :
> I've seen similar messages when attempting to build it on GUB,
> although they specify /contributor/ instead.
Please send me the same info I asked in my reply to Francisco, otherwise
there is little chance I see why extract-texi
Le dimanche 06 décembre 2009 à 19:37 +0100, Francisco Vila a écrit :
> I have rm-rf'ed completely out* and Documentation/, then reset them
> hard, and still
>
>*** Can't open ./out-www/learning/ for writing: Is a directory,
>
> after 41 min of compilation.
To investigate this, I need the Git
2009/12/6 John Mandereau :
>> *** Can't open ./out-www/learning/ for writing: Is a directory
>> Documentation/./out-www/learning/index.fr.html
>
> I got this too (but only in my working tree) while fixing
> extract_texi_filenames.py and lilypond-texi2html.init. As a result,
> Texi2HTML now bombs o
Le samedi 05 décembre 2009 à 11:18 +, Graham Percival a écrit :
> I've seen similar messages when attempting to build it on GUB,
> although they specify /contributor/ instead. I haven't seen them
> when building it natively, though. I'll try building the online
> target and see if that dies.
Le samedi 05 décembre 2009 à 11:32 +0100, Francisco Vila a écrit :
> WARNING: Node 'Index de LilyPond' was NOT found in the map
> File name: index-de-lilypond.html
There is a lot of debug prints from the init file, a lot of them are
commented out; I'll remove most of them when the init file will b
On Sat, Dec 05, 2009 at 11:32:14AM +0100, Francisco Vila wrote:
> Hello all, I'm trying to build the docs and after many lines of the form
>
> WARNING: Node 'Index de LilyPond' was NOT found in the map
> File name: index-de-lilypond.html
>
> I finally obtain
>
> *** Can't open ./out-www/learning
Hello all, I'm trying to build the docs and after many lines of the form
WARNING: Node 'Index de LilyPond' was NOT found in the map
File name: index-de-lilypond.html
I finally obtain
*** Can't open ./out-www/learning/ for writing: Is a directory
Documentation/./out-www/learning/index.fr.html
ma
65 matches
Mail list logo
