[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft-devel] gamma correction and stem darkening

From: Patrick Lam
Subject: Re: [ft-devel] gamma correction and stem darkening
Date: Tue, 19 Jan 2016 16:39:13 +0100

JROT: yes, none of the Noto fonts use it, but other fonts do. The
right way to support it in a bytecode analysis tool is probably to
rewrite the bytecode to not use it. There is partial support for JROT
right now, but it is not complete.

Regeneration of TrueType bytecode should be fairly straightforward; it
just requires some development resources.

As I have time I've been going through the code and refactoring it, etc.


On Tue, Jan 19, 2016 at 4:31 PM, Behdad Esfahbod
<address@hidden> wrote:
> [+Patrick Lam]
> On 16-01-19 04:16 PM, Werner LEMBERG wrote:
>>>> I think it *is* possible.  The method, as implemented by
>>>> Toshiya-san, compares various SFNT table checksums.  Among them is
>>>> the `cvs ' table, and modifying this table is essentially
>>>> impossible without interpreting and changing the bytecode.  Ditto
>>>> for `fpgm'.  I dare to say that even a subsetted font with a single
>>>> glyph contains the original `cvs ' and `fpgm' tables unmodified,
>>>> which should enable FreeType to discover its trickyness.
>>> Note that this will eventually change ;).
>> Interesting.  Reading the thesis (from 2014) I see that they don't
>> mention ttfautohint, which really suprises me.  It also says that some
>> instructions like JROT[] aren't supported because they couldn't find
>> fonts that use it.  Well, fonts auto-hinted with ttfautohint *do* use
>> it :-)  [It seems that the git repository has added support meanwhile.]
>> Of course, the most difficult part IMHO is the regeneration of
>> TrueType code,
> I wouldn't say it's the most difficult part.  But yes, it's not implemented so
> far.
>>  which is not covered in the thesis.  Has this been
>> implemented meanwhile?  There is no real documentation of the code in
>> the git repository...
> Let's discuss it on the github issue:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]