>> (a) ignore changes of the horizontal advance widths due to hinting
>> instructions (not implemented yet), and
>>
>> (b) ensure that all instructions behave correctly even if the
>> horizontal resolution is increased (this is ClearType
>> compatibility mode, already implemented).
>
>
If the entire text could be made available in a formatted and readable
form, I would be happy to proof-read it for typos, grammar and correct
English.
Gladly! Love must be spread correctly (old German sentiment). Thanks :)
freetype-262-blog.odt
Description: application/vnd.oasis.opendocument.t
On 6 December 2015 at 22:42, Nikolaus Waxweiler wrote:
> Would you be willing to host the site on Github Pages?
>>
>> http://pages.github.com
>>
>
> Is this addressed to Werner?
Yes
> I personally would vote in favor of moving the FreeType site and main code
> repository to GitHub, simply bec
On 06/12/2015 15:19, Nikolaus Waxweiler wrote:
The autohinter has a new toggable stem darkening property
A couple of typos:
"The autohinter has a new toggable stem darkening property": The word
'toggable' doesn't exist. I think you mean 'toggleable' (although that
is not the happiest of coina
Would you be willing to host the site on Github Pages?
http://pages.github.com
Is this addressed to Werner? I personally would vote in favor of moving
the FreeType site and main code repository to GitHub, simply because
it's the most popular service with the largest user base and has nice
th
On 1 December 2015 at 04:07, Werner LEMBERG wrote:
> Basically, I don't object.
Would you be willing to host the site on Github Pages?
http://pages.github.com
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/
2nd revision of my post. Reorganized headings and tried to better
explain the blending examples.
diff --git a/index.html b/index.html
index c92d541..e4493a0 100644
--- a/index.html
+++ b/index.html
@@ -106,71 +106,9 @@
FreeType 2.6.2 ships with three interesting details for
It must
(a) ignore changes of the horizontal advance widths due to
hinting instructions (not implemented yet), and
(b) ensure that all instructions behave correctly even if the
horizontal resolution is increased (this is ClearType
compatibility mode, already implemente