Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Masamichi Hosoda]

>>> 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 opinion,
>> both options `-dgs-load-fonts' and `-dgs-load-lily-fonts'
>> should be deprecated.
>>
>> I think that should be noted as deprecated in the document.
>>
>>
> Sorry to appear pendantic but I am having a hard time parsing that -
> or perhaps you are using the wrong word?
> 
> When you say 'should' be deprecated do you mean these commands 'are'
> deprecated or that you 'would like them to be' deprecated because they
> *do* work (except in this case) or are they not expected to work at
> all properly.
> 
> I just am concerned there might be users that have a genuine use-case
> for this option and it still works for them even in the later
> versions?
> 
> Perhaps you can give some words (like you have done before) that might
> be suitable for the warning/note and I, if needed, can make them more
> succinct in the English doc?

Sorry.
My explanation was poor.

I'd like "-dgs-load-fonts" and "-dgs-load-lily-fonts" to be deprecated.

If I understand correctly,
the both options use a ghostscript language extension ".loadfont".
Ghostscript developers seem to want us
to not use the ghostscript language extension.
http://bugs.ghostscript.com/show_bug.cgi?id=696823
http://bugs.ghostscript.com/show_bug.cgi?id=696824

As they said, to "use the documented method for loading fonts",
the both options can not be used.

So I propose that the both options are not used.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[James]

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#entire-document-fonts

?

In my humble opinion,
both options `-dgs-load-fonts' and `-dgs-load-lily-fonts'
should be deprecated.

I think that should be noted as deprecated in the document.


Sorry to appear pendantic but I am having a hard time parsing that - or 
perhaps you are using the wrong word?


When you say 'should' be deprecated do you mean these commands 'are' 
deprecated or that you 'would like them to be' deprecated because they 
*do* work (except in this case) or are they not expected to work at all 
properly.


I just am concerned there might be users that have a genuine use-case 
for this option and it still works for them even in the later versions?


Perhaps you can give some words (like you have done before) that might 
be suitable for the warning/note and I, if needed, can make them more 
succinct in the English doc?


James



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Masamichi Hosoda]

>>> 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.cgi?id=696823
http://bugs.ghostscript.com/show_bug.cgi?id=696824

They seem to want us to not use ghostscript language extension.

If I understand correctly,
LilyPond option `-dgs-load-fonts' and `-dgs-load-lily-fonts'
use the ghostscript language extension `.loadfont'.

In my humble opinion, both options should be `deprecated'.
I'm trying to remove them used in `make doc' and lilypond-book.
https://sourceforge.net/p/testlilyissues/issues/4882/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Masamichi Hosoda]

> 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 opinion,
both options `-dgs-load-fonts' and `-dgs-load-lily-fonts'
should be deprecated.

I think that should be noted as deprecated in the document.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[James Lowe]

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 explanation?

If I understand correctly, there is four issues at least.


First, "Noto Sans CJK JP" in NotoSansCJK.ttc cannot be used.

I think that the biggest hurdle is OTC fonts.
As you know, current ghostscript does not support OTC fonts.
http://bugs.ghostscript.com/show_bug.cgi?id=696808

I'm not familiar with OSX
but I've heard that most (all?) OSX 10.11 Japanese fonts are OTC fonts.
http://tug.org/pipermail/luatex/2015-October/005377.html

In other words,
if you use OSX 10.11,
most Japanese fonts cannot be used with `-dgs-load-fonts'.

Moreover, Debian / Ubuntu / Fedora provide the package
that contains OTC version's Noto Sans CJK.
There is not OTF version.

On the other hand,
without `-dgs-load-fonts', my patches will add OTC font supports.
In my experiment, I've succeeded to use OTC font "NotoSansCJK.ttc".


Second, "MS PMincho" in msmincho.ttc cannot be used.

I've reported this issue to ghostscript developers.
http://bugs.ghostscript.com/show_bug.cgi?id=696823

Maybe, ghostscript cannot load the font which has index!=0
in TrueType Collection.
All Japanese fonts that I've seen in modern Windows are TTC fonts.
Most Japanese fonts in Windows cannot be used with `-dgs-load-fonts'.
Only index=0 fonts can be used.

Without `-dgs-load-fonts', there is no problem even if index!=0.


Third, "IPAexMincho" in ipaexm.ttf cannot be used.

I've reported this issue to ghostscript developpers.
http://bugs.ghostscript.com/show_bug.cgi?id=696824

