Comment #1 on issue 1496 by pnorcks: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
tools::pango checks out okay, but I haven't built any of the installers yet.
To clarify, this patch bumps Pango from 1.26.0 to 1.28.3. This has the
following effects (that I've
On Fri, Jan 28, 2011 at 11:05 PM, Patrick McCarty wrote:
>
> After further testing, I'm almost 100% sure that this problem can be
> solved by upgrading Pango to the latest stable release (in GUB).
>
> Graham, would you be willing to bump Pango in GUB? I've been running
> Pango 1.28.3 with my self
Status: Accepted
Owner: pnorcks
Labels: Type-Build Priority-High
New issue 1496 by pnorcks: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
GUB is currently using Pango 1.26.0, but over time I've noticed some major
regressions with shaping of Khmer script, and no
On Fri, Jan 28, 2011 at 10:50 PM, Patrick McCarty wrote:
> On Fri, Jan 28, 2011 at 1:03 PM, James Samir Ismail wrote:
>> So this seems like a bug after all. How do I get this into the queue? I'd be
>> more than happy to help out with testing.
>
> Which version of LilyPond are you using? The 2.1
On Fri, Jan 28, 2011 at 1:03 PM, James Samir Ismail wrote:
> So this seems like a bug after all. How do I get this into the queue? I'd be
> more than happy to help out with testing.
Hi,
Which version of LilyPond are you using? The 2.13 series has many,
many improvements in font/text handling t
Comment #12 on issue 37 by mts...@gmail.com: collision notehead and beams
http://code.google.com/p/lilypond/issues/detail?id=37
New patch on http://codereview.appspot.com/4022045.
Attachments:
full-beam-collision.png 14.5 KB
___
bug-lilypon
On 1/28/11 2:03 PM, "James Samir Ismail" wrote:
> So this seems like a bug after all. How do I get this into the queue? I'd be
> more than happy to help out with testing.
The first thing to do is to run the specified command from a terminal
window:
lilypond -dshow-available-fonts x
You said be
Comment #7 on issue 1470 by ahawry...@gmail.com: Change keep-inside-line
defaults to true
http://code.google.com/p/lilypond/issues/detail?id=1470
Ah, that explanation of the mensural ligatures makes sense. Given that the
horizontal spacing with keep-inside-line == ##t is no more odd than th
So this seems like a bug after all. How do I get this into the queue? I'd be
more than happy to help out with testing.
-Samir
On 1/28/11, at 9:10 AM, James Samir Ismail wrote:
>> I tried this:
>>
>> \relative c' {
>> c4^\markup { \override #'(font-name . "KacstOffice")
>>"الع
Status: Accepted
Owner:
New issue 1495 by jan.nieuwenhuizen: mac line endings and line comment
disaster
http://code.google.com/p/lilypond/issues/detail?id=1495
In certain cases, adding a line comment in a .ly that uses
Mac-style line ending (^M-only) has the effect of commenting-out
the
Create a file `arabic.ly' in the current directory (with arbitrary
contents) and say
lilypond arabic.ly
I get this logging output
> lilypond arabic.ly
GNU LilyPond 2.13.45
Processing `/usr/local/share/lilypond/2.13.45/ly/arabic.ly'
Parsing...
success: Compilation successfully comple
> I tried this:
>
> \relative c' {
>c4^\markup { \override #'(font-name . "KacstOffice")
> "العربية" }
> d e f |
>g^\markup { "english" }
> f e d |
> }
>
> and get the attached image as output, which seems to be correct
> (please correct me if I'm wrong). This
> This is what I tried, and got the same (wrong) result (Arabic
> characters not correctly displaying in their medial and initial
> forms):
I tried this:
\relative c' {
c4^\markup { \override #'(font-name . "KacstOffice")
"العربية" }
d e f |
g^\markup { "english"
Comment #6 on issue 1470 by benko@gmail.com: Change keep-inside-line
defaults to true
http://code.google.com/p/lilypond/issues/detail?id=1470
Does anyone know why the 'mensural-ligatures' regression test
would have been affected by keep-inside-line = ##t?
mensural ligatures interact wi
Updates:
Labels: -Patch-review Patch-needs_work
Comment #17 on issue 1268 by percival.music.ca: [PATCH] span-bar problem
http://code.google.com/p/lilypond/issues/detail?id=1268
Neil has identified some problems with this patch.
Unfortunately I really should move ahead with 2.13.47 right
Updates:
Labels: -Patch Patch-needs_work
Comment #2 on issue 1417 by percival.music.ca: regtests "time" field is
broken
http://code.google.com/p/lilypond/issues/detail?id=1417
Hmm. I'm going to say "patch-needs_work", not because the patch doesn't
work, but rather because I'd like
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_13_47
Comment #3 on issue 1424 by percival.music.ca: [PATCH]coloratio, black
mensural notation
http://code.google.com/p/lilypond/issues/detail?id=1424
Thanks, pushed.
___
bug-lil
> \markup { \override #'(font-name . "new font") "العربية" }
>
> where "new font" is the name of the font to use.
This is what I tried, and got the same (wrong) result (Arabic characters not
correctly displaying in their medial and initial forms):
\score
{
\relative d'
{
Comment #5 on issue 400 by mts...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
My most recent patch for Issue 37 fixes this issue.
http://codereview.appspot.com/4022045
___
bug-lilypond mailing list
bug-li
Updates:
Labels: -Patch Patch-needs_work
Comment #4 on issue 400 by percival.music.ca: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Mike, was your patch on Jan 10 a serious one? I'm not certain where we
stand on this particular issue... I suspect that
Updates:
Labels: -Patch Patch-needs_work
Comment #6 on issue 39 by percival.music.ca: collision flag notehead with
polyphony
http://code.google.com/p/lilypond/issues/detail?id=39
Mike, was your patch in comment 3 a serious one? I'm not certain where we
stand on this particular issu
Updates:
Labels: -Patch Patch-needs_work
Comment #2 on issue 1278 by percival.music.ca: Enhancement: arrow notation
for quarter-tones
http://code.google.com/p/lilypond/issues/detail?id=1278
Due to the 4-week delay between submitting this patch and anybody looking
at it, git master h
Comment #25 on issue 1454 by jonlance...@gmail.com: lilybuntu 3
http://code.google.com/p/lilypond/issues/detail?id=1454
I haven't uploaded the iso yet. I'll change it and then upload. I can
probably get to this tonight. Has anyone tried using a ~/.mime.types file
though?
_
Comment #2 on issue 631 by chris...@gmail.com: Dynamics collide with
cross-staff barlines when attached to skips
http://code.google.com/p/lilypond/issues/detail?id=631
I've had something similar to this, but the dynamics were too far to the
left and were colliding with the bar before it. Fo
Comment #26 on issue 1454 by jonlance...@gmail.com: lilybuntu 3
http://code.google.com/p/lilypond/issues/detail?id=1454
The new .iso is now available here:
http://files.lilynet.net/
It's filename ubuntu-lilydev-remix-1.1.iso
___
bug-lilypond mail
25 matches
Mail list logo