[OpenFontLibrary] WordPress & fonts, bundling vs. linking

[nooalf at aol.com]

Soundz like converting text to picturez iz still the best way to go. 


If you are concerned about it not being searchable, you can put plain text in anyway below the main paje or hidden or az an alternate pop up.  



-----Original Message-----
From: Manuel Schmalstieg <webdev at ms-studio.net>
To: Open Font Library <openfontlibrary at lists.freedesktop.org>
Sent: Sat, Nov 16, 2013 7:17 pm
Subject: Re: [OpenFontLibrary] WordPress & fonts, bundling vs. linking


Thanks Dave for pitching in.

Vernon, indeed that font is for the WordPress UI that is being "modernized".

Regarding filesize: a default WordPress install is pretty small, about
6.5 mb (compressed). If you include a font with a wide character set,
x 4 weights, x 4 formats (WOFF, SVG, TTF, EOT), suddenly the font
takes a significant % of the whole package...

There's some worrying that the non-subsetted version "can actually
crash some mobile browsers".

As Dave wrote, it's not trivial: "Since WordPress doesn’t have a
dynamic font subsetter, you’ll need a set of language subsets and a
set of hint subsets."

Matt Mullenweg has noted that "if we can solve this in a standalone
way (the script not loading any of the rest of WP) we avoid licensing
issues [between GPLv2, the license of WordPress, and Apache, the
license of Open Sans] and also solve a general problem many people
across the web have."

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openfontlibrary/attachments/20131117/ccd70ca7/attachment.html>