Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 033867E6C for ; Sat, 13 Aug 2011 11:19:26 +0000 (UTC) Received: (qmail 14176 invoked by uid 500); 13 Aug 2011 11:19:24 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 14059 invoked by uid 500); 13 Aug 2011 11:19:23 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 14051 invoked by uid 99); 13 Aug 2011 11:19:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Aug 2011 11:19:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bitvaizs@gmail.com designates 209.85.212.43 as permitted sender) Received: from [209.85.212.43] (HELO mail-vw0-f43.google.com) (209.85.212.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Aug 2011 11:19:17 +0000 Received: by vws10 with SMTP id 10so3538623vws.30 for ; Sat, 13 Aug 2011 04:18:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=/8l1x4mOC4eTbVUFunLbSN2s2UV5w6mzaVjdnNmAOag=; b=HTDBDj0klv4/ONl9cfx6VA/fYJMZmQopdl3NWyy8TESWzD5MvEMD4BEGN3QeaKVmfU mLHKxlaEY/OSOcla218L7HxV3EB5VYby6b1NHxBJjhVqKfRgmNSUazx2SKA7lzfes0Nr /rQ3L44Ac4kGH85TwgJgwJww6WzOhfo9JLyHg= Received: by 10.52.135.40 with SMTP id pp8mr109933vdb.354.1313234336092; Sat, 13 Aug 2011 04:18:56 -0700 (PDT) MIME-Version: 1.0 Sender: bitvaizs@gmail.com Received: by 10.52.186.41 with HTTP; Sat, 13 Aug 2011 04:18:36 -0700 (PDT) From: bizso09 Date: Sat, 13 Aug 2011 12:18:36 +0100 X-Google-Sender-Auth: C3CLXQwRRJXUxp9B5hDks8jMAxQ Message-ID: Subject: [sanselan] are these formats supported? To: user@commons.apache.org Content-Type: multipart/alternative; boundary=bcaec52c67311c105b04aa61323b --bcaec52c67311c105b04aa61323b Content-Type: text/plain; charset=ISO-8859-1 ---------- Forwarded message ---------- From: bizso09 Date: Sat, Aug 13, 2011 at 11:26 AM Subject: Re: [sanselan] are these formats supported? To: user@commons.apache.org Can someone please explain very briefly how to write IPTC and XMP fields? I have managed to read/write EXIF data using this sample http://commons.apache.org/sanselan/xref-test/org/apache/sanselan/sampleUsage/WriteExifMetadataExample.html but I cannot find any tag constants for iptc or xmp On Sat, Aug 13, 2011 at 10:49 AM, bizso09 wrote: > Hi, > > I'm wondering if these formats are supported by Sanselan? > > Caption-Abstract > @ > http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/IPTC.html#ApplicationRecord > > RegionPersonDisplayName > RegionRectangle > @ http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/Microsoft.html#MP > > Thanks --bcaec52c67311c105b04aa61323b--