Hey all,
An update on this patch.
After having correctly skylined dynamics, I'm realizing that serifed fonts and
italicized fonts are posing a problem for snug vertical alignment. Joe and I
have been back and forth about a solution and he has graciously accepted to
tag-team the problem with
Reinhold Kainhofer writes:
A) Development of ly2xml
Reviewers would probably argue that this is not really scientific
research and should be funded by an industry partner instead.
Some may even note that the hardest part of this has already been
prototyped as part of schikkers list and argue
Jan Nieuwenhuizen jann...@gnu.org writes:
Reinhold Kainhofer writes:
A) Development of ly2xml
Reviewers would probably argue that this is not really scientific
research and should be funded by an industry partner instead.
Some may even note that the hardest part of this has already been
2012/3/8 David Kastrup d...@gnu.org:
The situation should now be under control again. The translation branch
has been merged with a helper branch that should bring in all the
changes from commits that the merge history suggests to be present.
Thank you, David. I apologize. I feel bad for your
David Kastrup writes:
Jan Nieuwenhuizen jann...@gnu.org writes:
Reinhold Kainhofer writes:
A) Development of ly2xml
Reviewers would probably argue that this is not really scientific
research and should be funded by an industry partner instead.
Some may even note that the hardest part of
Hello,
On 8 March 2012 11:08, David Kastrup d...@gnu.org wrote:
...
In any case: I think you should merge (merge!) more often, master to
translation, translation to staging. It does not make all that much
sense if translations come 2 versions later into master than they have
been written.
James pkx1...@gmail.com writes:
On 8 March 2012 11:08, David Kastrup d...@gnu.org wrote:
...
In any case: I think you should merge (merge!) more often, master to
translation, translation to staging. It does not make all that much
sense if translations come 2 versions later into master
- Original Message -
From: Phil Holmes em...@philholmes.net
To: Peekay pkx1...@gmail.com; Colin Hall colingh...@gmail.com;
Eluze elu...@gmail.com; Marek Klein ma...@gregoriana.sk; Ralph
Palmer palmer.r.vio...@gmail.com
Cc: Graham Percival gra...@percival-music.ca; d...@gnu.org
Sent:
On Thu, Mar 08, 2012 at 05:24:51PM -, Phil Holmes wrote:
One thought. Some issues are best verified by checking lily output
- http://code.google.com/p/lilypond/issues/detail?id=2246 for
example. Can we break a normal rule and check these against a newly
made binary? What we'd then be
Hello, Janek!
Quoting Janek Warchoł janek.lilyp...@gmail.com:
I'm attaching the Scheme code with a convoluted example (3 staves with
3 voices on each).
I don't have the time to dive into details, but the output looks good!
Be sure to post it on Rietveld for a review when you come back.
On 3/8/12 2:44 PM, Pavel Roskin pro...@gnu.org wrote:
Hello, Janek!
Quoting Janek Warchoł janek.lilyp...@gmail.com:
I'm attaching the Scheme code with a convoluted example (3 staves with
3 voices on each).
I don't have the time to dive into details, but the output looks good!
Be sure to
For 20:00 MDT Sunday March 11, 2012
Defect:
Issue 2376
http://code.google.com/p/lilypond/issues/detail?id=2376: Automatic
footnotes on \null markups causes unexpected results - R 5755058
http://codereview.appspot.com/5755058/
Enhancement:
Issue 2348
12 matches
Mail list logo