com.itextpdf.kernel.xmp Documentation Differences

iText 9.5.0 Overview Package Class Text Changes Statistics Help

Generated by
JDiff

PREV PACKAGE NEXT PACKAGE FRAMES NO FRAMES

com.itextpdf.kernel.xmp Documentation Differences

This file contains all the changes in documentation in the package com.itextpdf.kernel.xmp as colored differences. Deletions are shown ~~like this~~ , and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a tag will cause all subsequent paragraphs to be displayed differently.

 
  
 Class XMPMetaFactory, XMPMeta parse(InputStream, ParseOptions)
  

  

  
   These functions support parsing serialized RDF into an XMP object, and serailizing an XMP object into RDF. The input for parsing may be any valid Unicode encoding. ISO Latin-1 is also recognized, but its use is strongly discouraged. Serialization is always as UTF-8. 
   
 parseFromBuffer() parses RDF from an InputStream. The encoding is recognized automatically. @param in an InputStream @param options Options controlling the parsing.
   
 The available options are: 
    
     XMP_REQUIRE_XMPMETA - The  XML element is required around 
      
     {@code 
      
       }
      . 
     XMP_STRICT_ALIASING - Do not reconcile alias differences, throw an exception. 
   
 Note:The XMP_STRICT_ALIASING option is not yet implemented. @return Returns the XMPMeta-object created from the input. @throws XMPException If the file is not well-formed XML or if the parsing fails.
   
  
 Class XMPPathFactory, String composeFieldSelector(String, String, String, String)
  

  

  
   Compose the path expression to select an alternate item by a field's value. The path syntax allows two forms of "content addressing" that may be used to select an item in an array of alternatives. The form used in ComposeFieldSelector lets you select an item in an array of structs based on the value of one of the fields in the structs. The other form of content addressing is shown in ComposeLangSelector. For example, consider a simple struct that has two fields, the name of a city and the URI of an FTP site in that city. Use this to create an array of download alternatives. You can show the user a popup built from the values of the city fields. You can then get the corresponding URI as follows: 
    
          String path = composeFieldSelector ( schemaNS, "Downloads", fieldNS, 
          "City", chosenCity ); 
      XMPProperty prop = xmpObj.getStructField ( schemaNS, path, fieldNS, "URI" );
  
   
 @param arrayName The name of the array. May be a general path expression, must not be null or the empty string. @param fieldNS The namespace URI for the field used as the selector. Must not be null or the empty string. @param fieldName The name of the field used as the selector. Must be a simple XML name, must not be null or the empty string. It must be the name of a field that is itself simple. @param fieldValue The desired value of the field. @return Returns the composed path. This will be of the form {@code ns:arrayName[fNS:fieldName='fieldValue']}, where "ns" is the prefix for schemaNS and "fNS" is the prefix for fieldNS. @throws XMPException Thrown if the path to create is not valid.