Re: [ft] bold problem with some fonts

2006-10-04 Thread Werner LEMBERG

  Now I have a question about problem in bold rendering with some 
  font, for example VLGothic font (http://dicey.org/vlgothic/).

Attached is a font file which contains just the zero glyph of this
font.


Werner


zero.ttf
Description: Binary data
___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype


[ft] Testing new LCD rendering mode

2006-10-04 Thread Ismail Donmez
Hi,

I tested new libXft LCD Filtering patch and I got some screenshots to show 
too :-)

http://cekirdek.pardus.org.tr/~ismail/tmp/knode-old-lcd-rendering.png

shows the rendering with old LCD rendering patch, its all good there.

http://cekirdek.pardus.org.tr/~ismail/tmp/knode-new-lcd-filtering.png

shows the rendering with new LCD filtering patch, notice that the blurriness 
of the font makes it look bad especially when its bold, also notice there are 
color fringes which looks like the case for vanilla libXft + enabling 
subpixel hinting.

Test Environment: 8pt Tahoma, 96 dpi

I downloaded libXft-2.1.7 and applied patch libXft-2.1.7-lcd-filter-2.patch .

Thoughts?

P.S: Example application used is KNode.

Regards,
ismail


___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype


Re: [ft] Testing new LCD rendering mode

2006-10-04 Thread David Turner
Did you enable the bytecode interpreter in FreeType for the second
example ? It doesn't seem so.

Regards,

- David

On Wed, 4 Oct 2006 18:02:04 +0300, Ismail Donmez [EMAIL PROTECTED] said:
 Hi,
 
 I tested new libXft LCD Filtering patch and I got some screenshots to
 show 
 too :-)
 
 http://cekirdek.pardus.org.tr/~ismail/tmp/knode-old-lcd-rendering.png
 
 shows the rendering with old LCD rendering patch, its all good there.
 
 http://cekirdek.pardus.org.tr/~ismail/tmp/knode-new-lcd-filtering.png
 
 shows the rendering with new LCD filtering patch, notice that the
 blurriness 
 of the font makes it look bad especially when its bold, also notice there
 are 
 color fringes which looks like the case for vanilla libXft + enabling 
 subpixel hinting.
 
 Test Environment: 8pt Tahoma, 96 dpi
 
 I downloaded libXft-2.1.7 and applied patch
 libXft-2.1.7-lcd-filter-2.patch .
 
 Thoughts?
 
 P.S: Example application used is KNode.
 
 Regards,
 ismail
 
 
 ___
 Freetype mailing list
 Freetype@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/freetype




___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype


Re: [ft] Testing new LCD rendering mode

2006-10-04 Thread Ismail Donmez
04 Eki 2006 Çar 19:45 tarihinde şunları yazmıştınız:
 Did you enable the bytecode interpreter in FreeType for the second
 example ? It doesn't seem so.

Freetype library did not change between tests ( I am actually just installing 
old libXft testing, installing new libXft testing ), so I don't think thats 
the problem but I agree it just looks like that indeed.

Regards,
ismail


___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype


Re: [ft] Testing new LCD rendering mode

2006-10-04 Thread David Turner

On Wed, 4 Oct 2006 20:02:33 +0300, Ismail Donmez [EMAIL PROTECTED] said:
 04 Eki 2006 Çar 19:52 tarihinde, Ismail Donmez #351;unlar#305; 
 yazm#305;#351;t#305;: 
  04 Eki 2006 Çar 19:45 tarihinde #351;unlar#305; 
  yazm#305;#351;t#305;n#305;z:
   Did you enable the bytecode interpreter in FreeType for the second
   example ? It doesn't seem so.
 
  Freetype library did not change between tests ( I am actually just
  installing old libXft testing, installing new libXft testing ), so I don't
  think thats the problem but I agree it just looks like that indeed.
 
They're clearly different, look at the shapes of the 2 or 6, especially the
horizontal stems in these glyphs.

I think I understand now. I forgot to mention that you should enable
medium or full hinting in your fonts preference dialog. That's
because light hinting will now always invoke the auto-hinter (with the
exception of fonts which require the unpatented hinter to load properly,
e.g. MingLiU).

I believe it should remove the difference you see. If not, send more 
screenshots :-)

Regards,

- David Turner
- The FreeType Project  (www.freetype.org)



 For reference I applied the following patch to Freetype sources before 
 building.
 
 Thanks,
 ismail




