> Recently some ClearType byte code interpreter patents have
> expired. Subpixel rendering ones, not quite. Most of them expired in
> November last year, but these are still active until end of July:
>
> https://patents.google.com/patent/US6282327
> https://patents.google.com/patent/US6393145
>
Dear Development Team,
Recently some ClearType byte code interpreter patents have
expired. Subpixel rendering ones, not quite. Most of them expired in
November last year, but these are still active until end of July:
https://patents.google.com/patent/US6282327
> I have the following approach in mind:
>
> - Code the new stuff in the repo
> - Write a program (with a `main' function) that will eventually
> trigger the "newly added" part somehow.
> - Use GDB to set a break point on the "newly added" part and then
> step through it and confirm whether
Hi Moazin,
> I want to inquire about how FreeType devs, whenever they are fixing a bug or
> adding a new feature, code and test the new additions?
I think everyone has their own way of approaching it, just quickly highlighting
my approach and, TLDR; your approach pretty much sums it up IMO --
Hi,
I want to inquire about how FreeType devs, whenever they are fixing a bug
or adding a new feature, code and test the new additions?
I have the following approach in mind:
- Code the new stuff in the repo
- Write a program (with a `main' function) that will eventually trigger the
"newly
