Hi Daryna,
There is always the possibility to export your work in MuseScore to MusicXML
and import it in Lilypond. The MusicXML export for MuseScore is very
accurate and I believe Reinhold did a very good job with the import. So
certainly something to try out.
Daryna Baikadamova wrote:
Graham Percival wrote Wednesday, August 19, 2009 12:10 AM
On Tue, Aug 18, 2009 at 01:00:10PM +0100, Joseph Wakeling wrote:
Trevor Daniels wrote:
Trevor: the actual table goes in pitches.itely (obviously),
while
we should add a NR 2.9.2 Makam or Turkish or something. I
guess
that
Trevor Daniels wrote:
Alexander Kobel wrote Tuesday, August 18, 2009 8:03 PM
the last sentence in NR 6.8, Difficult tweaks, should probably read
Note, however, that \override, applied to _NonMusicalPaperColumn_ and
PaperColumn, still works as expected within \context blocks.
instead of
Trevor Daniels wrote:
The makam pitches contain 1/9-tone alterations,
so they will not fit into the existing note-name
tables. It will need, as you, Joseph, suggested
a new subsection in 1.1.1. for non-Western pitches.
Let's use that as the heading. The material there
should be restricted
On Tuesday 18 August 2009, John Mandereau wrote:
Le lundi 17 août 2009 à 16:20 -0400, David Raleigh Arnold a écrit :
You do a great job summarizing the minor versions of the development
versions, but there is nothing in news-gmane-lilypond.devel about
stable
minor changes.
The only
Carl Sorensen schrieb:
[...]
Make a simple snippet that shows the problem (you don't need to include the
Staff, just the TabStaff) and send it to bug-lilyp...@gnu.org with a subject
like
Enhancement request: automatic polyphony in TabStaff context
As nobody has added this to the tracker (as
I looked in the nano documentation on how to create a syntax
definition. It said that it was all regex. Then I went to wikipedia
and read how to do regex. That's it really. No searching, or maybe I
misunderstand what you mean.
On 19.08.2009, at 01:25, -Eluze wrote:
James E. Bailey-3
In my text, I write \fbox{a} is ..., but my \fbox{a} isn't spaced
exactly like the box produced by stencil. There are probably many examples
like this. I can live with them, but it could also be improved.
My first instinct is that something like this could be fixed,
although not without a
Carl Sorensen wrote:
You forgot that tabStaff needs tabVoice, and both of your constructs used
Voice contexts, instead of tabVoice contexts.
The first, ... \\ ... , implicitly creates Voice contexts.
The second explicitly creates Voice contexts.
I think you've found a good enhancement
James E. Bailey-3 wrote:
No searching, or maybe I misunderstand what you mean.
i guess you had to apply this regex to a file or files - were these all
lilypond (program-) files or did you go thru the docs or what?
an additional question of course is, if you found *all* lilypond
Mats Bengtsson schrieb:
Carl Sorensen wrote:
You forgot that tabStaff needs tabVoice, and both of your constructs
used
Voice contexts, instead of tabVoice contexts.
The first, ... \\ ... , implicitly creates Voice contexts.
The second explicitly creates Voice contexts.
I think you've
2009/8/19 Marc Hohl m...@hohlart.de:
Carl, do you have any hints where to start such an enhancement?
If you search for `separator' you should find the code which splits
the music into voices. It will have a context-spec-music block which
will need amending to use Bottom rather than Voice to
Mats Bengtsson wrote Wednesday, August 19, 2009 5:15 PM
(see also
http://lists.gnu.org/archive/html/lilypond-user/2005-05/msg00016.html
which exploits an still undocumented feature/bug).
Hhm. This doesn't seem to work with Voice
contexts. If you take the first example in
5.1.3 and comment
Hi Marc,
I actually sent two enhancement requests to bug-lilyp...@gnu.org one week ago
(13 Aug. 2009). I wonder what happened to them. (Enhancement request: automatic
polyphony in TabStaff context; Enhancement request: Automatic glissando marks
in chords). Where can I see what's on the
Robert Keller wrote:
On Jun 11, 2009, at 5:19 AM, Grammostola Rosea wrote:
lasconic wrote:
I took some time yesterday night to take a look to improvisor code and
estimate the cost of adding musicXML export. Import is indeed more
complicated.
I downloaded the code of improvisor 3.39. It's the
Hi,
I'd like to create a command that will create a textual crescendo split
into three parts : cre - - - scen - - - do, with the following properties :
- aligned on dynamic-line (well, like \crescTextCresc) ;
- with the scen part in the middle (X-axis speaking) of cre and
do (that should be
Ah, I understand. nano loads a config file when it starts, so if a
file's extension matches any of the ones defined in the config file,
it then loads the appropriate syntax.
As to what I decided to hilight. That was a completely personal
issue, and since it was my first (and only) attempt
2009/8/19 Alexander Kobel n...@a-kobel.de:
Does fixed in the developement branch also mean it's fixed in the docs for
upcoming releases of the stable branch, too, by the way?
Yes, it was backported a few weeks ago, so should be fixed whenever
2.13.3 gets released.
Regards,
Neil
2009/8/16 Graham Percival gra...@percival-music.ca:
(nobody checks the regression tests for each release, for example
-- and that's trivially done with a web browser!)
As far as I can remember, Stan Sanderson was in charge of the regtest
checking (but perhaps this needs to be updated?).
That
On Wed, Aug 19, 2009 at 10:51:40AM -0400, David Raleigh Arnold wrote:
What I do not understand is how mere bugfixes are irrelevant to the
user of stable releases. Seems to me that fixes are the most important
factors, if not the only factors, in making a choice of *minor* versions
of stable
On Wed, Aug 19, 2009 at 06:04:41PM +0200, denis.roe...@loria.fr wrote:
My first instinct is that something like this could be fixed,
although not without a proper minimal example.
Sorry, I should have posted a minimal example. Here is one:
http://www.loria.fr/~roegel/tmp/test.tex
On 8/19/09 9:46 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
[...]
Make a simple snippet that shows the problem (you don't need to include the
Staff, just the TabStaff) and send it to bug-lilyp...@gnu.org with a subject
like
Enhancement request: automatic polyphony in
22 matches
Mail list logo
