Talk:Webarchive

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Computing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Apple Inc.

	This article is within the scope of WikiProject Apple Inc., a collaborative effort to improve the coverage of Apple, Mac, iOS and related topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Apple Inc.Wikipedia:WikiProject Apple Inc.Template:WikiProject Apple Inc.Apple Inc. articles
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Not even wrong

Webarchives are simply ObjC plist representations of the web DOM that happens to include the embedded binary files.

It's NSKeyedArchiver, not NSKeyedEncoder (maybe older versions of ObjC). But that doesn't really matter much. You can extract to a plist with NSPropertyListSerialization from an NSData image of the NSBundle file (the web archive itself).

You can find ~10 line ObjC code snippet ("Restoring a property list (Objective-C)") to build a property list for a web archive in the Apple "Property List Programming Guide" under "Serializing a Property List". Just change the BSBundle:pathForResource:ofType type from "plist" to "webarchive" and feed it the file in place of @"Data" - it's coded for a "Data.plist" file. Then you have a property list that resembles an XML DOM except that it's accessed through dictionaries and arrays instead of XML API or XPATH calls.

http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/PropertyLists/SerializePlist/SerializePlist.html

You can also load a WebArchive into the developer tool shipped Property List Editor application to understand the webarchive plist structure without writing any code.

http://en.wikipedia.org/wiki/Apple_Developer_Tools#Property_List_Editor

It's not rocket science. — Preceding unsigned comment added by 123.193.138.96 (talk) 00:05, 4 July 2011 (UTC)[reply]