>> The syntax being discussed is nothing but a way of saying,
>> "this accidental isn't really necessary."
> No, it's a way of saying "If you're a printer program, print this with
> parentheses around the sharp". "This accidental isn't necessary" is
> one of the things we use parentheses to indi
> "John" == John Atchley <[EMAIL PROTECTED]> writes:
John> How do you figure that is going to "clutter up the clef with
John> unnecessary accidentals whether they're needed or not???"
I was thinking you were going to parse ABC notes without accidentals
if someone said they wanted cau
On Thu, 16 Nov 2000, Laura Conrad wrote:
> > "John" == John Atchley <[EMAIL PROTECTED]> writes:
>
> John> Just in case I got too wordy and unclear in my other
> John> response here's a bit of pseudo-code:
>
> John> if (accidental_in_abc_source is musically_necessary) {
> Joh
John A.,
I agree with you 100% that cautionary accidentals can and should be handled
by the typesetting program, NOT with special syntax in the ABC music
file. I took the liberty to rewrite your pseudo code. IMO, if the user
specifies an unnecessary accidental, then the typesetter should sho
> "John" == John Atchley <[EMAIL PROTECTED]> writes:
John> Just in case I got too wordy and unclear in my other
John> response here's a bit of pseudo-code:
John> if (accidental_in_abc_source is musically_necessary) {
John> unconditionally display accidental
John> }
> "John" == John Atchley <[EMAIL PROTECTED]> writes:
>> The (^) syntax is precisely a method for the person who wants to print
>> a sharp in parentheses to specify this. Whether the sharp is one that
>> the program would figure out to add or not. What's your idea for how
>>
On Thu, 16 Nov 2000, Laura Conrad wrote:
> The (^) syntax is precisely a method for the person who wants to print
> a sharp in parentheses to specify this. Whether the sharp is one that
> the program would figure out to add or not. What's your idea for how
> to get this?
Just in case I got too
On Thu, 16 Nov 2000, Laura Conrad wrote:
> Either I don't understand what you're proposing, or you aren't talking
> about the same thing as the rest of us. How do you let the person
> printing the score control what accidentals are printed without
> providing a syntax for doing so?
>
> The (^)
On Thu, 16 Nov 2000, Phil Taylor wrote:
> It's a lovely idea, but it gets awfully complicated when you think
> about it. What would the output of such a parser be? Some programs want
> to make a picture of the staff notation, and would therefore want
> postscript, gif or something of that ilk.
Phil Taylor <[EMAIL PROTECTED]> wrote:
>The early music people need a different convention, where accidentals
>affect only the note to which they are attached, but I think that behaviour
>should be obtainable via a local switch, and the modern convention should
>be the default.
This seems right.
Let me throw in my support for advisory accidentals in parentheses. It's
clearly intuitive--pretty obvious to someone who's reading abc, even
without looking documentation.
John Chambers' ([EMAIL PROTECTED] Wed, 15 Nov 2000 09:07:45 -0800)
mention of optional slurs and optional chords reminded m
Phil Taylor writes:
| John Henckel wrote:
| > ... Perhaps someone could write a really portable ABC parser and then
| >give away the source code that each developer can just "plug it in" to
| >their ABC tool (abc2midi, abc2abc, abc2ps, abc2win, abc2???,
| >etc...) There's no sense in everyone re
John Henckel wrote:
>It's true that when the new ABC standard become approved (I say, hopefully)
>then a lot of software will need to be rewritten to handle the new file
>format. Perhaps someone could write a really portable ABC parser and then
>give away the source code that each developer can j
> "John" == John Atchley <[EMAIL PROTECTED]> writes:
John> On Wed, 15 Nov 2000, John Henckel wrote:
>> At 09:33 AM 11/15/2000 +, Phil wrote:
>> >Seems reasonable, although just putting the accidental in a paren would
>> >be more intuitive: (^)C etc. Harder to code though,
It's true that when the new ABC standard become approved (I say, hopefully)
then a lot of software will need to be rewritten to handle the new file
format. Perhaps someone could write a really portable ABC parser and then
give away the source code that each developer can just "plug it in" to
Hi music friends!
Recently, there was a discussinon here on the free Finale NotePad
encoder/decoder from Cora. On november 13.th Cora published free plug-in
docoders for MUS files, embedded is Web-pages, received with Netscape
Communicator and Internet Explorer browsers for Windows. (Mac version
16 matches
Mail list logo
