James Lowe wrote Tuesday, May 04, 2010 11:19 AM
Trevor Daniels wrote:
Mark Polesky wrote Tuesday, May 04, 2010 5:34 AM
Trevor Daniels wrote:
Carl Sorensen wrote:
I think we should always use bar-checks when the piece
is more than one bar long. That's a good habit to get
into; we ought to
Trevor Daniels wrote:
A brief description of bar checks in 1.2.2 Working on
input files would be good. I think bar checks are at
least as important as a \version statement, which is
mentioned there.
I think a better place would be in a new @subsection at the
top of 2.1 Single staff notation,
Am Dienstag, 4. Mai 2010 18:10:42 schrieben Sie:
I have seen in LilyPond's commits that you seem to have worked on the
cueDuring system.
[...]
I thought you could maybe help me again... ;D
I asked 7 months ago a question on -user about something I wanted to do
with \cueDuring but it didn't
I'd be happy with this too.
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: Carl Sorensen c_soren...@byu.edu; lilypond-devel
lilypond-devel@gnu.org; Trevor Daniels t.dani...@treda.co.uk
Cc: Graham Percival gra...@percival-music.ca; James Lowe
Hi Francisco,
Your last set of LSR texidocs included several missing the -es suffix.
I've pushed a fix for this, but wondered whether it's worth getting
makelsr.py to do this automatically
(http://codereview.appspot.com/1105042/show).
Cheers,
Neil
On 5/4/10 11:19 AM, Mark Polesky markpole...@yahoo.com wrote:
Trevor Daniels wrote:
A brief description of bar checks in 1.2.2 Working on
input files would be good. I think bar checks are at
least as important as a \version statement, which is
mentioned there.
I think a better place
On 3 May 2010 22:42, Benkő Pál benko@gmail.com wrote:
will the attached do?
Thanks, that's fine.
I've pushed your changes with a few minor tweaks to the regtest
(version number and some formatting nitpicks).
Cheers,
Neil
___
lilypond-devel
2010/5/4 Neil Puttock n.putt...@gmail.com:
Hi Francisco,
Your last set of LSR texidocs included several missing the -es suffix.
Argh! Thank you. They were all the new snippets, never translated before.
I've pushed a fix for this, but wondered whether it's worth getting
makelsr.py to do
Are we allowed to quote Star Wars without attribution in
our docs?
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/usage/lilypond-book.itely;h=5bcd666;hb=HEAD#l85
The change originated here:
Carl Sorensen c_soren...@byu.edu writes:
On 4/15/10 3:00 AM, David Kastrup d...@gnu.org wrote:
Something like that. Splitting scanning and evaluating into two should
ensure that the evaluation happens not at a time when the parsing of
preceding constructs has not yet properly completed.
In the HTML docs, the context-example.eps image doesn't
get displayed in LM 3.3.1 Contexts explained, though it
does show up in the PDF.
http://kainhofer.com/~lilypond/Documentation/learning-big-page.html#Contexts-explained
Also, this worked in 2.12*, but after some minor detective
work, I
I posted a new patch set incorporating most of the requests
you guys made. Please have a look at the new one and let me
know what you think: http://codereview.appspot.com/1056041
Thanks.
- Mark
___
lilypond-devel mailing list
Hello
Trevor Daniels wrote:
I'd be happy with this too.
Trevor
Thanks all.
I'll get a patch made some time this evening.
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Mark,
I think it's an improvement. I've made specific comments inline.
Thanks!
Carl
http://codereview.appspot.com/1056041/diff/11001/12001
File Documentation/learning/common-notation.itely (right):
http://codereview.appspot.com/1056041/diff/11001/12001#newcode313
On Tue, May 04, 2010 at 10:19:52AM -0700, Mark Polesky wrote:
Trevor Daniels wrote:
A brief description of bar checks in 1.2.2 Working on
input files would be good. I think bar checks are at
least as important as a \version statement, which is
mentioned there.
I think a better place
Carl Sorensen c_soren...@byu.edu writes:
On 4/15/10 3:00 AM, David Kastrup d...@gnu.org wrote:
Something like that. Splitting scanning and evaluating into two
should ensure that the evaluation happens not at a time when the
parsing of preceding constructs has not yet properly completed.
I guess not. Graham insisted on removing my two
bars of Over the Rainbow.
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: lilypond-devel lilypond-devel@gnu.org
Sent: Wednesday, May 05, 2010 6:01 AM
Subject: copyright question
Are we allowed to quote Star
Graham Percival wrote Wednesday, May 05, 2010 3:51 PM
On Tue, May 04, 2010 at 10:19:52AM -0700, Mark Polesky wrote:
Trevor Daniels wrote:
A brief description of bar checks in 1.2.2 Working on
input files would be good. I think bar checks are at
least as important as a \version statement,
Mark Polesky wrote Wednesday, May 05, 2010 7:16 AM
In the HTML docs, the context-example.eps image doesn't
get displayed in LM 3.3.1 Contexts explained, though it
does show up in the PDF.
http://kainhofer.com/~lilypond/Documentation/learning-big-page.html#Contexts-explained
Also, this
Graham Percival wrote:
If we need it for 2.3 Songs... which I suppose we should
do... then I'd put it as either the last item inside
2.1.6 Advanced rhythmic commands, or as a new 2.1.7.
A bar check is hardly an advanced rhythmic command...
- Mark
On Wed, May 5, 2010 at 5:37 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Graham Percival wrote Wednesday, May 05, 2010 3:51 PM
or as a new 2.1.7.
I suppose this would do, as long as the previous examples
didn't include bar checks.
The only part that might need them are some of the slur
Hello. From a while ago, my Evince pdf reader throws this message on
console, hundredths of times repeated:
Error: Illegal entry in bfrange block in ToUnicode CMap
It only happens when I open lilypond-made PDFs; other documents do not
show that.
Not a big problem because they are open and
Of course we're not allowed to do that, regardless of the attribution.
Please change it immediately.
Cheers,
- Graham
On Wed, May 5, 2010 at 6:01 AM, Mark Polesky markpole...@yahoo.com wrote:
Are we allowed to quote Star Wars without attribution in
our docs?
es
*** closing `itemize' (in
/home/graham/lilypond/lilypond-git/Documentation/es/included/generating-output.itexi
l. 16)
fr
** Node following `Manuels' in menu `Community' and in sectionning
`Communauté' differ
** `Communauté' doesn't appear in menus
On Wed, May 5, 2010 at 11:57 AM, carl.d.soren...@gmail.com wrote:
I think it's an improvement. I've made specific comments inline.
sweet mao... you're adding barline checks to every single example?!
cis4 ees fisis, aeses |
I definitely do **not** like this.
cis4 ees fisis, aeses
is just
On Sun, May 2, 2010 at 7:01 PM, Mark Polesky markpole...@yahoo.com wrote:
First, if you haven't looked at it yet, you should know that
one direct result of the patch is the increase in length of
many of the examples (vertically). Graham has already
expressed his dissatisfaction with this,
On Mon, May 3, 2010 at 2:40 PM, Marek Klein ma...@gregoriana.sk wrote:
Hi Graham,
I would like to ask for some advices concerning tracking of patches:
1. Is there an easy way to find out if some patch was pushed?
When I apply a patch, I try to always reply to the same forum that I
saw it
I'm not certain it's a texi2html bug, or a bug in our texi2html init
file, but either way it should be in the tracker.
Bug Squad: please add this. Type-build, priority-medium.
Cheers,
- Graham
On Fri, Apr 30, 2010 at 5:38 PM, Mark Polesky markpole...@yahoo.com wrote:
I've noticed that
On Wed, May 5, 2010 at 7:01 AM, Mark Polesky markpole...@yahoo.com wrote:
Are we allowed to quote Star Wars without attribution in
our docs?
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/usage/lilypond-book.itely;h=5bcd666;hb=HEAD#l85
Heh. That's funny :-)
I think it's
Sorry, Neil suggested it was related to a libpoppler bug, cf.
http://lists.gnu.org/archive/html/lilypond-user/2010-04/msg00255.html
Seems to be fixed in last version...
Cheers,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
lilypond-devel mailing
On 5/5/10 2:04 PM, Francisco Vila paconet@gmail.com wrote:
2010/5/5 Mark Polesky markpole...@yahoo.com:
Are we allowed to quote Star Wars without attribution in
our docs?
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/usage/lil
Francisco Vila wrote:
These are multiline text files. Which text should we
look for?
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/usage/lilypond-book.itely;h=5bcd666;hb=HEAD#l85
85 \begin{lilypond}
86 \relative c' {
87 c2 g'2 \times 2/3 { f8 e d } c'2 g4
88 }
89
On Wed, May 05, 2010 at 05:42:07PM +0100, Trevor Daniels wrote:
Mark Polesky wrote Wednesday, May 05, 2010 7:16 AM
In the HTML docs, the context-example.eps image doesn't
get displayed in LM 3.3.1 Contexts explained, though it
does show up in the PDF.
I've tried to fix it more than once,
2010/5/5 Francisco Vila paconet@gmail.com:
Hello. From a while ago, my Evince pdf reader throws this message on
console, hundredths of times repeated:
Error: Illegal entry in bfrange block in ToUnicode CMap
It only happens when I open lilypond-made PDFs; other documents do
not show
On 5/5/10 12:01 PM, Graham Percival gra...@percival-music.ca wrote:
On Wed, May 5, 2010 at 11:57 AM, carl.d.soren...@gmail.com wrote:
I think it's an improvement. I've made specific comments inline.
sweet mao... you're adding barline checks to every single example?!
cis4 ees fisis,
On Wed, May 05, 2010 at 10:04:21PM +0200, Francisco Vila wrote:
2010/5/5 Mark Polesky markpole...@yahoo.com:
Are we allowed to quote Star Wars without attribution in
our docs?
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/usage/lilypond-book.itely;h=5bcd666;hb=HEAD#l85
On 5/5/10 11:40 AM, Francisco Vila paconet@gmail.com wrote:
Hello. From a while ago, my Evince pdf reader throws this message on
console, hundredths of times repeated:
Error: Illegal entry in bfrange block in ToUnicode CMap
It only happens when I open lilypond-made PDFs; other
On 5/5/10 6:11 PM, Graham Percival gra...@percival-music.ca wrote:
On Wed, May 05, 2010 at 06:04:42PM -0600, Carl Sorensen wrote:
On 5/5/10 12:01 PM, Graham Percival gra...@percival-music.ca wrote:
On Wed, May 5, 2010 at 11:57 AM, carl.d.soren...@gmail.com wrote:
I think it's an
On Wed, May 05, 2010 at 06:04:42PM -0600, Carl Sorensen wrote:
On 5/5/10 12:01 PM, Graham Percival gra...@percival-music.ca wrote:
On Wed, May 5, 2010 at 11:57 AM, carl.d.soren...@gmail.com wrote:
I think it's an improvement. I've made specific comments inline.
sweet mao... you're
On 5/5/10 11:03 AM, Ian Hulin i...@hulin.org.uk wrote:
Hi all,
I put this patch up for review about a month back. Patrick has given some
feedback and I have implemented his comments. Could someone have a look and
if it's OK push, please?
I didn't see any issues in the patch, except that
On Tue, 2010-05-04 at 12:43 +0200, Reinhold Kainhofer wrote:
For fixing the figured bass alignment (i.e. the 4 6 4 case with extenders
turned onn), I have a problem with the vertical alignment:
8 6 4 8 5 3
Should appear as
8
6 5
4 3
I'm adding the elements to the
Francisco,
This message was discussed in a thread on bug and user (not devel) :)
'error message from PDF viewer'
on 18th April.
The last message in the thread was
On Mon, 19 Apr 2010, Graham Percival wrote:
On Sun, Apr 18, 2010 at 07:25:29PM +0200, Martin Tarenskeen wrote:
OK. Here is a
42 matches
Mail list logo
