Bug 1909

I've installed libfreetype6-2.4.4-5.1.mga1.tainted.i586 and
freetype2-demos-2.4.4-5.1.mga1.tainted.i586.

Logged out/in.  No obvious difference, on my system.

Presumably there is a way to activate the subpixel hinting that I'm missing,
otherwise what does it accomplish?

CC: (none) => davidwhodgins

A freetype2 build with subpixel rendering enabled should enable you to use the fontconfig lcdfilter settings (which would be ignored altogether with a non-subpixel-enabled freetype2 build).

I forgot to say, this only affects GTK+ apps, Qt4/KDE apps aren't affected at all.

I installed task-gnome, and used System/Preferences/Appearance to turn on
subpixel smoothing for the fonts.  After logging out/back in, I don't see
any noticeable difference on my crt monitor.

How can someone check to see if subpixel rendering is being used?

IIUC, the subpixel rendering is more for LCD monitors, though they say "some users reported is made fonts looks better or CRT monitors too".

If there is anyone with a 64 bit system available to confirm it installs
cleanly there, I think that would be enough to allow pushing from
tainted-updates-testing to tainted-updates.

Sorry, should have included the packages that needs to be tested on x64/pushed
from tainted updates testing to tainted updates are
freetype2-demos
libfreetype6
libfreetype6-devel
libfreetype6-static-devel.

I think simply installing them, and confirming the display on a gnome system
doesn't get messed up, should be enough.

The whole point of providing a tainted build of freetype2 is offering an "opt-in" option for users who actually used subpixel-rendering-enabled freetype2 from PLF.

I don't see how the display on a GNOME installation would get messed up by a freeype2 tainted build.

I didn't mean to imply it would mess things up.  Just that the installation
should also be tested on a 64 bit system.  Once that's done, the packages
listed in comment 6 should be pushed to tainted updates.

I did test packages from Tainted Updates testing , and they are working :)

CC: (none) => hrvoje.senjan

Then the following packages are ready to push from Tainted Updates Testing
to Tainted updates on both i586 and x86-64.

freetype2-demos
libfreetype6
libfreetype6-devel
libfreetype6-static-devel

Do you have an advisory text for this update ?

CC: (none) => boklm

Proposed Advisory text:
=========================================
FreeType2 as shipped in Mageia 1 doesn't have subpixel rendering enabled (a build time option). This update provides FreeType2 packages with sub-pixel rendering enabled only in the tainted section as this feature is covered by some software patents which violate copyright laws in some countries in the world.
=========================================

I don't think it violates "copyright laws", but maybe "patent laws".

Maybe we can just say "feature is covered by some software patents"  ?

pushed to updates.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

(In reply to comment #13)
> I don't think it violates "copyright laws", but maybe "patent laws".
> 
> Maybe we can just say "feature is covered by some software patents"  ?

Yes, sorry, I was probably too sleepy.

I've noticed that the packages
freetype2-demos
libfreetype6-devel
libfreetype6-static-devel
libfreetype6
are in Core Updates Testing.  Does the build system now generate both the
Core and tainted versions at the same time?

If so should these packages be pushed too, along with the srpm?

(In reply to comment #16)
> I've noticed that the packages
> freetype2-demos
> libfreetype6-devel
> libfreetype6-static-devel
> libfreetype6
> are in Core Updates Testing.  Does the build system now generate both the
> Core and tainted versions at the same time?
> 

No, it doesn't; we submit in both locations every time.

@sysadm: please move these ones to core/updates too.

> If so should these packages be pushed too, along with the srpm?