Mark Polesky wrote Saturday, July 25, 2009 4:29 AM
We all okay with this patch?
LGTM
Of course it's a new command and a syntax change; I don't know if
that means some special process has to be taken; updating the
parser, etc. I have no idea, actually. Let me know.
Nothing else is
Hi Graham,
Graham Percival wrote:
On Fri, Jul 24, 2009 at 06:15:31PM -0700, Mark Polesky wrote:
Thanks, Neil. My editor does confusing things with tabs.
I hate them. Who would object if I just started running
tabs-spaces on the source docs? I think we should have
a strict no-tabs rule. And I'm
I really would be glad, if there was a possibility to make notes (including
heads, stems, beams, flags, slurs, clefs, accidentals, ...) smaller.
Unfortunately the \small, \tiny, \set fontSize commands don't affect all parts
of notes (beams, ... are not affected).
Something like
\cueNotes or just
Hi Werner (et al,),
Please use two spaces after a full stop in documentation strings
for consistence.
Since this is incorrect typographical practice, and Lilypond prides
itself on beautiful typography, I'm surprised this is the standard in
the docs — why/how was this decision made?
Thanks, Neil. My editor does confusing things with tabs.
Then use a different editor.
I hate them.
I dislike them, too, but there are many editors which handle them just
fine. I don't see a problem here.
Werner
___
lilypond-devel mailing
Please use two spaces after a full stop in documentation strings for
consistence.
Since this is incorrect typographical practice,
It really depends. IIRC, the Chicaco manual of style recommended
this.
and Lilypond prides itself on beautiful typography, I'm surprised
this is the standard
Hi Werner,
It really depends. IIRC, the Chicaco manual of style recommended this.
The view at CMOS is that there is no reason for two spaces after a
period in published work.
http://www.chicagomanualofstyle.org/CMS_FAQ/OneSpaceorTwo/
OneSpaceorTwo03.html
Also see page 28 of Robert
The view at CMOS is that there is no reason for two spaces after a
period in published work.
Ok, whatever :-) Look up references to TeX and LaTeX for more on this
topic.
However, the PDF (e.g., the NR) *appears* to preserve double-space
sentence separations — where (e.g., some
Marc,
Thanks a million for pointing me at the articulation and MIDI discussion. I
now have a pretty good idea of where to go from here, and I'm almost done
with the first item on my todo list.
Thanks again.
On Tue, Jul 14, 2009 at 2:23 AM, Marc Hohl m...@hohlart.de wrote:
Hello Alan,
Alan
On Sat, 2009-07-25 at 09:58 -0700, Mark Polesky wrote:
...tabs in the source code...
Werner Lemberg wrote:
I dislike them, too, but there are many editors which handle
them just fine. I don't see a problem here.
But would you be *opposed* to a strict no-tab rule?
I like spaces just
I don't know if this needs an additional command, but in Tchaikovsky's 6th
symphony there is a pp (6 p's) during the clarinet solo at the end
of the exposition.
What's funny is that he only uses ff at the beginning of the next
section, which is one of the loudest orchestral moments I
Joe Neeman wrote:
I like spaces just fine, but I'd prefer it if you could hold off
on this for a little while. I have a big patch that I'd like to
merge and I'm not so keen on resolving a bunch of whitespace
conflicts...
Okay, I'll make a note: I'll wait for Han-Wen, Jan, and Joe.
Thanks.
-
On 7/25/09 10:58 AM, Mark Polesky markpole...@yahoo.com wrote:
...tabs in the source code...
Werner Lemberg wrote:
I dislike them, too, but there are many editors which handle
them just fine. I don't see a problem here.
But would you be *opposed* to a strict no-tab rule?
Carl
Hi Werner,
To cite the texinfo info pages:
Thanks for the reference — for subsequent thread-followers, I also
recommend
http://en.wikipedia.org/wiki/Double-spaced_sentences
Indeed, I just see that @frenchspacing is only used for French and
Japanese (the latter only partially). It should
Jonathan Wilkes wrote:
I don't know if this needs an additional command, but in
Tchaikovsky's 6th symphony there is a pp (6 p's) during
the clarinet solo at the end of the exposition.
Yes, and I mentioned the on the last page of book 2 of
the Ligeti etudes. Graham proposed a
On Sat, Jul 25, 2009 at 01:30:45PM -0400, Kieren MacMillan wrote:
Excellent!
Then I nominate @frenchspacing (i.e., single-spaced sentences) be used
for the English docs, consistent with the overwhelming majority of modern
English typographic style guides and practice...
Seconder? Opposed?
Carl Sorensen wrote:
No, Jan was not in favor of it unless it became a standard for
GNU coding. Hence the comment on first making it a standard
(i.e., a GNU standard) and sending a patch to emacs-devel.
The current standard is to let tabs and spaces be handled as
emacs handles them.
Oh, is
On 25 Jul 2009, at 19:39, Patrick McCarty wrote:
One thing you could do right now, without awaiting approval, is to
check for lines that have tabs *after* spaces at the beginning. These
should be converted to tabs *followed* by spaces.
This is not correct, as if tabs are set to 8 spaces, 2
Kieren MacMillan wrote:
Excellent!
Then I nominate @frenchspacing (i.e., single-spaced sentences)
be used for the English docs, consistent with the overwhelming
majority of modern English typographic style guides and
practice... Seconder? Opposed? Abstentions?
Seconder.
On 7/25/09 11:47 AM, Mark Polesky markpole...@yahoo.com wrote:
Carl Sorensen wrote:
No, Jan was not in favor of it unless it became a standard for
GNU coding. Hence the comment on first making it a standard
(i.e., a GNU standard) and sending a patch to emacs-devel.
The current
In message 20090725.163011.184567355...@gnu.org, Werner LEMBERG
w...@gnu.org writes
Indeed, I just see that @frenchspacing is only used for French and
Japanese (the latter only partially). It should be activated for all
languages except, perhaps, English. Note that I don't care what you
native
Le 25 juil. 09 à 20:19, Mark Polesky a écrit :
So, is there any reason that it's markup? and not ly:markup?.
Ditto with markup-list?.
The ly: prefix was supposed to be used for functions defined in
the C++ part, which markup? and markup-list? are not.
Nicolas
On Sat, Jul 25, 2009 at 11:01:44AM -0700, Mark Polesky wrote:
Kieren MacMillan wrote:
Excellent!
Then I nominate @frenchspacing (i.e., single-spaced sentences)
be used for the English docs, consistent with the overwhelming
majority of modern English typographic style guides and
On 7/25/09 12:01 PM, Mark Polesky markpole...@yahoo.com wrote:
Kieren MacMillan wrote:
Excellent!
Then I nominate @frenchspacing (i.e., single-spaced sentences)
be used for the English docs, consistent with the overwhelming
majority of modern English typographic style guides and
Carl Sorensen wrote:
Two spaces after a full stop allows the emacs sentence detection code to
work properly.
@frenchspacing eliminates the extra space after the full stop at the end of
the sentence.
Aren't we glad we use typesetting software instead of WYSIWYG word
processors? We can
Hi Carl (et al.),
Two spaces after a full stop allows the emacs sentence detection
code to work properly.
@frenchspacing eliminates the extra space after the full stop at
the end of the sentence.
Then it's settled — excellent!
Thanks,
Kieren.
This was never resolved:
http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00434.html
I'm on Windows, and I can see the console with the help of
LilyPondTool. But how do I view console output without a gui?
It's not in the log file.
Anyone?
- Mark
2009/7/24 Werner LEMBERG w...@gnu.org:
I don't object to add it to the font, so please add it as a feature
request.
Here goes: http://code.google.com/p/lilypond/issues/detail?id=822
Regards,
Valentin
___
lilypond-devel mailing list
Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit :
Step 1) Move all Texinfo documentation in user/ and topdocs/ one
directory higher (done in my working tree), in translations too.
Step 2) Update all build and maintenance scripts and the CG.
At the end of this step docs
2009/7/25 Mark Polesky markpole...@yahoo.com:
Thanks, Neil. My editor does confusing things with tabs.
I hate them. Who would object if I just started running
tabs-spaces on the source docs? I think we should have
a strict no-tabs rule. And I'm in good company:
You can run it from the dos cmd prompt. Just do lilypond foobar.ly and it
should work.
Jon
On Sat, Jul 25, 2009 at 2:02 PM, Mark Polesky markpole...@yahoo.com wrote:
This was never resolved:
http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00434.html
I'm on Windows, and I can
http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00417.html
Oh, I haven't played around with make-dynamic-script yet. I guess it's not
necessary to have a pre-defined command for pp and the like,
since it's so easy to add these extreme dynamics as needed. Thanks for
the
Jonathan Kulp wrote:
You can run it from the dos cmd prompt. Just do lilypond
foobar.ly and it should work.
Yes it does... thank you, that helps. But shouldn't the output
be sent to the log file? I wish it were. Does anyone know how
to do that?
Thanks.
- Mark
Indeed, I just see that @frenchspacing is only used for French and
Japanese (the latter only partially). It should be activated for all
languages except, perhaps, English. Note that I don't care what you
native speakers actually decide for English
Excellent! Then I nominate
Then I nominate @frenchspacing (i.e., single-spaced sentences) be
used for the English docs, consistent with the overwhelming
majority of modern English typographic style guides and practice...
Seconder? Opposed? Abstentions?
Don't we want to be following the GNU Coding Standards? They
Le samedi 25 juillet 2009 à 09:58 -0700, Mark Polesky a écrit :
But even in such cases, as long as my tab-width matches the
tab-widths in the source, tabs2spaces should be fine. Is it
correct to say that git (or savannah) translates all tabs to 8
spaces without exception?
Git doesn't
On Sat, Jul 25, 2009 at 09:25:01PM +0200, John Mandereau wrote:
Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit :
Step 1) Move all Texinfo documentation in user/ and topdocs/ one
directory higher (done in my working tree), in translations too.
Step 2) Update all build
On Sat, Jul 25, 2009 at 1:05 PM, Patrick McCartypnor...@gmail.com wrote:
On Sat, Jul 25, 2009 at 09:25:01PM +0200, John Mandereau wrote:
Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit :
Step 1) Move all Texinfo documentation in user/ and topdocs/ one
directory higher (done
2009/7/25 Mark Polesky markpole...@yahoo.com:
In the meantime, I'll wait for someone to verify the
revised patch.
+ (sort
(map symbol-string
(hashq-ref iface-grob-table
On Sat, Jul 25, 2009 at 1:16 PM, Patrick McCartypnor...@gmail.com wrote:
On Sat, Jul 25, 2009 at 1:05 PM, Patrick McCartypnor...@gmail.com wrote:
On Sat, Jul 25, 2009 at 09:25:01PM +0200, John Mandereau wrote:
Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit :
Step 1) Move
2009/7/25 Jonathan Wilkes jancs...@yahoo.com:
There's something in NR 3.5.5 that describes how to control MIDI behavior
for (custom) dynamics. But if I just use make-dynamic-script to print out
ff or z in the score, and I don't use any other dynamics,
it gets softer when the custom
Kieren MacMillan wrote Saturday, July 25, 2009 6:30 PM
Thanks for the reference — for subsequent thread-followers, I also
recommend
http://en.wikipedia.org/wiki/Double-spaced_sentences
Indeed, I just see that @frenchspacing is only used for French
and
Japanese (the latter only partially).
I'm trying to build lilypond after doing a make distclean.
make runs through the creation of the .o and the executable. It finishes
the fonts, then when it starts compiling the snippets it ends with:
make PACKAGE=LILYPOND package=lilypond -C J.S.Bach all make
PACKAGE=LILYPOND package=lilypond
After pulling the latest changes, the contributor guide pdf version is not
building. The html big-page and all other docs are built properly with
their new names. I looked through the build log and can't find any errors
saying why the CG pdf wouldn't get built.
Jon
--
Jonathan Kulp
On 2009/07/24 23:30:00, Patrick McCarty wrote:
On 2009/07/21 18:43:10, joeneeman wrote:
I think it would be helpful if you gave an example or 2 of the sort
of string
you expect to match here. I'm a bit worried also about the fact that
you
require
the attributes to be in a specific order.
It seems as though rietveld wants to send my code-comments and my
reply-to-comments comments in two separate emails. Sorry for the noise.
http://codereview.appspot.com/96083/diff/1015/20
File lily/pango-font.cc (right):
http://codereview.appspot.com/96083/diff/1015/20#newcode354
Line 354: bool
Hi Jon,
On Sat, Jul 25, 2009 at 5:57 PM, Jonathan Kulpjonlancek...@gmail.com wrote:
After pulling the latest changes, the contributor guide pdf version is not
building. The html big-page and all other docs are built properly with
their new names. I looked through the build log and can't find
On Sat, Jul 25, 2009 at 7:03 PM, joenee...@gmail.com wrote:
On 2009/07/24 23:30:00, Patrick McCarty wrote:
The new code uses a generalized regular expression that will match a glyph
element with attributes in any order.
The code is slower now, I think due to the complexity of the new regular
As you're aware, I've been working on a patch for autobeaming.
It affects c++, scheme, and documentation files.
Now I want to apply the patch to master. But the problem is that all of the
documentation files have moved to Documentation/ISOLANG/notation instead of
Documentation/ISOLANG/user
So
49 matches
Mail list logo
