[Fonts] Re: where to include ~/.fonts.conf

2003-02-08 Thread Mike FABIAN 
James Richard Tyrer [EMAIL PROTECTED] $B$5$s$O=q$-$^$7$?(B:
(B
(B Mike FABIAN wrote:
(B James Richard Tyrer [EMAIL PROTECTED] $B$5$s$O=q$-$^$7$?(B:
(B
(BMike FABIAN wrote:
(B
(BI wonder where in /etc/fonts.fonts.conf exactly is the best
(Bplace to put the include statement for ~/.fonts.conf.
(BIt cannot be at the very end of /etc/fonts/fonts.conf because
(Bthen the following would not work:
(B
(BPut it at the end of the list starting with:
(B
(B dir/usr/X11R6/lib/X11/fonts/dir
(B But if ~/.fonts.conf is included there (i.e. very early in
(B /etc/fonts/fonts.conf), it is not possible to override the rules from
(B /etc/fonts/fonts.conf in the personal ~/.font.conf file.
(B
(B I appear to need more sleep as I have given the correct answer, but it
(B sappers to be for the wrong question -- not the one which you asked.
(B
(B Doesn't you: "fonts.conf" file already have the line:
(B
(B   include ignore_missing="yes"~/.fonts.conf/include
(B
(B in it?
(B
(BYes, it is already  there in the /etc/fonts/fonts.conf
(Bfrom XFree86 CVS. But it is included rather close to
(Bthe top of fonts.conf and followed by many rules.
(BI experimented a bit and it appears to me, that I cannot
(Boverride these rules by anything I write into ~/.fonts.conf
(Bbecause the rule which comes last always wins.
(B
(BTo make it possible to override as much as possible of
(Bthe global settings  in /etc/fonts/fonts.conf with user
(Bpreferences in ~/.fonts.conf, it seems to be better
(Bto put the line
(B
(Binclude ignore_missing="yes"~/.fonts.conf/include
(B
(Bat the end of /etc/fonts/fonts.conf.
(B
(BObviously rules which depend on special settings in ~/.fonts.conf
(Bmust follow below the line
(B
(Binclude ignore_missing="yes"~/.fonts.conf/include
(B
(Bfor example Keith's trick with "prefer_outlines".
(B
(BBut I couldn't find a reason to put anything else below this line,
(Btherefore I wondered why it isn't already close to the bottom in
(BXFree86 CVS and whether that should be changed.
(B
(BOr am I overlooking something?
(B
(B-- 
(BMike Fabian   [EMAIL PROTECTED]   http://www.suse.de/~mfabian
$B?gL2ITB-$O;E;v$NE($@!#(B
(B___
(BFonts mailing list
([EMAIL PROTECTED]
(Bhttp://XFree86.Org/mailman/listinfo/fonts

Re: [Fonts] Re: where to include ~/.fonts.conf

2003-02-08 Thread Keith Packard 
Around 22 o'clock on Feb 8, Mike FABIAN wrote:

 To make it possible to override as much as possible of
 the global settings  in /etc/fonts/fonts.conf with user
 preferences in ~/.fonts.conf, it seems to be better
 to put the line

The subtleties of the contents of /etc/fonts/fonts.conf appear to be lost 
here.  The placement of the include of ~/.fonts.conf is intended to 
carefully allow overriding of all of the values in /etc/fonts/fonts.conf.

In particular, because prefer aliases insert names directly ahead of the 
matching family, the sequence:

!-- in ~/.fonts.conf --

alias
familysans-serif/family
prefer
familyArial/family
/prefer
/alias

...
!-- in /etc/fonts/fonts.conf --

alias
familysans-serif/family
prefer
familyNimbus Sans/family
/prefer
/alias

results in the family list

Arial,Nimbus Sans,sans-serif

As you see, in this case the users preferred font (arial) takes precedence 
over the system default.

That's the bulk of the configuration below the include of ~/.fonts.conf.

The only other rules below ~/.fonts.conf are to map PostScript families to 
TrueType equivalents.  Perhaps those should be moved above the include,
I don't have a strong opinion.

-keith


___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts

[Fonts] No bitmapped fonts in Qt 3.1.1

2003-02-08 Thread Nathaniel Gray 
I've got the same problem.  I don't know if it's a Qt problem or an X 
problem though.

XFree86 4.2.99.4, Qt 3.1.1, KDE 3.1

Cheers,
-n8
-- 
-- Nathaniel Gray -- Caltech Computer Science --
-- Mojave Project -- http://mojave.cs.caltech.edu --

___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts

Re: [Fonts] A serious problem about freetype module

2003-02-08 Thread Chisato Yamauchi 
  Ok.

  This problem is buffer overflow fundamentally.  By applying
the following patch, the crash is avoidable.

*** xc/lib/font/FreeType/ftfuncs.c.orig 2002-10-03 00:06:12.0 +0900
--- xc/lib/font/FreeType/ftfuncs.c  2003-02-08 15:45:38.0 +0900
***
*** 600,609 
  bpr = (((wd + (instance-bmfmt.glyph3) - 1)  3)  
 -instance-bmfmt.glyph);
  if(tgp) {
! raster = (char*)xalloc(ht * bpr);
  if(raster == NULL) 
  return AllocError;
! memset(raster, 0, ht * bpr);
  }
  
  if(dx == 0  dy == 0  bpr == bitmap-pitch) {
--- 600,609 
  bpr = (((wd + (instance-bmfmt.glyph3) - 1)  3)  
 -instance-bmfmt.glyph);
  if(tgp) {
! raster = (char*)xalloc((ht+2) * bpr);
  if(raster == NULL) 
  return AllocError;
! memset(raster, 0, (ht+2) * bpr);
  }
  
  if(dx == 0  dy == 0  bpr == bitmap-pitch) {


  Not (ht+2) but (ht+1) may be more appropriate.  However, I
think that (ht+2) is safer.  Since the calculation of metric
may be wrong.

  I'd like the maintainer of freetype module to investigate
in detail.


Chisato Yamauchi
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts

Re: [Fonts] A serious problem about freetype module

2003-02-08 Thread Chisato Yamauchi 
 Can you reproduce this bug with ftview?
 

  No.

  I don't know how to view 2-bytes fonts with ftview.
This crash occurs only with jisx0208.1983 rgstry.
I also confirmed the crash with xfd.


Chisato Yamauchi
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts