Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the Esperanto team of translators. The file is available at:
http://translationproject.org/latest/lilypond/eo.po
(We can arrange things so t
Answers to comments.
https://codereview.appspot.com/343970043/diff/1/mf/GNUmakefile
File mf/GNUmakefile (right):
https://codereview.appspot.com/343970043/diff/1/mf/GNUmakefile#newcode145
mf/GNUmakefile:145: cd $(outdir) && mv $(notdir $@).otf $(notdir $@)
On 2018/05/26 16:25:25, lemzwerg wrote:
Changes:
Command line:
"-O size" is gone
"-O legacy" is added, uses our old non-encodings code
"-O TeX" new default as the pdf files are smaller.
"-O TeX-GS" use if you want to include lilypond pdfs in TeX document and
postprocess the resulting pdfs with ghostscript. You also need to give
/path/
Am 30.05.2018 um 11:49 schrieb David Kastrup:
-dSAFER, that is broken on windows.
So the question is: has that apparent group read permission problem (?)
been fixed in the last 13 years?
Unless somebody has a clue, I lean towards just trying this out and
waiting for problem reports. At le
Knut Petersen writes:
> Hi everybody!
>
> Could someone please explain why we use ghostscript in -dNOSAFER
> mode if the windows platform is used?
>
>(define-public (postscript->pdf paper-width paper-height
> base-name tmp-name is-eps)
> (let* ((pdf-
Hi everybody!
Could someone please explain why we use ghostscript in -dNOSAFER
mode if the windows platform is used?
(define-public (postscript->pdf paper-width paper-height
base-name tmp-name is-eps)
(let* ((pdf-name (string-append base-name ".pdf")
