<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>In my mind this seems to imply that your directory, file names
and maybe even your associated metadata have characters not shared
between Linux and Windows.</p>
<p>Linux uses UTF-8 while Windows CP-1252. They are different code
pages and when characters unique to one or other code page is used
in a system that is not code-page aware -- like Windows, the
programs get upset.<br>
</p>
The only way to resolve the issue is to fix the offending paths,
file names or metadata.<br>
<br>
This is applicable for any program and is not unique to DigiKam.<br>
<br>
Although this may not be the main problem, my understanding is that
the path of files are stored as UUID+Path. I am not sure how robust
the conversion routines are converting paths between Linux/UNIX
format and Windows Format. Some of the issues may relate to this.
Certainly most people report problems when moving their data between
drives as this changes the UUID.<br>
<br>
If I have the time, to test, I'd create one directory with a small
number of files. Check all of them for any character that is are not
a-z, A-Z, 0-9, space and _<br>
<br>
Duplicate on your NAS.<br>
<br>
Try creating a database in Linux using one of the directories.<br>
Try creating a database in Windows using the other directory.<br>
<br>
Try adding the Linux directory to Windows install and visa versa. I
suspect this won't work. If it does, then the issue you are
reporting is probably just code page incompatibility and you need to
seek out the offending characters.<br>
<br>
<b>@Gilles -- This list regularly gets queries about how to setup a
central photo repositories and have multiple clients looking into
the a single database. In most cases, like Clive its involves
mixed operating systems. I have never seen a clear response from
the developers if this is even feasible. Can you please clarify?</b><b><br>
</b><br>
<div class="moz-cite-prefix">On 09/07/18 02:01, Gilles Caulier
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHFG6sFRjZrbMmJyF1trzp01nw2EpVdid0Ymhin94FSsuDB45Q@mail.gmail.com">
<div dir="ltr">Hi,
<div><br>
</div>
<div>This message do not come from digiKam directly, but from
Exiv2 shared library. It's not a bug as the message is clear :
it's a limitation.</div>
<div><br>
</div>
<div>Now the question is why it appear under Windows and not
Linux. I don't know. The Question must be posted to Exiv2
team, to be clear.</div>
<div><br>
</div>
<div>Best</div>
<div><br>
</div>
<div>Gilles Caulier</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2018-07-08 13:40 GMT+02:00 cliver <span
dir="ltr"><<a href="mailto:clive@reynoldscrc.me.uk"
target="_blank" moz-do-not-send="true">clive@reynoldscrc.me.uk</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
I'm new to Digikam and image management in general so please
bear with me.<br>
<br>
I am trying to organise all my old photos and maintain
things ongoing. I<br>
have a collection of older images, mainly jpegs and some
newer RAW images<br>
taken from a Nikon D7200 camera. All stored on a local NAS.<br>
<br>
I have 2 instances of Digikam installed.<br>
Version 5.6.0 on a laptop running Ubuntu Mate<br>
Version 5.9.0 on an different Laptop running Windows 10<br>
<br>
I installed the Ubuntu version first and set it up and it
seems to be<br>
running OK. However my windows 10 laptop is far more
powerful so I decided<br>
to try the windows version.<br>
On this instance when I set up Digikam the same and add the
same NAS folder<br>
as a collection I get a load of errors when I run Digikam
and when I try to<br>
open any of the RAW images downloaded from the camera.<br>
<br>
The errors I am getting are:<br>
Read Error at Scanline xxxxxxx, got 252 bytes, expected
8160<br>
Unknown Field with tag 36867 (0x9003) encountered<br>
ASCII value for TAG 'Copyright' contains null byte in
value<br>
Value incorrectly truncated during reading due to
implementation<br>
limitations<br>
<br>
These errors despite reading exactly the same files in both
instances.<br>
<br>
So my question:<br>
Have I missed something in the setup on the windows version?<br>
Or is this a bug in the Windows version of Digikam?<br>
Or perhaps a bug in either the Nikon camera software or even
windows (heaven<br>
forbid ;)<br>
<br>
I am contemplating setting the windows machine to dual boot
linux but it's<br>
brand new and still under warranty so would like to at least
delay that if I<br>
can.<br>
<br>
Can anyone guide me as to the best way forward in getting it
to run on<br>
windows?<br>
<br>
Thanks and Regards<br>
Clive<br>
<br>
<br>
<br>
<br>
--<br>
Sent from: <a
href="http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://digikam.1695700.n4.<wbr>nabble.com/digikam-users-<wbr>f1735189.html</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
Cheers Simon <br>
<br>
<span style="padding:3em"> Simon Cropper</span><br>
<span style="padding:3em"> Principal Consultant</span><br>
<span style="padding:3em"> Botanicus Australia Pty Ltd</span><br>
<span style="padding:3em"> M: 0420 531 754.</span><br>
<span style="padding:3em"> W:
<a class="moz-txt-link-freetext" href="http://www.simonchristophercropper.com">http://www.simonchristophercropper.com</a></span><br>
<br>
</div>
</body>
</html>