Comments on: Type rendering: operating systems https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/ News about Typekit Mon, 15 Nov 2010 11:28:11 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Angus Fretwell https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1894 Mon, 15 Nov 2010 11:28:11 +0000 http://blog.typekit.com/?p=1650#comment-1894 At my school the admins seem to have disabled the antialiasing on our (not so) beloved Windows XP machines. It hurts me every time I need to do some research or type up a document at school.

]]> By: Florian https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1893 Thu, 11 Nov 2010 21:30:33 +0000 http://blog.typekit.com/?p=1650#comment-1893 Question: When a Windows XP user has disabled anti-aliasing system wide will -webkit-font-smoothing: antialiased; re-activate it in Safari & Chrome?

More on -webkit-font-smoothing: antialiased; here: http://maxvoltar.com/archive/-webkit-font-smoothing

]]> By: BEENA https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1892 Mon, 08 Nov 2010 08:45:05 +0000 http://blog.typekit.com/?p=1650#comment-1892 good

]]> By: origiNell https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1891 Thu, 28 Oct 2010 21:44:08 +0000 http://blog.typekit.com/?p=1650#comment-1891 In reply to origiNell.

Ah thank you for that info!

]]> By: jjgod https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1890 Thu, 28 Oct 2010 18:13:54 +0000 http://blog.typekit.com/?p=1650#comment-1890 In reply to Christopher Lloyd.

I second with Christopher. The role of Core Text and Core Graphics are explained clearly in Apple documentation: Core Text Programming Guide. The results of Core Text (glyph ids and positions) will be fed to Core Graphics, then Core Graphics will do the actual rendering.

]]> By: jjgod https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1889 Thu, 28 Oct 2010 18:10:47 +0000 http://blog.typekit.com/?p=1650#comment-1889 In reply to origiNell.

Pango does not in charge for font rendering, it simply outsource it to FreeType. So does Qt, it uses FreeType rather than it’s own subpixel rendering now.

]]> By: origiNell https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1888 Tue, 26 Oct 2010 21:56:36 +0000 http://blog.typekit.com/?p=1650#comment-1888 In reply to origiNell.

Always a pleasure 🙂

]]> By: Tim Brown https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1887 Tue, 26 Oct 2010 14:59:04 +0000 http://blog.typekit.com/?p=1650#comment-1887 In reply to origiNell.

Thanks for sharing all of this, Luis!

]]> By: origiNell https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1886 Tue, 26 Oct 2010 11:46:26 +0000 http://blog.typekit.com/?p=1650#comment-1886 Font rendering under *nix systems is actually a quite interesting theme since you can plug in various backends.. To get a slight idea, here are some links:
http://www.linux.com/archive/feed/39513 (point: apple holds 3 patents on truetype hinting)

http://en.wikipedia.org/wiki/FreeType (font rasterization engine, heck there is a patch which even makes OSX style rendering possible)

Furthermore each Window toolkit (Specifically GTK+ and QT) has some kind of own font engine.. For GTK+ it’s Pango (http://en.wikipedia.org/wiki/Pango) – QT has it’s own (http://labs.qt.nokia.com/2008/09/01/subpixel-antialiasing-on-x11/).

Note that I’m NOT an expert on this field on *nix like systems. This is just what I guess/know. Hope it helps as a start and gives some overview. Fonts are an interesting theme on *nix since the rendering depends on a lot of factors – from X11, over some engines to your window toolkit’s engine..

Seriously, does someone know everything about this when it comes to linux :O?!

]]> By: Antwan https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/#comment-1885 Mon, 25 Oct 2010 20:39:29 +0000 http://blog.typekit.com/?p=1650#comment-1885 WPF is so ugly… 🙁
I pray each day someone at Microsoft will open his eyes and decide to fix it, since it begins to be very used (It think at IE9, FF4, etc.)

]]>