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
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
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 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 years as we need to preserve
all of the mystic BDF
On Sun, 2005-12-18 at 18:20, Chia-I Wu wrote:
FT_Get_BDF_Fontname(face)
FT_Get_BDF_Comments(face)
Couldn't they just be treated like normal properties?
Well they aren't in the bdf file format, they are handled quite
differently, so the bdf parser handles them differently.
The pcf file format
On Sun, 2005-12-18 at 18:20, Chia-I Wu wrote:
FT_Get_BDF_Fontname(face)
FT_Get_BDF_Comments(face)
Couldn't they just be treated like normal properties?
Ok, I have removed those entry points and made them behave like normal
properties.
This is incompatible with previous behavior. But since
George Williams wrote:
I downloaded fonttosfnt from x.org's cvs repository.
So I suggest the following patch (I have no write access to the cvs tree
myself)
To get patches into code in X.Org's CVS, please file bug reports at:
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
and
On Sat, 2005-12-17 at 18:42, Chia-I Wu wrote:
I suggest the following APIs, making iterator merely an iterator:
/* to iterate... */
FT_Get_BDF_Iterator( face, iter );
while ( FT_Iterare_BDF_Property( face, iter, name, aprop ) )
{
/* do something; */
}
/* to get property count...
On Sat, Dec 17, 2005 at 04:01:38PM -0800, George Williams wrote:
Ok, here is an iterator.
FT_GetIterate_BDF_Property(FT_Face,BDF_PropertyIteratorRec *aprop)
To get the first property set,
aprop-index = 0
(each call will automagically increment)
aprop-cnt will be set to the
Drat.
PCF fonts include the FONT keyword and value in the list of
properties. Strictly speaking FONT is not a bdf property (it comes
outside of the STARTPROPERTIES list) -- however to do round trip
conversion it is necessary.
The value is available internally as face-bdffont-name, but I don't
see
On Thu, 2005-12-08 at 10:29, Juliusz Chroboczek wrote:
You will find what I believe is the most up-to-date version of
fonttosfnt in the X.Org CVS tree. There's also a version in XFree86,
but I'm not sure it has been kept up to date.
I downloaded fonttosfnt from x.org's cvs repository.
I build
___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype
Hi George,
I just added support to this new table to FreeType, it's now in the CVS.
This is controled through TT_CONFIG_OPTION_BDF within ftoption.h
(enabled by default, at the moment).
When defined, FT_Get_BDF_Property will work IF you have previously
selected a size that correspond to one
On Wed, 2005-12-14 at 13:16, David Turner wrote:
PS: By the way, your .otb file doesn't display correctly in ftview,
I'll try
to investigate this later...
I believe this is because the three strikes I used to build the otb file
have different character sets -- none of which is complete.
On Mon, 2005-12-12 at 20:12 +0100, Juliusz Chroboczek wrote:
Keith,
I'm not quite sure what you mean by ``round-trip'', but that might be
more difficult than you think: as you've surely noticed, fonttosfnt
crops glyphs by default, as there's no reason to propagate X's ``-c-''
fonts into
: vendredi 9 décembre 2005 02:47
À : Keith Packard
Cc : freetype@nongnu.org; fonts@xfree86.org
Objet : Re: [ft] Creating an [OT]TF font from BDF font
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
I realized last night that my proposal was incomplete. I like David's
suggestion of getting rid of my separate lists (for prop/non-prop) and
including that in the type field -- however non-properties can have
non-string values and both properties and non-properties can have arrays
of integers as
Juliusz Chroboczek wrote:
You will find what I believe is the most up-to-date version of
fonttosfnt in the X.Org CVS tree. There's also a version in XFree86,
but I'm not sure it has been kept up to date.
Precisely the answer I was looking for. Thanks, Juliusz.
--
Can anyone recommend programs that create [OT]TF fonts from BDF fonts?
fontforge: http://fontforge.sourceforge.net/
---
- Nelson H. F. BeebeTel: +1 801 581 5254 -
-
Juliusz wrote fonttosfnt [...]
[...] 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 years as we need to preserve all of the mystic BDF
properties, and be able to regenerate BDF fonts as needed (BDF being
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
Hi,
Juliusz wrote fonttosfnt which combines multiple BDF sizes into a single
SFNT. It's in CVS at freedesktop.org in the xapps module
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 =
22 matches
Mail list logo
