| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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 .
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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 _.
|
| |
|
|
|
|
|
| |
and classes to it from musicxml2ly.py that are also used in
musicxml.py.
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts resolved in:
python/musicexp.py
python/musicxml.py
scripts/musicxml2ly.py
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 ...
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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 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.
|
| |
| |
| |
| | |
since the Philomelos version was split off.
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
version of musicxml2ly.
|
| |
| |
| |
| | |
In musicxml2ly.py store the LilyPond version in one variable, lilypond_version.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
changes made directly in the LilyPond repository. Those changes will be
reintroduced subsequently.
|
|/ |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit 8c769fc52f092210a21288e81d008dc3f700a626.
|
| |
|
|
|
|
| |
This mostly concerns expression arguments, particularly Scheme expressions.
|
|
|
|
| |
This reverts commit 94644b3a701073c99eabb88d95b20cd3f3ac5af0.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
Issue 4347
Set CFLAGS and LDFLAGS to build python modules
cygwin and mingw need LDFLAGS for building python modules
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Change property name
Change description
Add convert-ly rule
Update all language docs
|
|
|
|
|
|
| |
xxx.yyy.zzz ="
This reverts commit 7f34e80b8d8bebfa4b1f3721a12718b04d7e02f4.
|
|
|
|
|
|
| |
Alist assignments can also use symbol list syntax as of issue 3748.
So the examples for nested layout variable assignments should actually
use those.
|
| |
|