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.
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
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
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
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
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),
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
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
