Just an FYI... I've found a few issues with the patch I've submitted
here, as well as some additional enhancements. So at this moment, I
still don't think these modifications would be ready for integration
into Freetype.
On 09/09/2010 06:49 PM, Moony wrote:
I've updated the patch
I've updated the patch in accordance with your requests. The first
patch adds the subpixel hinting functionality, without enabling it. The
second patch enables the functionality. I've removed entirely the
emboldening patch, as it is unrelated to subpixel hinting.
You mentioned smaller patch
Yes, I will certainly do the things you are requesting.
Again, this should moved to a different patch.
I would be glad to incorporate your work, but I need smaller patch
sets split into logical units, with no tabs and better formatting in
accordance with the rest of the FreeType code
Also... there are a couple other patches included in this one, that can
/ would be disabled by default, like zipped fonts, etc.
Another feature that I've enabled in this version of the patch is one
that makes the emboldening function ignore the Y direction. In my
opinion, it looks
Yes, I can do that. Perhaps I use FT_LOAD_SUBPIXEL_HINTING instead? Or
do you want to use FT_LOAD_CLEARTYPE_HINTING so that people understand
what this is attempting to duplicate? Just looking at it from a
trademark point-of-view.
I would also like to get others to test the patch before
Yes, I used the grayscale hinting setting for a few reasons. Perhaps
I'm not completely understanding what I am doing, but my reasons were this:
- Currently in Freetype, there is a setting for grayscale vs. bi-level
TT hinting, however in reality there exists only TT bi-level hinting.
In
Ah yes, you have found the major weaknesses of the patch. :) I am
still trying to determine why DejaVu doesn't seem to be hinted at all,
or very poorly, and why Palatino doesn't render. On the other hand,
Liberation fonts and most legacy MS fonts look great. Some Apple ones
look good and
Here is an updated patch that does a better job of setting the stage for
a split between grayscale and subpixel. I'm still forcing subpixel in
ttinterp.c because there AFAIK there is no way to set this with
fontconfig currently.
http://www.infinality.net/blog/?p=67
___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype
Hi Werner,
Another thing I'm struggling with is how to detect whether points
have been touched in the non-freedom vector direction during
deltaps. Do you have any insights into this, Werner?
Can you elaborate? What do you want to achieve?
I think I've gotten past this problem by
While hinting, the four extra phantom points which control the
horizontal and vertical advance width aren't handled specially.
However, they are stored separately (`pp1' to `pp4' in the `TT_Loader'
structure). In ttgload.c, the `TT_LOADER_SET_PP' macro sets them; and
in `compute_glyph_metrics'
, such as n, m,
h, or u and also leaving enough room for certain glyphs, like v, w,
X, etc. Any thoughts on this?
I like the idea about adding PGM output... seems relatively easy to
implement.
-Moony
Freetype-rendered, using default LCD filter:
http://www.infinality.net/files/arial-default
Sorry- I said PGM in the last email- I meant PPM!
On 03/13/2010 03:12 PM, Werner LEMBERG wrote:
A nice option to ftview/ftdiff might be png output!
WL Go forth and add it! However, I rather suggest to produce an
WL image in the PGM image format
Or ppm, given that each supports
I think in general, the modern, free, replacement fonts render pretty
well. Liberation is also worth checking out. I personally like the
shapes of the MS versions, when they render correctly at least, but the
open source versions are very well done. Here is a sample of DejaVu
bold and
Werner,
I am totally fine with calling this whatever you'd like. Subpixel
hinting makes sense to me.
2010-03-10:
* Changed the function names to end in _sph instead of _ttslight
* Added code back in that deals with x, and divided distance by 32,
instead of ignoring completely.
* Removed
I'm very grateful that you take some time to play with these things...
Thanks... the biggest thing I have going for me is that I really,
really want the end result. Other than that, I'm pretty clueless about
freetype and truetype, and know a little bit about fonts and font
rendering.
Slowly but surely
http://www.infinality.net/files/ttinterp.c.patch
http://www.infinality.net/files/segoeuii22.png
http://www.infinality.net/files/trebucbd12.png
http://www.infinality.net/files/segoeui12.png
http://www.infinality.net/files/verdana17.png
Slowly but surely
http://www.infinality.net/files/ttinterp.c.patch
http://www.infinality.net/files/segoeuii22.png
http://www.infinality.net/files/trebucbd12.png
http://www.infinality.net/files/segoeui12.png
http://www.infinality.net/files/verdana17.png
/typography/cleartype/truetypecleartype.aspx
-Moony
___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype
I've found that this small hack/patch does amazing things toward a
CT-like rendering, when TT interpreter is enabled at compile time:
--- ttinterp.c.orig 2010-02-23 18:48:43.0 -0600
+++ ttinterp.c 2010-02-23 18:49:16.0 -0600
@@ -1641,7 +1641,7 @@
{
FT_UNUSED_EXEC;
of
interpreting looks substantially better than most alternatives, and is
well worth it for fonts you are looking at for 10+ hours per day.
Thanks,
Moony
___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype
21 matches
Mail list logo
