« A good reason to get Leopard | Back to main page | The most persecuted religion in the world »
12.06.07
Unexpected end of a Safari
Update: A solution for the crashes is available (see comments or here).
The keynote for Apple's World Wide Developer's Conference given by Steve Jobs yesterday followed the pattern developed in the past years: No announcements of new hardware (these will probably follow in the coming weeks), but a focus on software and strategic developments instead. A lot of Leopard's new features look rather interesting. I'm just a bit disappointed that there was no mention of ZFS.
One rather surprising step was Apple's decision to port their web browser Safari to Windows. It does make sense, if you consider the need for syncing or admin software for the iPhone (and I think Safari will play a role there). It's a nice touch that a public beta of Safari for Windows is already available.
I wouldn't recommend downloading it, however. On the German Windows XP system I tried it on, it failed to display any text in bold or italic fonts (including headlines). It also crashed the computer when I tried to submit a bug report (!). And when despite these circumstances, I tried to write this blog entry using Safari, it crashed when I pasted some text into the blog entry's subject field. Not impressive at all. Contrary to what is promised on the Safari website, no bookmarks were imported, and when I tried to open the bookmark folder, Safari crashed. I was able to look at the preferences, but there is a noticable delay when switching between different preference panes (on a Core 2 Duo system no less!).
I am rather disappointed that Apple would consider calling something like this a beta version. The only positive thing was that Safari detected and used the local proxy configuration.
Just for fun, here's a shortened overview of the information Safari reveals in its HTTP headers and via Javascript. The Javascript output reveals that Safari automatically detected the plugins I had installed for Firefox.
| HTTP_ACCEPT | text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 |
| HTTP_ACCEPT_ENCODING | gzip, deflate |
| HTTP_ACCEPT_LANGUAGE | en |
| HTTP_CONNECTION | Keep-Alive |
| HTTP_HOST | web42.com |
| HTTP_USER_AGENT | Mozilla/5.0 (Windows; U; Windows NT 5.1; de) AppleWebKit/522.11.3 (KHTML, like Gecko) Version/3.0 Safari/522.11.3 |
| SERVER_PROTOCOL | HTTP/1.0 |
Microsoft® DRM: DRM Netscape Network Object (npdrmv2.dll)
Adobe Acrobat: Adobe Acrobat Plug-In Version 7.00 for Netscape (nppdf32.dll)
QuickTime Plug-in 7.1.6: The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site. (npqtplugin.dll)
Shockwave Flash: Shockwave Flash 9.0 r45 (NPSWF32.dll)
iTunes Application Detector: iTunes Detector Plug-in (npitunes.dll)
Apple Java Plug-In: Apple Java Plug-In (npJavaPlugin.dll)
Mozilla Default Plug-in: Default Plug-in (npnul32.dll)
Windows Media Player Plug-in Dynamic Link Library: Npdsplay dll (npdsplay.dll)
Microsoft® DRM: DRM Store Netscape Plugin (npwmsdrm.dll)
Posted by crenz, 12.06.07 10:31
Trackback-Pings
TrackBack-URL zu diesem Eintrag:
http://christian.web42.com/mt/mt-tb.cgi/162
Die folgenden Weblogs beziehen sich auf diesen Eintrag Unerwartetes Ende einer Safari · Unexpected end of a Safari:
» Den Safari-Abstürzen ein Ende bereiten · End the Safari crashes from public thoughts
Thanks to a comment Niels Leenheer left in my blog entry talking about my Safari problems, I was able to fix the crashes I encountered. In the installation directory of the Safari Beta (C:\Program Files\Safari) I found two directories called... [Weiter lesen]
Verlinkt am 12.06.07 15:01
Kommentare
You can make the crashes go away by opening the folder in which you installed Safari and look for folders that end with .lproj. Then duplicate those folders and rename them. English.lproj to German.lproj and en.lproj to de.lproj.
The problem is that the beta version only contains english localisation items, and you are running a non-english system. It can
Verfasst von: Niels Leenheer um 12.06.07 12:32
hello,
also i am disappointed with the quality of the windows release, it was probably more accurate to name it an alpha.
but i wouldn't be surprised if there was some pressure from a certain key executive know so he could announce it today :)
it surely is not the code base, as it is very stable and fast on os x, regardless of locale (i use korean), i think it is some issues with the port to windows.
Verfasst von: nexusprime um 12.06.07 12:52
hello,
also i am disappointed with the quality of the windows release, it was probably more accurate to name it an alpha.
but i wouldn't be surprised if there was some pressure from a certain key executive know so he could announce it today :)
it surely is not the code base, as it is very stable and fast on os x, regardless of locale (i use korean), i think it is some issues with the port to windows.
Verfasst von: nexusprime um 12.06.07 12:52
Niels, thank you very much for the hint! It worked perfectly for me. I still have the font rendering problems, though.
Verfasst von: Christian um 12.06.07 14:45
Did you already have a Lucida Grande font (or maybe Helvetica on this page) installed? That apparently causes problems, since many of them are broken.
Verfasst von: astrange um 12.06.07 15:13
astrange, no, I didn't. I tried a page without any CSS information (which is displayed in the default font) and tried changing the default font to various settings (an OpenType Font, a TrueType Font, etc.), but still couldn't get it to work. I think it might have to do with localization as well, since I have read of someone on an English system where it worked.
Verfasst von: Christian um 12.06.07 15:26
The font rendering problem is also a localisation issue. If you use an English version of XP it will work without problems. There have been some reports that setting the locale of Windows will fix things, but I can't confirm this.
Verfasst von: Niels Leenheer um 12.06.07 19:55
