Re: Errors in examples
David,
2012/2/6 David Kastrup d...@gnu.org:
\layout {
\context {
\Voice
\settingsFrom \voiceOne
}
}
The settingsFrom command looks useful and I vageuly recall you
announced it in the mailing list. However, I don't see it documented
or used in any snippet/example.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: having trouble fetching all remote branches
Janek Warchoł janek.lilyp...@gmail.com writes:
My local repository wasn't created with git clone, and i have only one
remote branch ('origin/master'); i cannot push to staging because of
that. I've tried 'git fetch --all', but the other remote branches do
not appear, and i don't see a solution in git fetch description. Any
help?
A list search... it is not like I have not answered this about once a
month for the last half year. Make sure that your .git/config contains
[remote origin]
fetch = +refs/heads/*:refs/remotes/origin/*
url = ssh://git.sv.gnu.org/srv/git/lilypond.git
Your lines most likely are missing the wildcards. The next git fetch
should bring you up to date.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: having trouble fetching all remote branches
2012/2/7 Janek Warchoł janek.lilyp...@gmail.com:
My local repository wasn't created with git clone, and i have only one
remote branch ('origin/master'); i cannot push to staging because of
that. I've tried 'git fetch --all', but the other remote branches do
not appear, and i don't see a solution in git fetch description. Any
help?
I don't know if this is correct. If not, please say so:
git branch --track staging origin/staging
git checkout staging
(... commits etc)
git push origin staging
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: having trouble fetching all remote branches
Francisco Vila paconet@gmail.com writes:
2012/2/7 Janek Warchoł janek.lilyp...@gmail.com:
My local repository wasn't created with git clone, and i have only one
remote branch ('origin/master'); i cannot push to staging because of
that. I've tried 'git fetch --all', but the other remote branches do
not appear, and i don't see a solution in git fetch description. Any
help?
I don't know if this is correct. If not, please say so:
git branch --track staging origin/staging
Won't work if git does not fetch origin/staging. If you want to do this
via command line rather than just editing .git/config, you will need
some git remote variation. I think I tried about four times to get
this right, and then decided just to post the config file extract.
I am really bad at working with user interfaces. And this is not even a
GUI but the command line.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: having trouble fetching all remote branches
2012/2/7 David Kastrup d...@gnu.org:
Francisco Vila paconet@gmail.com writes:
2012/2/7 Janek Warchoł janek.lilyp...@gmail.com:
My local repository wasn't created with git clone, and i have only one
remote branch ('origin/master'); i cannot push to staging because of
that. I've tried 'git fetch --all', but the other remote branches do
not appear, and i don't see a solution in git fetch description. Any
help?
I don't know if this is correct. If not, please say so:
git branch --track staging origin/staging
Won't work if git does not fetch origin/staging.
Right, it works for me because I have .git/config properly configured.
Thanks
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: having trouble fetching all remote branches
On Tue, Feb 07, 2012 at 08:51:24AM +0100, Janek Warchoł wrote:
My local repository wasn't created with git clone, and i have only one
remote branch ('origin/master'); i cannot push to staging because of
that. I've tried 'git fetch --all', but the other remote branches do
not appear, and i don't see a solution in git fetch description. Any
help?
Delete your lilypond directory and start it fresh with a new git
clone. Of course, back up any work you have first by doing git
format-patch origin and double-check that you have the right
patches.
It is seriously not worth trying to change your .git/config.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: having trouble fetching all remote branches
2012/2/7 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com writes:
My local repository wasn't created with git clone, and i have only one
remote branch ('origin/master'); i cannot push to staging because of
that. I've tried 'git fetch --all', but the other remote branches do
not appear, and i don't see a solution in git fetch description. Any
help?
A list search...
ok, i'm really stupid. Indeed you helped me with this problem a month
ago... I searched internet and stackoverflow for git tips, but didn't
realize the answer was so close...
I'm sorry.
2012/2/7 Graham Percival gra...@percival-music.ca:
Delete your lilypond directory and start it fresh with a new git
clone.
It is seriously not worth trying to change your .git/config.
Unless i want to learn how things work, which is the case.
thanks,
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Cheat sheet
On 07/02/2012 10:02, Francisco Vila wrote: Hello Reinhold, Here is my work in progress with a Spanish version of the Cheat sheet you posted some time ago. http://paconet.org/lilypond/lilypond-cheat-sheet-es.pdf (source attached) If you don't want to give away your source code, which I understand, I would like nevertheless to ask you a few questions or clues about the implementation. Some tricks look very clever from your PDF. The complete code is available at: https://gitorious.org/lilypond-cheatsheet/ Please use the new-baposter branch, which builds on a customized version of the baposter package (included in the git repo). I haven't yet tried it with the latest official baposter release, which includes all my changes (but might add some other things that break the cheatsheet). If you decide to send me even fractional, incomplete chunks of the source file, you'd be credited in the sheet as the author and myself as translator with the same license you used and in the same way you did. I do not plan to sell it. No problem, I realized that you cannot make money off lilypond, so I'm putting also the source code under the creative commons license. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Cheat sheet
2012/2/7 Reinhold Kainhofer reinh...@kainhofer.com: The complete code is available at: https://gitorious.org/lilypond-cheatsheet/ Thank you very much! -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: having trouble fetching all remote branches
Graham Percival gra...@percival-music.ca writes: Delete your lilypond directory and start it fresh with a new git clone. Of course, back up any work you have first by doing git format-patch origin and double-check that you have the right patches. It is seriously not worth trying to change your .git/config. That approach loses your reflog and your local branches. Any of your local work that has not been sent upstream is lost. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Cheat sheet
Reinhold Kainhofer reinh...@kainhofer.com writes: No problem, I realized that you cannot make money off lilypond, The jury's still out on that. Better hope you are wrong, or I'll have to go elsewhere. so I'm putting also the source code under the creative commons license. If LilyPond development grows by leaps and bounds because of the massive inflow of money from private and commercial users alike, the source code under that license will become outdated and you'll still be able to sell wagonloads of the updated versions you'll create then under commercial licenses for oodles of money. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Directs makeinfo and texi2html output to logfiles (issue 5645046)
Reviewers: dak, Graham Percival, Julien Rioux, Message: Slightly complicated (for me, anyway) but please review and ask questions if it's not clear what I'm doing here. Description: This uses a shell script that I've written to direct the output from a command to a logfile, and to issue a line identifying the logfile if the command fails. I've updated the calls (all of them, I believe) to makeinfo and texi2html to use this script. The result is about 3400 fewer lines output from make doc, and lots of lovely logfiles to check for errors - it makes debugging docs a lot easier. It's slightly non-trivial to test, since neither makeinfo or texi2html stops on errored input by default. If you force it to do so (see below) sample output is: /home/phil/lilypond-git/scripts/build/CheckAndRun.sh DEPTH=../../.. AJAX_SEARCH= TOP_SRC_DIR=/home/phil/lilypond-git PERL_UNICODE=SD texi2html --error-limit=0 --I=/home/phil/lilypond-git/input/regression/lilypond-book --I=./out-www -I /home/phil/lilypond-git/Documentation --I=/media/IntelSSD/lilypond/lilypond-git/build/./out-www/xref-maps --init-file=/home/phil/lilypond-git/Documentation/lilypond-texi2html.init --output=out-www/collated-files.html out-www/collated-files.texi collated-files.texilog.log Please check the logfile collated-files.texilog.log for errors make[4]: *** [out-www/collated-files.html] Error 2 make[4]: Leaving directory `/media/IntelSSD/lilypond/lilypond-git/build/input/regression/lilypond-book' make[3]: *** [WWW-2] Error 2 make[3]: Leaving directory `/media/IntelSSD/lilypond/lilypond-git/build/input/regression' make[2]: *** [WWW-2] Error 2 make[2]: Leaving directory `/media/IntelSSD/lilypond/lilypond-git/build/input' make[1]: *** [WWW-2] Error 2 make[1]: Leaving directory `/media/IntelSSD/lilypond/lilypond-git/build' make: *** [doc] Error 2 Command exited with non-zero status 2 The logfile that's fingered contains this: *** Duplicate node found: Top (in out-www/papersize-docs.texi l. 8) Max error number exceeded To show this in action, you would need to edit texinfo-vars.make as below. -TEXI2HTML_FLAGS += $(TEXI2HTML_INCLUDES) $(TEXI2HTML_INIT) $(TEXI2HTML_LANG) +TEXI2HTML_FLAGS += --error-limit=0 $(TEXI2HTML_INCLUDES) $(TEXI2HTML_INIT) $(TEXI2HTML_LANG) Please review this at http://codereview.appspot.com/5645046/ Affected files: M Documentation/GNUmakefile M make/doc-i18n-root-rules.make A scripts/build/CheckAndRun.sh M stepmake/stepmake/texinfo-rules.make Index: Documentation/GNUmakefile diff --git a/Documentation/GNUmakefile b/Documentation/GNUmakefile index 22da2d8fa8d73a3746c11f5d9d64f641fb45fda1..a93926a1553f5cdb87f89e005e9d596af2f781af 100644 --- a/Documentation/GNUmakefile +++ b/Documentation/GNUmakefile @@ -195,7 +195,7 @@ endif ### Rules $(outdir)/lilypond-%.info: $(outdir)/%.texi $(outdir)/$(INFO_IMAGES_DIR).info-images-dir-dep $(outdir)/version.itexi $(outdir)/weblinks.itexi - $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$@ $ + $(top-src-dir)/scripts/build/CheckAndRun.sh $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$@ $ $*.makeinfo.log txt-to-html: $(OUT_TXT_FILES) $(OUT_TXT_FILES:%.txt=%.html) @@ -231,11 +231,11 @@ endif # Ugh, using '%' twice not possible $(outdir)/notation/notation.xml: $(outdir)/notation.texi mkdir -p $(dir $@) - $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$(dir $@) --docbook $ + $(top-src-dir)/scripts/build/CheckAndRun.sh $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$(dir $@) --docbook $ $*.makeinfo.log $(outdir)/internals/internals.xml: $(outdir)/internals.texi mkdir -p $(dir $@) - $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$(dir $@) --docbook $ + $(top-src-dir)/scripts/build/CheckAndRun.sh $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$(dir $@) --docbook $ $*.makeinfo.log $(outdir)/learning.texi $(outdir)/notation.texi: $(OUT_PDF_IMAGES) Index: make/doc-i18n-root-rules.make diff --git a/make/doc-i18n-root-rules.make b/make/doc-i18n-root-rules.make index 3cdd664471ffc6541a413c2c4c019950c3d77a9f..b19364c11d3868c3864aa1619e04465ceef4f230 100644 --- a/make/doc-i18n-root-rules.make +++ b/make/doc-i18n-root-rules.make @@ -7,14 +7,14 @@ $(outdir)/web.texi: $(outdir)/weblinks.itexi $(top-build-dir)/Documentation/$(outdir)/%/index.$(ISOLANG).html: $(outdir)/%.texi $(XREF_MAPS_DIR)/%.$(ISOLANG).xref-map $(TRANSLATION_LILY_IMAGES) mkdir -p $(dir $@) mkdir -p $(outdir)/$* - DEPTH=$(depth)/../ $(TEXI2HTML) $(TEXI2HTML_SPLIT) $(TEXI2HTML_FLAGS) --output=$(outdir)/$* $ $*.splittexi.log 21 + $(top-src-dir)/scripts/build/CheckAndRun.sh DEPTH=$(depth)/../ $(TEXI2HTML) $(TEXI2HTML_SPLIT) $(TEXI2HTML_FLAGS) --output=$(outdir)/$* $ $*.splittexi.log find $(outdir)/$* -name '*.html' | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!$(outdir)/!!g' | xargs $(buildscript-dir)/mass-link --prepend-suffix .$(ISOLANG) hard $(outdir) $(top-build-dir)/Documentation/$(outdir)
articulations on EventChord
I have been just rewritting a snippet that used to add text spanners to elements working purely on EventChord. It now has to add to articulations on a NoteEvent, and to elements on EventChord. As an element of courtesy to programmers, I would like to allow people to add to articulations on EventChord. That way, you can do extract-named-music on both EventChord and NoteEvent, and just plaster your stuff into articulations' without worrying which of the two you got. As long as this is just user generated content, there is not much more to do rather than let the event chord iterator replay articulations after elements. It might make sense at some point of time to actually let the parser generate this arrangement as well. However, that would be a change of format that should likely be left for another time. What's your take on this? Just replaying articulations is not likely to cause any incompatibilities (though of course snippets making use of that trick generate incompatible music streams in the process). -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Gets vertical skylines from grob stencils (issue 5626052)
On Feb 6, 2012, at 11:55 PM, David Kastrup wrote: m...@apollinemike.com m...@apollinemike.com writes: I'll look into doing 1. Meanwhile, if someone can tell me how to push changes to a remote branch (after having created the branch), I'd be much obliged! If it is a fast forward, just push like the initial push. If it is not, you can't push at all given the current repository settings. Instead you need to _delete_ the branch git push origin :dev/skyline and then push a fresh one git push origin HEAD:refs/heads/dev/skyline -- David Kastrup Hey all, I did some experiments with caching that are up on: dev/skylines-cached To install it, you need to run a make clean and rerun autogen.sh Bizarrely, with many of the calculations cached in hash tables, it takes as long as (if not longer than) the previous branch I posted. All speed-up suggestions are welcome! Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
New French PO file for 'lilypond' (version 2.15.29)
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the French team of translators. The file is available at: http://translationproject.org/latest/lilypond/fr.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) All other PO files for your package are available in: http://translationproject.org/latest/lilypond/ Please consider including all of these in your next release, whether official or a pretest. Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. The following HTML page has been updated: http://translationproject.org/domain/lilypond.html If any question arises, please contact the translation coordinator. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. coordina...@translationproject.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directs makeinfo and texi2html output to logfiles (issue 5645046)
Looks basically good, I just have some trivial quibbles. This should vastly simplify debugging doc problems, though! http://codereview.appspot.com/5645046/diff/1/Documentation/GNUmakefile File Documentation/GNUmakefile (right): http://codereview.appspot.com/5645046/diff/1/Documentation/GNUmakefile#newcode198 Documentation/GNUmakefile:198: $(top-src-dir)/scripts/build/CheckAndRun.sh $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$@ $ $*.makeinfo.log Could this be condensed into $(RUN_WITH_LOG) or something like that? i.e. define RUN_WITH_LOG = $(top-src-dir)/scripts/build/CheckAndRun.sh somewhere in a main build file (maybe stepmake.make?) and then just call that definition everywhere else? http://codereview.appspot.com/5645046/diff/1/scripts/build/CheckAndRun.sh File scripts/build/CheckAndRun.sh (right): http://codereview.appspot.com/5645046/diff/1/scripts/build/CheckAndRun.sh#newcode3 scripts/build/CheckAndRun.sh:3: # CheckAndRun.sh. Takes 2 parameters - the command to be run and sorry, totally silly complaint, but I wince every time I see this: unix people are generally allergic to Capital letters. Maybe because it requires pressing shift, and the whole point of the command-line is to be lazy? Could this be check_and_run.sh or check-and-run.sh ? I think that would fit in with other scripts/build/* items as well. Also, technically I'd call it run-and-check.sh, since it runs the command first, and then checks the results afterwards. http://codereview.appspot.com/5645046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Run regression tests for lilypond-book (issue 2223). (issue 5569045)
http://codereview.appspot.com/5569045/diff/3001/input/regression/lilypond-book/GNUmakefile
File input/regression/lilypond-book/GNUmakefile (right):
http://codereview.appspot.com/5569045/diff/3001/input/regression/lilypond-book/GNUmakefile#newcode19
input/regression/lilypond-book/GNUmakefile:19: OUT_TEXI_FILES +=
${TEXI_FILES:%.texi=$(outdir)/%.info}
how are the OUT_X_Y definitions used? Is there a generic rule for OUT_X
? other than that, I can't see how they'd have any effect?
http://codereview.appspot.com/5569045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Run regression tests for lilypond-book (issue 2223). (issue 5569045)
On 2012/02/07 20:05:49, Graham Percival wrote:
http://codereview.appspot.com/5569045/diff/3001/input/regression/lilypond-book/GNUmakefile
File input/regression/lilypond-book/GNUmakefile (right):
http://codereview.appspot.com/5569045/diff/3001/input/regression/lilypond-book/GNUmakefile#newcode19
input/regression/lilypond-book/GNUmakefile:19: OUT_TEXI_FILES +=
${TEXI_FILES:%.texi=$(outdir)/%.info}
how are the OUT_X_Y definitions used? Is there a generic rule for
OUT_X ?
other than that, I can't see how they'd have any effect?
Yes those rules are in one of two dozen files in the make folder, I
forgot which one, but they are effective. They test that the files
generated by -book are compilable to .info and .pdf (as well as .html)
Cheers,
Julien
http://codereview.appspot.com/5569045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directs makeinfo and texi2html output to logfiles (issue 5645046)
Graham basically covered it... http://codereview.appspot.com/5645046/diff/1/Documentation/GNUmakefile File Documentation/GNUmakefile (right): http://codereview.appspot.com/5645046/diff/1/Documentation/GNUmakefile#newcode198 Documentation/GNUmakefile:198: $(top-src-dir)/scripts/build/CheckAndRun.sh $(MAKEINFO) -I$(src-dir) -I$(outdir) --output=$@ $ $*.makeinfo.log Can you use $(buildscript-dir) here? That could make these lines a bit shorter. http://codereview.appspot.com/5645046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directs makeinfo and texi2html output to logfiles (issue 5645046)
On 2012/02/07 19:49:46, Graham Percival wrote: i.e. define RUN_WITH_LOG = $(top-src-dir)/scripts/build/CheckAndRun.sh somewhere in a main build file (maybe stepmake.make?) and then just call that definition everywhere else? in make/genericgeneric-vars.make, I would think http://codereview.appspot.com/5645046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Documentation about unpure-pure containers is unclear
Hello!
The issue 2275 has Patch-needs_work now. I guess the needed work is
asking some questions in the list, so that the documentation becomes
easier to understand and the example would actually illustrate it.
This is the page I'm taking about:
http://lilypond.org/doc/v2.15/Documentation/notation/unpure_002dpure-containers
Quote:
When a function overrides a Y-offset and/or Y-extent it is assumed that
this will trigger line breaking calculations too early during
compilation. So the function is not evaluated at all
squareLineCircleSpace doesn't override Y-offset or Y-extent, yet the
output is ugly. Why?
Why do stems have to be hidden? Do they force calculations that would
otherwise be delayed? Or do they reserve horizontal space that the
noteheads with overridden stencil won't reserve?
Why is this showing correct output?
roundNotes = {
\override NoteHead #'stencil = #(make-circle-stencil 0.5 0.1 #f)
}
smartRoundNotes = {
\roundNotes
\override NoteHead #'Y-extent =
#(ly:make-unpure-pure-container
ly:grob::stencil-height
(lambda (grob start end) (ly:grob::stencil-height grob)))
}
\new Voice
\relative c'' {
\time 4/1
\roundNotes
cis1 ces cisis c
\smartRoundNotes
cis1 ces cisis c
}
And why does the output break if roundNotes is rewritten with a
lambda?
roundNotes = {
\override NoteHead #'stencil =
#(lambda (grob) (make-circle-stencil 0.5 0.1 #f))
}
What's so different between the above stencil definitions? Does
Lilypond actually try to classify functions as pure and unpure by
parsing them?
--
Regards,
Pavel Roskin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: utf-8-string
Hi Mike,
On Mon, Feb 6, 2012 at 4:55 AM, m...@apollinemike.com
m...@apollinemike.com wrote:
Hey all,
I see a shortcut for utf-8-strings in pango-font.cc. This is
all well and good except that it is hard to do box
approximations on these guys (it'd require adding lots of code).
How mad would LilyPond be if I just deleted all of the
utf-8-string business? I don't think it'd change the visual
output...it'd just get rid of a shortcut. Does anyone have any
justification for keeping this shortcut?
Yes :) It's not actually a shortcut, despite the code comment.
Every backend is a Pango-based backend if it uses a text
stencil.
utf-8-string is absolutely critical for the SVG backend (not sure
about the socket backend)...
In the code, description_string() (see lily/pango-font.cc:378)
returns a string in the PangoFontDescription format. This format
is best described in the pygtk docs:
http://www.pygtk.org/docs/pygtk/class-pangofontdescription.html
The SVG backend uses this information (font style, weight, etc.)
to assign accurate attribute values. Then they are output as SVG
text elements with the appropriate font-weight, style, etc. If
this information did not exist, any string in the SVG output not
using a LilyPond font would likely display incorrectly.
utf-8-string is not used in the PS backend because Pango takes
care of the processing internally, calculating kerning, font
weight, and other attributes before the stencil expression is
evaluated in the backend. IIRC, every string of text using a
non-LilyPond font is a glyph-string in the PS backend.
That said, what issues are you seeing with the box approximations
for utf-8-string? I'm seeing tight fits when running `lilypond
-dbackend=svg -dpreview', for example with
\version 2.15.28
\markup { Lily }
Regards,
Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCH: Countdown to 20120209
For 20:00 MST Thursday, February 9th, 2012
Enhancement:
Issue 2286
http://code.google.com/p/lilypond/issues/detail?id=2286: Patch: Make
#{ c' #} and x=c' create a pitch instead of a NoteEvent - R 5633043
http://codereview.appspot.com/5633043/
Issue 2299
http://code.google.com/p/lilypond/issues/detail?id=2299: Patch: Adds
stencil command suppressions to changes - R 5633048
http://codereview.appspot.com/5633048/
Issue 2300
http://code.google.com/p/lilypond/issues/detail?id=2300: Patch: do not
tinker with the position of a pitched rest - R 5434061
http://codereview.appspot.com/5434061/
Patch:
Issue 2296
http://code.google.com/p/lilypond/issues/detail?id=2296: Patch: Stops
woodwind diagram info appearing on terminal - R 5636048
http://codereview.appspot.com/5636048/
Ugly:
Issue 2148
http://code.google.com/p/lilypond/issues/detail?id=2148: vertical
skylines should use stencil integrals - R 5626052
http://codereview.appspot.com/5626052/
Cheers,
Colin
--
I've learned that you shouldn't go through life with a catcher's mitt on both
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: utf-8-string
On Tue, Feb 7, 2012 at 7:19 PM, Patrick McCarty pnor...@gmail.com wrote: On Mon, Feb 6, 2012 at 4:55 AM, m...@apollinemike.com m...@apollinemike.com wrote: Hey all, I see a shortcut for utf-8-strings in pango-font.cc. This is all well and good except that it is hard to do box approximations on these guys (it'd require adding lots of code). How mad would LilyPond be if I just deleted all of the utf-8-string business? I don't think it'd change the visual output...it'd just get rid of a shortcut. Does anyone have any justification for keeping this shortcut? utf-8-string is absolutely critical for the SVG backend (not sure about the socket backend)... To follow up, I just noticed your patch that reworks vertical skylines, and I assume that your concern about utf-8-string is related to this. Let me know if I'm wrong. For now, here's an idea: - Introduce a new argument to 'utf-8-string' that exposes vertical extent information for each glyph in the string. It could be a simple list of pairs. For example: (utf-8-string Century Schoolbook L Bold 16 test '((0.0 . 1) (0.0 . 0.6) (0.0 . 0.6) (0.0 . 1))) The number of pairs in the list will match the length of the (UTF-8) string, of course. I don't think the glyph width, offsets, and characters are really needed in the list, unless you can think of a use for them in your vertical skyline calculations. In the long term, it may be better to unify the stencil expressions used for text, but as it stands, I think it would be easier to add information to the existing stencil expressions (as you are doing for 'glyph-string' in your patchset). Regards, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
