Le lundi 18 novembre 2019 à 20:13 +0100, Aurélien Pierre a écrit :
> Don't, it's fine.
>
> But serious bug reports like crashes, regressions, Mac/Win/Nux and
> CPU/GPU inconsistencies do pile up faster than fixes, so all the
> cosmetic talk about the proper way to write grey is kind of
> hilarious
Don't, it's fine.
But serious bug reports like crashes, regressions, Mac/Win/Nux and
CPU/GPU inconsistencies do pile up faster than fixes, so all the
cosmetic talk about the proper way to write grey is kind of hilarious. I
wonder sometimes if users realize we are just a handful working on a
day-to
My apologies
On Mon, Nov 18, 2019 at 10:58 AM Aurélien Pierre
wrote:
> Forget about segfaults and crashes, our first priority is now to make
> every native English speaker feel respected in his difference and identity,
> offering fully differentiated support of every English dialect : en_GB,
> e
Forget about segfaults and crashes, our first priority is now to make
every native English speaker feel respected in his difference and
identity, offering fully differentiated support of every English dialect
: en_GB, en_AU, en_US, en_ZA, en_CA, en_NZ, en_FJ…
Meanwhile, people speaking languages f
-- Tongue firmly in cheek --
en-GB or en-US ?
That is the real question.
They are two very different languages, at present darktable seems to
assume they are the same!
R.
On 18/11/2019 14:36, Julian Rickards wrote:
grAy is the American spelling and there's nothing wrong with that
(despite being
Well, my point was not about American vs British. It was just an
example of inconsistency. And odd tradition of lowercasing all capitals
make it only worse. Regarding this particular case... Well I think this
information (colorspace, type of curve) somehow must be delivered to
user. Otherwise devel
grAy is the American spelling and there's nothing wrong with that (despite
being a Canadian and using British spelling, LoL) but Timur is correct,
there should be consistency and, in addition to sticking to the same
spelling of gray/grey, I think that that the English version of the
documentation (
Maybe it's time to choose project leader and start collecting
donations?
On Mon, 2019-11-18 at 15:11 +0100, Aurélien Pierre wrote:
> darktable also lacks a board of investors, a CTO, a head of UX, a
> project management, a panel of test users, a famous photographer as a
> brand ambassador, many tr
darktable also lacks a board of investors, a CTO, a head of UX, a
project management, a panel of test users, a famous photographer as a
brand ambassador, many tracking features to collect statistics on usage
"to improve the performance", an annual coding sprint in the Bahamas and
a couple of off-sh
Well, that’s the problem with basic adjustment module - IMHO it shouldn’t
exist, because it duplicates functionality of other modules, while adding
problems like the one discussed here.
> On 18 Nov 2019, at 16:13, Moritz Moeller wrote:
>
> On 15.11.19 12:02, parafin wrote:
>> I think these n
Actually I agree. Darktable lacks of terminology unification across
modules. E.g. AFAIR there are around 6 different names for 18% gray. In
some places it is "grey" but in others it is "gray".
Timur.
On Mon, 2019-11-18 at 14:03 +0100, Moritz Moeller wrote:
> On 15.11.19 12:02, parafin wrote:
> >
On 15.11.19 12:02, parafin wrote:
I think these numbers don't have units, so why do expect them to mean
the same thing in different modules, even if we ignore the pipe order?
Because that's the most basic requirement of usability. That things
named the same way act the same way and mean the sa
12 matches
Mail list logo
