Re: [darktable-devel] D800E Noise Calibration done (was: Noise profiles D800E derived from D800 , exif buffer length)

2013-02-21 Thread johannes hanika
tings >> LOx and HIx (<100 and >6400), script fixed. >> --> Found ISO 0 image: ./DSC_... >> >> >> 'git diff' attached, >> dt-noiseprofile-20130221.tar.gz (2,1MB) on request as personal mail? > > yes please :) > > the

Re: [darktable-devel] update nl.po into darktable 1.1.x

2013-02-21 Thread Simon Spannagel
Hi, done that. Thanks! /Simon Am 21.02.2013 20:09, schrieb Ger Siemerink: > Pascal, > > will you push the patch into darktable 1.1.xr? > an update for nl.po > > > > > -- > Everyone hates slow websites. So do we. > Ma

Re: [darktable-devel] D800E Noise Calibration done (was: Noise profiles D800E derived from D800 , exif buffer length)

2013-02-21 Thread johannes hanika
. yea, the script got a lot smarter.. since i first wrote that. thanks for profiling! > * the exiv part in gen-profile returned '0' for iso settings > LOx and HIx (<100 and >6400), script fixed. > --> Found ISO 0 image: ./DSC_... > > > &#x

Re: [darktable-devel] Urgent Translations Issue

2013-02-21 Thread Pascal de Bruijn
On Thu, Feb 21, 2013 at 7:20 PM, Alexandre Prokoudine wrote: > On Thu, Feb 21, 2013 at 10:16 PM, Pascal de Bruijn wrote: > >> And this :) >> >> https://github.com/darktable-org/darktable/commit/31cfce9062a7f4bb6d69a661820c85c36f9919c4 >> >> As translations between between master and darktable-1.1.

Re: [darktable-devel] help about maps / GPS

2013-02-21 Thread Matthias Bodenbinder
Am 21.02.2013 14:29, schrieb jeremy rosen: > I don't want to have too many ways of reseting/undoing etc... I like > the idea of having either undo or restart from scratch which is what > we currentlyu have and is very simple. For me, everything else would > need a "clear semantic" i.e a good use c

Re: [darktable-devel] Urgent Translations Issue

2013-02-21 Thread Tobias Ellinghaus
Am Donnerstag, 21. Februar 2013, 19:10:06 schrub Alexandre Prokoudine: > On Thu, Feb 21, 2013 at 10:05 PM, Pascal de Bruijn wrote: > > parafin already fixed ru.po: > > > > https://github.com/darktable-org/darktable/commit/947e88f5e12cddcfbc19c3a > > dcd3c0fdaddef380d > > Based on the patch all I

Re: [darktable-devel] Urgent Translations Issue

2013-02-21 Thread Alexandre Prokoudine
On Thu, Feb 21, 2013 at 10:16 PM, Pascal de Bruijn wrote: > And this :) > > https://github.com/darktable-org/darktable/commit/31cfce9062a7f4bb6d69a661820c85c36f9919c4 > > As translations between between master and darktable-1.1.x had already > diverged... Yes, I thought you were done with 1.1.x a

Re: [darktable-devel] Urgent Translations Issue

2013-02-21 Thread Pascal de Bruijn
On Thu, Feb 21, 2013 at 7:10 PM, Alexandre Prokoudine wrote: > On Thu, Feb 21, 2013 at 10:05 PM, Pascal de Bruijn wrote: > >> parafin already fixed ru.po: >> >> https://github.com/darktable-org/darktable/commit/947e88f5e12cddcfbc19c3adcd3c0fdaddef380d And this :) https://github.com/darktable-org

Re: [darktable-devel] Urgent Translations Issue

2013-02-21 Thread Alexandre Prokoudine
On Thu, Feb 21, 2013 at 10:05 PM, Pascal de Bruijn wrote: > parafin already fixed ru.po: > > https://github.com/darktable-org/darktable/commit/947e88f5e12cddcfbc19c3adcd3c0fdaddef380d Based on the patch all I can say is that i18n implementation in darktable is fscked :) A fuzzy translation shoul

Re: [darktable-devel] Urgent Translations Issue

2013-02-21 Thread Pascal de Bruijn
On Thu, Feb 21, 2013 at 6:42 PM, Pascal de Bruijn wrote: > On Thu, Feb 21, 2013 at 6:38 PM, Pascal de Bruijn > wrote: >> Hi, >> >> We recently uncovered a problem where translations were likely >> affecting Darktable functionality (which ideally should be >> structurally fixed in the long run),

[darktable-devel] D800E Noise Calibration done (was: Noise profiles D800E derived from D800 , exif buffer length)

2013-02-21 Thread Wolfgang Goetz
00), script fixed. --> Found ISO 0 image: ./DSC_... 'git diff' attached, dt-noiseprofile-20130221.tar.gz (2,1MB) on request as personal mail? kind regards Wolfgang diff --git a/src/common/exif.cc b/src/common/exif.cc index 4f9a06a..a468d28 100644 --- a/src/common/exif.c

Re: [darktable-devel] Urgent Translations Issue

2013-02-21 Thread Pascal de Bruijn
On Thu, Feb 21, 2013 at 6:38 PM, Pascal de Bruijn wrote: > Hi, > > We recently uncovered a problem where translations were likely > affecting Darktable functionality (which ideally should be > structurally fixed in the long run), but in the short run the only way > to fix it, is to make sure the t

[darktable-devel] Urgent Translations Issue

2013-02-21 Thread Pascal de Bruijn
Hi, We recently uncovered a problem where translations were likely affecting Darktable functionality (which ideally should be structurally fixed in the long run), but in the short run the only way to fix it, is to make sure the translation are proper. I've done a brief inspection, and these trans

Re: [darktable-devel] help about maps / GPS

2013-02-21 Thread jeremy rosen
On Thu, Feb 21, 2013 at 12:13 PM, Pascal Obry wrote: > Jeremy, > >> I'd like to point out that there are use case for "resetting image to >> default processing" (including gps data) and that use case is handled >> by DT, but I don't really see a use case for resetting only GPS data. > > Agreed. I

Re: [darktable-devel] help about maps / GPS

2013-02-21 Thread Pascal Obry
Jeremy, > I'd like to point out that there are use case for "resetting image to > default processing" (including gps data) and that use case is handled > by DT, but I don't really see a use case for resetting only GPS data. Agreed. I think it would be nice to be able to reset data from the RAW/jp

Re: [darktable-devel] help about maps / GPS

2013-02-21 Thread jeremy rosen
I'd like to point out that there are use case for "resetting image to default processing" (including gps data) and that use case is handled by DT, but I don't really see a use case for resetting only GPS data. GPS data is usually either set by the camera at capture time and not touched, or set glo

Re: [darktable-devel] export preset and picasa

2013-02-21 Thread Jose Carlos Garcia Sogo
The preset is not intended to store the credential, as that is not a secure storage, and the credential allows full access to your google account. I will be working in the following days to provide an oAuth 2.0 based mechanism and the ability to store multiple accounts. Regards, On Thu, Feb 21, 2

[darktable-devel] export preset and picasa

2013-02-21 Thread Pascal Obry
I need to export into different Picasa accounts and found out that a preset does not store the credential. Is that by design or an oversight in the implementation? Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org ht