Am 07.04.2016 um 12:11 schrieb David Kastrup:
> David Kastrup <d...@gnu.org> writes:
>
>> Carl Sorensen <c_soren...@byu.edu> writes:
>>
>>> What about if you delete python/out and redo make doc?
>>>
>>> Just wondering if there's something wrong with the build script that
>>> python/out isn't properly recreated when python/*.py changes. In my
>>> setup, python/*.py is not executable, but python/out/*.py is. So make is
>>> apparently copying the .py files, setting them executable, and creating
>>> the .pyc files.
>>>
>>> Again, untested. But I have done a grep for blockquote and it only shows
>>> up in book_html.py as far as I can see. So I think it must be
>>> book_html.py.
>> Documentation/lilypond-texi2html.init: 'begin' => q{"<blockquote>"},
>> Documentation/lilypond-texi2html.init: 'end' => q{"</blockquote>\n"},
>>
>> looks relevant to me as well.
> In fact, I'd guess that book_html.py would be relevant when writing
> _HTML_ with embedded LilyPond, not when writing _Texinfo_ with embedded
> LilyPond.
>
I don't think so.
book_XXX.py contain code to format LilyPond snippets in different target
formats (HTML, LaTeX, docbook etc.) and are used from within
lilypond-book. But I'm not sure about the role lilypond-book plays
within "make doc".
I skimmed through lilypond-texi2html.init, and althought these two
<blockquote> references may be related to the issue I don't think
they're relevant.
I'll now look into book_snippets and see if I can find anything in its
classes.
Urs
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
