[ft] glyph name bug

Hi All,

any idea what's wrong with the font

    http://www.quiss.org/files/font.ttf

?

freetype tells me (via FT_Get_Glyph_Name()), that 
glyph 47 is "L", yet actually the "L" is in glyph 46, and
character 47 is empty.
It seems that all char names are shifted one position to
the right.

This font came from a pdf created (it seems) with iText 1.3
(lowagie.com).

Any help or information much appreciated. I'm using freetype 2.1.9.

Greetings,

Matthias

Re: [ft] glyph name bug

>     http://www.quiss.org/files/font.ttf
> 
> freetype tells me (via FT_Get_Glyph_Name()), that glyph 47 is "L",
> yet actually the "L" is in glyph 46, and character 47 is empty.  It
> seems that all char names are shifted one position to the right.

Please try the current CVS or FreeType 2.1.10 -- I can't repeat it.

    Werner

Re: [ft] glyph name bug

Hi,

On Wed, Dec 07, 2005 at 07:47:33PM +0100, Matthias Kramm wrote:
> freetype tells me (via FT_Get_Glyph_Name()), that 
> glyph 47 is "L", yet actually the "L" is in glyph 46, and
> character 47 is empty.
> It seems that all char names are shifted one position to
> the right.
The font's `post' table is of version 1, which means glyphs have the
standard Macintosh ordering.  Thus glyph 47 should be `L' and glyph 46
should be `K'.  It is a bug of the font.

--

-- 
Regards,
olv

Re: [ft] glyph name bug

> > freetype tells me (via FT_Get_Glyph_Name()), that glyph 47 is "L",
> > yet actually the "L" is in glyph 46, and character 47 is empty.
> > It seems that all char names are shifted one position to the
> > right.
>
> The font's `post' table is of version 1, which means glyphs have the
> standard Macintosh ordering.  Thus glyph 47 should be `L' and glyph
> 46 should be `K'.  It is a bug of the font.

Thanks, I missed that.  What do you think of extending ftview to show
the glyph name of the current glyph index, if available?  Do you have
time to implement that?

    Werner

Creating an [OT]TF font from BDF font

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 written one; I just can't 
find the relevant message in my email archive.

The next generation of the http://crl.nmsu.edu/~mleisher/xmbdfed.html editor, 
*gbdfed* (not available yet), uses the GTK+ toolkit, so it can be compiled and 
run on Windows as well as various species of Unix/Linux. I had a request to 
add the ability to create pixel fonts for use with Flash and web pages. So the 
plan is to let the user specify a set of strikes to be made into an OTF font.

P.S. Now is a good time to get in your requests for any other features to be 
included in gbdfed.

P.P.S. I'm also looking for volunteers to compile and test *gbdfed* on Windows.
--

-- 
---------------------------------------------------------------------------
Mark Leisher
Computing Research Lab            A sneer is the weapon of the weak.
New Mexico State University         -- James Russell Lowell (1819-1891)
Box 30001, MSC 3CRL
Las Cruces, NM  88003

Re: [ft] Creating an [OT]TF font from BDF font

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.
--

-- 
---------------------------------------------------------------------------
Mark Leisher
Computing Research Lab            A sneer is the weapon of the weak.
New Mexico State University         -- James Russell Lowell (1819-1891)
Box 30001, MSC 3CRL
Las Cruces, NM  88003

Re: [ft] Creating an [OT]TF font from BDF font

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.org in the xapps module

$ cvs -d :pserver:anoncvs <at> cvs.freedesktop.org:/cvs/xapps co fonttosfnt

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 properties, and be able to regenerate BDF fonts as
needed (BDF being the only X standard for font distribution).

-keith

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

[ft] Re: How to turn off anti-aliasing...

Hi,

I want to completely turn off anti-aliasing, auto-hinting, and all
other tricks freetype uses.

Jonathan

Re: [ft] Creating an [OT]TF font from BDF font

>> Can anyone recommend programs that create [OT]TF fonts from BDF fonts?

	fontforge:	http://fontforge.sourceforge.net/

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe <at> math.utah.edu  -
- 155 S 1400 E RM 233                       beebe <at> acm.org  beebe <at> computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------

[ft] otf2bdf tool...

Hi,

This is probably the wrong place, but it concerns freetype I believe.

http://dst.purevoid.org/antialiasing-to-mono.png is a screenshot of my
BDF renderer at work (I have no idea why the y-offsets are wrong), and
I'm particularly concerned about the output of Courier New  <at> 
13pt/72dpi.

To me, it seems like freetype2 is doing anti-aliasing, when using the
function: FT_Render_Glyph(face->glyph, FT_RENDER_MODE_MONO). Is there
a way to disable anti-aliasing? IMO, I think it's a bad choice if it
can't be done.

Jonathan