Being lazy, I'm asking here before actually looking around. Can anyone
recommend programs that create [OT]TF fonts from BDF fonts?
[I] seem to recall that someone on one of the Freetype lists might
have also written one;
You may be thinking of my fonttosfnt. It does something completely
On Thu, 2005-12-08 at 09:26 -0700, Mark Leisher wrote:
Being lazy, I'm asking here before actually looking around. Can anyone
recommend programs that create [OT]TF fonts from BDF fonts?
Juliusz wrote fonttosfnt which combines multiple BDF sizes into a single
SFNT. It's in CVS at
On Fri, 2005-12-09 at 01:07 +0100, Werner LEMBERG wrote:
Hmm, why not simply adding a special `BDF ' table which holds all
properties? This should be straightforward, and you get lossless
conversion.
Yes, this was my plan. I got side-tracked before I managed to implement
it though.
I need
On Thu, 2005-12-08 at 16:46, Keith Packard wrote:
Yes, this was my plan. I got side-tracked before I managed to implement
it though.
I need this + a utility to regenerate BDF files from the TTF so I can
validate a lossless round-trip for the existing BDF files.
If anyone wants to pick up
Hi George,
I think it's a nice proposal, but I'd like to provide an alternative.
The idea being that to avoid two subtables indirections, as well as
the separation of properties/non-properties you made, since I believe
it might be important to re-create a BDF font file with atoms listed
in the
So I'd like to make the following changes to David's proposal:
All of this looks very promising. I think the final decision on the
table format can only be done after converting a bunch of BDFs forth
and back.
Werner
___
Fonts mailing list
On Wed, 2005-12-14 at 22:16 +0100, David Turner wrote:
I'd like to know the following:
- is this feature useful for fontconfig / libXft ? Or should we yank
it from
FreeType ?
It's not terribly useful for fontconfig or libXft, where it is useful is
in converting sfnt back into BDF files
I tried fonttosfnt some weeeks ago and found that it uses
FT_Bitmap_Size-{height,width} for ppemY and ppemX. Shouldn't it be
ppemX = ppemY = FT_Bitmap_Size-y_ppem?
The reason that ppemX should be equal to ppemY is that an em-sqaure with
unequal ppems means x and y axes are scaled
It's not terribly useful for fontconfig or libXft, where it is useful is
in converting sfnt back into BDF files in case you want to take a font
and use it with old non-TTF supporting X servers.
Well, that you already can do, using fstobdf (it's still in the tree,
right?). Now, if there are
On Wed, 2005-12-21 at 15:18 +0100, Juliusz Chroboczek wrote:
It's not terribly useful for fontconfig or libXft, where it is useful is
in converting sfnt back into BDF files in case you want to take a font
and use it with old non-TTF supporting X servers.
Well, that you already can do,
On Wed, 2005-12-21 at 09:36 -0800, George Williams wrote:
On Thu, 2005-12-08 at 10:50, Keith Packard wrote:
should do the trick. It's reasonably functional, the plan was to use it
to eliminate BDF/PCF fonts from the X distribution and ship only TTF
files. That's been stalled for a couple of
BTW, have we finally decided that such fonts have the extension .otb?
This was discussed on the xfree86-fonts and -devel lists a long time
ago (before the events), and this was definitely the best suggestion.
In particular, it was only used by one obscure piece of MS-DOS software,
and works on
On Tue, 2006-01-17 at 15:12 -0800, George Williams wrote:
I was told so when I implemented them in fontforge. But I wasn't in the
initial discussions so I'm not the best source.
I also recall discussions which discovered that the .otb extension was
otherwise unused in most of the world. It
I also recall discussions which discovered that the .otb extension
was otherwise unused in most of the world. It doesn't matter at all
to me; I ask FreeType to try and open the font, completely ignoring
the extension has proven a valuable property, although it does
sometimes challenge the
14 matches
Mail list logo
