[Bug 151719] New: patch: non latin1 in iptc keywords

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 151719] New: patch: non latin1 in iptc keywords

piotr_tarnowski
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151719         
           Summary: patch: non latin1 in iptc keywords
           Product: digikam
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: piotr_tarnowski wp pl


Version:           0.9.2-final (using KDE KDE 3.5.5)
Installed from:    Compiled From Sources
OS:                Linux

I know that in digiKam 0.10.0 XMP will be used for keywords, but for inpatient (like me) i provide workaround for using entering non-latin1 keyword names. Everything is implemented in metadatahub.cpp class:

1) if you want to store keywords in another (8-bit) encoding, you should add a tag which path ends with 'tags.encoding/<encoding>' example "extra/my.tags.encoding/ISO-8859-2"

2) load method checks for such a tag and if notices one corrects encoding of other tags

3) write method does the same

I know that this is quick and dirty but it works and what is  important stores information about encoding within image (so you can have images with different tags encoding and you do not have to remember which one has what encoding)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 151719] patch: non latin1 in iptc keywords

piotr_tarnowski
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151719         




------- Additional Comments From piotr_tarnowski wp pl  2007-11-01 22:02 -------
Created an attachment (id=21976)
 --> (http://bugs.kde.org/attachment.cgi?id=21976&action=view)
enable non-latin1 in iptc keyword names
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 151719] patch: non latin1 in iptc keywords

Gilles Caulier-4
In reply to this post by piotr_tarnowski
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151719         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Metadata



------- Additional Comments From caulier.gilles gmail com  2007-11-01 22:24 -------
Piotr,

This is the way. You need to set the Iptc.Envelope.CharacterSet properlly to describe witch encoding is used in _all_ iptc text tags.

A method need to check if this tag is alreday set and use it as well accordinly.

If this tag is not set, interpret iptc tag text content using a default text codec (set in config metadata page) and re-encrypt all text tag using the new codec, _accordinly_ with the new char encoding settings.

This is the only way to respect operability over others photo tool !

Note : all this job need to be done in libkexiv2, not digiKam core. Unforget than kipi-plugins need to do it also... There is also a report in B.K.O about this subject :

http://bugs.kde.org/show_bug.cgi?id=132244

The patch provided in this bugzilla entry is a first approach, but not _all_ is right. In fact, Iptc.Envelope.CharacterSet is never repected at all... So take a care about this code... This is why i have not yet intergrated the patch in svn.

Read the IPTC/IIM spec for details of possible char encoding in IPTC:

http://www.iptc.org/std/IIM/4.1/specification/IIMV4.1.pdf

Take a look also in this interresing thread about how to use IPTC UTF-8 char encoding with ExifTool :

http://www.cpanforum.com/threads/2114#2115

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 151719] patch: non latin1 in iptc keywords

Gilles Caulier-4
In reply to this post by piotr_tarnowski
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151719         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Metadata                    |libkexiv2
            Product|digikam                     |kipiplugins
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 151719] patch: non latin1 in iptc keywords

Gilles Caulier-4
In reply to this post by piotr_tarnowski
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151719         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|digikam-devel kde org       |kde-imaging kde org
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel