On Mon, 5 Nov 2018 16:54:37 +0100, Fredrik Roubert <fred...@roubert.name> wrote: > On Mon 05 Nov 2018 at 23:26 +0900, Byeongsik Jeon wrote: > >> - v35: MS cleartype font(ex. Consolas) rendering is ugly. >> - v40: MS legacy font rendering is ugly. > > See this related question with answers from last year: > > http://lists.nongnu.org/archive/html/freetype/2017-09/msg00031.html >
Exactly. Thank you. My problem is that I applied only FT_LOAD_DEFAULT. In v35, the hinter was activated by this alone. But it didn’t work on v40. FT_LOAD_TARGET_XXX was used to solve it. But only the B/W hinted rendering. In the runtime, what is the appropriate way to render the MS legacy fonts(Tahoma, Arial, ...) as v35 and the MS ClearType fonts(Consolas, ...) as v40? Microsoft Windows GDI displays two types of fonts at the same time. PSEUDO CODE: ---- gasp_version = get_gasp_version( font ); interpreter_version = gasp_version ? 40 : 35; LOCK(); FT_Property_Set( ..., &interpreter_version ); FT_Load_Glyph( ..., load_flags ); UNLOCK(); ---- Is there any problem with this method? Or is there another appropriate solution? I think it would be possible for FT_Load_Glyph to implement this operation on its own without FT_Property_Set. Is there any plan that the Freetype will provide this characteristic? _______________________________________________ Freetype mailing list Freetype@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype
