[445bf3bb2fbd1f259fe43ade204fb34d68bdd581]
Folks,
have a look at NR section `Percent Repeats', `Known Issues and
Warnings'. There is code like
\relative c'' {
\repeat percent 3 { \time 5/4 c2. 2 \time 4/4 2 2 }
}
which generates the attached image. The generation of a second staff
On 7/22/16 12:35 PM, "James" wrote:
>
>jlowe@jloweDesktop ~/lilypond-git/build/input $ du -smh * | sort -hr
>1.9Gregression
>8.0Kout-www
>8.0Kout
>4.0KGNUmakefile
Do we turn off point and click when doing the doc builds?
Carl
James writes:
> NB> It seems that the Japanese docs are built using its own 'build'
> dir (i.e. it has its own out-www build doc and doesn't seem to share
> any of the files the other docs do while building, but I am probably
> not understanding this).
>
> Are we wasting build time
hello,
On 22/07/16 18:48, Carl Sorensen wrote:
On 7/22/16 9:35 AM, "lilypond-devel on behalf of David Kastrup"
wrote:
A 30% reduction in the final output file size sounds nice. Personally,
I find the prospect of
On 7/22/16 9:35 AM, "lilypond-devel on behalf of David Kastrup"
wrote:
>
>A 30% reduction in the final output file size sounds nice. Personally,
>I find the prospect of not having 4GB of disk usage for running
>> For remote PDF links, rather than they are lost, I think that PDF
>> destination names are replaced.
>
> Hmm. This smells fishy.
>
>> Would you know a tool other than texinfo that can generate remote
>> PDF links?
>
> Sorry, no.
I've noticed that
plain pdfTeX (without texinfo) can generate
>> Comparing the `--bigpdfs' method with the fontless PDF approach as
>> outlined above, the latter creates a final output file about 30%
>> smaller (at least in my small test).
>
> A 30% reduction in the final output file size sounds nice.
This is an *additional* 30%, since `--bigpdfs' already
Werner LEMBERG writes:
> About a month ago we discussed how to reduce the disk space necessary
> for builing the lilypond documentation.
>
>> [...] Since lilypond itself converts all fonts to PostScript
>> resources, why not writing those resources to a `fontresource'
>> directory
> ps2pdf -I \
> -dNOSAFER -P \
> Fontless.pdf WithEmbeddedFonts.pdf
This should rather be
ps2pdf -I \
-dNOSAFER \
Fontless.pdf WithEmbeddedFonts.pdf
I've tested with the fonts in the current directory, thus `-P'.
Werner
About a month ago we discussed how to reduce the disk space necessary
for builing the lilypond documentation.
> [...] Since lilypond itself converts all fonts to PostScript
> resources, why not writing those resources to a `fontresource'
> directory instead of embedding? We could add a
Hello,
I made 2 patches for issue #4814 and for a FTBFS witch gcc 6 on Fedora 24.
These 2 patches seem to solve that problem for me.
Best regards
Guido Aulisi
From 682f75315e6820220ecf45717664f6d32f480c98 Mon Sep 17 00:00:00 2001
From: Guido Aulisi
Date: Fri, 22 Jul 2016
On 2016/07/22 07:55:54, dak wrote:
On 2016/07/22 07:41:00, http://mark_opus11.net wrote:
> On 2016/07/22 04:26:01, lemzwerg wrote:
> > LGMT. Thanks a lot!
>
> Might it be a good idea to keep one example using the old define
method, which
> is still more convenient for setting the value for
Reviewers: lemzwerg, mark_opus11.net,
Message:
On 2016/07/22 07:41:00, mark_opus11.net wrote:
On 2016/07/22 04:26:01, lemzwerg wrote:
> LGMT. Thanks a lot!
Might it be a good idea to keep one example using the old define
method, which
is still more convenient for setting the value for
On 2016/07/22 04:26:01, lemzwerg wrote:
LGMT. Thanks a lot!
Might it be a good idea to keep one example using the old define method,
which is still more convenient for setting the value for multiple usages
of \afterGrace (or globally)?
https://codereview.appspot.com/304200043/
https://codereview.appspot.com/303980043/diff/20001/scm/time-signature-settings.scm
File scm/time-signature-settings.scm (right):
https://codereview.appspot.com/303980043/diff/20001/scm/time-signature-settings.scm#newcode73
scm/time-signature-settings.scm:73: ((beamExceptions . ((end . ((1/20 .
15 matches
Mail list logo