Comment #1 on issue 1039 by hanwenn: Clean up Font_metric interface
http://code.google.com/p/lilypond/issues/detail?id=1039
I am busy cleaning out a lot of cruft.
I'll see if I can also fix how each Pango_font the fonts it uses for each
snippet of
text.
--
You received this message because
On 14 March 2010 20:32, T.Skeggs wrote:
> I feared something much more complex than your suggestion.
> I tried it but could see no discernible difference, so printed it with
> affinity UP and DOWN, overlapped them in front of a strong light and could
> see no difference.
> (I even tried setting a
Updates:
Status: Fixed
Comment #2 on issue 1032 by markpolesky: Documentation:
automatically-generated list of articulations
http://code.google.com/p/lilypond/issues/detail?id=1032
(No comment was entered for this change.)
--
You received this message because you are listed in the ow
Comment #23 on issue 838 by pnorcks: Inconsistency in tests output size
http://code.google.com/p/lilypond/issues/detail?id=838
To avoid this situation in the future, maybe we should use a different
branch for
"release testing" purposes. That way, you won't have to modify your
release proces
Comment #22 on issue 838 by pnorcks: Inconsistency in tests output size
http://code.google.com/p/lilypond/issues/detail?id=838
Also, we can't modify git history in the central repo (AFAIK). If savannah
did have
that capability, I could have interactively removed the test commit from
release/
Comment #21 on issue 838 by pnorcks: Inconsistency in tests output size
http://code.google.com/p/lilypond/issues/detail?id=838
Sorry about that.
However, we *do* want to be merging release/unstable into master, in
general, though,
because it's helpful to see the release commit in the gitweb s
Comment #20 on issue 838 by percival.music.ca: Inconsistency in tests
output size
http://code.google.com/p/lilypond/issues/detail?id=838
Umm. Now we have a commit 910b1ff742f07dacf5f9e3808bc1165def61c715 with
the message
"TEST COMMIT, DO NOT MERGE WITH MASTER. (if possible)"
I guess the
Updates:
Status: Fixed
Labels: fixed_2_13_15
Comment #19 on issue 838 by pnorcks: Inconsistency in tests output size
http://code.google.com/p/lilypond/issues/detail?id=838
Okay, I merged release/unstable into master.
Let's move the Font_metric discussion to issue 1039.
--
You r
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1039 by pnorcks: Clean up Font_metric interface
http://code.google.com/p/lilypond/issues/detail?id=1039
The current Font_metric interface was designed back when TeX was still used
with LilyPond. Now that many fonts are
LGTM.
Cheers,
- Graham
On Sun, Mar 14, 2010 at 7:16 PM, Mark Polesky wrote:
> Here's a patch. Okay to push?
>
> - Mark
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
>
__
Updates:
Labels: -Patch
Comment #3 on issue 732 by percival.music.ca: Alignment problems when
vertically stacking horizontally centered stencils.
http://code.google.com/p/lilypond/issues/detail?id=732
Reinhold removed his patch because it broke other stuff.
--
You received this messa
Here's a patch. Okay to push?
- Mark
From 363fcb320d75d25385304411da22efe9eac23436 Mon Sep 17 00:00:00 2001
From: Mark Polesky
Date: Sun, 14 Mar 2010 11:53:49 -0700
Subject: [PATCH] Doc: NR: Organize `List of articulations' appendix.
---
Documentation/included/script-chart.ly
Updates:
Status: Fixed
Comment #9 on issue 844 by percival.music.ca: clean up website maintenance
http://code.google.com/p/lilypond/issues/detail?id=844
Central location: done and documented in the CG.
ajax stuff: split into issue 815.
htaccess: split into issue 1038
"online target":
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Critical Frog website
New issue 1037 by percival.music.ca: links to old manuals
http://code.google.com/p/lilypond/issues/detail?id=1037
Apparently we want to keep links to all the old manuals. This should
happen in Documentation/w
Status: Accepted
Owner:
Labels: Type-Build Priority-Critical website
New issue 1038 by percival.music.ca: htaccess links
http://code.google.com/p/lilypond/issues/detail?id=1038
Make sure the short links / .htaccess redirects are good after switching to
/website/ instead of /web/.
On 29 May
Status: Accepted
Owner:
Labels: Type-Build Priority-Postponed
New issue 1036 by percival.music.ca: Links to accented anchors
http://code.google.com/p/lilypond/issues/detail?id=1036
%% report from Francisco about doc translation build.
%% current lilypond version: 2.13.15.
Hello. This is fo
Comment #18 on issue 838 by percival.music.ca: Inconsistency in tests
output size
http://code.google.com/p/lilypond/issues/detail?id=838
Time with random:
real9m8.964s
user20m16.000s
sys 0m57.332s
Time **without** random:
real7m27.668s
user18m43.626s
sys 0m54.719s
I
On 2010-03-14, Ian Hulin wrote:
>
> general-scheme.cc: In function 'scm_unused_struct*
> ly_stderr_redirect(scm_unused_struct*, scm_unused_struct*)':
> general-scheme.cc:448: warning: ignoring return value of 'FILE*
> freopen(const char*, const char*, FILE*)', declared with attribute
> warn_unused
On Sat, Jan 9, 2010 at 6:40 PM, Carl Sorensen wrote:
> When strings are given for notes in a fret diagram, and the notes are too
> low, the fret diagram will try to put dots on negative frets, instead of
> giving an error and producing nothing.
Added as http://code.google.com/p/lilypond/issues/de
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1035 by v.villenave: Negative frets in fret diagrams
http://code.google.com/p/lilypond/issues/detail?id=1035
% new report by Carl:
When strings are given for notes in a fret diagram, and the notes are too
low, the fret d
On Sun, Mar 14, 2010 at 1:49 PM, Ian Hulin wrote:
> Hi all,
Greetings Ian,
such reports actually belong more to -devel than bug- (normal users
are not expected to daily build LilyPond ;-)
> I've just tried rebuilding from the latest git (using a totally new git
> repository)
> and
> $ sh autoge
Hi all,
I've just tried rebuilding from the latest git (using a totally new git
repository)
and
$ sh autogen.sh
$ ./configure --prefix $HOME/usr
$ make all
gives me this
general-scheme.cc: In function 'scm_unused_struct*
ly_stderr_redirect(scm_unused_struct*, scm_unused_struct*)':
general-sc
22 matches
Mail list logo
