https://issues.apache.org/bugzilla/show_bug.cgi?id=55383
--- Comment #51 from Konstantin Preißer <kpreis...@apache.org> --- Hi Christopher, thanks for your comments. (In reply to Christopher Schultz from comment #50) > (In reply to Konstantin Preißer from comment #49) > > I'd like to switch the font used for the Tomcat Website and Docs (currently > > "Lucida Sans Unicode") to "Open Sans" [1] which is released by Google using > > a Apache 2.0 Licence. This also means that the font can be displayed on > > every platform like Windows, Mac and Linux. > > It's worth noting that the current CSS for font-family is just a suggestion > to the browser. The font you get depends very heavily on the environment > where the pages are being viewed. > > > I plan to add the Font files (.woff) (the variant which contains only the > > Latin characters) directly instead of using a CSS link to Google, so that > > the Site and the Docs (which may be viewed offline) don't depend on external > > Google resources. > > I'm not a huge fan of WOFF for a few reasons: > > 1. It requires yet another file to download, and font files tend to be big > (I couldn't find a download link so I don't know the exact size of the Open > Sans font). Google Fonts allows to explicitely select the charsets which should be included in the Font, to keep the file sizes down. E.g. in this case it would be (400, 400 italics, 600, 600 italics): 84 KB, which should be an acceptable size in today's relations (e.g. the ASF feather PNG image (asf-feather.png) has 40 KB). > 2. Most browsers I've seen tend to render the page as quickly as possible, > and then apply the custom-font afterward, which results in a weird > post-adjustment of the font, even for fonts that are already downloaded. I > haven't done extensive testing recently, so it's possible that this is no > longer an issue. This applies if you visit the page the first time: Some browsers (Firefox) will display the page with an alternate font until the WOFF is downloaded, then switch to the WOFF. Other browsers (Chrome) will display spaces until the WOFF is loaded. However, after that if you browse on other pages then the WOFF is already in the cache and the browser will use it immediately (at least this is the case with Firefox, IE and Chrome), so there should be no issues when browsing through various links on the site. > 3. Ultimately, the font choice is up to the browser, anyway, so you can't > really "force" them to use Open Sans. Yes (but this should also be the case with local fonts). > > Given the above, why bother with a change at all? I know designers get all > hot and bothered by things like kerning, serif angles, etc. but I'm not sure > that adding another font-choice here really adds anything. I'm also not a designer but I think it looks a bit more modern than the currently used Lucida Sans Console (and as it is a platform-independent format, other platforms will be able to use the font). I use it on my own websites and e.g. this site uses it: http://www.html5rocks.com/en/tutorials/websockets/basics/ -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
