I thought that the effort to implement and at least minimally
document the command-line option would be greater than the value to
the users of TeX + LilyPond + pdfsizeopt (excluding Knut, who can
already already use his patch).
Well, his test shows
19.979.555 original 2.18.2 notation.pdf +
When environment variable PATH is undefined, the following error occurs.
```
C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\binset PATH=
C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\binlilypond
GNU LilyPond 2.19.16
terminate called after throwing an instance of 'std::logic_error'
what():
On 29.12.2014 05:56, Werner LEMBERG wrote:
Please report this to the author of pdfsizeopt.py, who is still
maintaining the program (though not *very* active, it seems).
I'll do that soon, but first I'll look at the code myself.
- link targets in files processed by ghostscript git master are
2014-12-28 21:50 GMT+01:00 Keith OHara k-ohara5...@oco.net:
Jean-Charles Malahieude lilyfan at orange.fr writes:
I've locally merged master into translation, and before merging
translation back to staging will correct bad cross-links.
Sorry, I should have changed the rlearning links.
- link targets in files processed by ghostscript git master are
lost.
Is this a bug in gs?
No, not really. It's a missing feature. See
http://bugs.ghostscript.com/show_bug.cgi?id=695747
Interesting.
Unfortunately that means that the patch should not be used to
generate the lilypond
2014-12-29 11:07 GMT+01:00 Werner LEMBERG w...@gnu.org:
PS: What about creating a single PDF from *all* lilypond manuals?
This should then be able to benefit from your changes, right? I
can even imagine that this `complete' document would be
considerably smaller than the the
Is somebody actually feeling responsible for this issue? Comments have
not been adressed, but it would appear that both Rietveld issue and
Google issue have been created by the same person, so he should have
seen the comments?
https://codereview.appspot.com/191260043/
David,
On 29/12/14 11:22, d...@gnu.org wrote:
Is somebody actually feeling responsible for this issue? Comments have
not been adressed, but it would appear that both Rietveld issue and
Google issue have been created by the same person, so he should have
seen the comments?
On 29.12.2014 09:15, Werner LEMBERG wrote:
If you find it straightforward to encapsulate the code, then we can
probably incorporate it.
Knut, are you willing to work on that, this is, adding a command line
argument and properly documenting it?
Yes, I could do that.
cu,
Knut
On 28.12.2014 23:46, Keith OHara wrote:
if we can avoid whatever problems induced HanWen to move to using glyph names in the .ps.
Well, using glyphshow and glyphnames was and is easy, and for a normal document
it is a very efficient solution.
cu,
Knut
Knut,
On 29/12/14 14:05, Knut Petersen wrote:
On 29.12.2014 09:15, Werner LEMBERG wrote:
If you find it straightforward to encapsulate the code, then we can
probably incorporate it.
Knut, are you willing to work on that, this is, adding a command line
argument and properly documenting it?
Hi all,
Is there something that I need to do at this point in the system? I see the
comment about the unnecessary `progn` in the code. Should I nix that and
resubmit?
Cheers,
Peter
On Mon, Dec 29, 2014 at 4:44 AM, James Lowe p...@gnu.org wrote:
David,
On 29/12/14 11:22, d...@gnu.org wrote:
On 2014/12/29 15:39:40, pschmied wrote:
Hi all,
Is there something that I need to do at this point in the system? I
see the
comment about the unnecessary `progn` in the code. Should I nix that
and
resubmit?
The progn is a style issue but not a show stopper. However,
unconditionally
Oops. Good catches. I'll make those edits and resubmit today.
On Mon, Dec 29, 2014 at 8:21 AM, d...@gnu.org wrote:
On 2014/12/29 15:39:40, pschmied wrote:
Hi all,
Is there something that I need to do at this point in the system? I
see the
comment about the unnecessary `progn` in the
Hello,
Here is the current patch countdown list. The next countdown will be on
January 1st.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaitingcolspec=Patch%20Owner%20ID%20Summarysort=patch
15 matches
Mail list logo
