On Fri, 2021-03-26 at 18:22 +0100, Erik Faye-Lund wrote:
> On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote:
> > TLDR; I'm proposing to standardize on US English in our public-
> > facing
> > documentation.
> >
> > I proposed an MR a while back that changed the only occurrence of
> > the
>
On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote:
> TLDR; I'm proposing to standardize on US English in our public-facing
> documentation.
>
> I proposed an MR a while back that changed the only occurrence of the
> UK English spelling "optimisation" for the US English spelling
>
+1 to recommending the use of US English spelling in Mesa docs & code.
I certainly would not want to impose any heavy burdens on contributors
who are accustomed to UK/AU spelling. I don't think we should block any
patches because of UK/US/AU spelling, and people should feel free to
not think
On Mon, 2021-03-15 at 10:54 -0700, Ian Romanick wrote:
>
> If anyone doesn't feel comfortable speaking out publicly about this,
> please feel free to contact Erik or me privately.
Just thought I'd mention; I've gotten a vote against the proposal
through other channels. Because I haven't gotten
>Absolutely. Apparently I forgot to write the final line which is that I
>think standardising on US English across the board is a good thing
Standardise on any flavour of English you'd like, one of them is still
wrong ;-)
___
mesa-dev mailing
Hi,
On Mon, Mar 15, 2021 at 01:44:18PM +0100, Erik Faye-Lund wrote:
> The main reason I want to standardize on an English variant is that I'm
> trying create a word-list for domain-specific/technical language to
> detect spelling mistakes in the docs more easily.
Are you aware of codespell[1]?
On Tue, 16 Mar 2021 at 13:08, Jason Ekstrand wrote:
> On March 16, 2021 05:06:53 Daniel Stone wrote:
>
>> On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand
>> wrote:
>>
>>> Three comments:
>>>
>>> 1. +1
>>> 2. Khronos has generally standardized on American English in their
>>> specs so I guess
On March 16, 2021 05:06:53 Daniel Stone wrote:
On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand wrote:
Three comments:
1. +1
2. Khronos has generally standardized on American English in their
specs so I guess that provides some sort of prior art or something.
3. I'd generally be a fan of
Just one detail to fill in:
I just got a question on #dri-devel if this suggestion would place an
additional burden on most developers to additionally look up every word
of new documentation to see if it's US or UK English.
I'm not proposing to place any additional burden on people writing
docs.
On Tue, 2021-03-16 at 10:06 +, Daniel Stone wrote:
> On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand
> wrote:
> > Three comments:
> >
> > 1. +1
> > 2. Khronos has generally standardized on American English in their
> > specs so I guess that provides some sort of prior art or something.
> >
On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand wrote:
> Three comments:
>
> 1. +1
> 2. Khronos has generally standardized on American English in their
> specs so I guess that provides some sort of prior art or something.
> 3. I'd generally be a fan of encouraging American spellings in common
>
On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote:
> TLDR; I'm proposing to standardize on US English in our public-facing
> documentation.
+1
J.A.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
On Mon, 15 Mar 2021 at 22:44, Erik Faye-Lund
wrote:
>
> TLDR; I'm proposing to standardize on US English in our public-facing
> documentation.
>
> I proposed an MR a while back that changed the only occurrence of the
> UK English spelling "optimisation" for the US English spelling
>
+1 to all of this.
On Mon, Mar 15, 2021 at 1:54 PM Jason Ekstrand wrote:
>
> Three comments:
>
> 1. +1
> 2. Khronos has generally standardized on American English in their
> specs so I guess that provides some sort of prior art or something.
> 3. I'd generally be a fan of encouraging American
Three comments:
1. +1
2. Khronos has generally standardized on American English in their
specs so I guess that provides some sort of prior art or something.
3. I'd generally be a fan of encouraging American spellings in common
code as well. As someone who doesn't use auto-complete, having to
On 3/15/21 5:44 AM, Erik Faye-Lund wrote:
> TLDR; I'm proposing to standardize on US English in our public-facing
> documentation.
>
> I proposed an MR a while back that changed the only occurrence of the
> UK English spelling "optimisation" for the US English spelling
> "optimization", which is
TLDR; I'm proposing to standardize on US English in our public-facing
documentation.
I proposed an MR a while back that changed the only occurrence of the
UK English spelling "optimisation" for the US English spelling
"optimization", which is already used 34 times in the docs. I've done
similar
17 matches
Mail list logo
