The thing is, the bytecode interpreter is a build time option, I am not sure it can be disabled after building by a runtime option/config...

It can be, with the "autohint" fontconfig option.

IMO this belongs to the KDE/GNOME/etc font settings dialog, as that is where the other settings are as well.

I'm not against global MCC config, though.

(In reply to comment #2)
> It can be, with the "autohint" fontconfig option.
> 

I don't know, so I'll defer to you. :)

> IMO this belongs to the KDE/GNOME/etc font settings dialog, as that is where
> the other settings are as well.
> 
> I'm not against global MCC config, though.

I am more for the idea that is should be a DE font settings dialogue/tool option.

IMHO the bytecode interpreter should be disabled globally by default, the only screens were it doesn't look bad is on high dpi netbook/notebook screens.

Maybe we could have two variants of the package one that gets installed on netbooks/notebooks with bytecode enabled, and one that gets installed on desktops with bytecode disabled.

The per DE setting dialogs are unpractical, since they need to be set for each DE and aren't easy to find for someone who doesn't know where they are.
Also this is really a global setting not a DE setting.

CC: (none) => tux99

(In reply to comment #4)
> IMHO the bytecode interpreter should be disabled globally by default, the only
> screens were it doesn't look bad is on high dpi netbook/notebook screens.
> 

Fonts look much better here with BCI enabled, a 1920x1080 LCD monitor with 101 DPI.

> Maybe we could have two variants of the package one that gets installed on
> netbooks/notebooks with bytecode enabled, and one that gets installed on
> desktops with bytecode disabled.
> 

I don't think that's needed at all since there's a runtime config that controls it, c.f. comment#2.

> The per DE setting dialogs are unpractical, since they need to be set for each
> DE and aren't easy to find for someone who doesn't know where they are.
> Also this is really a global setting not a DE setting.

Really? and where do users:
- Set sub-pixel rendering options
- Enable/disable fonts anti-aliasing
- Set the hinting style
- the various UI font sizes

all that is done via the DE font config tool, and those preferences vary from one user to another. So the BCI/Autohinting settings should be in each DE font configuration tool.

> > The per DE setting dialogs are unpractical, since they need to be set for each
> > DE and aren't easy to find for someone who doesn't know where they are.
> > Also this is really a global setting not a DE setting.
> 
> Really? and where do users:
> - Set sub-pixel rendering options
> - Enable/disable fonts anti-aliasing
> - Set the hinting style
> - the various UI font sizes

And how many average users know about those settings and even more so know what those settings actually mean?

It's first impressions that count and with bytecode interpreter enabled fonts look really bad on many screens (I have seen this myself and/or received comments from users for at least 20-30 installs over the last few years with plf v. mdv freetype2 packages), while the improvement on screens where it looks better are only slight.

I agree that is better in the DE settings. Example for KDE with the fonts settings, as mentioned Ahmad. Is the place that every user will go to try to configure his fonts

I proposed the Mageia control center because i dont know if it is possible to make a request to each DE project to add this feature. May be the easier way is the MCC as it will be available for all DE.

(In reply to comment #7)
> I agree that is better in the DE settings. Example for KDE with the fonts
> settings, as mentioned Ahmad. Is the place that every user will go to try to
> configure his fonts

Not every user, I'd try drakfont because I use MCC a lot and hardly ever look at the KDE system settings

> 
> I proposed the Mageia control center because i dont know if it is possible to
> make a request to each DE project to add this feature. May be the easier way is
> the MCC as it will be available for all DE.

@ Thierry

assigning to you because of the wish to get this in MCC

Assignee: bugsquad => thierry.vignaud

I'm convinced this should go into mcc
I think this should be in KDE/GNOME preferences

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

(In reply to comment #9)
> I'm convinced this should go into mcc
> I think this should be in KDE/GNOME preferences

@ Thierry

In which line should the word *not* be added?

@ everyone

Is this request still valid/needed?

This is fixed in KDE in ROSA.  A ROSA developer alerted me to this.

Here's their patch:
https://abf.rosalinux.ru/import/kdebase4-workspace/raw/rosa2012.1/kde-workspace-4.9.4-fontconfig.patch

(In reply to comment #11)
@marja: to the first one obviously :-)

reassigning because of the patch.

URL: (none) => https://abf.rosalinux.ru/import/kdebase4-workspace/raw/rosa2012.1/kde-workspace-4.9.4-fontconfig.patch
Keywords: (none) => PATCH
Assignee: thierry.vignaud => nicolas.lecureuil
Source RPM: freetype2 drakxtools => kdebase4

Removed because the requested info is given.

Roelof

Keywords: NEEDINFO => (none)
CC: (none) => r.wobben

When will this patch be added?

CC: (none) => loginov_alex

I asked to add it upstream:
https://bugs.kde.org/show_bug.cgi?id=321481

Upstream may add this patch through some years. Why is it waiting to add in Mageia?

Nicolas, do you think something about this ? 
Please tell us,
thanks in advance.

May be you want to vote for it:
http://forum.kde.org/viewtopic.php?f=83&t=117320

Created attachment 5048 [details]
python3-qt4 script

did it by my own

for comment 20

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

This rpm installs the script and adds a desktop entry in menu>Settings http://glenbox.free.fr/autohint-onoff/autohint-onoff-1.0-2mgr5.noarch.rpm

Dimitrios, thank you,

- button "Close..." does not work and I can not close program using "x" button if there is no ~/.config/fontconfig directory.
- missing localization for program and for .desktop.
- button "Close..." should be "Close", because If to press here, then there is no new window (standard for using "...")

Works for me.

Thanks Alex for found this. I corrected and i changed the 'Close' to 'OK' (without ...) and the 'x' of the window close the dialog and discards the changes

Next step, i will add the i18n support

http://glenbox.free.fr/autohint-onoff/autohint-onoff-1.1-1mgr5.noarch.rpm

Seems OK.
Maybe to add Cancel button also? And I want to translate.
Good job!

Status: RESOLVED => REOPENED
Resolution: WORKSFORME => (none)

Ok, with Cancel button and translations:
http://svnweb.mageia.org/packages/cauldron/autohint-onoff/
http://glenbox.free.fr/autohint-onoff/autohint-onoff-1.3-1mgr5.noarch.rpm

I have only 1 proposal to change desktop file in new version:

Exec=autohint-onoff

Program works fine. Bug is fully resolved.

Status: REOPENED => RESOLVED
Resolution: (none) => WORKSFORME

I will take a look, i wanted to have the script in /usr/share and an executable in /usr/bin in case that you wanted to launch it in terminal; most to avoid the icon jumping

(In reply to Alex Loginov from comment #27)
> I have only 1 proposal to change desktop file in new version:
> 
> Exec=autohint-onoff
> 
> Program works fine. Bug is fully resolved.

Hi Alex, the above is ok in version 1.6

The option to enable/disable autohint has been added in lxqt control panel:
https://github.com/lxde/lxqt-config/pull/13#event-187605798