___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype


Re: [ft] Testing new LCD rendering mode

2006-10-04 Thread Ismail Donmez
04 Eki 2006 Çar 20:51 tarihinde, David Turner şunları yazmıştı: 
[...]
 They're clearly different, look at the shapes of the 2 or 6, especially the
 horizontal stems in these glyphs.

 I think I understand now. I forgot to mention that you should enable
 medium or full hinting in your fonts preference dialog. That's
 because light hinting will now always invoke the auto-hinter (with the
 exception of fonts which require the unpatented hinter to load properly,
 e.g. MingLiU).

 I believe it should remove the difference you see. If not, send more
 screenshots :-)

Sadly I still see problems: 
http://cekirdek.pardus.org.tr/~ismail/tmp/knode-new-lcd-filtering-fullhinting.png

I added following to ~/.fonts.conf ( actually changed hintmedium to hintfull 
so it was already using medium hinting ) and run fc-cache after :

 match target=font 
  edit mode=assign name=hintstyle 
   consthintfull/const
  /edit
 /match

P.S: Thanks for working on these amazing set of patches. My eyes owe a lot to 
you.

Regards,
ismail


___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype


Re: [ft-devel] Z/OS status

2006-10-04 Thread Werner LEMBERG

 BTW, how are PS fonts handled on z/OS?  Or, more general, how is
 PostScript handled on z/OS?  Since PS is plain text normally, it
 could be EBCDIC also.

And another follow-up: What about BDF and PCF?  The former are pure
text files, and the latter could be different too (in case they are
based on EBCDIC text files).  Do you know a document which covers
fonts on z/OS and how they are stored and processed?


Werner


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel


Re: [ft-devel] Rendering problem with 'y' character

2006-10-04 Thread Werner LEMBERG

 Attached patch shows a rendering problem with 'y' character with
 Tahoma font (in python and system ). Notice that top-left part
 of y looks cropped.  Dpi is 96, and font size is 9 pts. I only see
 the problem when italic text is used.

Which tahoma font have you used?  I only have normal and bold, but no
slanted version.

 Does anyone know if this is a problem in KDE/Qt or a known problem?
 And how to debug this better?

Can you reproduce the bad behaviour with ftview?


Werner


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel


Re: [ft-devel] Rendering problem with 'y' character

2006-10-04 Thread Ismail Donmez
04 Eki 2006 Çar 08:13 tarihinde şunları yazmıştınız:
  Attached patch shows a rendering problem with 'y' character with
  Tahoma font (in python and system ). Notice that top-left part
  of y looks cropped.  Dpi is 96, and font size is 9 pts. I only see
  the problem when italic text is used.

 Which tahoma font have you used?  I only have normal and bold, but no
 slanted version.

I have the following :

212bc6614bb04a673ce8b93656c1dccb3415b54f  tahomabd.ttf
28bde5b328ae7e9dade8e5e9d405210578e4d52a  tahoma.ttf

  Does anyone know if this is a problem in KDE/Qt or a known problem?
  And how to debug this better?

 Can you reproduce the bad behaviour with ftview?

I am not _yet_ able to reproduce with ftview, I am wondering khtml/Qt does 
font substition somehow although I set Konqueror to use Tahoma only.

Regards,
ismail


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel


Re: [ft-devel] Z/OS status

2006-10-04 Thread Tom Quarendon

Is there a possibility for the z/OS compiler to select the encoding of
an input file?  This would be the easiest solution.


There is, but this doesn't completely work. It only covers cases where 
they may be string literals in the code which are expected to be in 
ascii. It still leaves open the possibility of there being algorithmic 
problems (there are, for example, functions called things like 
utf8_to_ascii and so on -- clearly they are broken on an EBCDIC system, 
regardless of the code page you use to compile the code). I don't find 
this a satisfactory solution.






___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel


Re: [ft-devel] Z/OS status

2006-10-04 Thread Werner LEMBERG

 I've never actually run the XWindows system on Z/OS [...]

Oops, this answers the question in my previous mail.  Still wondering
what kind of fonts are used for the z/OS graphics display...


Werner


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel


Re: [ft-devel] Rendering problem with 'y' character

2006-10-04 Thread Werner LEMBERG
  Can you reproduce the bad behaviour with ftview?

 I am not _yet_ able to reproduce with ftview, [...]

Well, it seems that Qt does slanting by itself -- this isn't supported
within ftview.


Werner


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel