summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110513/004660.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110513/004660.html')
-rw-r--r--zarb-ml/mageia-dev/20110513/004660.html141
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110513/004660.html b/zarb-ml/mageia-dev/20110513/004660.html
new file mode 100644
index 000000000..3b7e4968b
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110513/004660.html
@@ -0,0 +1,141 @@
+<!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=%3CBANLkTinSNRp2BvA6QjrO%3DgOZn8Zsc5-MiQ%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="004656.html">
+ <LINK REL="Next" HREF="004662.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] why not disable bytecode interpreter in freetype2 ?</H1>
+ <B>Z&#233;</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=%3CBANLkTinSNRp2BvA6QjrO%3DgOZn8Zsc5-MiQ%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] why not disable bytecode interpreter in freetype2 ?">mmodem00 at gmail.com
+ </A><BR>
+ <I>Fri May 13 17:28:24 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="004656.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
+</A></li>
+ <LI>Next message: <A HREF="004662.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4660">[ date ]</a>
+ <a href="thread.html#4660">[ thread ]</a>
+ <a href="subject.html#4660">[ subject ]</a>
+ <a href="author.html#4660">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>2011/5/13 Buchan Milne &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at staff.telkomsa.net</A>&gt;:
+&gt;<i> On Friday, 13 May 2011 11:12:41 Z&#233; wrote:
+</I>&gt;&gt;<i> 2011/5/13 Z&#233; &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mmodem00 at gmail.com</A>&gt;:
+</I>&gt;&gt;<i> &gt; 2011/5/13 Dimitrios Glentadakis &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dglent at gmail.com</A>&gt;:
+</I>&gt;&gt;<i> &gt;&gt; &#931;&#964;&#953;&#962; &#928;&#945;&#961;&#945;&#963;&#954;&#949;&#965;&#942; 13 &#924;&#940;&#953;&#959;&#962; 2011 00:39:55 Z&#233; &#947;&#961;&#940;&#968;&#945;&#964;&#949;:
+</I>&gt;&gt;<i> &gt;&gt;&gt; 2011/5/12 Dick Gevers &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dvgevers at xs4all.nl</A>&gt;:
+</I>&gt;&gt;<i> &gt;&gt;&gt; &gt; On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about
+</I>&gt;<i>
+</I>&gt;&gt;<i> &gt;&gt;&gt; perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+</I>&gt;&gt;<i> &gt;&gt;&gt; #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER &#160;\*/|'
+</I>&gt;&gt;<i> &gt;&gt;&gt; include/freetype/config/ftoption.h
+</I>&gt;&gt;<i> &gt;&gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt;&gt; dont forget to also increase Release to avoid conflicts with existant
+</I>&gt;&gt;<i> &gt;&gt;&gt; freetype2, and then build the package.
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; Why do all these things when you can simply add an entry in the
+</I>&gt;&gt;<i> &gt;&gt; font.conf file ?
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; Thats a fact, but hat should happen is that freetype2 should have
+</I>&gt;&gt;<i> &gt; bytecode interpreter disabled by default, since so far users prefer
+</I>&gt;&gt;<i> &gt; it.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Seams Fedora choosed to finally fix it, it reverted freetype2 with a
+</I>&gt;&gt;<i> patch to disable bytecode interpreter. -&gt;
+</I>&gt;&gt;<i> <A HREF="https://bugzilla.redhat.com/show_bug.cgi?id=547532">https://bugzilla.redhat.com/show_bug.cgi?id=547532</A>
+</I>&gt;<i>
+</I>&gt;<i> No, this is not what is covered in this bug report.
+</I>
+Yes, correct i miss understood what as the bug report about.
+
+&gt;<i> Firstly, here are the non-problems:
+</I>&gt;<i> 1)The bytecode interpreter *can* make fonts look better, *if* they have
+</I>&gt;<i> hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS
+</I>&gt;<i> fonts *do* have hinting.
+</I>&gt;<i>
+</I>&gt;<i> So, historically, the recommended approach was to use the PLF freetype *if*
+</I>&gt;<i> you had imported MS fonts (e.g. from a dual-boot Windows installation).
+</I>Well i always avoid using PLF freetype and for what i have read in
+ML's all the users that answered to it said that also avoid PLF
+freetype.
+
+So far for hat i have seen, all users prefered like fonts were
+rendered wen patents were still valid...
+
+&gt;<i> 2)The Freetype autohinter was implemented later, and improves things for
+</I>&gt;<i> unhinted fonts, but hinted fonts still looked better with the bytecode
+</I>&gt;<i> interpreter.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> This is the problem:
+</I>&gt;<i> 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or,
+</I>&gt;<i> could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts.
+</I>&gt;<i>
+</I>&gt;<i> The Fedora bug isn't about disabling the bytecode interpreter, but by still
+</I>&gt;<i> allowing auto-hinting for unhinted fonts if the bytecode interpreter.
+</I>&gt;<i>
+</I>&gt;<i> *This* is the right fix. Your insistence to *disable* the bytecode interpreter
+</I>&gt;<i> (leaving users with *no* options, in case they need hinted fonts) is the wrong
+</I>&gt;<i> fix.
+</I>Well this way users cant also set to have autohint, seams theres
+always some app failing.
+
+Why not having it disabled by default? users will always be able to
+set their preferences about using or not autohint, but that way
+ensures that all fonts are better rended.
+All this came up after patents end in wich showed users how fonts
+appear poor rended, until that point i didnt saw any complains about
+fonts, and this is what should be fixed.
+
+&gt;<i> But, thanks for the pointer to the bug, which points to the patches.
+</I>&gt;<i>
+</I>&gt;&gt;<i> Why dont we also do the same thing?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Since theres users complaining about it, why not solve it once for all?
+</I>&gt;<i>
+</I>&gt;<i> Regards,
+</I>&gt;<i> Buchan
+</I>&gt;<i>
+</I>
+
+
+--
+Z&#233;
+</PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="004656.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
+</A></li>
+ <LI>Next message: <A HREF="004662.html">[Mageia-dev] why not disable bytecode interpreter in freetype2 ?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4660">[ date ]</a>
+ <a href="thread.html#4660">[ thread ]</a>
+ <a href="subject.html#4660">[ subject ]</a>
+ <a href="author.html#4660">[ 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>