Re: ftview segfault on ArefRuqaaInk-Regular.ttf (one of google web fonts)

[Werner LEMBERG]

> You guys seem to be talking about something different than what I am
> experiencing?  I found that it is "-l 1" (antializing) which is
> consuming a lot of memory then segfault.  Any of 0,2-6 are fine, and
> all of them b/w (despite it being a colour font).  Git head differs
> from 2.13 only in the zero(?) width glyphs as green vs red.

You mean `ftview`, right?  I cannot repeat this.  Using current git,

```
ftview -l 1 -kZ ArefRuqaaInk-Regular.ttf 
```

works just fine (`-kZ` switches off SVG rendering).  And yes, B/W (or
rather gray-scale) output is expected since FreeType doesn't support
'COLR' v1 rendering.

> Also found small bug / confusion in the man page - you talk about
> "render(ing) mode" 0 to 6, but in F1, "render mode" is 1 to 5 (all
> glyphs, strokes, given strings, water falls etc).  What "-l" does is
> changing the lcd mode. What render mode in F1 partially corresponds
> to the -m command line switch.

Thanks, fixed in git.

> Anyway, the segfault seems to be related to antialiasing,

Maybe you can run a debugger or valgrind to get more information.


    Werner