On 15/08/17 20:55, Francisco Vila wrote:
> All in all, one of the most usefulness of LilyPond is completely lost,
> which is to make beautifully typeset music automatically from a terse,
> meaningful symbolic language.
>
It must be said, however, that a blind Spanish user today told me that
somethi
On 15/08/17 20:25, Jacques Menu Muzhic wrote:
> Hello Francisco,
>
>> - The converted code has \stemUp and \stemDown in every single note,
>> which had to be searched and replaced. Also all articulations are
>> forced up or down.
>
> Don’t know why musicxml2ly recently enforced such behavior, with
Hello Francisco,
> - The converted code has \stemUp and \stemDown in every single note, which
> had to be searched and replaced. Also all articulations are forced up or
> down.
Don’t know why musicxml2ly recently enforced such behavior, without any option
to prevent it.
The same holds for \po
On 15/08/17 15:01, Richard Shann wrote:
> I agree with this advice, which is why Denemo's MusicXML is still so
> primitive. It has a few hiccups but it ignores most of what is not the
> the music per se but is instead decisions about how the music should
> look. I think LilyPond would be well serve
On Tue, 2017-08-15 at 13:25 +0200, Francisco Vila wrote:
> From my work on Daahoud Salim's sextet, I can tell to those interested
> some things to do and some not to. Today I am focusing on the XML
> import alone.
>
> Long story short: avoid it.
[...]
>
> My advice to all copyists is: unless you
>From my work on Daahoud Salim's sextet, I can tell to those interested
some things to do and some not to. Today I am focusing on the XML import
alone.
Long story short: avoid it.
This is a very small piece when compared to dozens of huge works we all
in the list have seen on the years, but it is
