> 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 t
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 do
> > In connection with that I wonder which of your patches you've sent
> > to the list shall go into FreeType.
>
> I rather think none. The more I looked into it the more changes I
> needed to make to the bdf loader to avoid losing information, and
> eventually I decided that freetype wasn't the r
On Mon, 2006-01-16 at 21:45, Werner LEMBERG wrote:
> In connection with that I wonder which of your patches you've sent to
> the list shall go into FreeType.
I rather think none. The more I looked into it the more changes I needed
to make to the bdf loader to avoid losing information, and eventuall
> I've finally released a build of fontforge containing the code for
> the 'BDF ' sfnt-table.
In connection with that I wonder which of your patches you've sent to
the list shall go into FreeType.
> I'm attaching two (fontforge) scripts that can be used to convert a
> bunch of bdf/pcf files into
I've finally released a build of fontforge containing the code for the
'BDF ' sfnt-table.
I'm attaching two (fontforge) scripts that can be used to convert a
bunch of bdf/pcf files into an otb and back to bdf files.
$ fontforge -script bdf2sfnt.pe outputfile.otb strike1.bdf [strike2.bdf ...]
$ fo
> 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 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 cou
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 proper
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
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 th
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 believe the entrySel field in the table directory of the
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 bui
___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype
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 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 fil
On Wed, 2005-12-14 at 13:16, David Turner wrote:
> - I don't understand completely the difference between atoms and
> non-property
> strings. Aren't these the same things ? Why distinguish them then ?
Well 5005.BDF_Spec.pdf says that the thing that comes after the FONT
keyword should be a PostScr
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 o
> 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.
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 de
> 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 sca
On Sat, 2005-12-10 at 00:42, Werner LEMBERG wrote:
> 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.
Ok. I have a version of fontforge which puts bdf properties into a
'BDF ' table in an sfnt, a
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 in
> 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
> 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
___
Freetype mailing list
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 va
Type Project (www.freetype.org)
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] la
> part de George
> Williams
> Envoyé : vendredi 9 décembre 2005 02:47
> À : Keith Packard
> Cc : freetype@nongnu.org; fonts@xfree86.org
> Obje
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 = FT_Bitmap_S
On Thu, 2005-12-08 at 16:07, 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.
Well, you would need a separate sub-table for each BDF strike.
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 p
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
> 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
>> 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 -
- Uni
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 freedesktop.
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.
--
-
Being lazy, I'm asking here before actually looking around. Can anyone
recommend programs that create [OT]TF fonts from BDF fonts?
I have Taro MURAOKA's bdf2ttf
(http://www.kaoriya.net/dist/bdf2ttf-2.0.tar.bz2), but seem to recall that
someone on one of the Freetype lists might have also writt
35 matches
Mail list logo
