Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2432
Your paranoid andr
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2433
Your paranoid andr
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2430
Your paranoid andr
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2431
Your paranoid andr
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=2429
Your paranoid andr
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=23747
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=23751
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=23748
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=23750
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=23749
Your paranoid android
Hi,
On 10/01/12 13:07, Julian Rüger wrote:
Hi Francois,
- * size [I] How much percent of cache space should be free.
+ * size [I] How many percents of the cache should be free.
Maybe something like "Precentage of cache that should be free" would
sound more natural. Howe
Hi Francois,
> - * size [I] How much percent of cache space should be free.
> + * size [I] How many percents of the cache should be free.
Maybe something like "Precentage of cache that should be free" would
sound more natural. However I'm not sure of the intended meaning her
Hi Francois,
> -/* if we set the bufferpointer to NULL here UrlUnescape fails and
> string gets not converted */
> +/* if we set the buffer pointer to NULL here UrlUnescape fails and
> the string is not converted */
for consistency with the other buffer pointer comments and be
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=21742
Your paranoid android
On Thu, 3 May 2012, Nicolas Le Cam wrote:
[...]
> > IMO they shouldn't be translated, since they indicate the long version
> > of options.
[...]
> You're right !
> (Even if code seems to only check if the second letter is a 'a' or
> anything else .. and windows only advertise /MIN and /MAX as valid
2012/5/3 Frédéric Delanoy :
> On Thu, May 3, 2012 at 7:07 AM, Nicolas Le Cam wrote:
>> Le 3 mai 2012 02:45, "Francois Gouget" a écrit :
>>
>>
>>> @@ -9429,9 +9429,9 @@ msgstr ""
>>> "start [options] document_filename\n"
>>> "\n"
>>> "Options:\n"
>>> -"/M[inimized] Start the program minimized.\
On Thu, May 3, 2012 at 7:07 AM, Nicolas Le Cam wrote:
> Le 3 mai 2012 02:45, "Francois Gouget" a écrit :
>
>
>> @@ -9429,9 +9429,9 @@ msgstr ""
>> "start [options] document_filename\n"
>> "\n"
>> "Options:\n"
>> -"/M[inimized] Start the program minimized.\n"
>> -"/MAX[imized] Start the program
Le 3 mai 2012 02:45, "Francois Gouget" a écrit :
> @@ -9429,9 +9429,9 @@ msgstr ""
> "start [options] document_filename\n"
> "\n"
> "Options:\n"
> -"/M[inimized] Start the program minimized.\n"
> -"/MAX[imized] Start the program maximized.\n"
> -"/R[estored] Start the program normally (neither
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=13664
Your paranoid android
com/nonexistent
> http://www.thefreedictionary.com/non-existent
> http://dictionary.reference.com/browse/nonexistent
> http://dictionary.reference.com/browse/non-existent
>
> Overall 'nonexistent' seemed better referenced in the dictionaries and
> more 'legitimate'. But I can leave either form as is if that's
> preferred.
It is not a spelling fix then and shouldn't be included in a "spelling
fixes" patch. You could do a "Standardize to 'nonexistent'" patch but
that would IMHO stretch the scope of this kind of janitorial fixes.
bye
michael
The errors reported by testbot are not related to this patch.
Should I resent a version without the "failing" hunks?
Frédéric
On 8/3/11 4:23 PM, Francois Gouget wrote:
On Wed, 3 Aug 2011, Frédéric Delanoy wrote:
[...]
-rem Removing non-existent directory
+rem Removing nonexistent directory
[...]
There is apparently no hard rule on the usage of hypens between 'non'
and a subsequent adjective, but I've seen lots of "no
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=13256
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=13249
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=13236
Your paranoid android
On Wed, 3 Aug 2011, Frédéric Delanoy wrote:
[...]
> > -rem Removing non-existent directory
> > +rem Removing nonexistent directory
[...]
> There is apparently no hard rule on the usage of hypens between 'non'
> and a subsequent adjective, but I've seen lots of "non-" (sometimes
> even "non ") so I
On Wed, Aug 3, 2011 at 11:36, Francois Gouget wrote:
> diff --git a/programs/cmd/tests/test_builtins.cmd
> b/programs/cmd/tests/test_builtins.cmd
> index eb79fb2..be1eead 100644
> --- a/programs/cmd/tests/test_builtins.cmd
> +++ b/programs/cmd/tests/test_builtins.cmd
> @@ -530,7 +530,7 @@ mkdir f
Thanks for sending a patch for this. It seems it was not committed,
probably because your mailer added line-breaks, making it difficult to
apply.
Could you resend as an attachment, or without the line breaks if you
can configure your mailer to do that?
Or, if you prefer, I can send this with fixe
2008/12/28 Francois Gouget :
> -FIXME("No free constant found to load environemnt bump mapping
> matrix into the shader. texbem instruction will not apply bump mapping\n");
> +FIXME("No free constant found to load environement bump mapping
> matrix into the shader. texbem
On 22/04/2008, Austin English <[EMAIL PROTECTED]> wrote:
> -/* Declare loop registers aLx */
> +/* Declare loop registers alx */
> for (i = 0; i < reg_maps->loop_depth; i++) {
> shader_addline(buffer, "int aL%u;\n", i);
> shader_addline(buffer, "int tmpInt%u;\n", i);
This patch does not apply for me, I get the following errors:
[EMAIL PROTECTED]:/home/httpd/html/winehq_org$ git am ~/Downloads/patch.eml
Applying Assorted spelling fixes.
.dotest/patch:38: trailing whitespace.
between GDI/USER and the KERNEL, that is not absolutely needed, must be
.dotest
Am Donnerstag, 28. Februar 2008 18:19:28 schrieb Vitaly Lipatov:
> Changelog:
> - replace 'iff' with 'if' (just a spelling fixes)
The usual meaning of iff is "if and only if", so its not necessarily a typo
signature.asc
Description: This is a digitally signed message part.
Dan Kegel wrote:
lav at etersoft.ru wrote:
- replace 'iff' with 'if' (just a spelling fixes)
'iff' is shorthand for 'if and only if'.
http://en.wikipedia.org/wiki/If_and_only_if
So many of those 'typos' might actually be correct.
Car
lav at etersoft.ru wrote:
> - replace 'iff' with 'if' (just a spelling fixes)
'iff' is shorthand for 'if and only if'.
http://en.wikipedia.org/wiki/If_and_only_if
So many of those 'typos' might actually be correct.
Careful!
- Dan
On Thursday 24 January 2008 23:25:53 Dan Kegel wrote:
> On Jan 24, 2008 2:20 PM, Austin English <[EMAIL PROTECTED]> wrote:
> > > I never thought about it before, but "centred" is perfectly fine
> > > English, at least in England.
> > > Guess I need to add that to stop.txt.
> >
> > I've never seen i
On Jan 24, 2008 4:25 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> On Jan 24, 2008 2:20 PM, Austin English <[EMAIL PROTECTED]> wrote:
> > > I never thought about it before, but "centred" is perfectly fine
> > > English, at least in England.
> > > Guess I need to add that to stop.txt.
> >
> > I've neve
On Jan 24, 2008 2:20 PM, Austin English <[EMAIL PROTECTED]> wrote:
> > I never thought about it before, but "centred" is perfectly fine
> > English, at least in England.
> > Guess I need to add that to stop.txt.
>
> I've never seen it used personally.
My test for whether a word is commonly used is
On Jan 24, 2008 1:37 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> Austin wrote:
> >-/* centred vertically and in the right side of the password edit
> control */
> >+/* centered vertically and in the right side of the password
> edit control */
>
> I never thought about it before, but "centre
Austin wrote:
>-/* centred vertically and in the right side of the password edit
control */
>+/* centered vertically and in the right side of the password
edit control */
I never thought about it before, but "centred" is perfectly fine
English, at least in England.
Guess I need to add that
Austin wrote:
>only used for optimization, so just check for a very small set of
>- criteria that guarantee the types are equivalent; assume every thing
>+ criteria that guarantees the types are equivalent; assume everything
The original was correct, please don't change that.
Firstly, it'
Any reason this patch wasn't applied? I didn't see any feedback on wine-patches.
http://www.winehq.org/pipermail/wine-patches/2008-January/048933.html
-Austin
Now how did that one slip in. Reading the diff before sending is a bit
hard, since there are so many typos, they get hard to track. I'll
resend in a couple minutes. Thanks for catching it.
-Austin
On Jan 10, 2008 11:20 AM, Jonathan Ernst <[EMAIL PROTECTED]> wrote:
>
> On jeu, 2008-01-10 at 10:53
On jeu, 2008-01-10 at 10:53 -0600, Austin English wrote:
> - * which is essentially an input, is the destiantion register
> because it is the first
> - * param. According to the msdn, this must be register r5, but
> let's keep it more flexible
> + * which is essentially an input, is th
On Tuesday 08 January 2008, Dan Kegel wrote:
> A few issues:
>
> 1.
> * DPMI_xalloc
> - * special virtualalloc, allocates lineary monoton growing memory.
> + * special virtualalloc, allocates linear monoton growing memory.
>
> Um... Probably should be 'linearly'.
> But if you're opening
James McKenzie:
> I am a long time programmer and expect the include to be next
> to the # sign. However, you are correct in that it does not
> break code, and if it is not broken, why fix? Is it possible
> to indent the entire line by two spaces (I think it is not)?
Probably not. I know the
Francois Gouget wrote:
> #ifdef HAVE_UNISTD_H
> -# include
> +#include
> #endif
> #include
> #include
>
> I think this chunk should not be applied because:
> * as pointed out before, it's not a spelling fix
> * it's perfectly valid to have a space there
> * the indentation makes the scop
Austin English wrote:
> On Jan 8, 2008 10:42 AM, Francois Gouget <[EMAIL PROTECTED]> wrote:
>
>> - *3 - controller supports hardware stereoscopic signalling
>> + *3 - controller supports hardware stereoscopic signaling
>> *4 - =0 stereo signalling via external VESA ster
Glad I asked then. I won't touch these. Sorry for the noise.
Austin English wrote:
> I'm seeing quite a few abbreviations. While they don't hurt anything,
> they do give the code a slang tone. I personally think that wine is a
It's not slang but jargon!
> very professional project, and it's code should reflect that. While
This is an open source project and
I also object to removing abbreviations or Britishisms.
The key to being a successful spelling policeman
is to stick to noncontroversial spelling fixes,
and avoiding anything controversial or non-spelling-related.
On Jan 8, 2008 2:44 PM, Austin English <[EMAIL PROTECTED]> wrote:
> I'm seeing quite a few abbreviations. While they don't hurt anything,
> they do give the code a slang tone. I personally think that wine is a
> very professional project, and it's code should reflect that. While
> this is obviously
I'm seeing quite a few abbreviations. While they don't hurt anything,
they do give the code a slang tone. I personally think that wine is a
very professional project, and it's code should reflect that. While
this is obviously a very generic question, I wanted to clarify before
submitting some chang
On Tue, 8 Jan 2008, Austin English wrote:
[...]
> Just so I know, are we going with American or British English? There's
> a lot of inconsistency, though the majority seems to be American...
We're not standardising on either, that is, both spellings should be
considered valid. Any other course of
> Just so I know, are we going with American or British English? There's
> a lot of inconsistency, though the majority seems to be American...
I think there's a weak preference for American spelling, but I don't
see much reason to "correct" spelling from British to American
English.
--Juan
On Jan 8, 2008 10:42 AM, Francois Gouget <[EMAIL PROTECTED]> wrote:
>
> - *3 - controller supports hardware stereoscopic signalling
> + *3 - controller supports hardware stereoscopic signaling
> *4 - =0 stereo signalling via external VESA stereo connector
> *
- *3 - controller supports hardware stereoscopic signalling
+ *3 - controller supports hardware stereoscopic signaling
*4 - =0 stereo signalling via external VESA stereo connector
*=1 stereo signalling via VESA EVC connector
Why are you changing 'signalling
#ifdef HAVE_UNISTD_H
-# include
+#include
#endif
#include
#include
I think this chunk should not be applied because:
* as pointed out before, it's not a spelling fix
* it's perfectly valid to have a space there
* the indentation makes the scope of the #ifdef clearer. So removing it
ma
A few issues:
1.
* DPMI_xalloc
- * special virtualalloc, allocates lineary monoton growing memory.
+ * special virtualalloc, allocates linear monoton growing memory.
Um... Probably should be 'linearly'.
But if you're opening the can of worms, might as well really
improve it. I suspect
On Jan 7, 2008 11:57 PM, Juan Lang <[EMAIL PROTECTED]> wrote:
> Hi Austin,
>
> -case 0x32: /* ENABLE/DISABLE VIDEO ADDRERSSING */
> +case 0x32: /* ENABLE/DISABLE VIDEO ADDRRESSING */
>
> That's still misspelled.
Thanks for catching that/these. After looking at all these
misspellings
Hi Austin,
-case 0x32: /* ENABLE/DISABLE VIDEO ADDRERSSING */
+case 0x32: /* ENABLE/DISABLE VIDEO ADDRRESSING */
That's still misspelled.
- * special virtualalloc, allocates lineary monoton growing memory.
+ * special virtualalloc, allocates linear monoton growing memory.
Monot
I changed that in two places. The first one had another typo in the
same file, so I went ahead and fixed both typos. The second occurrence
was in a separate file, but I corrected it for consistency.
- Austin
On Jan 4, 2008 11:28 AM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> Francois wrote:
> > I'd s
Francois wrote:
> I'd say "'coz" is not a typo, but was written that way intentionally to
> give a 'slang-ish' tone to the comment by someone who knows full well
> the standard spelling. As such it should not be modified.
I've seen too many people who aren't
even aware of the difference between sl
> -/* test has been removed 'coz MMSYSERR_BASE is 0, and gcc did
> emit
> +/* test has been removed because MMSYSERR_BASE is 0, and gcc did
> emit
I'd say "'coz" is not a typo, but was written that way intentionally to
give a 'slang-ish' tone to the comment by someone w
On Fri, 7 Dec 2007, H. Verbeet wrote:
> On 07/12/2007, Francois Gouget <[EMAIL PROTECTED]> wrote:
> > --- a/dlls/wined3d/glsl_shader.c
> > +++ b/dlls/wined3d/glsl_shader.c
> > - * out. The nvidia driver only does that if the parameter is inout
> > instead of out, hence the
> > - *
On 07/12/2007, Francois Gouget <[EMAIL PROTECTED]> wrote:
> --- a/dlls/wined3d/glsl_shader.c
> +++ b/dlls/wined3d/glsl_shader.c
> - * out. The nvidia driver only does that if the parameter is inout
> instead of out, hence the
> - * inout.
> + * out. The nvidia driver only d
s/concensus/consensus
On Tue, 26 Oct 2004, Filip Navara wrote:
> Francois Gouget wrote:
>
> >Index: wwn/wn20041015_244.xml
> >===
> >RCS file: /var/cvs/lostwages/wwn/wn20041015_244.xml,v
> >retrieving revision 1.1
> >diff -u -r1.1 w
Francois Gouget wrote:
Index: wwn/wn20041015_244.xml
===
RCS file: /var/cvs/lostwages/wwn/wn20041015_244.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20041015_244.xml
--- wwn/wn20041015_244.xml 15 Oct 2004 03:59:52 - 1.1
+++ wwn/w
67 matches
Mail list logo
