Hi,
I propose to switch the handling of "-rpath" in freetype-config
during the configuration. For the compatibility with the last
release, it is expected to be disabled by default, and possible
to enable it with some option to the configure. Also it is
possible to guess if the installation desti
Understood. Thanks a lot for the explanation!
On Thu, Feb 7, 2013 at 5:35 PM, Werner LEMBERG wrote:
>
> > I think I read somewhere that TrueType should be rasterized with
> > "non-zero" rule, isn't that true?
>
> This is correct.
>
> > Yes, I know FreeType supports both rules - I'm asking why i
Thanks for the reply!
On Thu, Feb 7, 2013 at 1:00 PM, Werner LEMBERG wrote:
>
> How do you come to the impression that TrueType fonts are handled with
> the even-odd rule?
Do you mean "non-zero"? Because I said TrueType should be using "non-zero"
rule (and not "even-odd"). I think I read some
> I think I read somewhere that TrueType should be rasterized with
> "non-zero" rule, isn't that true?
This is correct.
> Yes, I know FreeType supports both rules - I'm asking why it is the
> case. Is the reason that it is "generic module" and can be used for
> different purposes than font rend
> Why does FreeType implement the "even-odd" fill rule? TrueType fonts
> are supposed to be filled with "non-zero" rule, I cannot think of a
> situation where "even-odd" would be needed.
How do you come to the impression that TrueType fonts are handled with
the even-odd rule? It is possible to m
Hello,
I'm new here, hope it's ok to post such message in "freetype-devel",
instead of "freetype" as I'm specifically interested in developers' opinion.
Why does FreeType implement the "even-odd" fill rule? TrueType fonts are
supposed to be filled with "non-zero" rule, I cannot think of a situati
