> Define 'improve hinting'. It's not clear to me what you actually want to achieve. Currently we are using FT_LOAD_RENDER | FT_LOAD_TARGET_MONO | FT_LOAD_MONOCHROME and still seeing very bad appearance So not sure if I missed anything there in order for the monochrome character to look nicer?
Thank You. Best Regards JM Moon On Wed, 8 Nov 2023 at 13:35, Werner LEMBERG <w...@gnu.org> wrote: > >> No, (good) auto-hinting is not available for monochrome display. > > > > Does this mean even if I load the glyph with FT_LOAD_FORCE_AUTOHINT, > > the autofit algorithm also will not perform any hinting? > > It will perform hinting but expect very ugly results. > > > I'm using the TrueType font, any way to improve the hinting other > > than FT_LOAD_TARGET_MONO? > > Define 'improve hinting'. It's not clear to me what you actually want > to achieve. > > >> A segmentation fault shouldn't happen; I guess you are forgetting > >> to check a return value somewhere. If the problem persists please > >> provide a small stand-alone code snippet for testing purposes that > >> I can compile and run on the command line. > > > > bad case : Segmentation fault "potentially unexpected fatal signal 11" > > -->tried with combination of > > FT_LOAD_RENDER | FT_LOAD_FORCE_AUTOHINT > > FT_LOAD_RENDER | FT_LOAD_TARGET_MONO | FT_LOAD_FORCE_AUTOHINT > > FT_LOAD_RENDER | FT_LOAD_MONOCHROME | FT_LOAD_FORCE_AUTOHINT > > Thanks, but these images don't help in any way to identify a possible > bug in FreeType. As I said, I need a small, compilable, stand-alone > snippet (written in C) that runs on the command line and exhibits the > problem. This means some work on your side to reduce your code as > much as possible – you are done if removing anything from the example > no longer triggers the problem. > > > Werner >
