"The ability to download and immediately render non-standard web fonts is just one of several advancements Apple has planned for Safari 3.1, a small but significant update to its share-gaining web browser for both the Mac and Windows PCs. The release, which underwent private testing this week, will tie in a number of other enhancements, most of which have been under constant development as part of the company's WebKit open source application framework since last fall. They aim to provide Web developers a means of writing more dynamic and customizable web pages and iPhone apps, which will in turn provide surfers with a more feature-rich and enjoyable experience."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-09-10
The use of Windows-1252 encoding (and the other related ones) is perfectly valid, as long as it's not served as latin1 (iso-8859-1) or similar. It's this behaviour that's not allowed in FF strict mode I suspect. To be honest though for 99% of sites the proper solution would be to move to UTF-8.
Member since:2005-06-29
Besides that, Safari for Windows have terrible problems with accents. By using accents in web forms, it just ignores everything you wrote after the accent... not just forms, but and coping to clipboard to. Also, it didn't properly converted the line breaks to the correct (in Windows), leaving you with a bunch of characters to clean up...
But as far as I know, most of the problems are gone in the current versions of Safari for Windows.
I do use it from time to time to check some links when my Opera9 or Firefox3 windows are too populated... Or when Flash video playback bug (just stop after some seconds, have to click the seek bar all the time to continue the playback for some more seconds... it just sucks) prevents me from watching them in my browsers.
Member since:
2008-01-08
Actually, Safari CAN show accented characters, what it does not do (either by choice or technical limitation) is not render windows specific characters. For instance, the character 'é' if attained via charmap (or a different language typeset keyboard) will use the windows character encoding directly. Most web browsers will be lenient when rendering these characters and show the correct ones anyway, but Safari does not (and neither does Firefox if you put it into Strict xhtml mode, etc).
Sure fire way to get those chars appearing is by using the html encoded character in it's place:
< !ENTITY eacute CDATA "é" -- latin small letter e with acute, U+00E9 ISOlat1 -->
If you view the source of my post, you'll see that while I can render the char 'é', I have to use the html encoding to make it render in Safari.
http://www.w3.org/TR/html401/sgml/entities.html
EDIT: ARG
OSNews is garbaging all my hard work, even though their preview renders it correctly, the site escapes my html encoded stuff... just check out that link.
Edited 2008-02-07 18:30 UTC