That XMP was shared by you and it contains coordinates next to Valatie. The JPEG from the same post is read fine in dt for me with coordinates in Newark. So far I couldn’t reproduce any errors. All tests were with , as the decimal separator.
So if the XMP you shared there wasn’t written by Lr but is the auto generated file from dt let’s ignore it from now on and just discuss the JPG. What place does it get put on when running dt with an English GUI and the Windows settings left at the French defaults (,)? You can try it by adding this to your command line arguments:
--conf ui_last/gui_language=C
I’ll be afk for the rest of the week so it might take a while for me to answer.
Sorry, you are correct, I shared the xmp and it is the one generated by dt.
I went though the two changes you asked and yes, with an english langage of dt and comma separator for Windows, there is no mistake. So the mistake comes from the fench version of dt… and can somehow be “corrected” by changing the defaults number settings of Windows
I was so happy to have tried to recently do my first export using DT for Win! Unfortunately, I noticed that only a portion of the primary watermark I use was exported together with my photos. I use a SVG file that has both an image and text. The text portion doesn’t get fully included in the exported image. Has anyone experienced this, too?
So far I’ve tried re-inkscaping (no expert here) the SVG file and used different fonts for the text, but that only creates either a filled black box or have the text too spaced out on where the text is supposed to be
Any helpful ideas (or theories) appreciated, thanks!
sorry for this rather late reply. I only have found time to re-emerge out of submarine mode now.
After compiling git master I tried to proceed with noise profiling my D7500. At the end of the gen-profile I always received an error message, but a presets.json file and pdf files were created. So I manually copied the settings into noiseprofiles.json. After thisI tested my profile the last few weeks quite successfully and found out, that it works slightly better than using Ari El’s D500 profile (same sensor as D7500). i used tried it out on about a 100 pictures at ISO 3200 and on half a dozen ISO 2000 pictures. I am happy with it.D7500NPN.7z (6.5 MB)
This is yet another snapshot installer that should fix the bug with exporting. When selecting a path in the file chooser it will now escape all \ characters. Please give it a try.
I’d prefer to fix this properly. Unfortunately I can’t reproduce. I tried setting my locale settings in the Windows preferences to French, I tried setting LC_NUMERIC=fr, nothing triggered the bug when opening the Newark JPG.
@csierra02: Do you have a build environment set up to compile darktable on Windows? Otherwise I would provide you a test compile that has a bunch of debug outputs to maybe track down where it fails.
It’s strange that you can’t reproduce. I got the bug as I had a French default windows setting AND DT language : French
If you loose one of these two conditions either Windows, either DT language, the bug disappears.
To be able to test both the french DT and the english one, I tried to install DT twice, one in French and one in English in two separate folders at the root of my C harddisk. And also two separate folders for the pictures… This did no work. Went back with one installation with the two folders. I got mixed results, as soon as I open the picture with Dt in French, I do also have the bug as I open the other folder with DT set to English… So the parameters of the picture are not only written to the xmp sidecar file but also within DT
I am finally left to DT in English.
No I don’t have a compile environment. I am not an IT guy only a non professional photographer…
What happens when you import the image in an English darktable (so everything is correct), close darktable and open it in French? Where does the map put your image? The right place?
If I remember it correctly, Windows has f-i-v-e different major FR settings (Belgium, Canada, France, Luxembourg, Switzerland) plus e-i-g-h-t minor ones (Cameroon, Congo, Côte d’Ivoire, Mali, Monaco, Morocco, Senegal, West Indies), i.e. 13 different settings for one parameter or more.
Would DT recognize them all or could this be the reason for the non-correct interpretation?
@Claes I suppose there will always be regional differences. We just need to be aware of language conventions that actually interfere with the programming efforts of our dear (grumpy) devs.
That is why I used the vague term conventions. Look no further than conventions within a country. Even then, people can’t decide how to format their date and time.
