summaryrefslogtreecommitdiff
path: root/python
Commit message (Collapse)AuthorAgeFilesLines
* Issue 4974/2: convert-ly rule: id -> output-attributesPaul Morris2016-10-041-0/+23
| | | | | | Running scripts/auxiliar/update-with-convert-ly.sh with the new rule produced no changes, so there is no separate commit for that step.
* Issue 4914/2: convert-ly rule for removing Output_property_engraverDavid Kastrup2016-07-101-1/+5
| | | | | | | | It's highly unlikely that users will redefine the Score context from scratch, so the convert-ly rule just removes every occurence of Output_property_engraver from user source. Obviously, when running the rule on the LilyPond code base, we will need to fix up the Score engraver manually to retain the Output_property_engraver .
* Issue 4911/2: convert-ly rule to put \with before context modsDavid Kastrup2016-07-101-0/+11
|
* Reimplement issue 4781 for musicxml2ly more literally. ReimplementationJohn Gourlay2016-07-071-13/+8
| | | | | was necessary as part of the implementation of issue 4751, but some of the code changes for 4781 were omitted. This reproduces all the 4781 changes.
* Remove a nonsensical line from the \paper section of ly output.John Gourlay2016-05-261-1/+0
|
* In python/musicexp.py:John Gourlay2016-05-262-2/+8
| | | | | | | In the ly output add a space between a direction modifier and quote. Remove a redundant <<. In python/musicxml2ly_conversion.py: Add a definition for _.
* Import rational in musicxml2ly_conversion.pyJohn Gourlay2016-05-121-0/+1
|
* Resurrect the file musicxml2ly_conversion.py, moving the few functionsJohn Gourlay2016-05-121-0/+51
| | | | | and classes to it from musicxml2ly.py that are also used in musicxml.py.
* Merge branch 'master' into philomelosJohn Gourlay2016-04-293-17/+71
|\ | | | | | | | | | | | | Conflicts resolved in: python/musicexp.py python/musicxml.py scripts/musicxml2ly.py
| * Issue 4811/2: convert-ly rule for nicer beatStructure syntaxDavid Kastrup2016-03-291-0/+17
| |
| * Issue 4803: Amend convert-ly 2.17.6 rules for \tweakDavid Kastrup2016-03-221-2/+2
| | | | | | | | | | | | | | | | | | | | Double application was problematic. Since grob properties start with lowercase letters or X or Y while grob names start with A-W, it can be reliably avoided to do the incorrect double conversion \tweak #'style #'none ... -> \tweak style #'none ... -> \tweak style.none ...
| * Issue 4799: Let musicxml2py generate current override/revert syntaxDavid Kastrup2016-03-191-15/+15
| |
| * Define French as a separate input languageValentin Villenave2016-03-071-0/+6
| | | | | | | | | | | | | | French users now have the ability to enter the D pitch as "ré" instead of Italian-like "re". In addition, the French input language accepts double sharps entered using the -x suffix.
| * Musicxml: Fix musicxml.py for Reg Test 42aTobias Kretschmar2016-03-041-13/+27
| | | | | | | | | | | | | | | | | | | | | | MusicXML regression test 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml is missing the first note in voice 2. Subsequently the lyrics of voice 2 is moved one note to the right.
* | Bring musicxml2ly up to date with changes made in the LilyPond versionJohn Gourlay2016-04-281-1/+1
| | | | | | | | since the Philomelos version was split off.
* | Correct a misplaced << in the body of a TabStaff block.John Gourlay2016-04-191-56/+7
| | | | | | | | | | | | At this point modifications to the Philomelos version of musicxml2ly have made it able to process all of the MusicXML regression tests without errors either from it or from LilyPond processing its output.
* | Convert miscellaneous description elements to texidoc items.John Gourlay2016-03-221-2/+3
| |
* | Remove references to philomelos, which are not appropriate in LilyPond's ownJohn Gourlay2016-03-221-12/+0
| | | | | | | | version of musicxml2ly.
* | In musicexp.py generate "Staff.keyAlterations" rather than "Staff.keySignature".John Gourlay2016-03-151-1/+1
| | | | | | | | In musicxml2ly.py store the LilyPond version in one variable, lilypond_version.
* | Handle LilyPond version better.John Gourlay2016-03-041-2/+2
| |
* | Correct an inconsistency in the Lyric class.John Gourlay2016-03-011-2/+2
| |
* | Add a new file utilities.py.John Gourlay2016-03-011-0/+268
| |
* | Incorporate musicxml2ly_conversion.py into musicxml2ly.py.John Gourlay2016-02-251-3296/+0
| |
* | Copy the lastest musicxml2ly files from Philomelos. These versions overwriteJohn Gourlay2016-02-182-832/+1858
| | | | | | | | | | changes made directly in the LilyPond repository. Those changes will be reintroduced subsequently.
* | Add new file musicxml2ly_conversion.py.John Gourlay2016-01-281-0/+3296
|/
* Issue 4734: Add lilypond-book can use XeTeX backend for auto-detectMasamichi Hosoda2016-01-191-0/+2
| | | | | | | | lilypond-book uses TeX engine for auto-detect default settings. In the case of using XeTeX , the detection did not work. When there is no glyphs, pdfTeX creates PDF. However, XeTeX does not create PDF. Threfore, the detection is failed.
* Issue 4671: convert-ly rule for ly:music-function-extractDavid Kastrup2015-12-071-1/+10
| | | | | | The extracted music function no longer takes parser/location arguments since version 2.19.22. This convert-ly rule caters with the simplest use of ly:music-function-extract, calling one music function from inside another.
* Issue 4504/2 convert-ly rule: whiteout-box --> whiteoutPaul Morris2015-11-111-0/+7
|
* Issue 4131/2: convert-ly rule "partcombine*Once -> \once \partcombine*"David Kastrup2015-10-051-0/+10
|
* Issue 4614/3: convert-ly rule c:5.x, c:5^x, c:sus -> c:3.5.x, c:3.5^x, c:5David Kastrup2015-09-261-0/+11
|
* Issue 4557: Small typos in code baseDavid Kastrup2015-08-201-1/+1
|
* Issue 4507/1: Let \applyOutput take an optional grob specDavid Kastrup2015-07-211-1/+3
|
* Issue 4492: Redundant music-has-type -> music-is-of-type?David Kastrup2015-07-181-0/+6
|
* Issue 4418/3 convert-ly rule: whiteout -> whiteout-boxPaul Morris2015-06-181-1/+10
|
* Issue 4442/1: convert rule: (xxx ... parser ...) -> (xxx ... ...)David Kastrup2015-06-161-2/+57
|
* Issue 4422/4: convert-ly rule for removing parser/locationDavid Kastrup2015-06-021-0/+16
|
* Revert "Some more issue 3229 rules"David Kastrup2015-05-291-55/+0
| | | | This reverts commit 8c769fc52f092210a21288e81d008dc3f700a626.
* Some more issue 3229 rulesDavid Kastrup2015-05-291-0/+55
|
* Improve some patterns/conversions for convert-lyDavid Kastrup2015-05-291-6/+9
| | | | This mostly concerns expression arguments, particularly Scheme expressions.
* Revert "Issue 3229: Prefer \relative { ... } over \relative x'' { ... }"David Kastrup2015-05-181-32/+0
| | | | This reverts commit 94644b3a701073c99eabb88d95b20cd3f3ac5af0.
* Issue 3229: Prefer \relative { ... } over \relative x'' { ... }David Kastrup2015-05-171-0/+32
| | | | | | | | | | | | | | | As a followup to the commits for issue 3245, this conversion rule replaces uses of \relative with reference pitch by those without reference pitch for a number of patterns where convert-ly can detect the first actual note reliably. The rule is prepared to skip over files containing \include or \language with a non-c-using notename language since the patterns do not work for them. However, this part of the rule is disabled in this commit as it turns out that the LilyPond code base converts well (and more thoroughly) without it.
* Issue 4384: Remove convert-ly rule \shiftOff -> \undo\shiftOnDavid Kastrup2015-05-171-1/+0
| | | | | | | | | | | | For the rationale, see <URL:https://codereview.appspot.com/190500043/#msg1> The presence of the rule will cause similarly surprising effects to users as it would to the current state of documentation translations. Even if it were properly mentioned in the diagnostic description of the conversion rule, people would rarely look closely enough to notice.
* Issue 4372: convert-ly misses some bflat -> b-flatDavid Kastrup2015-05-161-1/+14
| | | | | | | | | | In python/convert-rules.py, using '\b' for note name boundaries turns out to be too audacious since bflat4 is one word. A proper solution would be to match the variable wordsyntax and let the match expression use a replacement function that triggers on the right words. However, such a large number of matches would be expensive. So instead we are using positive lookahead and lookbehind expressions to get reasonably good matches.
* Set CFLAGS and LDFLAGS to build python modulesMasamichi Hosoda2015-04-211-1/+2
| | | | | | | | Issue 4347 Set CFLAGS and LDFLAGS to build python modules cygwin and mingw need LDFLAGS for building python modules
* make \shiftOff an assertive \override, not a \revertKeith OHara2015-01-171-0/+1
|
* Run grand replace for 2015.Werner Lemberg2015-01-042-2/+2
|
* Issue 4209: Change notename csharp et al. to c-sharp et al.David Kastrup2014-12-061-1/+3
|
* Issue 4151: implicitTimeSignatureVisibility->initialTimeSignatureVisibilityTrevor Daniels2014-11-031-0/+5
| | | | | | | Change property name Change description Add convert-ly rule Update all language docs
* Revert "Issue 4068: Add a convert-ly rule for xxx #'yyy #'zzz = -> ↵David Kastrup2014-08-241-6/+0
| | | | | | xxx.yyy.zzz =" This reverts commit 7f34e80b8d8bebfa4b1f3721a12718b04d7e02f4.
* Issue 4068: Add a convert-ly rule for xxx #'yyy #'zzz = -> xxx.yyy.zzz =David Kastrup2014-08-241-0/+6
| | | | | | Alist assignments can also use symbol list syntax as of issue 3748. So the examples for nested layout variable assignments should actually use those.
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-21 13:18:08 +0000