diff options
author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
---|---|---|
committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20110513/004660.html | |
parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip |
Diffstat (limited to 'zarb-ml/mageia-dev/20110513/004660.html')
-rw-r--r-- | zarb-ml/mageia-dev/20110513/004660.html | 141 |
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é</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 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at staff.telkomsa.net</A>>: +><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 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 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>><i> +</I>><i> No, this is not what is covered in this bug report. +</I> +Yes, correct i miss understood what as the bug report about. + +><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 MS +</I>><i> fonts *do* have hinting. +</I>><i> +</I>><i> So, historically, the recommended approach was to use the PLF freetype *if* +</I>><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... + +><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 still +</I>><i> allowing auto-hinting for unhinted fonts if the bytecode interpreter. +</I>><i> +</I>><i> *This* is the right fix. Your insistence to *disable* the bytecode interpreter +</I>><i> (leaving users with *no* options, in case they need hinted fonts) is the wrong +</I>><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. + +><i> But, thanks for the pointer to the bug, which points to the patches. +</I>><i> +</I>>><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>><i> +</I>><i> Regards, +</I>><i> Buchan +</I>><i> +</I> + + +-- +Zé +</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> |