Bug 7491 - Font in ml.mageia.org is terrible
Summary: Font in ml.mageia.org is terrible
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Atelier Team
QA Contact:
URL: https://ml.mageia.org/
Whiteboard:
Keywords: Atelier
Depends on:
Blocks:
 
Reported: 2012-09-16 13:25 CEST by Jens Maucher
Modified: 2017-07-18 17:12 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
sympa (12.80 KB, image/png)
2012-09-16 13:28 CEST, Jens Maucher
Details

Description Jens Maucher 2012-09-16 13:25:28 CEST
The font in sympa ins crabbed. 
I attached a screenshot what it looks like in Firefox on a fresh installed mga2.
Comment 1 Jens Maucher 2012-09-16 13:28:16 CEST
Created attachment 2802 [details]
sympa
Comment 2 Jens Maucher 2012-09-16 13:35:58 CEST
In the style.css are a lot of microsoft fonts, and AFAIK mageia didn't offer a rpm package of ms-fonts.
Maybe it could be a solution to change this fonts to dejavu, bitstream or something else that is installed by default on workstations.

Cheers
Comment 3 Romain d'Alverny 2012-09-16 13:53:17 CEST
It looks like both a font-family and a font-size issue. But just this:

--- style.css.orig	2012-09-16 13:51:07.000000000 +0200
+++ style.css	2012-09-16 13:51:20.000000000 +0200
@@ -19,7 +19,7 @@
        }
 
 body {
-       font-size: 62.5%;
+       font-size: 80%;
        background: #DEE7F7;
        }

improves a lot.

Keywords: (none) => Atelier
URL: (none) => https://ml.mageia.org/
CC: (none) => rdalverny

Comment 4 Jens Maucher 2012-09-16 14:31:44 CEST
I changed with firebug (firefox addon) the font-family to

font-family: "sans-serif";

and it looks great. Just deleting Trebuchet and so on.
Comment 5 Rémi Verschelde 2015-09-10 15:43:10 CEST
Any clue as to where this should be fixed? I don't see it on gitweb.mageia.org.
Comment 6 Manuel Hiebel 2017-07-18 17:12:07 CEST
looks the update of sympa fixed this

(test on edge/IE under win10 too)

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


Note You need to log in before you can comment on or make changes to this bug.