On Tuesday 20 August 2002 9:57 pm, Juliusz Chroboczek wrote:
| OT> I'm pretty sure Microsoft ships a number of .ttf files with only
| OT> bitmaps and no outlines with Windows...
|
| Interesting. Which ones?
GulimChe.ttf (Korean lang.font) has enermous amount of bitmaps, I think, for
all poin
On Tuesday 20 August 2002 9:32 pm, Keith Packard wrote:
| Around 19 o'clock on Aug 20, Pablo Saratxaga wrote:
| > Yes, I agree. My concern was for programs not using fontconfig (like in
| > other OS), or using freetype at a very low level and expecting there
| > are always outlines; as if the
OT> I'm pretty sure Microsoft ships a number of .ttf files with only
OT> bitmaps and no outlines with Windows...
Interesting. Which ones?
Juliusz
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mai
PS> what will happen if one of such programs tries to use a bitmap
PS> only font for displaying at a size for xhich there are no bitmaps
PS> embedded ?
It will get sixty-odd thousand blank glyphs.
Juliusz
___
Fon
Around 19 o'clock on Aug 20, Pablo Saratxaga wrote:
> Yes, I agree. My concern was for programs not using fontconfig (like in
> other OS), or using freetype at a very low level and expecting there
> are always outlines; as if the bitmap only fonts cause problems with those,
> then bad press coul
Kaixo!
On Tue, Aug 20, 2002 at 10:50:09AM -0400, Owen Taylor wrote:
> I'm pretty sure Microsoft ships a number of .ttf files with only bitmaps and
> no outlines with Windows...
And what happens when a size not covered is requested ?
I find it difficult to believe that there would be ttf fonts
> So, using a different extension name will solve a lot of trouble.
Note that fontconfig doesn't care what the extension is; it scans every
file to see if it's a font.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Font
Pablo Saratxaga <[EMAIL PROTECTED]> writes:
> Kaixo!
>
> On Tue, Aug 20, 2002 at 05:44:13PM +0400, Vadim Plessky wrote:
>
> > | You should also decide on an extenson name other than .ttf, to avoid
> > | that those bitmap only ttf files get confused wwith real scalable
> > | fonts by people
Kaixo!
On Tue, Aug 20, 2002 at 05:44:13PM +0400, Vadim Plessky wrote:
> | You should also decide on an extenson name other than .ttf, to avoid
> | that those bitmap only ttf files get confused wwith real scalable
> | fonts by people out there, otherwise there would be a lot of bad
> | conseq
On Tuesday 20 August 2002 1:21 am, Pablo Saratxaga wrote:
| Kaixo!
|
| On Mon, Aug 19, 2002 at 07:35:33PM +0200, Juliusz Chroboczek wrote:
| > I'm currently exploring the possibility of moving XFree86 from the PCF
| > format to the sfnt format for bitmap fonts. I've encountered a number
|
|
Kaixo!
On Mon, Aug 19, 2002 at 07:35:33PM +0200, Juliusz Chroboczek wrote:
> I'm currently exploring the possibility of moving XFree86 from the PCF
> format to the sfnt format for bitmap fonts. I've encountered a number
You should also decide on an extenson name other than .ttf, to avoid
that
Hello,
Thanks a lot for the previous fix, I'll try it out tonight.
I'm currently exploring the possibility of moving XFree86 from the PCF
format to the sfnt format for bitmap fonts. I've encountered a number
of minor bugs in FreeType 2.1.2 that prevent me from using such
bitmap-only sfnts.
1.
12 matches
Mail list logo