[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: preliminary GLISS discussions
From: |
Graham Percival |
Subject: |
Re: preliminary GLISS discussions |
Date: |
Sat, 1 Sep 2012 12:40:40 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sat, Sep 01, 2012 at 01:27:23PM +0200, David Kastrup wrote:
> 172 ~ 188 is an abomination anyway. It would be reasonably
> straightforward to accept a pair here, like #(172 . 188) or
> 172/188 which is equivalent.
Straightforward from a programming perspective, but as far as
printed music is concerned, a tempo range doesn't look anything
like 172/188. I'm not wild about the scheme range #(172. 188)
either.
Hmm, I wonder if we could steal a page from LaTeX and use
172 -- 188
to indicate a range? of course then we might run into problems
with people writing
172 - 188
so it's not a foolproof solution.
- Graham
- Re: preliminary GLISS discussions, Jan Nieuwenhuizen, 2012/09/01
- Re: preliminary GLISS discussions, Graham Percival, 2012/09/01
- Re: preliminary GLISS discussions, David Kastrup, 2012/09/01
- Re: preliminary GLISS discussions, Han-Wen Nienhuys, 2012/09/01
- Re: preliminary GLISS discussions, David Kastrup, 2012/09/01
- Re: preliminary GLISS discussions, Han-Wen Nienhuys, 2012/09/01
- Re: preliminary GLISS discussions, David Kastrup, 2012/09/01
- Re: preliminary GLISS discussions, Keith OHara, 2012/09/01
- Re: preliminary GLISS discussions, Han-Wen Nienhuys, 2012/09/01
- Re: preliminary GLISS discussions, David Kastrup, 2012/09/01
- Re: preliminary GLISS discussions, David Kastrup, 2012/09/01
Re: preliminary GLISS discussions, Trevor Daniels, 2012/09/01