>> 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 makes the
final output file much smaller.
> Personally, I find the prospect of not having 4GB of disk usage for
> running lilypond-patchy-staging quite more compelling, and I would
> seriously suspect that all the amount of font juggling and merging
> subsetted fonts will not just take quite a bit of disk space but
> also of processing time. So if we could successfully pull this off
> and have it work reliably for lilypond-book, I consider it likely to
> end up as a real boon in resource usage.
Me too. The writing of font resources shouldn't be too difficult to
implement, at least for persons who are fluent with Scheme...
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
