From sanselan-dev-return-304-apmail-incubator-sanselan-dev-archive=incubator.apache.org@incubator.apache.org Wed Aug 13 10:50:05 2008 Return-Path: Delivered-To: apmail-incubator-sanselan-dev-archive@locus.apache.org Received: (qmail 18432 invoked from network); 13 Aug 2008 10:50:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Aug 2008 10:50:05 -0000 Received: (qmail 15168 invoked by uid 500); 13 Aug 2008 10:50:04 -0000 Delivered-To: apmail-incubator-sanselan-dev-archive@incubator.apache.org Received: (qmail 15147 invoked by uid 500); 13 Aug 2008 10:50:04 -0000 Mailing-List: contact sanselan-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: sanselan-dev@incubator.apache.org Delivered-To: mailing list sanselan-dev@incubator.apache.org Received: (qmail 15134 invoked by uid 99); 13 Aug 2008 10:50:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2008 03:50:04 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of charlesmchen@gmail.com designates 209.85.134.189 as permitted sender) Received: from [209.85.134.189] (HELO mu-out-0910.google.com) (209.85.134.189) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2008 10:49:08 +0000 Received: by mu-out-0910.google.com with SMTP id w9so2958618mue.0 for ; Wed, 13 Aug 2008 03:49:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=NVmvOHsujH3rdqEzdWDEJnJMZuttXihonPP05B9PYdU=; b=jbFcP4vVmrqOCBbaCZKX99NsnQdg/wLNoukY89yOjyMjR6R3gdLBeHN0Ls7iwHEqCl hhQNNKzKMo4nubsZzX29erlDmdz452aE+9sDJCdgtfm8zp+hmRPpDuvaenZv3zjyivVq YUGrtPxCKvGxdWE6AJhOYyAJFt2qt0ySc7/wQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=nSHMBT8DYwjafpTEwA/N13xUnnsF1aLqf1Kwp9LZJpu5lCSyWR9cG3Zp7gfqoWxL28 3Fq0Fs5Ze86Sdqh8Txab18oW/i7y1BsgyNVZF4vmqC+NQOVZD+pYxSsTr781nH5kf6Tw ST0b5RCieTjLj3S1h7LisaJJ9KWKQG+Al0R28= Received: by 10.103.172.7 with SMTP id z7mr7991602muo.40.1218624575367; Wed, 13 Aug 2008 03:49:35 -0700 (PDT) Received: by 10.103.178.16 with HTTP; Wed, 13 Aug 2008 03:49:35 -0700 (PDT) Message-ID: Date: Wed, 13 Aug 2008 12:49:35 +0200 From: "Charles Matthew Chen" To: sanselan-dev@incubator.apache.org Subject: Re: Is "writing IPTC" a priority? In-Reply-To: <03B33509-5951-4FCF-9D5D-9C8772C9D868@thebluncks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <80A626B7-8633-46F5-B498-B382AAF7A4B4@thebluncks.com> <03B33509-5951-4FCF-9D5D-9C8772C9D868@thebluncks.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi Christopher, There's nothing really blocking my work on IPTC - just finding the time. Thanks though. The documentation could use a lot of work. The things I was planing on doing myself are: - Exact list of what features, spec versions, modes, etc. are supported for each file format. - Comparison with other Java image libraries and description of why and when to use Sanselan. - More sample code. - Elaborating the FAQ. Charles On Mon, Aug 11, 2008 at 3:38 PM, Christopher Blunck wrote: > Ok cool. I have other work I can do on my project. I've got my code > pushing down to Sanselan to pull the IImageMetadata out of a rich byte[] and > I'm using the ExifRewriter to place the metadata into a naked byte[] > produced from JAI. Once your IPTC writing code is done it should fall into > place. :) > > Is there anything I can do to take some work off your plate? That would > give you more time to focus on IPTC writing which would of course help me. > :) > > I was thinking about cleaning up the docs/website a bit. There are a bunch > of broken links and whatnot... > > > -c > > On Aug 11, 2008, at 4:50 AM, Charles Matthew Chen wrote: > >> Hi Christopher, >> >> Thanks for your interest in the project. >> >> Writing (ie. removing, inserting and updating) IPTC to existing >> JPGs is under active development (by me). I expect it to be checked >> in within the next 3 months at the very latest. >> >> The project doesn't have any formal established development >> priorities. I'm personally working on IPTC support, as well as more >> granular control over reading and writing images, elaborating the unit >> test suite, improving the documentation, etc. >> >> Thanks for getting involved. >> >> Charles >> >> >> On Mon, Aug 11, 2008 at 5:31 AM, Christopher Blunck >> wrote: >>> >>> I just incorporated sanselan into my application and it works great for >>> enriching images with metadata from another file. It's perfect for >>> situations where you have to resize an image but wish to preserve as much >>> of >>> the metadata as possible. The one thing that's lacking is IPTC writing. >>> Sanselan is able to read the IPTC metadata but it can't write it back >>> out... >>> >>> I was just wondering ... is "writing IPTC" a priority for anyone? If >>> not, >>> what are the other priorities? I'm trying to figure out how long I'll >>> possibly have to wait for this feature and if it would be worth buying >>> into >>> a commercial project if I really need this feature for my application. >>> >>> Thanks for the great work on Sanselan so far... I plan on contributing >>> to >>> the documentation and what-not as much as I can. >>> >>> >>> -c >>> >>> > >