Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!xlned.com!feeder7.xlned.com!newsfeed.xs4all.nl!newsfeed1a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <8b4fd4f8-f626-4b0d-8bda-6b6813ca7403@googlegroups.com>
References: <9daf0806-02de-4447-964c-c8f8953c23e5@googlegroups.com> <10101874-2995-4acd-9851-989603f052e3@googlegroups.com> <bd158c7b-5511-472c-bce3-cc7b6b7747f6@googlegroups.com> <e2b2b9d5-56bd-4455-b8c3-205000d9acb3@googlegroups.com> <mailman.8369.1395437459.18130.python-list@python.org> <a0403642-c384-4623-bbfd-77c48285ec96@googlegroups.com> <mailman.8377.1395456097.18130.python-list@python.org> <dcd72881-7ee2-4bc3-90ab-7912b4bea05b@googlegroups.com> <lgj4sp$7ed$1@speranza.aioe.org> <532d5bd9$0$29994$c3e8da3$5496439d@news.astraweb.com> <lgoh7j$otg$1@speranza.aioe.org> <mailman.8440.1395651801.18130.python-list@python.org> <lgq8th$nj4$1@speranza.aioe.org> <mailman.8472.1395705541.18130.python-list@python.org> <0b78649a-16b3-4410-8258-e859578d62be@googlegroups.com> <mailman.8483.1395717465.18130.python-list@python.org> <a434e0d3-b2e1-400d-a9a2-ac35493c2c4a@googlegroups.com> <mailman.8486.1395719831.18130.python-list@python.org> <53311887$0$2756$c3e8da3$76491128@news.astraweb.com> <8b4fd4f8-f626-4b0d-8bda-6b6813ca7403@googlegroups.com>
Date: Tue, 25 Mar 2014 17:33:24 +1100
Subject: Re: Time we switched to unicode? (was Explanation of this Python language feature?)
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.8500.1395729208.18130.python-list@python.org>
Lines: 42
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:68981

On Tue, Mar 25, 2014 at 5:10 PM, Rustom Mody <rustompmody@gmail.com> wrote:
> Something that Chris may relate to:
>
> You type a music score into lilypond
> Then call lilypond to convert it into standard western staff notation
>
> Why not put up the lilypond (ASCII) directly on the piano/organ when you =
play?
>
> This is far from rhetorical... ABC,Guido,etc (not python's!) have some
> claim to be *musically* (not just textually) readable and easier to
> master than standard staff notation
>
> Still for someone
> - used to staff notation
> - under the standard presumptions of western music:
>   -- harmony
>   -- spelling c# =E2=89=A0 d=E2=99=AD
>   -- a note is a note ie C to D is as much a note as D to E
>
> staff notation is hard to beat

I wouldn't say it's hard to beat... I happily beat time while looking
at staff notation!

(Of course, I shouldn't beat time. He doesn't like that.)

Staff notation isn't perfect by any means (and there've been various
projects to improve on it), but it's a lot better than the "source
code" form in Lilypond. This is partly because my source code tends to
look at multiple (often four) separate lines of harmony, often plus a
separate line of chords, but when I'm playing, I want to be able to
eyeball all of it at once.

But I've used WYSIWYG notation editors plenty, and *for note entry*
they offer me nothing above Lilypond's notation. I don't yearn to be
able to scribble notes on a paper staff, scan it in, and have that
functional. I don't look back with longing at NoteWorthy Composer (for
which I do own a license, and could probably hunt down the install CD
if I tried). There's a huge difference between the two.

ChrisA