On Wed, 2 Jul 2003 17:58:05 +0100, Richard Robinson
[EMAIL PROTECTED] wrote:
[snip]
I thought %%MIDI: was a very nice starting point. Maybe it's too late for
an equivalent %%TYPESETTING: ?
abcm2ps accepts '%%fmt', as suggested by someone a long time ago.
--
Ken ar c'hentañ |
Thinking about abc and applications:
1. Some apps are abc-oriented and deal only with that format.
2. Others like mine will consider it an extra.
For the writers of type 1 apps, having a committee defining the
standard may be frustrating - even if they're on the committee :-)
They'll need new
David Webber wrote:
appname:info;
would allow people to go beyond the standard in a way in which other
apps could ignore. (Or pick up.) The rule would simply have to be
that if such elements are omitted, the remaining music has to obey
the standard and make sense.
For this kind of in-line
In message [EMAIL PROTECTED], David Webber
[EMAIL PROTECTED] writes
Thinking about abc and applications:
1. Some apps are abc-oriented and deal only with that format.
2. Others like mine will consider it an extra.
For the writers of type 1 apps, having a committee defining the
standard may be
On Wed, 2 Jul 2003, David Webber wrote:
The %%mozart: would indicate that this is information
for mozart only and the following stuff would be
interpreted by MOZART to say this is for an A4 page
with a five line stave 23 points high.
That's not a bad idea, but an ever better idea is to
Bernard == Bernard Hill [EMAIL PROTECTED] writes:
Bernard Maybe we need a register of accepted application names/codes.
There is one on the sourceforge ABC site. It seems to be down at the
moment, so I can't post an exact URL.
I want to echo some comments made by other members of the
Laura == Laura Conrad [EMAIL PROTECTED] writes:
Laura There is one on the sourceforge ABC site. It seems to be
Laura down at the moment, so I can't post an exact URL.
It's back up:
From: Bert Van Vreckem [EMAIL PROTECTED]
For this kind of in-line stuff, maybe you could use the
established !!
notation: !appname:info!
Thanks to everyone who pointed this out.
I must admit to having been under the impression that the !..!
elements were supposed to be more or less standard
On Wed, Jul 02, 2003 at 04:34:24PM +0200, Bert Van Vreckem wrote:
David Webber wrote:
appname:info;
would allow people to go beyond the standard in a way in which other
apps could ignore. (Or pick up.) The rule would simply have to be
that if such elements are omitted, the remaining
| David Webber wrote:
| appname:info;
|
| would allow people to go beyond the standard in a way in which other
| apps could ignore. (Or pick up.) The rule would simply have to be
| that if such elements are omitted, the remaining music has to obey
| the standard and make sense.
|
| For
On Wed, 2 Jul 2003, Laura Conrad wrote:
I do hope that the new effort won't completely ignore the work from
the old effort.
So where can we read the draft standard that you
prepared?
Irwin
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
On Wed, 2 Jul 2003, John Chambers wrote:
An alternative, of course, is that we also have the
[...:...] notation. So in addition to things like
[K:Gm] and [K:clef=alto], we could say
[mozart:something].
I prefer to keep this [...] notation for inline header
fields, and to use !...! for inline
From: Richard Robinson [EMAIL PROTECTED]
Or, would an inline header [%%appname:info] do it ?
Again I thought that [ ] was for in-lining established commands lime
M: and K. So either [] or !! would do as long as there were a
legal way to define app-specific (or user-specific) info within
In message [EMAIL PROTECTED], Laura Conrad
[EMAIL PROTECTED] writes
Bernard == Bernard Hill [EMAIL PROTECTED] writes:
Bernard Maybe we need a register of accepted application names/codes.
There is one on the sourceforge ABC site. It seems to be down at the
moment, so I can't post an exact
14 matches
Mail list logo
