On Tue, Jul 14, 2009 at 1:47 AM, Charles Matthew Chen<[email protected]> wrote: > +dev > > Hi Jonathan, > > Sanselan is in the process of moving into the Commons project - bear with > us. > > dev, user: how does Commons handle issue tracking? Should we open > an issue for this issue in our old JIRA issue tracker?
Looks to me like the existing Sanselan JIRA issue tracker has just been moved under commons. So yes nothing changes with creating issues - you can either point people to the same JIRA url here: http://issues.apache.org/jira/browse/SANSELAN or theres a page on the Sanselan site which provides guidance and useful urls for the Sanselan JIRA instance: http://commons.apache.org/sanselan/issue-tracking.html Niall > Jonathan: once we've sorted out the issue tracking question, please > open an issue. It would be very helpful if you could > attach/contribute an image and source that reproduce the issue. A > code snippet that demonstrates how you are using Sanselan is fine. > > Matthew > > > On Mon, Jul 13, 2009 at 6:25 PM, Jonathan > Giles<[email protected]> wrote: >> Hi there everyone, >> >> I'm trying to use Sanselan to write XMP data to an image. The problem is >> that in doing so, it appears to corrupt the other IPTC data such that it is >> not visible in all circumstances (i.e. Windows Explorer doesn't display it). >> It's there in the file, just not in the expected location perhaps. >> >> Is there a way to handle this such that the added XMP doesn't change the >> content of the rest of the file? I tried re-writing the IPTC metadata but to >> no avail. Perhaps I haven't discovered the magic sequence of events that >> need to be followed. >> >> Any pointers would be much appreciated! >> Cheers, >> Jonathan Giles >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
