[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: Export to XML
From:       Jean Abou Samra <jean () abou-samra ! fr>
Date:       2022-08-30 16:19:11
Message-ID: 8930f41f-0b9a-0643-edcc-3c78cf3e4766 () abou-samra ! fr
[Download RAW message or body]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="monospace">Le 30/08/2022 Ã  12:55, <a \
class="moz-txt-link-abbreviated" \
href="mailto:nitram45@posteo.net">nitram45@posteo.net</a> a  écrit  :<br>
    </font>
    <blockquote type="cite"
      cite="mid:20220830105529.r6pfyx75n2ttuyia@HP-DV7.localdomain">
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">A MusicXML export integrated into LilyPond \
has been discussed repeatedly, and everybody agrees that it is desirable, but it has \
not been implemented so far because, well, it's quite easier said than done. In a \
free (libre) / open source project, the only way to be sure something will get done
is to do it yourself.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
I didn't want to sound like complaining! I understand it should be a lot of
work to provide. I wasn't sure it was not implemented for technical or ethical
reasons.
</pre>
    </blockquote>
    <font face="monospace"><br>
      <br>
      I understand. I would say it is unimplemented not for ethical
      reasons,<br>
      nor even for technical reasons, but simply resource reasons —
      unlike most<br>
      of the other problems that are discussed frequently (grace
      synchronization,<br>
      cross-voice spanners), it isn't made hard by the way LilyPond is
      designed,<br>
      it's just a big chunk of work that needs people with all of time,<br>
      motivation and competence to tackle it.<br>
      <br>
    </font>
  </body>
</html>


[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic