I'm late to this thread (as usual)... (I'm in the middle of a little
piano trio tour around New England, so writing code is getting pushed
to the side.)
I guess I should have mentioned earlier that I've been continuing
some work in this vein. Since it sounds like this OS X-native stuff
is
Matthias Neeracher wrote:
On Jun 5, 2005, at 3:02 PM, Han-Wen Nienhuys wrote:
Matthias Neeracher wrote:
AFAIK, a .dfont is an archive of several TTFs, and should be
possible to extract the right TTF font from the .dfont directly.
Actually, we're not just dealing with dfonts here. Verdana,
On Jun 5, 2005, at 3:02 PM, Han-Wen Nienhuys wrote:Matthias Neeracher wrote: AFAIK, a .dfont is an archive of several TTFs, and should be possible to extract the right TTF font from the .dfont directly. Actually, we're not just dealing with dfonts here. Verdana, for instance, is a tradtional MacOS
Matthias Neeracher wrote:
Actually, we're not just dealing with dfonts here. Verdana, for
instance, is a tradtional MacOS font, as far as I can tell. Also, I
think that some font files may have the pfa font already embedded, so
going through the ttf version may entail a loss of quality.
Gotit
Matthias Neeracher wrote:
AFAIK, a .dfont is an archive of several TTFs, and should be possible
to extract the right TTF font from the .dfont directly.
Actually, we're not just dealing with dfonts here. Verdana, for
instance, is a tradtional MacOS font, as far as I can tell. Also, I
think th
On Jun 5, 2005, at 2:13 PM, Han-Wen Nienhuys wrote:Matthias Neeracher wrote: Yes, I guess that's best. I'd be grateful if you could find out how we can properly embed a dfont file. I know that there are utilities for extracting TTFs from dfonts. I think I found a solution that is reasonably gene
Matthias Neeracher wrote:
Yes, I guess that's best. I'd be grateful if you could find out how
we can properly embed a dfont file. I know that there are utilities
for extracting TTFs from dfonts.
I think I found a solution that is reasonably general: Why not pass all
unknown font files to
I have completed the fret diagram modifications to eliminate white-dot
and white-text, and to ensure that fret-diagrams work with 2.5.27.
I've also added a file /input/regression/fret-diagrams.ly that
excercises every option for the fret-diagrams code.
I've tried to commit to CVS, but it's been w
On Jun 3, 2005, at 2:08 AM, Han-Wen Nienhuys wrote:
Matthias Neeracher wrote:
It seems the changes in font.scm were harmful to MacOS X. On
processing, I get:
warning: don't know how to embed "Verdana"="/Library/Fonts/Verdana"
and in the resulting PDF file, the chord names look weird (I
b
Nicolas Sceaux wrote:
One of the other nice things of python is that we'd be able to run the
support scripts (both the wrapper for the standalone binary and
convert-ly) inside LilyPond.app.
A little technical question: do you write the Python code inside
XCode, or in another IDE, eg emacs?
(I'
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> - For reasons of maintainability, I prefer python over Objective
> C. Python's dynamic nature makes it a very natural match with
> Objective C.
>
> Given cocoa's nice MVC structure, I expect that it would be easy to
> replace the ObjC code with Pyth
Paul Hamelinck writes:
> Congratulations with your new MS windows release! I installed it today;
> I am impressed, that you got the point and click to work in Acrobat!
Thanks. I'm glad it works.
> However, I think I've got a small problem: Each time I open
> lilypond, it comes up with this welc
12 matches
Mail list logo
