Werner LEMBERG wrote:
Uh. Those braces are completely irritating!
The problem is this: in LSR, a user sees this:
The property @code{chordNameExceptions} can used to store a list of
special notations for specific chords.
and he wonders what on earth the @code means.
Mhmm. Why not c
> > Uh. Those braces are completely irritating!
>
> The problem is this: in LSR, a user sees this:
>
> The property @code{chordNameExceptions} can used to store a list of
> special notations for specific chords.
>
>
> and he wonders what on earth the @code means.
Mhmm. Why not creating
Werner LEMBERG wrote:
We're still working on formatting issues -- I tend to send one email
to Sebastiano each day; the latest issue was automatically escaping
@[EMAIL PROTECTED] for the texidoc strings.
Uh. Those braces are completely irritating!
The problem is this: in LSR, a user sees this
Trevor Bača wrote:
OTOH, I really do believe that the reason most
users walk around without a solid model of file structure (or score
structure) in their heads isn't because chapters 3 - 5 (which are
*amazingly* helpful and huge improvement over the previous manual,
which was essentially silent o
> I don't really know how to say this... thank you for cleaning up the
> formatting in input/lsr/... but those files are generated
> automatically from http://lsr.dsi.unimi.it/
:-) No problem.
> We're still working on formatting issues -- I tend to send one email
> to Sebastiano each day; the l
I see this in the git:
@c to get decent French quotes in ``foo''
@macro qq{TEXT}
@html
« \TEXT\ »
@end html
@end macro
shouldn't this be rather
@c to get decent French quotes in ``foo''
@macro qq{TEXT}
@html
« \TEXT\ »
@end html
@end macro
?
Werner
_
All the snippets in input/lsr/ should (in theory) be safe, since they
are generated from LSR, and LSR only accepts snippets if they compile in
--safe. Still, we should have an automatic testing before adding stuff
to GIT, so I don't have to look at the snippets myself all the time.
I can thin
Trevor Bača wrote:
I dunno. I don't wanna type more stuff (explicit \score and \book and
whatever) all the time, but I'm pretty convinced that both file
structure and score structure will remain confusing for new and even
experienced users right up until the point that we do make such a
requireme
On 2/8/07, Graham Percival <[EMAIL PROTECTED]> wrote:
Han-Wen Nienhuys wrote:
> Trevor Bača escreveu:
>> Wow. I really like this. Anyone else?
>
> I don't.
I don't like it either, but for different reasons.
- how do identifiers work? Where do we define them? Does it make sense
for an identifi
> -Original Message-
> From: Carl D. Sorensen
> Sent: Friday, February 09, 2007 7:48 AM
> >
> > independenty of this
> >
> > \book {
> > \score {
> > \layout {
> > %% A
> > }
> > }
> > \paper {
> >%% B
> > }
> >}
> >
> >
> No, top-level \paper sets a default for the \book level \paper.
> top-level \layout sets a default for \score level \layout.
>
> \layout { X }
> \paper { Y }
>
> mean
>
> $defaultlayout = \layout { \$defaultlayout X } $defaultpaper
> = \layout { \$defaultpaper X }
>
> independenty of this
Hi,
On Fri, 9 Feb 2007, Han-Wen Nienhuys wrote:
> Johannes Schindelin escreveu:
>
> > Well, I have seen my share of Python code. And I grew to hate it. It
> > is apparently very easy to write code which looks pretty, but is
> > utterly unreadable. (It does not help that there are white-space
On Fri, Feb 09, 2007 at 12:35:23AM -0800, Graham Percival wrote:
> Hi Werner,
>
> I don't really know how to say this... thank you for cleaning up the
> formatting in input/lsr/... but those files are generated automatically from
> http://lsr.dsi.unimi.it/
>
> We're still working on formatting i
The fix in ff60353aa3cbe1d44a9eb77b7966dfa9f95c8e5f for line-spanners is not
entirely successful. Can you review this?
input/regression/follow-voice-break.ly
shows the problem well enough.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Co
Hi Werner,
I don't really know how to say this... thank you for cleaning up the
formatting in input/lsr/... but those files are generated automatically from
http://lsr.dsi.unimi.it/
We're still working on formatting issues -- I tend to send one email to
Sebastiano each day; the latest issue w
15 matches
Mail list logo
