| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | Change Lilypond to LilyPond where it refers to the software | Carl Sorensen | 2016-08-06 | 1 | -2/+2 |
| * | (Optionally) embed ly source files inside generated PDF...By using the new -dembed-source-code command line switch,
users may now include their LilyPond source code in the
generated PDF (using the pdfmark EMBED feature); although
the PDF is not modified in any visible way, embedded .ly
files should appear in viewers that support this feature
(other viewers should degrade gracefully).
This patch adds a new ly:source-files function (with
an optional parser arg) that allows to retrieve the list
of (non distribution-provided) ly files involved in
making the current score.
| Valentin Villenave | 2016-03-07 | 1 | -0/+4 |
| * | Issue 4776/2 Doc: Usage 1.2: update svg default font info...Default svg font-family values are now
'serif' 'sans-serif' and 'monospace'
| Paul Morris | 2016-02-28 | 1 | -11/+12 |
| * | Doc: NR and Usage - improved links for SVG...Issue 4774
Added a few extra words
and an @ref so that users
do not miss some 'extra'
considerations when SVG
is the intended output
file type.
| James Lowe | 2016-02-24 | 1 | -0/+4 |
| * | Doc-es: update Usage/Updating. | Francisco Vila | 2016-02-05 | 1 | -1/+1 |
| * | Doc - Usage: delete spurious LF. | Francisco Vila | 2016-01-30 | 1 | -2/+1 |
| * | Doc-es: update Usage/Running. | Francisco Vila | 2016-01-30 | 1 | -2/+2 |
| * | Doc: Usage - Update svg & svg-woff backend text...Issue 4650
Update explanation so as to
inform the user that they will
need to make sure that the font/
WOFF font file information for
anything other than LP Music glyphs
are not included and need to be
'made available' to the SVG viewer
separately.
| James Lowe | 2015-11-13 | 1 | -33/+39 |
| * | Issue 4605: Doc: Usage - Fix svg backend explanation...This commit fixes svg backend explanation.
| Masamichi Hosoda | 2015-09-23 | 1 | -11/+38 |
| * | Doc: typos in AU/external | Jean-Charles Malahieude | 2015-08-09 | 1 | -2/+2 |
| * | Doc: External.itely - Add lyluatex...Issue 4525
Add reference to lyluatex.
Renamed cumbersome node names
and tidied up some @examples
to make the PDF and HTML doc
output easier to read.
| James Lowe | 2015-08-08 | 1 | -28/+45 |
| * | Doc: Usage - Update section on articulate.ly...Issue 4535
The section on MIDI w/articulate.ly
was out of date. This section
has been updated accordingly,
including an @ref to the
Notation Manual where
it is more fully explained.
Updated the intro para to this
section and includes some
useful @refs.
| James Lowe | 2015-08-08 | 1 | -25/+12 |
| * | Doc: Usage - tidy up of external.itely file...Issue 4536
In preparation for some
work done on this file
I have tried to get some
consistency with regard
to white space / line breaks
between @nodes, @cindex et al
to make the file easier to
follow. Also I have corrected
very obvious errors and excessive
line lengths.
Otherwise this is just a
'tidy up'patch.
| James Lowe | 2015-08-08 | 1 | -50/+60 |
| * | Doc: Usage - OOoLilyPond only works up to v4...Issue 4508
http://lists.gnu.org/archive/
html/lilypond-devel/2015-07/
msg00006.html
The wording is taken from
the same statement in the
'Easier Editing' section
already pushed with commit
dfd1134.
| James Lowe | 2015-07-24 | 1 | -1/+4 |
| * | Docs: remove implicit relative from @lilypond[verbatim]; issue 4371...Remove the lilypond-book feature of 'relative=n' in conjunctin with
'verbatim', so that examples cut-and-paste into user scores.
| Keith OHara | 2015-07-16 | 1 | -4/+4 |
| * | Issue 4442/2: Run scripts/auxiliar/update-with-convert-ly.sh -f 2.19.21...Also converts scm via
find scm -name \*.scm -exec out/bin/convert-ly -en -f 2.19.21 -t 2.19.22 {} +
| David Kastrup | 2015-06-16 | 1 | -2/+2 |
| * | Run scripts/auxiliar/update-with-convert-ly.sh...Afterwards revert all changes in Documentation/snippets/*.ly (thus
retaining Documentation/snippets/new), then run
scripts/auxiliar/makelsr.py, leaving only the files in
Documentation/snippets/new and their versions in Documentation/snippets
converted: if we don't want to retain the automatic conversion rule, we
only want to keep those files which do not get reconverted on reimport.
| David Kastrup | 2015-05-18 | 3 | -33/+33 |
| * | Doc:Usage - Additional info to General Suggestions...Issue 4143
Added suggestion, with example, of using Layout
blocks to separate music and style.
I also took the opportunity to update the text by
removing all personal pronouns and adding some
examples.
Also re-set text to a consistent line length.
| James Lowe | 2015-02-07 | 1 | -43/+84 |
| * | Reduce size of PDF files when inc. in *TeX docs...Issue 4251
This changes the way lilypond uses fonts to draw glyphs.
It avoids to used glyphshow for all emmentaler glyphs and
adds encoding vectors to the emmentaler fonts before they
are used. It also changes the ghostscript parameters used
to generate pdfs from postscript code.
These changes help to reduce pdf file sizes if you include
lilypond snippets in *TeX documents. The pdfs generated by
a patched lilypond and *tex themselves are _much_ bigger,
but if you run ghostscript and pdfsizeopt.py on those
files they implode.
Doc additions to the Usage Manual included:
Added a command line option
--bigpdf / -b, and documented that option in the german
and english versions of usage.pdf .
Internal hyperlinks are fully preserved with current
ghostscript git master.
External hyperlinks (GoToR) _to_ a file processed this
way are broken. Fixing this would require major changes
to ghostscript.
External hyperlinks _from_ a file processed this way to
other pdfs are preserved if the reader program isn't
broken (acroread is not broken in this respect, evince is).
For more details see Ghostscript bug #695747
<http://bugs.ghostscript.com/show_bug.cgi?id=695747#c22>
| Knut Petersen | 2015-01-31 | 1 | -0/+28 |
| * | warning message for unspecified voicing; issue 4255 | Keith OHara | 2015-01-17 | 1 | -4/+5 |
| * | Doc: Clarified how to use clip-systems option...Issue 4219
Improved explanation of how to extract music
fragments in the NR and the corresponding
clip-systems option in Usage.
Added some @cindex and @funindex as well as some
@seealso.
| James Lowe | 2015-01-11 | 1 | -1/+4 |
| * | Doc: usage.itely...correct bad copy&paste: convert -> process
| Jean-Charles Malahieude | 2014-12-30 | 1 | -1/+1 |
| * | Doc: Usage - added more examples for lilypond...Issue 4220
Added example for mass input file processing
including the cmds required for Windows Users.
This was done on the back of Issue 4187 and
the updates to the convert-ly section, also
including similar command examples.
| James Lowe | 2014-12-14 | 1 | -0/+38 |
| * | Doc: Usage - update Convert-ly chapters...Issue 4187
Added some more examples to run convert-ly
for 'mass' conversion. Included windows-specific
cmds as well.
I also took the opportunity (liberty?) to reword
some of the paragraphs, for some awkward syntax,
inconsistent use of phrases and file names and
improve some of the more hard-to-fathom explanations.
| James Lowe | 2014-12-14 | 1 | -76/+137 |
| * | Doc: Issue 3324: Add explanation of clashing note columns warning | Trevor Daniels | 2014-10-30 | 1 | -0/+36 |
| * | Doc: typos in lilypond-book.itely | Jean-Charles Malahieude | 2014-10-26 | 1 | -7/+5 |
| * | Doc: Usage 1.2 - Added note about using wildcards...Issue 4147
Added note about being able to use wildcards with
LilyPond in the 'Standard shell commands' section.
Changed some of the text for Windows and MacOS users,
who may not know what a 'shell' is, to reflect each
OS's own nomenclature for their 'Terminal' applicatoin.
Other minor typo fixes in this section.
| James Lowe | 2014-10-09 | 1 | -18/+25 |
| * | Doc: Usage: Add more explanation for LaTeX environ...Issue 4136
Taken from:
http://lists.gnu.org/archive/html/bug-lilypond/2014-08/msg00047.html
Added paragraph explaining the finer details on how LaTeX handles
environments using \begin{lilypond} ... \end{lilypond}
| James Lowe | 2014-10-02 | 1 | -6/+22 |
| * | Doc: Usage: Added a clarifying paragraph about Error Messages...Issue 3873
Added a clarifying paragraph explaining that (the same)
diagnostics message can occur in multiple places for
(the same) input depending on the type and its context.
| James Lowe | 2014-06-29 | 1 | -0/+7 |
| * | Issue 3950: \relative inside \unfold doesn't cause an extra staff anymore...This is a result of issue 3797. It might be nice to come up with
another example demonstrating undesired implicit context creation, but
this example was rather a bug than a direct consequence of well-defined
but possibly sometimes inconvenient default behaviors.
| David Kastrup | 2014-06-20 | 1 | -24/+0 |
| * | Doc: Point-and-Click has wrong default and ref to SVG added...Issue 3854
Also made sure that references to Point-and-click are consistent
through lily.scm and external.itely (including TexInfo formatting).
Tried to get some consistency with regard to remove @code{} for
PDF, PS and SVG when referring to the file type or viewer.
| James Lowe | 2014-02-23 | 2 | -25/+23 |
| * | Doc: make real destructive code innocuous. | Francisco Vila | 2014-02-12 | 1 | -2/+2 |
| * | Doc: Usage add .vimrc syntax highlighting...Issue 3492
| James Lowe | 2013-12-25 | 1 | -0/+1 |
| * | Doc: Add mention of LibreOffice...Issue 3686
OooLilyPond works for LibreOffice as well as OpenOffice.
| Martin Tarenskeen | 2013-12-16 | 1 | -4/+5 |
| * | Add Changes entry for -dstrokeadjust and "Usage" entry. | David Kastrup | 2013-12-07 | 1 | -0/+11 |
| * | Issue 3675: Make convert-ly -d only ever update on changed files...Previously, it updated unconditionally whenever a new stable version
came out, leading to merge conflicts. When the final applied
conversion is to an unstable version and the following stable version
is not beyond the conversion target, the following stable version is
used.
Note that this rule does not make a factual difference for continuous
updates of a code base (the normal use case for
scripts/auxiliar/update-with-convert-ly.sh), but it makes a difference
for the conversion/import of code that may have fallen behind a lot
(like with the LSR import, or when converting archived files).
| David Kastrup | 2013-12-01 | 1 | -2/+5 |
| * | Doc: External.itely - add missing comma...Typo
No tracker issue
| James Lowe | 2013-11-11 | 1 | -1/+1 |
| * | Issue 3572: convert-ly should produce several backup files for each invokation...This supports and documents the -b option for numbered backups. This
was actually written primarily by Eluze.
| David Kastrup | 2013-10-11 | 1 | -1/+7 |
| * | Doc: Remove backslash from all node names and references (3590)... English docs only
| Trevor Daniels | 2013-10-10 | 1 | -3/+3 |
| * | Change option description -x,--long-option to -x, --long-option consistently | David Kastrup | 2013-10-05 | 3 | -28/+28 |
| * | Issue 3584: Let convert-ly -d reflect last effective rather than last applied... | David Kastrup | 2013-10-04 | 1 | -3/+3 |
| * | Issue 3477: Usage manual: convert-ly can only upgrade | David Kastrup | 2013-09-12 | 1 | -5/+30 |
| * | Issue 3537: AU: Correct the description for convert-ly -d | David Kastrup | 2013-09-12 | 1 | -2/+4 |
| * | Documentation fix for compatibility with texinfo 5.1...Patch by Don Armstrong (minus the @top change in changes.tely)
Fixes issue 3382.
http://code.google.com/p/lilypond/issues/detail?id=3382
| Julien Rioux | 2013-07-21 | 1 | -8/+8 |
| * | Doc: Use @dots{} instead of ... in Usage | Jean-Charles Malahieude | 2013-06-20 | 4 | -41/+42 |
| * | Issue 3368: Give additional info about Xpdf versions crashing under Ubuntu | David Kastrup | 2013-05-21 | 1 | -2/+17 |
| * | Issue 3354: Add point-and-click configuration for Evince to documentation...This covers GNOME 2 and GNOME 3 configuration (which may work for
other viewers), and Apparmor configuration for Evince.
It's fascinating how user-friendly today's desktop environments have
become.
| David Kastrup | 2013-05-13 | 1 | -21/+113 |
| * | Doc: Error message: unexpected \new (3285)... Explain reason for the message and what should be
done to avoid it.
| Trevor Daniels | 2013-04-17 | 1 | -0/+51 |
| * | Issue 3244: Remove -d old-relative compatibility option...This removes the lily_1_8_relative variable and the code surrounding
it. lily_1_8_relative_used apparently was unused; Scheme code for
interpreting its setting was not connected to the actual variable.
The callback for repeat-music was not actually being used and has been
removed. While the command line option was still documented, it was
ineffective: only reenabling it in the file itself lead to any effect.
ly:relative-music::relative-callback and
ly:relative-music::no-relative-callback are now functionally
equivalent.
| David Kastrup | 2013-03-21 | 1 | -5/+0 |
| * | Run scripts/auxiliar/update-with-convert-ly.sh | David Kastrup | 2013-01-25 | 1 | -3/+3 |