Without `-dgs-load-fonts', there is no problem.


Fourth, "MS Mincho" in msmincho.ttc cannot be used.

In my newest investigation,
this is LilyPond issue.

This font does not have glyph names.
So LilyPond generate glyph names like "/uni3044"
by get_unicode_name () in pango-font.cc.

Without `-dgs-load-fonts', LilyPond embed generated glyph name table
by print_trailer () in ttf.cc.
Ghostscript can find glyph name.
There is no problem.

On the other hand,
with `-dgs-load-fonts',
LilyPond does not embed glyph name table but use the glyph name.
Ghostscript cannot find the glyph name.
So it uses TOFU glyph for all Japanese characters.

I think it can be fixed.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel




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

?


--
--

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Werner LEMBERG]

>> 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 mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Masamichi Hosoda]

>> 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, there is four issues at least.


First, "Noto Sans CJK JP" in NotoSansCJK.ttc cannot be used.

I think that the biggest hurdle is OTC fonts.
As you know, current ghostscript does not support OTC fonts.
http://bugs.ghostscript.com/show_bug.cgi?id=696808

I'm not familiar with OSX
but I've heard that most (all?) OSX 10.11 Japanese fonts are OTC fonts.
http://tug.org/pipermail/luatex/2015-October/005377.html

In other words,
if you use OSX 10.11,
most Japanese fonts cannot be used with `-dgs-load-fonts'.

Moreover, Debian / Ubuntu / Fedora provide the package
that contains OTC version's Noto Sans CJK.
There is not OTF version.

On the other hand,
without `-dgs-load-fonts', my patches will add OTC font supports.
In my experiment, I've succeeded to use OTC font "NotoSansCJK.ttc".


Second, "MS PMincho" in msmincho.ttc cannot be used.

I've reported this issue to ghostscript developers.
http://bugs.ghostscript.com/show_bug.cgi?id=696823

Maybe, ghostscript cannot load the font which has index!=0
in TrueType Collection.
All Japanese fonts that I've seen in modern Windows are TTC fonts.
Most Japanese fonts in Windows cannot be used with `-dgs-load-fonts'.
Only index=0 fonts can be used.

Without `-dgs-load-fonts', there is no problem even if index!=0.


Third, "IPAexMincho" in ipaexm.ttf cannot be used.

I've reported this issue to ghostscript developpers.
http://bugs.ghostscript.com/show_bug.cgi?id=696824

Without `-dgs-load-fonts', there is no problem.


Fourth, "MS Mincho" in msmincho.ttc cannot be used.

In my newest investigation,
this is LilyPond issue.

This font does not have glyph names.
So LilyPond generate glyph names like "/uni3044"
by get_unicode_name () in pango-font.cc.

Without `-dgs-load-fonts', LilyPond embed generated glyph name table
by print_trailer () in ttf.cc.
Ghostscript can find glyph name.
There is no problem.

On the other hand,
with `-dgs-load-fonts',
LilyPond does not embed glyph name table but use the glyph name.
Ghostscript cannot find the glyph name.
So it uses TOFU glyph for all Japanese characters.

I think it can be fixed.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Werner LEMBERG]

> 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

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Masamichi Hosoda]

>>> 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 I understand correctly, intermediate PDF become bigger.
> However, {pdf|Lua|Xe}TeX output PDF become smaller by `--bigpdfs' option.

I've created Issue 4882.
https://sourceforge.net/p/testlilyissues/issues/4882/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Masamichi Hosoda]

>> 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 I understand correctly, intermediate PDF become bigger.
However, {pdf|Lua|Xe}TeX output PDF become smaller by `--bigpdfs' option.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[David Kastrup]

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, don't they?

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Masamichi Hosoda]

> 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|gothic} packages
contain a fontconfig setting file that raise own priority.

> Any chance to get a more meaningful error-message?
> Or is there any criterion we could select such problematic fonts?

I've tried some Japanese fonts with `-dgs-load-fonts' option.

"IPAMincho" in ipam.ttf:
fine.

"IPAPMincho" in ipamp.ttf:
fine.

"IPAexMincho" in ipaexm.ttf:
compilation failed due to ghostscript error.

"MS Mincho" in msmincho.ttc:
compilation successful
but all Japanese characters are shown as TOFU.

"MS PMincho" in msmincho.ttc:
compilation successful but all Japanese characters are vanished.

"Noto Sans CJK JP" in NotoSansCJK.ttc:
compilation failed due to ghostscript error.

"Source Han Sans" in SourceHanSans-Regular.otf:
fine.

