pldes(1) [debian man page]

PLDES(1)						       GNUstep System Manual							  PLDES(1)

NAME

       plio, pldes, plser, plmerge, plparse, pl2link	 - property list tools

SYNOPSIS

       pldes filename(s)
       plget key[morekeys]
       plser filename(s)
       plmerge [ destination-file ] [ input-file(s) ]
       plparse filename(s)
       pl2link input-file [ destination-file ]
       plio -input [ input-file ]  -output [ destination-file ]

DESCRIPTION

       Property lists in GNUstep are hierarchical lists of values or attribute-value pairs.  Programmatically they are represented by instances of
       the NSString, NSData, NSArray, or NSDictionary (most common) class (which may contain other instances of such  classes).   These  instances
       can be serialized as binary objects to form a persistent representation.  In addition, there are two alternative human-readable representa-
       tions.  The first, utilized in NeXTstep and OpenStep, utilizes a text format with equals signs expressing attribute-value bindings and  set
       braces  expressing  hierarchical organization.  The second, often (uninformatively) referred to as "plist" format, is in XML and is used by
       Mac OS X.  The tools described here are utilities for manipulating the various persistent property list representations as files.

       pldes filename(s)
	   Converts a binary serialised property list (class instance) to a text representation.

       plget key
	   Reads a text representation of a dictionary in property list format as standard input, extracts the string value held in  that  dictio-
	   nary with the specified key, and writes the result to standard output.  Multiple keys may be used to extract values from nested dictio-
	   naries.

       plser filename(s)
	   Converts a text representation of a property list to a binary serialized representation.

       plmerge [ destination-file ] [ input-file(s) ]
	   Merges text property lists into a single property list

       plparse filename(s)
	   Checks that each file contains a valid text representation of a property list.

       pl2link input-file [ destination-file ]
	   Produces a desktop link file for KDE and Gnome for the given text representation of a property list.

       plio -input [ input-file ]
	   Takes the serialized plist represented by input-file and outputs it to standard output.

       plio -output [ destination-file ]
	   Takes a plist from standard input and serializes it into destination-file.

SEE ALSO

       defaults(1)

HISTORY

       Written 1999-2000.

       This manual page first appeared in gnustep-base 1.9.2 (March 2004).

AUTHORS

       pldes, plget, plparse, plser were written by Richard Frith-Macdonald <rfm@gnu.org>.

       plmerge was written by Jonathan Gapen  <jagapen@whitewater.chem.wisc.edu>.

       pl2link was written by Fred Kiefer <FredKiefer@gmx.de>.

       pl (renamed to plio in Debian) was written by Gregory Casamento <greg_casamento@yahoo.com>.

GNUstep 							    August 2003 							  PLDES(1)

PLIST(5)						      BSD File Formats Manual							  PLIST(5)

NAME

     plist -- property list format

SYNOPSIS

     plist

DESCRIPTION

     Property lists organize data into named values and lists of values using several Core Foundation types: CFString, CFNumber, CFBoolean,
     CFDate, CFData, CFArray, and CFDictionary. These types give you the means to produce data that is meaningfully structured, transportable,
     storable, and accessible, but still as efficient as possible. The property list programming interface allows you to convert hierarchically
     structured combinations of these basic types to and from two formats: standard XML and an optimized, opaque binary format. This document
     describes the standard XML format. The data can be saved to disk and later used to reconstruct the original Core Foundation objects. Note
     that property lists should be used for data that consists primarily of strings and numbers because they are very inefficient when used with
     large blocks of binary data.

     PROPERTY LIST STRUCTURE AND CONTENTS

     Property lists are constructed from the basic Core Foundation types CFString, CFNumber, CFBoolean, CFDate, and CFData. To build a complex
     data structure out of these basic types, you put them inside a CFDictionary or CFArray. To simplify programming with property lists, any of
     the property list types can also be referred to using a reference of type CFPropertyListRef.

     In a CFDictionary, data is structured as key-value pairs, where each key is a string and the key's value can be a CFString, a CFNumber, a
     CFBoolean, a CFDate, a CFData, a CFArray, or another CFDictionary. When using CFDictionary as a property list, all keys must be strings.

     In a CFArray, data is structured as an ordered collection of objects that can be accessed by index. In a property list, a CFArray can contain
     any of the basic property list types, as well as CFDictionary and other CFArray objects.

     PROPERTY LIST XML TAGS

     When property lists convert a collection of Core Foundation objects into an XML property list, it wraps the property list using the document
     type tag <plist>. The other tags used for the Core Foundation data types are listed in the table below:

     Core Foundation Types with XML Equivalents
	 CF type	 XML tag
	 CFString	 <string>
	 CFNumber	 <real> or <integer>
	 CFDate 	 <date>
	 CFBoolean	 <true/> or <false/>
	 CFData 	 <data>
	 CFArray	 <array>
	 CFDictionary	 <dict>

     When encoding the contents of a CFDictionary, each member is encoded by placing the dictionary key in a <key> tag and immediately following
     it with the corresponding value in the appropriate tag from the table above. See EXAMPLES below for an example XML data generated from a
     property list.

     The XML data format is documented here strictly for help in understanding property lists and as a debugging aid. These tags may change in
     future releases so you shouldn't rely on them directly. You should not edit the XML data by hand unless you are very familiar with XML syntax
     and the format of property lists. If you want to modify the contents of a property list saved on disk as XML data, use the Property List Edi-
     tor application.

     More complete documentation can be found on disk at

     /Developer/Documentation/CoreFoundation/ProgrammingTopics/CFPropertyLists/CFPropertyLists.html

     or online at

     http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFPropertyLists/index.html

     BINARY FORMAT PROPERTY LISTS

     The binary property list format is opaque and does not use XML. However, binary property lists and XML property lists are generally inter-
     changeable. The plutil(1) utility may be used to convert property lists between different formats. For example, to view a binary property
     list in XML format on stdout:

	   plutil -convert xml1 -o - <file name>

EXAMPLES

	   <?xml version="1.0" encoding="UTF-8"?>
	   <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
		   "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	   <plist version="1.0">
	   <dict>
	       <key>Year Of Birth</key>
	       <integer>1965</integer>
	       <key>Pets Names</key>
	       <array/>
	       <key>Picture</key>
	       <data>
		   PEKBpYGlmYFCPA==
	       </data>
	       <key>City of Birth</key>
	       <string>Springfield</string>
	       <key>Name</key>
	       <string>John Doe</string>
	       <key>Kids Names</key>
	       <array>
		   <string>John</string>
		   <string>Kyra</string>
	       </array>
	   </dict>
	   </plist>

SEE ALSO

     plutil(1)

Mac OS X							   July 9, 2003 							  Mac OS X