Re: Reduce size of PDF files when inc. in *TeX docs (issue 194090043 by address@hidden)

[pkx166h]

Thanks for your patience.




https://codereview.appspot.com/194090043/diff/20001/Documentation/de/usage/running.itely
File Documentation/de/usage/running.itely (right):

https://codereview.appspot.com/194090043/diff/20001/Documentation/de/usage/running.itely#newcode166
Documentation/de/usage/running.itely:166: notation.pdf (Lilypond 2.18.2)
ist ca. 26MB groß, erzeugt
On 2015/01/11 20:13:45, lemzwerg wrote:
> ... ca.@: 26MB ...

See comment above

https://codereview.appspot.com/194090043/diff/20001/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):

https://codereview.appspot.com/194090043/diff/20001/Documentation/usage/running.itely#newcode187
Documentation/usage/running.itely:187: font data which can make
significant reductions in file size.
On 2015/01/12 05:56:14, lemzwerg wrote:
> One point is missing: Why is the option called --bigpdfs if the we get
> significant reductions in file size?

I think this has now been explained and I have also rewritten the
explanation based on the main thread of the tracker.

https://codereview.appspot.com/194090043/diff/20001/Documentation/usage/running.itely#newcode199
Documentation/usage/running.itely:199: Using @code{pdfsizeopt.py} can
then be used to further optimize the size
On 2015/01/12 05:56:14, lemzwerg wrote:
> I would start with

>    Optionally, using @code{pdfsizeopt.py} ...

> to indicate that this is an extra bonus.

See above.

https://codereview.appspot.com/194090043/diff/20001/Documentation/usage/running.itely#newcode206
Documentation/usage/running.itely:206:
On 2015/01/12 05:56:14, lemzwerg wrote:
> Should the (current) problem with external links be mentioned here
too?

See above.

https://codereview.appspot.com/194090043/diff/20001/ps/encodingdefs.ps
File ps/encodingdefs.ps (right):

https://codereview.appspot.com/194090043/diff/20001/ps/encodingdefs.ps#newcode8
ps/encodingdefs.ps:8: /LilyNoteHeadEncoding [
On 2015/01/18 06:33:02, Keith wrote:
> This is a little different from "FetaNoteheadsEncoding" in
> 'mf/out/feta-noteheads11.enc' generated by
'scripts/build/mf-to-table.py'

I need some advice on what to do here from Knut.

https://codereview.appspot.com/194090043/diff/20001/ps/encodingdefs.ps#newcode108
ps/encodingdefs.ps:108: /noteheads.d0doFunk {<01> show} def
On 2015/01/18 06:33:02, Keith wrote:
> I suppose you use PS definitions here because the Scheme code does not
know the
> encoding table, so the Scheme does not know what number to write in
'\?? show'

Again I cannot comment - Knut?

https://codereview.appspot.com/194090043/diff/20001/scm/output-ps.scm
File scm/output-ps.scm (right):

https://codereview.appspot.com/194090043/diff/20001/scm/output-ps.scm#newcode64
scm/output-ps.scm:64: (ly:inexact->string i 8)))
On 2015/01/18 06:33:02, Keith wrote:
> This is the old code that output PS 'show' rather than 'glyphshow'

I don't know what to do here (if anything).

https://codereview.appspot.com/194090043/