<br><br><div><span class="gmail_quote">2007/3/9, Carrion, Fabian (GE Money, consultant) <<a href="mailto:Fabian.Carrion@ge.com">Fabian.Carrion@ge.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><span><font color="#0000ff" face="Arial" size="2">Hi,</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">Yeah I
have to take care about c++ exception.</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">I
haven't use your libkexiv2 interface because Jesper tells me to use that
library.</font></span></div></div></blockquote><div><br>This interface use Exception for you and take a care of IPTC string size. It a QT like interface, more easy to use than pure C++ using exception.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><span><font color="#0000ff" face="Arial" size="2">Ok I
had a look at your metadataedit plugin.</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">My
plugin should map directly ImageInfo datas to IPTC tags and IPTC tags to
ImageInfo datas.</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">Right
now I maped it that way from info to Iptc:</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Iptc.Application2.Headline <--
info.title</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Iptc.Application2.Caption <--
info.description</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Iptc.Application2.Category <-- <a href="http://album.name" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">album.name</a></font></span></div>
</div></blockquote><div><br>Wrong: "Category" is not a simple string. Use "subcategory" instead category and set "category" to the 3 char tag explained in IPTC doc.<br><br>Also, take a care than IPTC strings are size limited.
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><span><font color="#0000ff" face="Arial" size="2">Iptc.Application2.DateCreated
<--
info.time().toString("yyyy-MM-dd")</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Iptc.Envelope.TimeSent
<-- info.time().toString("hh:mm:ss")</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Iptc.Application2.Keywords <--
info.attributes().key("Keywords")</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Iptc.Application2.City
<-- info.attributes().key("Locations")</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2"><span><font color="#0000ff" face="Arial" size="2">Right now I maped
it that way from Iptc to info:</font></span></font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">info.setDescription
<-- Iptc.Application2.Caption</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">info.addAttributes("Keywords") <--
Iptc.Application2.Keywords</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">info.addAttributes("Locations") <--
Iptc.Application2.City</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">info.setTitle <--
Iptc.Application2.Headline</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">Just
want to know if you agree with this mapping. </font></span></div></div></blockquote><div><br>Well, in digiKam we have already a mapping interface with IPTC. Your mapping is a little bit different than digiKam. I recommend you to include this mapping code in KPhotoAlbum core, not like a common plugin.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><span><font color="#0000ff" face="Arial" size="2">Does
metadataedit do the same ?</font></span></div></div></blockquote><div><br>no. this plugin is a metadata tags editor from scratch (EXIF and IPTC).<br><br>There is also 2 plugins witch already do a part of your code : <br>
<br>-CommentEdit (from MetadataEdit plugin) about to batch Comments on Exif and IPTC <br>-TimeAdjust plugin witch batch date and time in IPTC and Exif.<br><br>All my code use libkexiv2, not Exiv2 directly. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><span><font color="#0000ff" face="Arial" size="2">If not
I can think about an integration between both plugin =)</font></span></div></div></blockquote><div><br>no, this is not the same. I recommend to put your code in KphotoAlbum core not kipi-plugins. It's too specific. I have do this with digiKa. My kipi-plugins are independant of kipi hosts metadata rules. They can be used from every hosts without break anything.
<br><br>Also, i recommend to read the IPTC doc. It's important to following this notice. IPTC is used by pro photograph and require to be following exactly, else others program witch support IPTC will cannot read properlly the metadata.
<br><br><a href="http://www.iptc.org/std/IIM/4.1/specification/IIMV4.1.pdf">http://www.iptc.org/std/IIM/4.1/specification/IIMV4.1.pdf</a><br><br>Gilles</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br></blockquote></div><br>