1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20why%20not%20disable%20bytecode%20interpreter%20in%20freetype2%20%3F&In-Reply-To=%3C201105131746.38818.bgmilne%40staff.telkomsa.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="004660.html">
<LINK REL="Next" HREF="004661.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] why not disable bytecode interpreter in freetype2 ?</H1>
<B>Buchan Milne</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20why%20not%20disable%20bytecode%20interpreter%20in%20freetype2%20%3F&In-Reply-To=%3C201105131746.38818.bgmilne%40staff.telkomsa.net%3E"
TITLE="[Mageia-dev] why not disable bytecode interpreter in freetype2 ?">bgmilne at staff.telkomsa.net
</A><BR>
<I>Fri May 13 17:46:38 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="004660.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI>Next message: <A HREF="004661.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4662">[ date ]</a>
<a href="thread.html#4662">[ thread ]</a>
<a href="subject.html#4662">[ subject ]</a>
<a href="author.html#4662">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Friday, 13 May 2011 17:28:24 Zé wrote:
><i> 2011/5/13 Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at staff.telkomsa.net</A>>:
</I>><i> > On Friday, 13 May 2011 11:12:41 Zé wrote:
</I>><i> >> 2011/5/13 Zé <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mmodem00 at gmail.com</A>>:
</I>><i> >> > 2011/5/13 Dimitrios Glentadakis <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dglent at gmail.com</A>>:
</I>><i> >> >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
</I>><i> >> >>> 2011/5/12 Dick Gevers <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dvgevers at xs4all.nl</A>>:
</I>><i> >> >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote
</I>><i> >> >>> > about
</I>><i> >> >>>
</I>><i> >> >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
</I>><i> >> >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER \*/|'
</I>><i> >> >>> include/freetype/config/ftoption.h
</I>><i> >> >>>
</I>><i> >> >>>
</I>><i> >> >>> dont forget to also increase Release to avoid conflicts with
</I>><i> >> >>> existant freetype2, and then build the package.
</I>><i> >> >>
</I>><i> >> >> Why do all these things when you can simply add an entry in the
</I>><i> >> >> font.conf file ?
</I>><i> >> >
</I>><i> >> > Thats a fact, but hat should happen is that freetype2 should have
</I>><i> >> > bytecode interpreter disabled by default, since so far users prefer
</I>><i> >> > it.
</I>><i> >>
</I>><i> >> Seams Fedora choosed to finally fix it, it reverted freetype2 with a
</I>><i> >> patch to disable bytecode interpreter. ->
</I>><i> >> <A HREF="https://bugzilla.redhat.com/show_bug.cgi?id=547532">https://bugzilla.redhat.com/show_bug.cgi?id=547532</A>
</I>><i> >
</I>><i> > No, this is not what is covered in this bug report.
</I>><i>
</I>><i> Yes, correct i miss understood what as the bug report about.
</I>><i>
</I>><i> > Firstly, here are the non-problems:
</I>><i> > 1)The bytecode interpreter *can* make fonts look better, *if* they have
</I>><i> > hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the
</I>><i> > MS fonts *do* have hinting.
</I>><i> >
</I>><i> > So, historically, the recommended approach was to use the PLF freetype
</I>><i> > *if* you had imported MS fonts (e.g. from a dual-boot Windows
</I>><i> > installation).
</I>><i>
</I>><i> Well i always avoid using PLF freetype and for what i have read in
</I>><i> ML's all the users that answered to it said that also avoid PLF
</I>><i> freetype.
</I>><i>
</I>><i> So far for hat i have seen, all users prefered like fonts were
</I>><i> rendered wen patents were still valid...
</I>
Were *all* these users using *hinted* fonts? I think they weren't using hinted
fonts at all.
><i> > 2)The Freetype autohinter was implemented later, and improves things for
</I>><i> > unhinted fonts, but hinted fonts still looked better with the bytecode
</I>><i> > interpreter.
</I>><i> >
</I>><i> >
</I>><i> > This is the problem:
</I>><i> > 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or,
</I>><i> > could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts.
</I>><i> >
</I>><i> > The Fedora bug isn't about disabling the bytecode interpreter, but by
</I>><i> > still allowing auto-hinting for unhinted fonts if the bytecode
</I>><i> > interpreter.
</I>><i> >
</I>><i> > *This* is the right fix. Your insistence to *disable* the bytecode
</I>><i> > interpreter (leaving users with *no* options, in case they need hinted
</I>><i> > fonts) is the wrong fix.
</I>><i>
</I>><i> Well this way users cant also set to have autohint, seams theres
</I>><i> always some app failing.
</I>
?
We need to apply the patch that enables the autohinter for unhinted fonts,
even if the bytecode interpreter is enabled, that is available from the bug
report for which you provided the link.
><i> Why not having it disabled by default?
</I>
So, you haven't read what I wrote in (3)?
><i> users will always be able to
</I>><i> set their preferences about using or not autohint, but that way
</I>><i> ensures that all fonts are better rended.
</I>
No, you ignore the case where some hinted fonts are almost unusable without
the bytecode interpreter, and others where they are rendered better.
><i> All this came up after patents end in wich showed users how fonts
</I>><i> appear poor rended, until that point i didnt saw any complains about
</I>><i> fonts, and this is what should be fixed.
</I>
You contradict yourself ... and you can't make blanket statements of "how
fonts appear poor rended", as it depends on the font (and whether it is hinted
or not).
Regards,
Buchan
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004660.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI>Next message: <A HREF="004661.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4662">[ date ]</a>
<a href="thread.html#4662">[ thread ]</a>
<a href="subject.html#4662">[ subject ]</a>
<a href="author.html#4662">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
