On Thu, 2 May 2002, Phil Taylor wrote:
The real problem with abc is that there isn't enough time in a lifetime.
Actually when I think it over, abc's biggest problem is that it's too nice
to let go...
--
love, peace harmony
Atte
To subscribe/unsubscribe, point your browser to:
Jeff Bigler writes:
...is ABC's biggest handicap
which catches the eye so effectively that nobody seems to have gotten
beyond it to comment on his suggestions. Just for the record, here's
something:
In the following example, I'm proposing to be a delimiter for
the following
Not exactly on topic, but anyway:
At 05:13 PM 5/2/02, John Walsh wrote:
you could say that you need a second space to end the beam, but this
works better for parsers than human readers---the difference between
one and two spaces is notoriously hard to spot. (Which pair of words
is
John Chambers wrote:
Out of curiousity: Are there any abc programs currently that will
accept something like ^ffGmG and do the right thing with it? I
know that abc2ps won't; it simply ignores all but the first chord
symbol. This should be fixed, of course, but today it doesn't work in
Am Mittwoch, 1. Mai 2002 15:55 schrieb Atte Andre Jensen:
Really? I think abc's biggest shortcomming is the fundamental of only
being able to put a chord where there is a melody-note. I consider this a
major bummer, and guess everybody (except me) writes stuff like
| A AmC4 |
Not me, I
if your software supports non-printing rests (BarFly, Skink) you can write
| AC4 Amx |
wil
Ulf wrote:
Am Mittwoch, 1. Mai 2002 15:55 schrieb Atte Andre Jensen:
Really? I think abc's biggest shortcomming is the fundamental of only
being able to put a chord where there is a melody-note. I
At 06:35 PM 05-01-2002 +, John Chambers you wrote:
| On the other hand, I still think that the lack of a way to represent
| dynamics and certain other commonly-used symbols is ABC's biggest
| handicap.
We could get into a real debate over what's the most serious handicap
in ABC. My vote
On Wed, 1 May 2002, Wil Macaulay wrote:
if your software supports non-printing rests (BarFly, Skink) you can write
| AC4 Amx |
Hey, that's pretty clever! Although is looks broken (5 notes to a 4/4
bar). And I was pretty amazed the abc2midi actually played it fine (pretty
hip harmonization
On Wed, 1 May 2002, Buddha Buck wrote:
At 06:35 PM 05-01-2002 +, John Chambers you wrote:
It's interesting... in response to Jeff's message, I've seen lots of people
comments on his choice for the title of ABC's biggest handicap, but no
comments on his proposal to fix his particular
Atte writes:
| On Wed, 1 May 2002, Wil Macaulay wrote:
|
| if your software supports non-printing rests (BarFly, Skink) you can write
|
| | AC4 Amx |
|
| Hey, that's pretty clever! Although is looks broken (5 notes to a 4/4
| bar). And I was pretty amazed the abc2midi actually played it fine
Atte wrote:
| On Fri, 26 Apr 2002, John Chambers wrote:
| Atte wrote:
| | !fine! exclamation-point abuse
|
| This reminds me: There has been a bit of discussion of this syntax
| off and on over the years. Some people have implemented it. Could
| people post information on which abc
I fail to see why discussion of new additions/changes to the standard
can abound for an extended period of time, and ultimately be beaten
into astalemate.
I don't quite know what the 'Standard Version Naming Scheme' for abc
is, but I thought the use of a #.# allowed small changes from say, 1.6
Phil, I seem to recall that you had an alternate proposal - can you resurrect it? I'm
almost at the point
of implementing this in Skink, so it would be useful to have the proposals
side-by-side.
wil
Phil Taylor wrote:
John Chambers wrote:
Atte wrote:
| On Fri, 26 Apr 2002, John Chambers
Phil Taylor wrote:
| John Chambers wrote:
| Atte wrote:
| | On Fri, 26 Apr 2002, John Chambers wrote:
| | Atte wrote:
| | | !fine! exclamation-point abuse
| | abcm2ps
| That's the only reply that I've seen. Is this the only abc program
| that understands the !foo! annotation syntax?
John Chambers wrote:
(about the !foo! construct)
Hmm ... I'd forgotten who didn't like it, of course. The general
feature does seem to be inherently useful, so I'd suppose that the
objection is to the particular syntax. The other one I've seen is the
one that uses double quotes and
One thing about macroes, however, is that you don't _have_ to use them;
you can fully expand the macro in the source if you want to for some reason.
Your proposal doesn't fit that need, because if I _want_ to write
fff (for fortissimo) in the tune, I can't distinguish it from three f notes unless
One thing about macroes, however, is that you don't _have_ to use them;
you can fully expand the macro in the source if you want to for some reason.
Your proposal doesn't fit that need, because if I _want_ to write
fff (for fortissimo) in the tune, I can't distinguish it from three f
notes unless
| One thing about macroes, however, is that you don't _have_ to use them;
| you can fully expand the macro in the source if you want to for some reason.
| Your proposal doesn't fit that need, because if I _want_ to write
| fff (for fortissimo) in the tune, I can't distinguish it from three f
Phil Taylor writes:
| One thing about macroes, however, is that you don't _have_ to use them;
| you can fully expand the macro in the source if you want to for some reason.
| Your proposal doesn't fit that need, because if I _want_ to write
| fff (for fortissimo) in the tune, I can't distinguish
Atte wrote:
| !fine! exclamation-point abuse
This reminds me: There has been a bit of discussion of this syntax
off and on over the years. Some people have implemented it. Could
people post information on which abc apps accept this syntax? It'd be
nice to get together a list like
20 matches
Mail list logo
