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 for which darktable is partially or even not translated can die screaming, we are too busy fixing gr(e|a)ys. Come back later (or preferably never). Next top-priority project : translating dt in signs language. The chief-translator position is open, send your resumes now. Obligatory mention : "We are a dynamic team of motivated people trying to change the world one step at a time. Join us to expand your horizons in an exciting opportunity to face new challenges and give a new start to your carreer." Le 18/11/2019 à 16:30, Richard Hobday a écrit : > -- 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 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 (and GUI) should be either all British or all American >> English spelling, not just American for some and British for others. >> >> On Mon, Nov 18, 2019 at 8:29 AM Timur Irikovich Davletshin >> <timur.davlets...@gmail.com <mailto:timur.davlets...@gmail.com>> wrote: >> >> 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: >> > > 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 same thing >> across a >> > single app – at the very least. >> > >> > > It's not promised anywhere in the documentation as far as I can >> > > see. >> > >> > <sarcasm> >> > I went through the Photoshop & Lightroom docs and I can't find >> any >> > promise in the entirety of them that slider ranges of things >> sharing >> > a >> > name will match in range & effect. >> > Yet they do. >> > Go figure ... >> > <sarcasm/> >> > >> > Beers, >> > >> > .mm >> > >> _____________________________________________________________________ >> > ______ >> > darktable developer mailing list >> > to unsubscribe send a mail to >> > darktable-dev+unsubscr...@lists.darktable.org >> <mailto:darktable-dev%2bunsubscr...@lists.darktable.org> >> > >> >> >> ___________________________________________________________________________ >> darktable developer mailing list >> to unsubscribe send a mail to >> darktable-dev+unsubscr...@lists.darktable.org >> <mailto:darktable-dev%2bunsubscr...@lists.darktable.org> >> >> >> ___________________________________________________________________________ >> >> darktable developer mailing list to unsubscribe send a mail to >> darktable-dev+unsubscr...@lists.darktable.org > > -- > http://lukecarville.jalbum.net > https://facebook.com/rlc.hobday > ___________________________________________________________________________ > > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
