jyapayne/glymur
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

The XMP uuid data is an ElementTree instance, not an Element instance.

Browse source
This commit is contained in:
jevans 2013-07-22 18:00:44 -04:00
commit e75cdcf686
1 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/source/how_do_i.rst
View file

@ -185,9 +185,8 @@ Work with XMP UUIDs?
==================== ====================
The example JP2 file shipped with glymur has an XMP UUID. :: The example JP2 file shipped with glymur has an XMP UUID. ::
>>> from glymur import Jp2k >>> import glymur
>>> file = glymur.data.nemo() >>> j = glymur.Jp2k(glymur.data.nemo())
>>> j = Jp2k(file)
>>> print(j.box[4]) >>> print(j.box[4])
UUID Box (uuid) @ (715, 2412) UUID Box (uuid) @ (715, 2412)
UUID: be7acfcb-97a9-42e8-9c71-999491e3afac (XMP) UUID: be7acfcb-97a9-42e8-9c71-999491e3afac (XMP)
@ -198,7 +197,7 @@ The example JP2 file shipped with glymur has an XMP UUID. ::
</rdf:RDF> </rdf:RDF>
</ns0:xmpmeta> </ns0:xmpmeta>
Since the UUID data in this case is returned as an ElementTree Element, one can Since the UUID data in this case is returned as an ElementTree instance, one can
use ElementTree to access the data. For example, to extract the use ElementTree to access the data. For example, to extract the
**CreatorTool** attribute value, the following would work:: **CreatorTool** attribute value, the following would work::