- **Needs**:  -->  
- **Patch**: new --> needs_work
- **Type**:  --> Enhancement
- **Comment**:

Fails a make check

~~~
touch  ./out-test/key-option.texidoc  ./out-test/key-option.options
/home/jlowe/lilypond-git/build/scripts/build/out/run-and-check 
"/home/jlowe/lilypond-git/build/out/bin/lilypond -H texidoc -H options -o 
./out-test /home/jlowe/lilypond-git/input/regression/midi/key-option.ly" 
"key-option.log"

Please check the logfile key-initial.log for errors

/home/jlowe/lilypond-git/./make/midi-rules.make:7: recipe for target 
'out-test/key-initial.midi' failed
make[2]: *** [out-test/key-initial.midi] Error 1
make[2]: *** Waiting for unfinished jobs....

Please check the logfile key-option-all-staves.log for errors

/home/jlowe/lilypond-git/./make/midi-rules.make:7: recipe for target 
'out-test/key-option-all-staves.midi' failed
make[2]: *** [out-test/key-option-all-staves.midi] Error 1

Please check the logfile key-option.log for errors

/home/jlowe/lilypond-git/./make/midi-rules.make:7: recipe for target 
'out-test/key-option.midi' failed
make[2]: *** [out-test/key-option.midi] Error 1
make[2]: Leaving directory 
'/home/jlowe/lilypond-git/build/input/regression/midi'
/home/jlowe/lilypond-git/./make/lysdoc-targets.make:12: recipe for target 
'local-test' failed
make[1]: *** [local-test] Error 2
make[1]: Leaving directory 
'/home/jlowe/lilypond-git/build/input/regression/midi'
GNUmakefile:313: recipe for target 'test' failed
make: *** [test] Error 2

~~~

If I check those log files referenced I don't see anything obvious - e.g:

~~~
Processing `./key-option-midi.ly'
Parsing...
Renaming input to: `out-test/key-option-midi.ly'
Interpreting music...
Preprocessing graphical objects...
Interpreting music...
MIDI output to `./key-option-midi.midi'...
Calculating line breaks... 
Drawing systems... 
Writing header field `texidoc' to `./key-option-midi.texidoc'...
Writing ./key-option-midi-1.signature
Layout output to `./key-option-midi.eps'...
Layout output to `./key-option-midi-1.eps'...
Writing ./key-option-midi-systems.texi...
Writing ./key-option-midi-systems.tex...
Writing ./key-option-midi-systems.count...
Writing timing to key-option-midi.profile...
~~~

That's it.

Sorry that I cannot find anything more.




---

** [issues:#5330] Allow use of Identity-H CMap and CID versions of Emmentaler**

**Status:** Started
**Created:** Sat May 26, 2018 12:54 PM UTC by Knut Petersen
**Last Updated:** Wed May 30, 2018 11:50 AM UTC
**Owner:** Knut Petersen
**Attachments:**

- 
[0001-Allow-use-of-Identity-H-CMap-and-CID-versions-of-Emm.patch](https://sourceforge.net/p/testlilyissues/issues/5330/attachment/0001-Allow-use-of-Identity-H-CMap-and-CID-versions-of-Emm.patch)
 (121.8 kB; text/x-patch)


I think we should remove the use of three encodings/subsets of emmentaler fonts 
from our postscript code and use CID versions of the emmentaler fonts combined 
with the Identity-H CMap instead.

Attached is a patch that implements (and uses) this enhancement:

* When -O TeX or -O TeX-GS is given, lilypond generates postscript code that 
instructs ghostscript to use the Identity-H CMap and CID versions of the 
emmentaler fonts. 
* Without '-O TeX' or '-O TeX-GS' we still use the traditional postscript code.
* Documentation is still missing.

Only a proof of concept, not ready for release, definitely not for lilypond 
2.20.


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • [Lily... Auto mailings of changes to Lily Issues via Testlilyissues-auto

Reply via email to