<font color='black' size='2' face='arial'>Soundz like converting text to picturez iz still the best way to go. <div><br> </div> <div>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. <br> <br> <br> <div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br> From: Manuel Schmalstieg <webdev@ms-studio.net><br> To: Open Font Library <openfontlibrary@lists.freedesktop.org><br> Sent: Sat, Nov 16, 2013 7:17 pm<br> Subject: Re: [OpenFontLibrary] WordPress & fonts, bundling vs. linking<br> <br> <div id="AOLMsgPart_0_348cf993-90aa-485c-adec-468f18bb1643" style="margin: 0px;font-family: Tahoma, Verdana, Arial, Sans-Serif;font-size: 12px;color: #000;background-color: #fff;"> <pre style="font-size: 9pt;"><tt>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." </tt></pre> </div>  </div> </div> </font>