https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #24 from Maik Qualmann ---
Wrong Comment 23 here.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #23 from Maik Qualmann ---
Hi Gilles,
I fixed the issue with the user comment by supporting UTF16. But the condition
is Qt >= 5.15. I think we can close here.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426000
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|normal |wishlist
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #22 from caulier.gil...@gmail.com ---
@Rex Lee,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framewor
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #21 from Maik Qualmann ---
@Rex Lee
You should open a bug report for Stable Diffusion. Encoding the Exif comment in
UTF-16 does not conform to the Exif standard. The Exif standard strongly
recommends UTF-8 here.
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #20 from Maik Qualmann ---
Git commit 4472657499fb213cf046440fe6797f9ce344c74d by Maik Qualmann.
Committed on 30/07/2023 at 13:39.
Pushed by mqualmann into branch 'master'.
support UTF16 Exif comment with >= Qt-5.15.0
M +19 -3core/l
https://bugs.kde.org/show_bug.cgi?id=426000
Rex Lee <726494...@qq.com> changed:
What|Removed |Added
CC||726494...@qq.com
--- Comment #19 fr
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #18 from caulier.gil...@gmail.com ---
@herb
digiKam 8.1.0 pre-release Windows bundle is now ported to Exiv2 0.28 which
come with a huge list of bugfixes :
https://github.com/Exiv2/exiv2/issues/2406#issuecomment-1529139799
Installer file is
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #17 from caulier.gil...@gmail.com ---
Hi all,
digiKam 8.0.0 is out. This entry still valid with this release ?
Best regards
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #16 from Maik Qualmann ---
Git commit 59d07f9e9566f3befb3259ba9ab7d198be3c1d3c by Maik Qualmann.
Committed on 01/06/2022 at 21:10.
Pushed by mqualmann into branch 'master'.
enable unicode in the Exif caption tab and show ASCII state with an
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #15 from herb ---
Hello Maik,
thanks for your suggestion.
Please be aware that digiKam is the only metadata system (I know) that tries to
follow EXIF-standrad to 100%.
I think it is not necessary to show a special flag for UTF8-strings.
But
https://bugs.kde.org/show_bug.cgi?id=426000
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #14 from Maik
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #13 from herb ---
Dear developers,
please allow UTF-8 strings inside EXIF metadata. I repeat my request from
August 2020.
Also IPTC.org does request this feature. Please read IPTC Photo Metadata
Mapping Guidelines (version 2022.1, 2022-05-
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #12 from caulier.gil...@gmail.com ---
Git commit 3d73903c9077cb06e4a62c15b450559e3533c659 by Gilles Caulier.
Committed on 31/08/2020 at 13:46.
Pushed by cgilles into branch 'master'.
Metadata editor : sync Exif Artist with Xmp dc creator.
M
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #11 from caulier.gil...@gmail.com ---
Git commit 88fb5093407ad0582b0945410486cf43f5fc01d6 by Gilles Caulier.
Committed on 31/08/2020 at 12:33.
Pushed by cgilles into branch 'master'.
MEtadat editor : sync Exif Copyright with XMP Copyright
M
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #10 from caulier.gil...@gmail.com ---
yes digiKam must follow by default the whole Exif standard. The Exif Metadata
editor (not the viewer) only propose the Standard Exif tags.
For all extra Exif tags, the changes are done case by case. Reme
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #9 from herb ---
Hello,
thanks for your comments.
For me this leads to the question: Should Digikam follow
(1) only the EXIF-standard:
In this case you are right, many tags (e.g. also artist) allow only ASCII
characters.
(2) also the M
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #8 from caulier.gil...@gmail.com ---
So for 7.1.0, it still point 2/ todo :
Note that Exif.Image.Copyright and Exif.Image.Artist do not support UTF8 =>
ASCII only.
For the point 4/, another file in bugzilla must be open to support these tag
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #7 from caulier.gil...@gmail.com ---
My response and my resume.
1/ This is already the cases on whole digiKam metadata engine code since a
while. We try to be compliant with MWG paper since the start.
2/
XMP-dc:Description <--> EXIF:ImageD
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #6 from herb ---
Hello,
thanks for your detailed analysis.
My request is based on the following:
1) MWG requests in their document "Guidelines for Handling Image Metadata"
version 2 November 2010
http://www.metadataworkinggroup.org/pdf/mwg
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #5 from caulier.gil...@gmail.com ---
Other non standards Exif tags are encoded in UTF8:
0xc6f3 50931 Image Exif.Image.CameraCalibrationSignature ByteA UTF-8
encoded string associated with the CameraCalibration1 and CameraCalibrati
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #4 from caulier.gil...@gmail.com ---
For all Exif.Image.XP* tags, there are read only. Look the story here:
https://bugs.kde.org/show_bug.cgi?id=421464
https://dev.exiv2.org/boards/3/topics/530
Gilles Caulier
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=426000
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Metadata-Editor |Metadata-Exif
--- Comment #3 from cau
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #2 from caulier.gil...@gmail.com ---
These non official Exif tags used by Windows encode strings as UTF16 :
0x9c9b 40091 Image Exif.Image.XPTitle ByteTitle tag used by
Windows, encoded in UCS2
0x9c9c 40092 Image Exif.Image
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #1 from caulier.gil...@gmail.com ---
Herb,
I double check and Exif.Photo.UserComment is the only one official tag from
Exif paper which support UTF8 encoding using charset="unicode" prefix.
digiKam support since a while UTF8 encoding for th
https://bugs.kde.org/show_bug.cgi?id=426000
caulier.gil...@gmail.com changed:
What|Removed |Added
Platform|Other |Microsoft Windows
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=426000
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Metadata-Exif |Metadata-Editor
CC|
27 matches
Mail list logo
