Patrick Schmidt [Fri, 7 Oct 2011 02:32:46 +0000 (20:32 -0600)]
musicxml2ly: title and subtitle (issue 1913), miscellaneous
musicxml2ly: titles (fixes issue 1913), tagline, conversion-info, <source>,
midi-cmd-line-option, center-column long instrument names
1) if XML: <work-title>bli</work-title> AND <movement-title>bla
</movement-title> --> LilyPond: title = bla subtitle = bli
2) the tagline of a piece engraved by LilyPond should not contain any
information as to the encoding software of the .xml file. The standard
Lilypond-tagline should be used.
3) the conversion info should contain the name of the conversion tool
4) the <source>-element is converted to a custom LilyPond-variable
named "source" in the header. (it is usually used for publishing
information)
5) a command line option for a midi block was added
6) multi-lined instrument names are now typeset in center-columns
7) the <miscellaneous>-element is currently translated into a header-
variable "texidoc" which is important for the documentation. I'd suggest
to call it "miscellaneous" by default and call it "texinfo" when
activated via a command line option. (Not implemented yet)
MIDI volume can exceed maximum value (fix 1938)
make Dynamic performer respect midiMinimumVolume
and midiMaximumVolume, also with (de)crescendi
which aren't terminated by absolute dynamic mark.
Mike Solomon [Wed, 5 Oct 2011 07:56:40 +0000 (09:56 +0200)]
Moves all functions related to the `position' property of beam to beam-quanting.cc.
This cosmetic fix is the second step towards consistent slopes after the
renaming of variables in beam-quanting.cc, allowing reviewers to see
the diffs between functions in this file alone.
Mike Solomon [Sat, 1 Oct 2011 18:05:12 +0000 (20:05 +0200)]
Fixes the reading of the positions property in tuplet-number.cc.
Positions can theoretically be "empty" if the left is higher than
the right. Thus, to find its center, we don't use the interval
center function and instead find the center manually.
Mike Solomon [Sat, 1 Oct 2011 14:40:28 +0000 (16:40 +0200)]
Improves horizontal spacing of vertical axis groups that span bars traverse.
Fixes issue 1846.
This patch introduces the idea of a pure-from-neighbor-interface.
The interface provides support for grobs whose pure height is difficult
to estimate (any grob that crosses staffs likely suffers from this)
by allowing for the creation of spacing "stubs" in the crossed
vertical axis groups. These stubs take their pure heights from their
neighbors. So long as one knows that a grob fully crosses a vertical
axis group and the grob should take up the full vertical space of this
axis group for its rank, using approximations of pure height's from the
grob's neighbors ensures that it will be as tall as the rest of the
axis group without triggering a vertical alignment.
Initially I intended to write about the LILYPOND_LOGLEVEL
and LILYPOND_BOOK_LOGLEVEL environment variables there, but
then changed my mind and documented them directly with the
--loglevel and --lily-loglevel options.
Mike Solomon [Thu, 29 Sep 2011 09:50:32 +0000 (11:50 +0200)]
Adds convert-ly rules for the Flag grob.
All Stem properties that are moved to Flag are now changed to Flag
properties. Additionally, Stem grobs' being overriden and reverted
to and from transparent triggers the same overrides and reverts with
Flags.
Fix 1477: Update regtests to suppress expected warnings
If a file contains (ly:expect-warning ....), the corresponding warning
string will be added to a list of expected warnings. If the corresponding
warning (or erro) is triggered, it will not be printed to stderr, but the
string will be removed from the list. So, each ly:expect-warning, suppresses
exactly one occurrence of the warning. To suppress a warning multiple times,
call ly:expect-warning multiple times.
After one file is processed, the list of expected warnings is checked.
If it is not empty, it means that an expected warning was not triggered,
which might be a bug. So we print out a warning message about this fact.
This allows the regtests to check proper warning messages, without
polluting the console output with those warning messages.
All warnings that are actually printed in the regtests are a bug.
For translated error message, there are two approaches: If the warning
is created from scheme, simply use
(ly:expect-warning (_ "msg with ~a") "args")
If the message is triggered from C++, the translated string is in printf
syntax, so we need to translate that and then convert it into a format
string for Scheme. This can be done with the new function
ly:translate-cpp-warning-scheme instead of _:
(ly:expect-warning (ly:translate-cpp-warning-scheme "msg with %s") "args")
This patch also adapts all regtests that are supposed to print warnings
to this new approach. After this patch is applied, the only warnings/errors
that are printed out by a regtest run are warnings/errors that should
NOT be there (with the exception of warn-expected-warning-missing.ly and
safe.ly).
Fix 1477: Add (ly:expect-warning msg args) to suppress expected warnings
If a file contains (ly:expect-warning ....), the corresponding warning
string will be added to a list of expected warnings. If the corresponding
warning (or erro) is triggered, it will not be printed to stderr, but the
string will be removed from the list. So, each ly:expect-warning, suppresses
exactly one occurrence of the warning. To suppress a warning multiple times,
call ly:expect-warning multiple times.
After one file is processed, the list of expected warnings is checked.
If it is not empty, it means that an expected warning was not triggered,
which might be a bug. So we print out a warning message about this fact.
This allows the regtests to check proper warning messages, without
polluting the console output with those warning messages.
All warnings that are actually printed in the regtests are a bug.
For translated error message, there are two approaches: If the warning
is created from scheme, simply use
(ly:expect-warning (_ "msg with ~a") "args")
If the message is triggered from C++, the translated string is in printf
syntax, so we need to translate that and then convert it into a format
string for Scheme. This can be done with the new function
ly:translate-cpp-warning-scheme instead of _:
(ly:expect-warning (ly:translate-cpp-warning-scheme "msg with %s") "args")
This patch does not yet adapt all regtests that are supposed to print warnings
to this new approach. This will follow in a separate patch.
* A list of ASCII aliases for special characters has been added.
* New add-text-replacements! command for \paper blocks.
* New markup command \replace.
James Lowe [Thu, 15 Sep 2011 21:44:42 +0000 (22:44 +0100)]
Doc: NR Clarify finer point of repeat unfold
This is for tracker issue 1801.
Explain as an example, that \repeat unfold 2 {music expression} is
not always the same as writing out the music expression twice - especially
in a \relative context.
Message-handling: Make the Input class use the functions in warn.cc
This allows us to handle all warnings/error really similar in warn.cc.
For example, we can then simply suppress some warnings by only checking
in warn.cc. This patch makes the whole handling much more consistent,
as now everything is in warn.cc
David Kastrup [Wed, 21 Sep 2011 21:38:10 +0000 (23:38 +0200)]
Parts from the optional music argument patch to make define-event-function work
Note that define-event-function, define-scheme-function and define-music-function
now wrongly claim to support optional music function arguments in their
documentation strings, in order not to complicate merging.
Mike Solomon [Thu, 22 Sep 2011 08:12:40 +0000 (10:12 +0200)]
Terminates Slur::outside_staff_callback early if grob is out of slur's range.
This reduces the chance that there will be a programming error when looking
for a Bezier intersection, as grobs that no longer intersect with the slur
will not be considered for shifting.
Mike Solomon [Thu, 22 Sep 2011 07:05:58 +0000 (09:05 +0200)]
Fixes Issue 1301 (colliding note and clef).
Loose columns are now:
-) better spaced between their fixed counterpoints
see spacing-loose-columns.cc
-) spaced with respect to the left column against which they collide,
not the column directly to the left.
see spacing-determine-loose-columns.cc
projects / lilypond.git / log