So most Japanese fonts can not be used with `-dgs-load-fonts' option.

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'.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Thomas Morley]

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 is >16MB again, though.
>
> Thank you for your results.
>
> If I understand correctly, it's a ghostscript issue.
>
> Ghostscript might not be able to handle IPAex fonts that you used.
>
> Using lilypond-book with `--pdf' option invokes lilypond
> with `-dgs-load-fonts' option.
> LilyPond with `-dgs-load-fonts' option generates ps file
> which is embedded font filename only.
> Without the option, the ps file is embedded font glyphs.
>
> If the glyphs are embedded, ghostscript works fine.
> However, if filename are embedded, ghostscript may not work fine.
>
> In the case of IPAex fonts,
> embedded filename brings the ghostscript error.
> But, for IPA fonts which are another Japanese fonts,
> embedded filename works fine.
>
> The GUB environment uses IPA fonts instead of IPAex fonts.
> So there is no problem.

Thanks a lot for your research and findings!

> Would you try the following commands?
>
> $ sudo apt-get install fonts-ipafont-mincho
> $ sudo apt-get install fonts-ipafont-gothic
>
> IPA fonts are `IPA Mincho' (Japanese serif font)
> and `IPA Gothic' (Japanese sans serif font).
> By default, fontconfig takes precedence over the IPA fonts than IPAex fonts.

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'.

Any chance to get a more meaningful error-message?
Or is there any criterion we could select such problematic fonts?


