Antialiasing and bold text

[GoogleCodeExporter]

A feature request.

1. use fb in true rgb way if available (do not use the 256-color palette to
convert 8bpp color to 32bpp), then render text to screen with its
antialiasing, hinting feature;

2. use bold font (bitmap or vector) when text is bold (<esc>[1m); if bold
font not availble, try to embolden it or use regular one.

What version of the product are you using? On what operating system?
fbterm-1.5, Debian GNU/Linux testing (squeeze)

Original issue reported on code.google.com by gnu...@gmail.com on 2 May 2009 at 7:57

[GoogleCodeExporter]

Request 1 seems to have something to do with fontconfig. After commenting out 
the
line `load_flags |= FT_LOAD_TARGET_MONO;' around line 244 in font.cpp, 
everything
goes well. 

In fbterm-1.5/src/font.cpp around line 220, is it `FT_New_Face(ftlib, (const 
char
*)name, id, &face)' that overwrites previous FcPattern in fontList->fonts[] 
which
contains configurations from fonts.conf? It seems FcPatternGetBool() from 
overwritten
pattern will return incorrect/undesired value.

If this is a bug or not, anyway, it is still a feature to request that proper
antialiasing and hinting style to be used only in real rgb way, otherwise
FT_PIXEL_MODE_GRAY still renders blurry font. 

Original comment by gnu...@gmail.com on 2 May 2009 at 10:39

[GoogleCodeExporter]

1. These are not bugs. It seems like you misunderstand technologies like 
antialias,
hinting. I guess the feature you requested is subpixel rendering, which is 
useful for
small font size. On text console, most users execute FbTerm with large font 
size, so
there isn't a plan to implement this feature in FbTerm.

2. linux tty utilizes special color for text with attributes like bold, italic,
underline, etc. The goal of FbTerm is compatible with linux tty. Some fonts 
don't
have a bold or italic version, especially for CJK fonts, and the auto-generated
glyphs by freetype for these fonts are ugly.

Original comment by zgchan...@gmail.com on 4 May 2009 at 3:58

[GoogleCodeExporter]

Original comment by zgchan...@gmail.com on 14 Nov 2009 at 2:09

• Changed state: WontFix

[GoogleCodeExporter]

I rechecked the source of fbterm-1.6, found that you've used 
FT_LOAD_TARGET_LIGHT in font.cpp when 
rendering glyphs with hinting. I think this is where my problem lies. 
FT_LOAD_TARGET_LIGHT implies 
FT_LOAD_FORCE_AUTOHINT which makes generated glyphs more fuzzy than usual and 
especially unclear 
under terminal. Why not FT_LOAD_TARGET_LCD or even FT_LOAD_TARGET_NORMAL for 
clearer 
appearance? Anyway this will not be a new feature but just fix of existing one.

Original comment by gnu...@gmail.com on 25 Feb 2010 at 3:49

Attachments:

• light.png
• normal.png