Last modified: 2014-04-06 11:12:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65591, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63591 - Windows renders Liberation Sans in very ugly way
Windows renders Liberation Sans in very ugly way
Status: RESOLVED DUPLICATE of bug 63512
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
PC Windows 7
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-06 10:25 UTC by piotr.jerzy.jurkiewicz
Modified: 2014-04-06 11:12 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Liberation Sans Windows 7 (111.19 KB, image/png)
2014-04-06 10:25 UTC, piotr.jerzy.jurkiewicz
Details
Arial Windows 7 (96.85 KB, image/png)
2014-04-06 10:25 UTC, piotr.jerzy.jurkiewicz
Details

Description piotr.jerzy.jurkiewicz 2014-04-06 10:25:06 UTC
Created attachment 15031 [details]
Liberation Sans Windows 7

After the last changes Liberation Sans precedes Arial in font-family for article body. It should not change anything on Windows, as it does not have Liberation Sans installed by default. However, it is not the case when someone uses LibreOffice. It installs Liberation Sans what results in Wikimedia pages being renders with this font.

Windows has significant problems with rendering Liberation Sans (Linux does it fine). Just take a look on screenshots attached. Letters are smudged and blurry. Reading is tiring for the eye. I use default ClearType settings, without any custom tuning.

Therefore, I would expect Liberation Sans not to being used on Windows, even when it is present in system.

Unfortunately, it would mean serving css file dynamically, basing on useragent header. Therefore, I think that the better way is to revert back font-family to the old setting (or place "Liberation Sans" after sans-serif at least).
Comment 1 piotr.jerzy.jurkiewicz 2014-04-06 10:25:26 UTC
Created attachment 15032 [details]
Arial Windows 7
Comment 2 Bartosz Dziewoński 2014-04-06 11:12:57 UTC

*** This bug has been marked as a duplicate of bug 63512 ***

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


Navigation
Links