Again many thanks,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[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 is >16MB again, though.

Thank you for your results.

If I understand correctly, it's a ghostscript issue.

Ghostscript might not be able to handle IPAex fonts that you used.

Using lilypond-book with `--pdf' option invokes lilypond
with `-dgs-load-fonts' option.
LilyPond with `-dgs-load-fonts' option generates ps file
which is embedded font filename only.
Without the option, the ps file is embedded font glyphs.

If the glyphs are embedded, ghostscript works fine.
However, if filename are embedded, ghostscript may not work fine.

In the case of IPAex fonts,
embedded filename brings the ghostscript error.
But, for IPA fonts which are another Japanese fonts,
embedded filename works fine.

The GUB environment uses IPA fonts instead of IPAex fonts.
So there is no problem.

Would you try the following commands?

$ sudo apt-get install fonts-ipafont-mincho
$ sudo apt-get install fonts-ipafont-gothic

IPA fonts are `IPA Mincho' (Japanese serif font)
and `IPA Gothic' (Japanese sans serif font).
By default, fontconfig takes precedence over the IPA fonts than IPAex fonts.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Thomas Morley]

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{lilypond}
>>>
>>> \end{document}
>>>
>>> %%% end of aaa-lilybook.lytex
>>>
>>> always fails with:
>>>
>>> $ lilypond-book --output=out --pdf aaa-lilybook.lytex
>>> lilypond-book (GNU LilyPond) 2.19.43
>>> Reading aaa-lilybook.lytex...
>>> Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default page 
>>> settings.
>>>
>>> Dissecting...
>>> Writing snippets...
>>> Processing...
>>> Running lilypond...
>>> GNU LilyPond 2.19.43
>>> Processing `./snippet-map--2641629851966957681.ly'
>>> Parsing...
>>> Processing `./55/lily-88e32432.ly'
>>> Parsing...
>>> Layout output to `./55/lily-88e32432.eps'...
>>> Converting to `./55/lily-88e32432.pdf'...
>>> warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
>>> -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
>>> -sOutputFile=./55/lily-88e32432.pdf -c.setpdfwrite
>>> -f./55/lily-88e32432.eps)' failed (256)
>>>
>>> fatal error: failed files: "55/lily-88e32432.ly"
>>> command failed: /home/hermann/lilypond-git/build/out/bin/lilypond
>>> --formats=ps -dbackend=eps  -I  "./"  -I  "../" --formats=eps --pdf
>>> -dinclude-eps-fonts -dgs-load-fonts  -deps-box-padding=3.00
>>> -dread-file-list -dno-strip-output-dir
>>> "/home/hermann/lilypondH/Test/forum/aaa-doc-test/out/snippet-names--2641629851966957681.ly"
>>> Child returned 1
>
> I made a fresh checkout from staging at
> b5b3e36 #4877: Revert #4747: (Remove (all) uses of is-absolute?)
> additionaly I applied your patches from
> https://codereview.appspot.com/301820043
> (Issue 4868: Add limited embedding support for OpenType/CFF Collection
> (OTC) fonts)
> and
> https://codereview.appspot.com/298320043
> (Issue 4867 Ignore some major OpenType/CFF Collection (OTC) fonts)

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.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[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{lilypond}
>>
>> \end{document}
>>
>> %%% end of aaa-lilybook.lytex
>>
>> always fails with:
>>
>> $ lilypond-book --output=out --pdf aaa-lilybook.lytex
>> lilypond-book (GNU LilyPond) 2.19.43
>> Reading aaa-lilybook.lytex...
>> Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default page 
>> settings.
>>
>> Dissecting...
>> Writing snippets...
>> Processing...
>> Running lilypond...
>> GNU LilyPond 2.19.43
>> Processing `./snippet-map--2641629851966957681.ly'
>> Parsing...
>> Processing `./55/lily-88e32432.ly'
>> Parsing...
>> Layout output to `./55/lily-88e32432.eps'...
>> Converting to `./55/lily-88e32432.pdf'...
>> warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
>> -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
>> -sOutputFile=./55/lily-88e32432.pdf -c.setpdfwrite
>> -f./55/lily-88e32432.eps)' failed (256)
>>
>> fatal error: failed files: "55/lily-88e32432.ly"
>> command failed: /home/hermann/lilypond-git/build/out/bin/lilypond
>> --formats=ps -dbackend=eps  -I  "./"  -I  "../" --formats=eps --pdf
>> -dinclude-eps-fonts -dgs-load-fonts  -deps-box-padding=3.00
>> -dread-file-list -dno-strip-output-dir
>> "/home/hermann/lilypondH/Test/forum/aaa-doc-test/out/snippet-names--2641629851966957681.ly"
>> Child returned 1

I made a fresh checkout from staging at
b5b3e36 #4877: Revert #4747: (Remove (all) uses of is-absolute?)
additionaly I applied your patches from
https://codereview.appspot.com/301820043
(Issue 4868: Add limited embedding support for OpenType/CFF Collection
(OTC) fonts)
and
https://codereview.appspot.com/298320043
(Issue 4867 Ignore some major OpenType/CFF Collection (OTC) fonts)



> Would you try the following command and show us the result?
>
> $ lilypond-book --output=out --verbose --pdf aaa-lilybook.lytex
>
> `--verbose' is added.

I did (with a renamed test-file, but same content)
lilypond-book --output=out --verbose --pdf 2> book-test.log
aaa-lilybook-test.lytex

book-test.log attached.

>
> Then, would you show us the generated eps file?
> Its filename is shown like `./55/lily-88e32432.eps'.

lily-a7047c84.eps attached

>
>> But in a .ly-file
>>
>> \markup {
>>   %foo bar buzz
>>   いろはにほへど ちりぬるを
>> }
>>
>> always returns a correct pdf.
>
> I'd like to compare.
> So would you try the following command and show us the result?
>
> $ lilypond --verbose --ps --pdf filename.ly

I did
lilypond-git --verbose --ps --pdf 2> file-test.log aaa-lily-test.ly

file-test.log attached.

>
> Then, would you show us the generated filename.ps?

aaa-lily-test.ps turns out to be a 16.7MB sized file !!
Too much to attach, but visible/downloadable here:
https://drive.google.com/file/d/0B99HjSI1yfY9T3RxSW1DSGQyN2s/view
lilypond-book: Setting LilyPond's output to --verbose, implied by lilypond-book's setting
lilypond-book (GNU LilyPond) 2.19.43
Reading aaa-lilybook-test.lytex...
Running `pdflatex' on file `/tmp/tmpuLUEnE.tex' to detect default page settings.

Executing: pdflatex /tmp/tmpuLUEnE.tex

Detected values:
  columns = 0
  columnsep = 10.0
  textwidth = 345.0
Dissecting...
Writing snippets...
Processing...
Invoking `/home/hermann/lilypond-git/build/out/bin/lilypond --formats=ps -dbackend=eps  -I  "./"  -I  "../" --formats=eps --pdf -dinclude-eps-fonts -dgs-load-fonts  --verbose -deps-box-padding=3.00  -dread-file-list -dno-strip-output-dir  "/home/hermann/lilypondH/Test/forum/aaa-doc-test/out/snippet-names--3768003740979461048.ly"'
Log level set to 287
GNU LilyPond 2.19.43
Relocation: is absolute: argv0=/home/hermann/lilypond-git/build/out/bin/lilypond
PATH=/home/hermann/lilypond-git/build/out/bin (prepend)
Setting PATH to /home/hermann/lilypond-git/build/out/bin:/home/hermann/git-cl:/home/hermann/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
Relocation: compile datadir=, new datadir=/home/hermann/lilypond-git/build/out/share/lilypond//current
Relocation: framework_prefix=/home/hermann/lilypond-git/build/out/bin/..
Setting INSTALLER_PREFIX to /home/hermann/lilypond-git/build/out/bin/..
PATH=/home/hermann/lilypond-git/build/out/bin/../bin (prepend)
Setting PATH to /home/hermann/lilypond-git/build/out/bin/../bin:/home/hermann/lilypond-git/build/out/bin:/home/hermann/git-cl:/home/hermann/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
Setting GUILE_MIN_YIELD_1 to 65
Setting GUILE_MIN_YIELD_2 to 65
Setting GUILE_MIN_YIELD_MALLOC to 65
Setting GUILE_INIT_SEGMENT_SIZE_1 to 10485760
Setting GUILE_MAX_SEGMENT_SIZE to 104857600

LILYPOND_DATADIR="/usr/local/share/lilypond/2.19.43"
LOCALEDIR="/usr/local/share/locale"

Effective prefix: "/home/hermann/lilypond-git/build/out/share/lilypond/current"

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[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-lilybook.lytex
> 
> always fails with:
> 
> $ lilypond-book --output=out --pdf aaa-lilybook.lytex
> lilypond-book (GNU LilyPond) 2.19.43
> Reading aaa-lilybook.lytex...
> Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default page 
> settings.
> 
> Dissecting...
> Writing snippets...
> Processing...
> Running lilypond...
> GNU LilyPond 2.19.43
> Processing `./snippet-map--2641629851966957681.ly'
> Parsing...
> Processing `./55/lily-88e32432.ly'
> Parsing...
> Layout output to `./55/lily-88e32432.eps'...
> Converting to `./55/lily-88e32432.pdf'...
> warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
> -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
> -sOutputFile=./55/lily-88e32432.pdf -c.setpdfwrite
> -f./55/lily-88e32432.eps)' failed (256)
> 
> fatal error: failed files: "55/lily-88e32432.ly"
> command failed: /home/hermann/lilypond-git/build/out/bin/lilypond
> --formats=ps -dbackend=eps  -I  "./"  -I  "../" --formats=eps --pdf
> -dinclude-eps-fonts -dgs-load-fonts  -deps-box-padding=3.00
> -dread-file-list -dno-strip-output-dir
> "/home/hermann/lilypondH/Test/forum/aaa-doc-test/out/snippet-names--2641629851966957681.ly"
> Child returned 1

Would you try the following command and show us the result?

$ lilypond-book --output=out --verbose --pdf aaa-lilybook.lytex

`--verbose' is added.

Then, would you show us the generated eps file?
Its filename is shown like `./55/lily-88e32432.eps'.

> But in a .ly-file
> 
> \markup {
>   %foo bar buzz
>   いろはにほへど ちりぬるを
> }
> 
> always returns a correct pdf.

I'd like to compare.
So would you try the following command and show us the result?

$ lilypond --verbose --ps --pdf filename.ly

Then, would you show us the generated filename.ps?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[David Kastrup]

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
problems here.  Have you tried the recent patches by Hosoda-san?  They
would appear to concern Japanese font problems, and there are two on
countdown.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Werner LEMBERG]

>> 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 as in the run without lilypond-book?  Can you do a run where
the intermediate files aren't deleted?


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Thomas Morley]

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) 2.19.43
Reading aaa-lilybook.lytex...
Running `xelatex' on file `/tmp/tmpcibKVM.tex' to detect default page settings.

Dissecting...
Writing snippets...
Processing...
Running lilypond...
GNU LilyPond 2.19.43
Processing `./snippet-map--3768003740979461048.ly'
Parsing...
Processing `./28/lily-a7047c84.ly'
Parsing...
Layout output to `./28/lily-a7047c84.eps'...
Converting to `./28/lily-a7047c84.pdf'...
warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
-dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
-sOutputFile=./28/lily-a7047c84.pdf -c.setpdfwrite
-f./28/lily-a7047c84.eps)' failed (256)

fatal error: failed files: "28/lily-a7047c84.ly"
command failed: /home/hermann/lilypond-git/build/out/bin/lilypond
--formats=ps -dbackend=eps  -I  "./"  -I  "../" --formats=eps --pdf
-dinclude-eps-fonts -dgs-load-fonts  -deps-box-padding=3.00
-dread-file-list -dno-strip-output-dir
"/home/hermann/lilypondH/Test/forum/aaa-doc-test/out/snippet-names--3768003740979461048.ly"
Child returned 1

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

[Werner LEMBERG]

> 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/lilypond-devel