Am 21.04.2013 08:14, schrieb Evan Driscoll:
(I couldn't find something that presented version control the way I
wanted to show it, so I wrote a description. In the unlikely event you
want to steal portions of it, feel free; I can drop a creative commons
license on
Am 21.04.2013 14:31, schrieb Denis Bitouzé:
Hi,
looks very nice though I currently have no time to read it carefully.
Just two remarks:
1. A table of contents would be nice.
This is on my todo-list. It's not a regular table of contents but one
for a subpart of the whole document (which
Urs Liska u...@openlilylib.org writes:
... for some reason XeLaTeX/fontspec isn't
willing to use the bold version of my chosen tt font (Inconsolata) -
so the listings were without syntax highlighting.
I have already done a workaround (by using the default tt font).
Inconsolata originally
David Kastrup writes:
Ask Wilbert about the LyBoek project...
Is that a work title?
Yes.
The official title is Liedboek, as in URL:http://www.liedboek.nl/
Indeed.
An exposition of the project logistics would be interesting, yes.
Yes, there are plans for a writeup of the project.
Jan
Hi David,
please let me take most of your comment as acknowledged and allow me one
further inquiry:
Am Montag, den 22.04.2013, 12:30 +0200 schrieb David Kastrup:
Urs Liska li...@ursliska.de writes:
Am Montag, den 22.04.2013, 11:41 +0200 schrieb David Kastrup:
Urs Liska li...@ursliska.de
Hi,
On Mon, Apr 22, 2013 at 12:00 PM, Urs Liska li...@ursliska.de wrote:
Am Montag, den 22.04.2013, 11:41 +0200 schrieb David Kastrup:
Uh, are we still talking about LilyPond?
Maybe I wasn't clear enough, and maybe this should actually have been
written in a private email.
I'm not refering
2013/4/22 David Kastrup d...@gnu.org:
Urs Liska li...@ursliska.de writes:
Am Montag, den 22.04.2013, 11:41 +0200 schrieb David Kastrup:
Urs Liska li...@ursliska.de writes:
[...] MusicXML [...]
indeed.
;)
I'd actually say it is crucial to have that in order to get LilyPond a
foot
Christ van Willegen cvwille...@gmail.com writes:
On Mon, Apr 22, 2013 at 12:00 PM, Urs Liska li...@ursliska.de wrote:
Am Montag, den 22.04.2013, 11:41 +0200 schrieb David Kastrup:
Uh, are we still talking about LilyPond?
Maybe I wasn't clear enough, and maybe this should actually have been
Janek Warchoł janek.lilyp...@gmail.com writes:
2013/4/22 David Kastrup d...@gnu.org:
Reality check.
_Nobody_ is writing a single line of code related to MusicXML.
Nobody is trying to see how much work it would be to consolidate some
of the MusicXML work from the Philomelos guys back into
Urs Liska li...@ursliska.de writes:
please let me take most of your comment as acknowledged and allow me one
further inquiry:
Am Montag, den 22.04.2013, 12:30 +0200 schrieb David Kastrup:
Reality check.
...
So moving LilyPond into a strategic position is more than just
vigorously
2013/4/23 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com writes:
Technically speaking, you are 100% correct. I agree that talking
doesn't get the job done, and i understand the frustration when
someone reminds you about an issue that you remember very well but
don't have
Janek Warchoł janek.lilyp...@gmail.com writes:
2013/4/23 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com writes:
Technically speaking, you are 100% correct. I agree that talking
doesn't get the job done, and i understand the frustration when
someone reminds you about an
2013/4/23 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com writes:
2013/4/23 David Kastrup d...@gnu.org:
But what word are we spreading? Can it work with our existing
scores and data, possibly through MusicXML? No, but if it could,
it would likely be the best at it.
Am Dienstag, den 23.04.2013, 13:45 +0200 schrieb David Kastrup:
Selling LilyPond with vaporware MusicXML makes only sense if we want
to
hook people on LilyPond with the promise that they can take their
scores
into other products eventually.
Yes, of course.
And that promise only makes
Urs Liska u...@openlilylib.org writes:
Am Dienstag, den 23.04.2013, 13:45 +0200 schrieb David Kastrup:
Selling LilyPond with vaporware MusicXML makes only sense if we want
to
hook people on LilyPond with the promise that they can take their
scores
into other products eventually.
Yes, of
David Kastrup writes:
Likely at best halfways. For example, no header is contained in the
hypothetical music output stream. Things like \transpose don't make
it into the music output stream but rather just its results.
Which may be enough for some workflows, but not necessary all. It does
Klaus Föhl klaus.fo...@uni-giessen.de writes:
David Kastrup writes:
Likely at best halfways. For example, no header is contained in the
hypothetical music output stream. Things like \transpose don't make
it into the music output stream but rather just its results.
Which may be enough for
David Kastrup wrote:
Klaus Föhl address@hidden writes:
Cross-referencing to that Frankfurt meeting: one problem described
to have happened at one point was that midi had turned staccato
into brief note -rest -brief note.
Well, that's the fault of the Midi backend. The music stream still has
Hi all,
thank you very much for your feedback.
It is very valuable to me and gave me a lot of ideas to think about -
although I'd claim that the majority of comments mainly push in the same
direction I'd have taken on my own ;-)
I don't have the time to answer individually right now because I'm
Hi,
2013/4/22 Urs Liska li...@ursliska.de:
I'm in a hurry to prepare the material for the oral presentation.
Good luck! If a recording will be available, i'd gladly watch it.
I will leave out as much of the technical details as possible and focus
on an endorsement of what can be done (and
Am Montag, den 22.04.2013, 10:28 +0200 schrieb Janek Warchoł:
Hi,
2013/4/22 Urs Liska li...@ursliska.de:
I'm in a hurry to prepare the material for the oral presentation.
Good luck! If a recording will be available, i'd gladly watch it.
No, surely not in that context.
I will leave
Urs Liska li...@ursliska.de writes:
[...] MusicXML [...]
indeed.
;)
I'd actually say it is crucial to have that in order to get LilyPond a
foot in the publishing world. We can't expect publishing houses to
easily switch their well-tested workflows. And it's hard to convince
editors or
Am Montag, den 22.04.2013, 11:41 +0200 schrieb David Kastrup:
Urs Liska li...@ursliska.de writes:
[...] MusicXML [...]
indeed.
;)
I'd actually say it is crucial to have that in order to get LilyPond a
foot in the publishing world. We can't expect publishing houses to
easily
Urs Liska li...@ursliska.de writes:
Am Montag, den 22.04.2013, 11:41 +0200 schrieb David Kastrup:
Urs Liska li...@ursliska.de writes:
[...] MusicXML [...]
indeed.
;)
I'd actually say it is crucial to have that in order to get LilyPond a
foot in the publishing world. We can't
Urs Liska tippte:
I think the quality of output is less a selling point compared to the
'big players' than the organizational potential inherent in the text format.
As I learned the other week (maybe more in Musikmesse thread),
publishing houses have invested quite some effort in music
looking
Urs,
I've read through most of the document. It looks well-written, technically
speaking. I have a few suggestions to offer:
* Begin with the current reality for most people. You mentioned in this
thread your frustration with Finale. I had the same frustrations when I was
using it at university
Urs Liska edited:
My target audience are people who are involved in writing scores and
text about music (maybe with a slight personal bias on people who
prepare editions), but who still use word processors and wysiwyg
notation programs.
So you mostly cannot count on familiarity with TeX or
On 4/19/2013 4:17 PM, Urs Liska wrote:
What I would prefer being commented on (of course I'll happily consider
*any* comments) is something like:
- Did I miss crucial aspects ('selling points')?
- Will it be (given the mentioned revision) convincing for
'not-yet-converts'?
Would they
Request for feedback on 'lobbying' paper
From: Urs Liska
Subject: Request for feedback on 'lobbying' paper
Date: Fri, 19 Apr 2013 23:17:08 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329
Thunderbird/17.0.5
Hi,
I like the tone of the paper, but I think it might be a bit
Hi,
looks very nice though I currently have no time to read it carefully.
Just two remarks:
1. A table of contents would be nice.
2. I guess listings are typeset thanks to the listings LaTeX
package. IMHO, such listings are much more readable with monospace
characters (such as the ones
Peter Wannemacher pe...@scriptureoftheweek.com writes:
Request for feedback on 'lobbying' paper
From: Urs Liska
Subject: Request for feedback on 'lobbying' paper
Date: Fri, 19 Apr 2013 23:17:08 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329
Thunderbird/17.0.5
Hi
Hi,
excellent!!
2013/4/20 Urs Liska li...@ursliska.de:
Of course it isn't fair to keep a judgment in one's heart that is based
on software more than a decade old, but my most prominent recollection
of my work with Finale is:
- Enter some music
- Make corrections:
- Move an object
-
David Kastrup d...@gnu.org writes:
Peter Wannemacher pe...@scriptureoftheweek.com writes:
==
You wrote on page 4:
Editor independent
There isn’t a inseparable unit between editing and processing a docu-
It is common to write:
There isn't an inseparable unit
And not
Urs Liska writes:
Hi,
today I finished the first draft of a paper on a plain text file based
toolchain for writing (about) music. The target audience are people who
regularely author such documents but aren't converted yet to 'our'
approach to authoring.
The text doesn't provide
Colin Hall colingh...@gmail.com writes:
Here is a piece of opinion from me, so you know my position. Users of
WYSIWYG engraving software accept the shortcomings because it is quick
and effective. Users of text-based approaches accept the additional
effort required because they are
On Sat, Apr 20, 2013 at 01:05:40PM +0200, David Kastrup wrote:
Colin Hall colingh...@gmail.com writes:
Here is a piece of opinion from me, so you know my position. Users of
WYSIWYG engraving software accept the shortcomings because it is quick
and effective. Users of text-based approaches
Hi Colin,
thanks for your valuable comments!
Am Samstag, den 20.04.2013, 11:50 +0100 schrieb Colin Hall:
Urs Liska writes:
Hi,
today I finished the first draft of a paper on a plain text file based
toolchain for writing (about) music.
...
Your paper reads well and the
Am Samstag, den 20.04.2013, 13:05 +0200 schrieb David Kastrup:
Colin Hall colingh...@gmail.com writes:
Here is a piece of opinion from me, so you know my position. Users of
WYSIWYG engraving software accept the shortcomings because it is quick
and effective. Users of text-based approaches
Am Samstag, den 20.04.2013, 12:13 +0100 schrieb Graham Percival:
On Sat, Apr 20, 2013 at 01:05:40PM +0200, David Kastrup wrote:
Colin Hall colingh...@gmail.com writes:
Here is a piece of opinion from me, so you know my position. Users of
WYSIWYG engraving software accept the
David Kastrup writes:
Colin Hall colingh...@gmail.com writes:
Here is a piece of opinion from me, so you know my position. Users of
WYSIWYG engraving software accept the shortcomings because it is quick
and effective. Users of text-based approaches accept the additional
effort required
Urs Liska writes:
Am Samstag, den 20.04.2013, 11:50 +0100 schrieb Colin Hall:
Can you be more specific about your audience?
This is an important comment because it clearly shows that there is some
work to do.
(Although I assume that with a revision of that first sketch I would
have
Urs Liska writes:
Am Samstag, den 20.04.2013, 12:13 +0100 schrieb Graham Percival:
By contrast, using a text-based tool (especially in conjunction
with source control such as git) leaves me in control. If
anything breaks (which it does occasionally), then I can easily
compare the
Hi,
today I finished the first draft of a paper on a plain text file based
toolchain for writing (about) music. The target audience are people who
regularely author such documents but aren't converted yet to 'our'
approach to authoring.
The text doesn't provide material to 'getting started'
43 matches
Mail list logo
