Great!
But, I failed to build in my Cygwin (case insensitive) environment.
I think there is potential confusion where the CID file has no
extension,
and just has capitalization to indicate it. Is this a standard for
CID-keyed fonts?
Actually, it is, but I don't see a reason to not use `.ci
On 2018-05-26 04:12 PM, David Kastrup wrote:
Arthur Reutenauer writes:
I have to correct a post from the other day: In my 30+ years on electronic
networks, *this* is the hardest I’ve ever seen anyone work to die on a hill not
worth dying on.
Hold that thought...
Well, that too.
I won't
https://codereview.appspot.com/343970043/diff/1/mf/GNUmakefile
File mf/GNUmakefile (right):
https://codereview.appspot.com/343970043/diff/1/mf/GNUmakefile#newcode145
mf/GNUmakefile:145: cd $(outdir) && mv $(notdir $@).otf $(notdir $@)
On 2018/05/26 15:17:09, Carl wrote:
I think there is potenti
Reviewers: ,
Description:
Let general-column deal reliable with empty args
Previously an args-list of empty-stencils issued a programming error:
Improbable offset for stencil: -inf staff space
This patch removes empty stencils from the args-list.
If args-list is empty, an empty stencil is retu
However, I believe that the case problem with MacOS needs to be fixed.
I
believe this patch won't work on MacOS -- only one version of the font
will be
installed (the last one to be created).
I wasn't aware of MacOS case handling, I'll have a look at it.
Thanks for pointing out that problem
Arthur Reutenauer writes:
>> I have to correct a post from the other day: In my 30+ years on electronic
>> networks, *this* is the hardest I’ve ever seen anyone work to die on a hill
>> not worth dying on.
>
> Hold that thought...
Well, that too.
I won't presume to judge the worthiness of t
> I have to correct a post from the other day: In my 30+ years on electronic
> networks, *this* is the hardest I’ve ever seen anyone work to die on a hill
> not worth dying on.
Hold that thought...
Arthur
___
lilypond-devel mailing list
lil
Carl Sorensen writes:
> On 5/26/18, 10:44 AM, "lilypond-devel on behalf of David Kastrup"
> d...@gnu.org> wrote:
>
>
> Entirely subjective which hill is worth dying on: Güllich was the first
> to extensively exposed hard "solo" routes, with the final climb being
> without prote
On 5/26/18, 10:44 AM, "lilypond-devel on behalf of David Kastrup"
wrote:
Entirely subjective which hill is worth dying on: Güllich was the first
to extensively exposed hard "solo" routes, with the final climb being
without protection where a missed or broken-out hold would h
lemzw...@googlemail.com writes:
> LGTM, but I share Carl's concerns, in particular the issue with font
> names that only differ in case.
That sounds like a problem not just on MacOSX but also on Windows.
> https://codereview.appspot.com/343970043/
--
David Kastrup
___
Kieren MacMillan writes:
> metachromatic wrote:
>>>To see how silly your comment on this issue is, let's calculate the
>>> difference in time twixt a tuplet like 7919/4451 against a tuplet
>>> 7909/4447 over the course of two minutes and 13 seconds of 4/4 time at
>>> a tempo of metronome mar
LGTM, but I share Carl's concerns, in particular the issue with font
names that only differ in case.
https://codereview.appspot.com/343970043/diff/1/mf/GNUmakefile
File mf/GNUmakefile (right):
https://codereview.appspot.com/343970043/diff/1/mf/GNUmakefile#newcode145
mf/GNUmakefile:145: cd $(ou
metachromatic wrote:
>>To see how silly your comment on this issue is, let's calculate the
>> difference in time twixt a tuplet like 7919/4451 against a tuplet
>> 7909/4447 over the course of two minutes and 13 seconds of 4/4 time at
>> a tempo of metronome marking 90:
>>
>>The difference
The patch looks well put together.
However, I believe that the case problem with MacOS needs to be fixed.
I believe this patch won't work on MacOS -- only one version of the font
will be installed (the last one to be created).
https://codereview.appspot.com/343970043/diff/1/mf/GNUmakefile
File
On Sat, May 26, 2018 at 8:35 AM, metachromatic wrote:
> To see how silly your comment on this issue is, let's calculate the
> difference in time twixt a tuplet like 7919/4451 against a tuplet
> 7909/4447 over the course of two minutes and 13 seconds of 4/4 time at
> a tempo of metronome mar
Reviewers: ,
Message:
Please review.
Description:
Allow use of Identity-H CMap and CID versions of Emmentaler
When -O TeX or -O TeX-GS is given, lilypond generates
postscript code that instructs ghostscript to use the
Identity-H CMap and CID versions of the emmentaler
fonts. Used e.g. by 'make
On 2018/05/23 12:22:09, bmwiedemann wrote:
sorting .o files instead of .cc
This is not quite what I meant. If it works for you, fine, but I think
it is more likely to break eventually than if you found the commands
that are being invoked and sorted their arguments. For example,
$(CXX) -o
Hello,
Here is the current patch countdown list. The next countdown will be on May
29th.
A quick synopsis of all patches currently in the review process can be found
here:
http://philholmes.net/lilypond/allura/
Push: No patches to push at this time.
Countdown:
5329 Improve make-brack
> On 26 May 2018, at 08:35, metachromatic wrote:
>
> ... let's calculate the
> difference in time twixt a tuplet like 7919/4451 against a tuplet
> 7909/4447 over the course of two minutes and 13 seconds of 4/4 time at
> a tempo of metronome marking 90:
>
>The difference is (0.00064839149)*6
> On 26 May 2018, at 08:35, metachromatic wrote:
>
> ... let's calculate the
> difference in time twixt a tuplet like 7919/4451 against a tuplet
> 7909/4447 over the course of two minutes and 13 seconds of 4/4 time at
> a tempo of metronome marking 90:
>
> The difference is (0.00064839149)*60
metachromatic writes:
If you want an answer, ask a question. Just stating something in the
hope that the correction will work as an answer is trying your luck.
>
>What's the point of asking a question on this forum? The answer
> always seems to be: "Go fix it yourself. Dig into th
21 matches
Mail list logo
