Re: Building documentation: bad PNG output

[James]

CCing dev list in case anyone who understand the build system knows what
is going on here


On 28/06/14 16:59, Aymeric O. wrote:
> I found where the problem is!
>
> In make/lilypond-vars.make, the options used by LilyPond to generate
> the output files are given there:
>
> ## override from cmd line to speed up.
> ANTI_ALIAS_FACTOR=2
> LILYPOND_JOBS=$(if $(CPU_COUNT),-djob-count=$(CPU_COUNT),)
> LANG_TEXIDOC_FLAGS:=$(foreach lang,$(LANGS),--header=texidoc$(lang))
> LANG_DOCTITLE_FLAGS:=$(foreach lang,$(LANGS),--header=doctitle$(lang))
>
> LILYPOND_BOOK_LILYPOND_FLAGS=-dbackend=eps \
> --formats=ps,png,pdf \
> $(LILYPOND_JOBS) \
> -dinclude-eps-fonts \
> -dgs-load-fonts \
> --header=doctitle \
> $(LANG_DOCTITLE_FLAGS) \
> --header=texidoc \
> $(LANG_TEXIDOC_FLAGS) \
> -dcheck-internal-types \
> -ddump-signatures \
> -danti-alias-factor=$(ANTI_ALIAS_FACTOR)
>
> And the problem comes from "-danti-alias-factor=$(ANTI_ALIAS_FACTOR)"
> (=2), which is responsible for the crushed PNG files. I tested it on
> my own scores, and it gives the same result.
>
> So it looks like the /usr/bin/lilypond I built can't handle
> "-danti-alias-factor>=2", but why? I tried this option whith the
> precompiled version of LilyPond, and I get the same PNG files, so it
> must be a system-wide problem, as it was suggested before.
>
> I'm using Zenwalk GNU/Linux, a Slackware-based system.
>
>
> On 06/27/2014 02:47 PM, James wrote:
>> Aymeric,
>>
>> On 27/06/14 13:06, Federico Bruni wrote:
>>> Helping you is a hard job and I've just run out of time.
>>> You are not telling us which source you are using. From a linux
>>> distro repository? From lilypond git repository?
>>> You should use git and checkout the 2.18.2 branch, otherwise you
>>> won't get much help from this list probably.
>>>
>>> And the logs of 'make doc'?
>>>
>>> I give up... Good luck!
>>
>> :)
>>
>> Yes diagnosing doc build problems can be very time consuming.
>>
>> Please make sure that
>>
>> 1. You are following the contributor guide which gives the minimum
>> requirements to build documentation successfully:
>>
>> http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#requirements
>>
>> and
>>
>> http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#requirements-for-building-documentation
>>
>> 2. Next, build the latest 2.19 documents from git
>>
>> http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#summary-for-experienced-developers
>>
>> At least prove that that works or does not work. I know it does at
>> the moment as I build the documentation daily, so if you are having
>> problems with 2.19 then it could simply be an evironmental issue than
>> a code issue.
>>
>> If you can build it fine and get your PNG files using 2.19 then use
>> the same git repo and use the 2.18 branch and then try.
>>
>> Then at least we can attempt to help, knowing we are all looking at
>> the same code as you.
>>
>> Regards
>>
>> James
>>
>>
>>
>>>
>>> 2014-06-27 13:27 GMT+02:00 Aymeric <address@hidden
>>> <mailto:address@hidden>>:
>>>
>>>     I'm trying to build 2.18.2, with... LilyPond 2.18.2, so there
>>>     should be no problem, and, as I said, I can generate PNG files
>>>     from my own scores. I even tried with the file you mentioned:
>>>
>>>     aymeric[snippets]$ lilypond -dbackend=eps -dno-gs-load-fonts
>>>     -dinclude-eps-fonts --png pitches-headword.ly
>>>     <http://pitches-headword.ly>
>>>     GNU LilyPond 2.18.2
>>>     Processing `pitches-headword.ly <http://pitches-headword.ly>'
>>>     Parsing...
>>>     Interpreting music...[8]
>>>     Preprocessing graphical objects...
>>>     Finding the ideal number of pages...
>>>     Fitting music on 1 page...
>>>     Drawing systems...
>>>     Layout output to `pitches-headword.eps'...
>>>     Converting to PNG...
>>>     Layout output to `pitches-headword-1.eps'...
>>>     Writing pitches-headword-systems.texi...
>>>     Writing pitches-headword-systems.tex...
>>>     Writing pitches-headword-systems.count...
>>>     Success: compilation successfully completed
>>>
>>>     And here's the output.
>>>
>>>
>>>
>>>     On 06/27/2014 01:18 PM, Federico Bruni wrote:
>>>
>>>         BTW, what's the purpose of building the current stable doc
>>>         (2.18.2)?
>>>         Which source are you using?
>>>
>>>
>>>
>>>         2014-06-27 13:16 GMT+02:00 Federico Bruni
>>>         <address@hidden <mailto:address@hidden>
>>>         <mailto:address@hidden <mailto:address@hidden>>>:
>>>
>>>
>>>             Ok, finally I see what's the problem. I never had such a
>>>         problem and
>>>             I cannot make a guess. You got no error when running
>>>         make doc?
>>>             You should check the log files in Documentation:
>>>
>>>             ./Documentation/notation.texi2pdf.log
>>>             ./Documentation/notation.bigtexi.log
>>>             ./Documentation/notation.splittexi.log
>>>             ./Documentation/notation.makeinfo.log
>>>
>>>             That file is
>>>         ./Documentation/snippets/pitches-headword.ly
>>>         <http://pitches-headword.ly>
>>>             <http://pitches-headword.ly>
>>>
>>>             It seems that the lilypond version you are using cannot
>>>         compile it.
>>>             Perhaps a version mismatch?
>>>
>>>
>>>
>>>
>>>
>>>             2014-06-27 13:10 GMT+02:00 Aymeric <address@hidden
>>>         <mailto:address@hidden>
>>>             <mailto:address@hidden <mailto:address@hidden>>>:
>>>
>>>
>>>                 No, I can see the score.
>>>
>>>                 Here's a screenshot of how it looks like with my build.
>>>
>>>
>>>
>>>                 On 06/27/2014 01:06 PM, Federico Bruni wrote:
>>>
>>>                     Those files names are randomly generated. We
>>>         don't have them!
>>>                     Can you see the same issue on the lilypond website?
>>>                    
>>>         http://lilypond.org/doc/v2.18/__Documentation/notation/pitches
>>>
>>>                    
>>>         <http://lilypond.org/doc/v2.18/Documentation/notation/pitches>
>>>
>>>                     Or send us a screenshot of your web page.
>>>
>>>
>>>                     2014-06-27 12:58 GMT+02:00 Aymeric
>>>         <address@hidden <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden> <mailto:address@hidden
>>>         <mailto:address@hidden>>>>:
>>>
>>>
>>>
>>>                          For example, in the HTML documentation:
>>>
>>>                    
>>>         
>>> file:///usr/doc/lilypond-doc-____2.18.2/html/Documentation/____notation/pitches.html
>>>
>>>                    
>>>         
>>> file:///usr/doc/lilypond-doc-____2.18.2/html/Documentation/eb/____lily-bd76d922.png
>>>
>>>
>>>
>>>                          looks the same as the image I sent before.
>>>
>>>
>>>
>>>                          On 06/27/2014 12:50 PM, Federico Bruni wrote:
>>>
>>>                              Don't look there, it's different from
>>>         what we have.
>>>                     Also, why
>>>                              caring for
>>>                              images in the directories?
>>>                              I'm asking: have you seen that image on
>>>         the html
>>>                     manual? If so,
>>>                              where?
>>>                              (manual, section, parapraph)
>>>
>>>
>>>                              2014-06-27 12:39 GMT+02:00 Aymeric
>>>                     <address@hidden <mailto:address@hidden>
>>>         <mailto:address@hidden <mailto:address@hidden>>
>>>                              <mailto:address@hidden
>>>         <mailto:address@hidden> <mailto:address@hidden
>>>         <mailto:address@hidden>>>
>>>                              <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>> <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>>>>>:
>>>
>>>                                  
>>>         lilypond-2.18.2/Documentation/______out-www/00
>>>
>>>
>>>
>>>                                   But all the PNG images look the
>>>         same. I tried
>>>                     to export
>>>                              some PNG
>>>                                   myself with LilyPond from my own
>>>         .ly files,
>>>                     and I don't
>>>                              have this error.
>>>
>>>
>>>                                   On 06/27/2014 12:31 PM, Federico
>>>         Bruni wrote:
>>>                                    >
>>>                                    > 2014-06-27 12:19 GMT+02:00 Aymeric
>>>                     <address@hidden <mailto:address@hidden>
>>>         <mailto:address@hidden <mailto:address@hidden>>
>>>                              <mailto:address@hidden
>>>         <mailto:address@hidden> <mailto:address@hidden
>>>         <mailto:address@hidden>>>
>>>                                   <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>> <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>>>>
>>>                                    > <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>> <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>>>
>>>                              <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>> <mailto:address@hidden
>>>         <mailto:address@hidden>
>>>                     <mailto:address@hidden
>>>         <mailto:address@hidden>>>>>>__:
>>>
>>>
>>>
>>>                                    >
>>>                                    >     I'm tring to build the LilyPond
>>>                     documentation since
>>>                              quite
>>>                                   some time,
>>>                                    >     and whereas the PDF and
>>>         HTLM output is
>>>                     great, the
>>>                              PNG are... well...
>>>                                    >     here is a sample.
>>>                                    >     Where do you think it's
>>>         coming from,
>>>                     and can you help me
>>>                                   solve this,
>>>                                    >     please?
>>>                                    >
>>>                                    >
>>>                                    >
>>>                                    > You should tell us where you
>>>         find this
>>>                     image in the html
>>>                                   documentation.
>>>                                    > In which section/paragraph?
>>>                                    >
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> lilypond-user mailing list
>>> address@hidden
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>