http://www.zenphoto.org/support/ zenphoto forums Tag: xmp en Sat, 25 May 2013 14:39:55 +0000 http://www.zenphoto.org/support/topic.php?id=10224#post-60250 Tue, 10 Jan 2012 16:52:53 +0000 guilhem 60250@http://www.zenphoto.org/support/ <p>All right, thanks for your work. </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60248 Tue, 10 Jan 2012 16:42:08 +0000 sbillard 60248@http://www.zenphoto.org/support/ <p>No, I do not, I get as you expect. I am guessing that what you see is a result of the browser tyring to interpret the <code>&amp;</code><code>§</code></p> <p>Anyway, I did my tests by saving the result to a disk file to keep the browser out of the picture. </p> <p>But I did notice that <code>&amp;</code><code>apos;</code> does not get converted. So maybe we really need a full XML character table and not just the PHP <code>html_entities_decode()</code> I'll work on that. </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60242 Tue, 10 Jan 2012 15:58:02 +0000 guilhem 60242@http://www.zenphoto.org/support/ <p>Ah? I know that <code>&amp;§</code> is not valid HTML, but with the first line of my above paste (it's raw, there is no translation), I would expect <code>&amp;&#39;&amp;&#39;&amp;x&amp;§&amp;e</code>, but I get <code><a href="http://i.imgur.com/hYVsx.png" rel="nofollow">http://i.imgur.com/hYVsx.png</a></code>.<br /> Don't you get the same result? </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60229 Tue, 10 Jan 2012 12:07:58 +0000 sbillard 60229@http://www.zenphoto.org/support/ <p>It looks like it is rendering correctly to me. However remember that the output may cause you issues: <code>&amp;</code><code>§</code> is not valid HTML </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60211 Mon, 09 Jan 2012 23:42:47 +0000 guilhem 60211@http://www.zenphoto.org/support/ <p>Oops, sorry for the mess. No I mean, if you write an entity that represents the ampersand, then in some cases the character that immediately follows is ignored. Try e.g., to render <code><a href="https://pastebin.com/raw.php?i=y77sUUcB" rel="nofollow">https://pastebin.com/raw.php?i=y77sUUcB</a></code>: the first line is messed up, while the second is fine. </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60208 Mon, 09 Jan 2012 19:27:32 +0000 sbillard 60208@http://www.zenphoto.org/support/ <p>It is hard to read/write html entities on a website. But it seems to me that what you are describing is that the translation fails when you have a naked ampersand preceding an entity. That is, of ocurse, not legal--ampersand is supposed to be represented by <code>&amp;</code><code>amp;</code> </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60196 Mon, 09 Jan 2012 13:42:12 +0000 guilhem 60196@http://www.zenphoto.org/support/ <p>Wow, that was fast!<br /> I checked it against <a href="https://en.wikipedia.org/wiki/Character_entity_reference" rel="nofollow">https://en.wikipedia.org/wiki/Character_entity_reference</a>, and as far I saw the entity and numeric (decimal and hexadecimal) references are rendered properly, except one thing: the &amp; (<code>&amp;</code>, <code>&amp;#38</code> and <code>&amp;#x26</code>) "eats" one character too many in some (!) cases: try eg, to render <code>&amp;&#39;&amp;&amp;apos;&amp;x&amp;&amp;sect;&amp;e</code>. On the other hand, <code>&amp;a&amp;a</code> looks fine </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60182 Sun, 08 Jan 2012 16:42:58 +0000 sbillard 60182@http://www.zenphoto.org/support/ <p>Normally, yes, but I have made the change and it will be in the nightly tonight. I would appreciate some testing, though. </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60181 Sun, 08 Jan 2012 15:20:32 +0000 guilhem 60181@http://www.zenphoto.org/support/ <p>All right thanks ;) If you want me to open a ticket just let me know. </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60180 Sun, 08 Jan 2012 14:07:59 +0000 sbillard 60180@http://www.zenphoto.org/support/ <p>The plugin probably should be decoding HTML entities. We will add that to the list. </p> http://www.zenphoto.org/support/topic.php?id=10224#post-60175 Sun, 08 Jan 2012 10:52:27 +0000 guilhem 60175@http://www.zenphoto.org/support/ <p>Hello, </p> <p>I'm wondering, since XMP is XML-friendly, shouldn't xmpMetadata decode HTML characters references? <code>exiftool -tagsfromfile img.jpg img.xmp</code> produces a XMP where &amp; (&amp;), ' (&#39;), " (&quot;), &gt; (&gt;), and &lt; (&lt;) are escaped. On the other hand <code>exiv2 ex -e xX img.jpg</code> is fine with quotes, but escapes linefeed (&amp;#xa) among others.</p> <p>Or perhaps there another way to circumvent HTML character references?<br /> Thanks anyway! </p> http://www.zenphoto.org/support/topic.php?id=8680#post-51149 Mon, 24 Jan 2011 13:21:28 +0000 sbillard 51149@http://www.zenphoto.org/support/ <p>Zenphoto does not refine access rights to the image level, only the album level. For more details, please refer to the documentation on the Zenphoto site. </p> http://www.zenphoto.org/support/topic.php?id=8680#post-51148 Mon, 24 Jan 2011 13:18:27 +0000 aviram 51148@http://www.zenphoto.org/support/ <p>These methods won't do exactly what I was thinking about. In my idea, single photo visibility or access permission (not just entire albums) should be calculated for each user visiting the site and not globally set the way setShow() does.</p> <p>Please confirm: apparently ZP user+group system controls only general access rights of the system as "can post comments" etc. You can assign this profile to root-level albums only, not to their sub-albums, not to single photos inside of them. </p> http://www.zenphoto.org/support/topic.php?id=8680#post-51143 Mon, 24 Jan 2011 11:48:25 +0000 acrylian 51143@http://www.zenphoto.org/support/ <p>You have to do this on the theme directly as tags have no relation to our user rights management. Each theme item object has a class method to check for a tag:<br /> <a href="http://www.zenphoto.org/documentation/classes/ThemeObject.html#methodhasTag" rel="nofollow">http://www.zenphoto.org/documentation/classes/ThemeObject.html#methodhasTag</a></p> <p>Then you could use this one to set the image unpublished:<br /> <a href="http://www.zenphoto.org/documentation/classes/ThemeObject.html#methodsetShow" rel="nofollow">http://www.zenphoto.org/documentation/classes/ThemeObject.html#methodsetShow</a></p> <p>Note that this will most likely confuse your thumbnail pagination. So best you do check for this before actually displaying content on your theme. </p> http://www.zenphoto.org/support/topic.php?id=8680#post-51142 Mon, 24 Jan 2011 11:39:13 +0000 aviram 51142@http://www.zenphoto.org/support/ <p>How can define access rights or visibility based on IPTC/XMP tags previously embedded on JPEG files ?</p> <p>For example, if a new image provided to ZP is tagged as "private", set it visible only to the administrator. Or a file tagged as "confidential" will be visible only to users of group "A". Or, even further, only JPEGs taken with specific camera model will be accessible to user "B".</p> <p>I'd like to be able to define these rules but couldn't find any module that let me do that.</p> <p>I don't care about doing it directly on the DB (I can script that) but would like to have some advise or pointers on how to do that.</p> <p>Thanks in advance </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38712 Wed, 16 Dec 2009 16:25:31 +0000 sbillard 38712@http://www.zenphoto.org/support/ <p>That makes 2 of us. This stuff is pretty obscure code. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38711 Wed, 16 Dec 2009 15:57:52 +0000 justonelux 38711@http://www.zenphoto.org/support/ <p>ok, i will do my best but i m not really sure to understand how the data are extracted and parsed from the exif infos. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38710 Wed, 16 Dec 2009 15:47:01 +0000 sbillard 38710@http://www.zenphoto.org/support/ <p>I'll add the code you show above. Thanks. If you are interested in improving the nikon exif handler we would welcome your changes. The best way to do this is to make the chagnes, test them out, and attach your changed nikon.php to a ticket on the Trac system.</p> <p>Just a note, we are preparing the 1.2.8 release now, so will not make any changes that add new text to be translated until after that release. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38708 Wed, 16 Dec 2009 15:24:19 +0000 justonelux 38708@http://www.zenphoto.org/support/ <p>ok, i will try it. </p> <p>Yesterday, i look at exif and nikon.php and found a possible improuvement in nikon.php line 105 for constant aperture zoom-lenses :<br /> if ($minFL == $maxFL) {<br /> $data = sprintf('%0.0f f/%0.0f',$minFL,$minSP);<br /> <strong>} elseif ($minSP == $maxSP) {<br /> $data = sprintf('%0.0f-%0.0fmm f/%0.1f',$minFL,$maxFL,$minSP);</strong><br /> } else {<br /> $data = sprintf('%0.0f-%0.0fmm f/%0.1f-%0.1f',$minFL,$maxFL,$minSP,$maxSP);<br /> }</p> <p>and <a href="http://owl.phy.queensu.ca/~phil/exiftool/TagNames/Nikon.html">a post about exif datas in nikon lenses</a>. Especially, at the end, how to calculate the exact lens type from a bunch of exif infos. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38664 Tue, 15 Dec 2009 16:46:45 +0000 sbillard 38664@http://www.zenphoto.org/support/ <p>After further investigation of the image you supplied. Seems there is a part of the standard that allows a shorthand notation. We did not implement that, but with tonight's nightly build it is there. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38647 Tue, 15 Dec 2009 10:23:44 +0000 justonelux 38647@http://www.zenphoto.org/support/ <p>ok, thanks again. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38646 Tue, 15 Dec 2009 10:19:58 +0000 sbillard 38646@http://www.zenphoto.org/support/ <p>The field should be EXIFLensType. We will fix that.</p> <p>You should open a ticket on this and attach the image that is not being correctly processed. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38645 Tue, 15 Dec 2009 10:18:33 +0000 sbillard 38645@http://www.zenphoto.org/support/ <p>The field should be EXIFLensType. We will fix that.</p> <p>You should open a ticket on this and attach the image that is not being correctly processed. </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38644 Tue, 15 Dec 2009 10:11:50 +0000 justonelux 38644@http://www.zenphoto.org/support/ <p>for the two F, they are in EXI<strong>FF</strong>LensType.</p> <p>i check again, there is lens data on the field aux:lens </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38607 Mon, 14 Dec 2009 16:58:56 +0000 sbillard 38607@http://www.zenphoto.org/support/ <p>Maybe your XMP data does not have the fields <code>aux:Lens</code>. There is no mapping defined for LensType.</p> <p>Where do you see the 2F? </p> http://www.zenphoto.org/support/topic.php?id=6616#post-38605 Mon, 14 Dec 2009 16:02:45 +0000 justonelux 38605@http://www.zenphoto.org/support/ <p>hi, </p> <p>i just enabled the xmp extension, check the file format in the options and check that my file had xmp datas.</p> <p>the function getImageData('EXIFLensInfo')does not return anything so i look in the image : print_r($_zp_current_image)).</p> <p>the fields [EXIFFLensType] =&gt; [EXIFLensInfo] =&gt; are empty to.</p> <p>where am i wrong ?</p> <p>thanks,<br /> Jérémie</p> <p>by the way, there is 2F in the field name EXIFFLensType, is it a bug ? </p> http://www.zenphoto.org/support/topic.php?id=2110#post-25464 Thu, 06 Nov 2008 09:17:17 +0000 sbillard 25464@http://www.zenphoto.org/support/ <p>It would be relative easy to add XMP support to zenphoto since it would parallel or extend the current EXIF/IPTC handling. Just create an intermediate interface module that is passed the desired field. That module would then decide if the data was stored in the standard form or in XMP and invoke the appropriate library.</p> <p>It just takes someone who is interested in this to do the work.</p> <p>BTW: Adobe Bridge is quite happy to store the metadata in the traditional EXIF/IPTC fileds. </p> http://www.zenphoto.org/support/topic.php?id=2110#post-25460 Thu, 06 Nov 2008 07:13:32 +0000 walkerblackwell 25460@http://www.zenphoto.org/support/ <p>This is a common miss-understanding with XMP. XMP can be both embedded and built as sidecars. My first impression of XMP was one of distaste because the format was not portable (ie: embedded into files like IPTC.) I was wrong about that though. Bridge and many other applications embed the data directly into the images.</p> <p>Because it's built on XML and has dynamic DTDs, we can specify any kind of data and embed that data portably into the file. This includes schema for videos, tifs, and all sorts of files. I think zenphoto has a great organizational backend and database. It now needs to extend to include many forms of media and media tagging schemas. If it does this, it can become the mama bear. </p> http://www.zenphoto.org/support/topic.php?id=2110#post-25137 Mon, 27 Oct 2008 08:28:11 +0000 olihar 25137@http://www.zenphoto.org/support/ <p>Isn't easy enough to save the keywords (tags) and other code in the JPG file that gets uploaded to the server and make ZenPhoto read it like it is right now. I am not seeing XMP reading something you need, as uploading RAW files is something we wouldn't do?</p> <p>I do love the XMP standard and how clean and handy it is. Well tough many people don't like it the reason given is all the small extra little files all over the place. I do like it however. I am looking forward to see how the DNG goes in the future where the XMP is "build" into the RAW file. </p> http://www.zenphoto.org/support/topic.php?id=2110#post-25135 Mon, 27 Oct 2008 07:27:19 +0000 walkerblackwell 25135@http://www.zenphoto.org/support/ <p>You can view the work that's going on with XMP here. <a href="http://www.adobe.com/devnet/xmp/" rel="nofollow">http://www.adobe.com/devnet/xmp/</a> I would suggest adding a Flex GUI for metadata handling. Adobe has already done a lot of the leg-work for XMP 2 via Flex. It wouldn't be to much to put this online and Adobe would probably hire anyone who does it. </p>