lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [git 17e68b85] make error in documentation


From: Patrick McCarty
Subject: Re: [git 17e68b85] make error in documentation
Date: Tue, 25 Aug 2009 12:19:21 -0700
User-agent: Mutt/1.5.20 (2009-06-14)

On 2009-08-24, Graham Percival wrote:
> On Mon, Aug 24, 2009 at 01:07:51PM -0700, Patrick McCarty wrote:
> > On Sun, Aug 23, 2009 at 9:08 AM, Werner LEMBERG<address@hidden> wrote:
> > > Can (b) be fixed at all?  This is, does the SVG format support glyph
> > > access by name?  Sinve SVG fonts themselves have glyph names I suspect
> > > it can be fixed...
> > 
> > I am willing to fix this file, but only if we are actually going to
> > use it somewhere.  As Graham noted earlier, we're not sure why this
> > example was added to master.
> 
> Screw it.  I've deleted that file.  Patrick: please change the
> other svg files to not use text.  Since this is happening on your
> local system, feel free to use whatever font(s) you want.
> 
> The bloody translation people can take care of the bloody
> translated images if they bloody well want to.  Although even
> then, I think they should just bloody make a new image, with
> modified text, converted to non-text, or whatever it is that
> you're going to do to the svg images.

Hmm.  I think the problem might have been solved after Werner
installed librsvg and recompiled imagemagick.  imagemagick will use
this library for the SVG output if found at compile time.

Now that I found the discussion about translating the SVG annotations
in the archives, it sounds like the translation team was enthusiastic
about the idea, so I'm hesitant about converting the SVG text to
paths now.

Werner, does the conversion from SVG->PNG work for you now?  I'll add
a configure rule soon if this does solve the problem.


Thanks,
Patrick




reply via email to

[Prev in Thread] Current Thread [Next in Thread]