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
|
<!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=%3C201105131209.18049.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="004655.html">
<LINK REL="Next" HREF="004660.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=%3C201105131209.18049.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 12:09:17 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="004655.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI>Next message: <A HREF="004660.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4656">[ date ]</a>
<a href="thread.html#4656">[ thread ]</a>
<a href="subject.html#4656">[ subject ]</a>
<a href="author.html#4656">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Friday, 13 May 2011 11:12:41 Zé wrote:
><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 about
</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 existant
</I>><i> >>> 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>
No, this is not what is covered in this bug report.
Firstly, here are the non-problems:
1)The bytecode interpreter *can* make fonts look better, *if* they have
hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS
fonts *do* have hinting.
So, historically, the recommended approach was to use the PLF freetype *if*
you had imported MS fonts (e.g. from a dual-boot Windows installation).
2)The Freetype autohinter was implemented later, and improves things for
unhinted fonts, but hinted fonts still looked better with the bytecode
interpreter.
This is the problem:
3)If the bytecode interpreter was enabled, auto-hinting was disabled (or,
could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts.
The Fedora bug isn't about disabling the bytecode interpreter, but by still
allowing auto-hinting for unhinted fonts if the bytecode interpreter.
*This* is the right fix. Your insistence to *disable* the bytecode interpreter
(leaving users with *no* options, in case they need hinted fonts) is the wrong
fix.
But, thanks for the pointer to the bug, which points to the patches.
><i> Why dont we also do the same thing?
</I>><i>
</I>><i> Since theres users complaining about it, why not solve it once for all?
</I>
Regards,
Buchan
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004655.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI>Next message: <A HREF="004660.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4656">[ date ]</a>
<a href="thread.html#4656">[ thread ]</a>
<a href="subject.html#4656">[ subject ]</a>
<a href="author.html#4656">[ 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>
|
