Re: xml2ly, a new translator from MusicXML to LilyPond

2018-09-03 Thread Menu Jacques
Thanks James for this information, I’m a newbie regarding the way the lilypond-devel people operate. JM > Le 3 sept. 2018 à 12:49, James Lowe a écrit : > > Hello Jaques > > > On 02/09/18 20:33, Menu Jacques wrote: >> Hello James, >> >> >>&g

Re: xml2ly, a new translator from MusicXML to LilyPond

2018-09-02 Thread Menu Jacques
Hello James, > Please also don't forget that it (whatever 'it' is, and assuming it is > accepted) will need to work when run against our regression tests (i.e. make > test-baseline/check). > > http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#musicxml-tests > >

Re: xml2ly, a new translator from MusicXML to LilyPond

2018-09-01 Thread Menu Jacques
Hello Urs, > Maybe the best bet would be to create a small wrapper that uses the library > and can be deployed with LilyPond. Well, actually, xml2ly is such a wrapper. JM ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: xml2ly, a new translator from MusicXML to LilyPond

2018-09-01 Thread Menu Jacques
> Le 1 sept. 2018 à 11:50, Urs Liska a écrit : > > > > Am 1. September 2018 11:37:14 MESZ schrieb Victor Rouanet > : >> Le 01/09/2018 à 10:25, Menu Jacques a écrit : >>> I only have read access to the github issue tracker yet. How can can >> I >>&g

Re: xml2ly, a new translator from MusicXML to LilyPond

2018-09-01 Thread Menu Jacques
09/2018 à 10:25, Menu Jacques a écrit : >> I only have read access to the github issue tracker yet. How can can I get >> working access to it? >> > I guess you have to ask the repository owner to grant you the appropriate > permission, but I don't know github very we

Re: xml2ly, a new translator from MusicXML to LilyPond

2018-09-01 Thread Menu Jacques
Hello Victor, Thanks for your positive feedback and help proposal! I only have read access to the github issue tracker yet. How can can I get working access to it? JM > Le 1 sept. 2018 à 10:19, Victor Rouanet a écrit : > > Good morning, > > thanks a lot for the sharing and well done for

Typo in the Contributor's Guide

2016-01-13 Thread Menu Jacques
Hello folks, ‘sortly’ instead of ‘shortly’. JM -- 14.7 Grand LilyPond Input Syntax Standardization (GLISS) Summary • Start: sortly after 2.14 comes out, which is currently estimated to happen in January 2011. • Length: 6-12 months. We’re not going to rush this.

2.19.31 Notation Reference glitch

2015-12-27 Thread Menu Jacques
Hello folks, Just for your information: at page 715, « π ≈ » is not displayed in: from markup-commands.tely: Make a fraction of two markups. @lilypond[verbatim,quote] \markup { π ≈ \fraction 355 113 } @end lilypond JM ___ lilypond-devel

Re: LilyDev 4.0 first impressions

2015-11-25 Thread Menu Jacques
Hello folks, Forgot to say: I tried to use VirtualBox 5.0.10, but: - I coudn’t manage the bridged network to work, not getting an IPv4 address for any of the interfaces on my machine (Mac OS X 10.11.1); - now and then, the cursor would switch to the 4 arrows one (from X11 I

Re: Missing epfs.tex when trying to build Lilypond

2015-11-24 Thread Menu Jacques
root@lilydev:/# apt list texlive Listing... Done texlive/stable,now 2014.20141024-2 all [installed,automatic] JM > Le 24 nov. 2015 à 13:14, Menu Jacques <imj-...@bluewin.ch> a écrit : > > Hello, > > I’m using LilyDev 4.0 (freshly installed), and following the instructions a

Re: Missing epfs.tex when trying to build Lilypond, solved

2015-11-24 Thread Menu Jacques
My 1€. The following: # add lily-git to the PATH PATH=$LILYPOND_GIT/scripts/auxiliar:"${PATH} » wasn’t at the right place. Sorry for the noise! JM > Le 24 nov. 2015 à 17:18, Menu Jacques <imj-...@bluewin.ch> a écrit : > > It looks to be an environment problem, in whi

LilyDev 4.0 first impressions

2015-11-24 Thread Menu Jacques
Hello folks, I’ve but the app and doc alright. At 4.6.3 Testing LilyPond binary, it is not said in which folder to cd prior to « make test ». Same remarque for 9.3 Compiling regression tests. At 2.3 Compiling with LilyDev, firefox should be replaced by chromium to test the doc. Launching it