On Wed, Oct 4, 2017 at 6:27 PM, Carl Sorensen wrote:
> I haven't pulled out all the fonts yet to see how big they are, but I'm
> uncomfortable with referencing a blob in a given commit on the repo.
I think the largest one was about 101KB. So perhaps 1.5MB for all 12 of them.
> I'd be happier if
On 10/4/17 4:06 PM, "lilypond-devel on behalf of Karlin High"
wrote:
>https://codereview.appspot.com/315850043/
>https://sourceforge.net/p/testlilyissues/issues/4998/
>
>I found this issue with the fonts while reading the LilyDev
>instructions on GitHub. To me, it looks like the easiest way to
>r
https://codereview.appspot.com/315850043/
https://sourceforge.net/p/testlilyissues/issues/4998/
I found this issue with the fonts while reading the LilyDev
instructions on GitHub. To me, it looks like the easiest way to
resolve it would be adding some WGET commands to the
~/.lilydev-setup.sh scrip
> Unfortunately, non-CID-keyed fonts can not use Identity-H encoding.
> XeTeX and LuaTeX seem to convert non-CID-Keyed font to CID-keyed
font on the
> fly, and embed it to PDF, use Identity-H encoding.
Should we create a tracker for this?
I think whoever has an idea and the time to solve
Thanks, as you can see I just submitted my first patch. I hope I did
everything correctly?
Am 04.10.2017 um 10:47 schrieb Phil Holmes:
Done.
--
Phil Holmes
- Original Message - From: "Malte Meyn"
To:
Sent: Wednesday, October 04, 2017 8:35 AM
Subject: issue tracker write access
H
Reviewers: ,
Message:
See
https://lists.gnu.org/archive/html/lilypond-user/2017-10/msg00012.html
for sort of bug report on the user list.
Description:
Merge_rests_engraver: fix vertical rest positions
When used with \magnifyStaff the engraver failed to position merged
rests correctly. Using sta
Issue 1255 is: "#1255 Extract hyphen dimensions and/or hyphen glyph
from the
font "
Your patch does not extract hyphen dimensions or the hyphen glyph from
the font.
It might get used for using the hyphen glyph (provided that you know
its
font-dependent character code) as a hyphen, so
Done.
--
Phil Holmes
- Original Message -
From: "Malte Meyn"
To:
Sent: Wednesday, October 04, 2017 8:35 AM
Subject: issue tracker write access
Hello list,
too long I have waited but now I would like to start contributing to
LilyPond. Currently I’m going through the “quick start
Hello list,
too long I have waited but now I would like to start contributing to
LilyPond. Currently I’m going through the “quick start” of the CG; could
you please give me (maltem on SourceForge) write access to the issue
tracker?
Cheers,
Malte
_
