[WineHQ] Assorted spelling fixes
Francois Gouget
fgouget at free.fr
Tue Feb 8 14:56:17 CST 2005
Changelog:
* templates/en/janitorial.template
templates/en/status_todo.template
wwn/wn20040903_238.xml
wwn/wn20050128_259.xml
wwn/wn20050204_260.xml
Assorted spelling fixes.
--
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
There are 10 types of people in the world...
those who understand binary and those who don't.
-------------- next part --------------
Index: templates/en/janitorial.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/janitorial.template,v
retrieving revision 1.68
diff -u -p -r1.68 janitorial.template
--- templates/en/janitorial.template 1 Feb 2005 16:17:44 -0000 1.68
+++ templates/en/janitorial.template 8 Feb 2005 18:49:07 -0000
@@ -36,8 +36,8 @@
Regedit lacks a few features. We need to improve regedit to:
<ul>
- <li>Allow display and editting of binary (REG_BINARY) values.
- <li>Allow display and editting of multi-string (REG_SZ_MULTI) values.
+ <li>Allow display and editing of binary (REG_BINARY) values.
+ <li>Allow display and editing of multi-string (REG_SZ_MULTI) values.
<li>Import registry files regerated by Windows 2000 regedit
</ul>
<p>
Index: templates/en/status_todo.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/status_todo.template,v
retrieving revision 1.14
diff -u -p -r1.14 status_todo.template
--- templates/en/status_todo.template 27 Jan 2005 15:21:25 -0000 1.14
+++ templates/en/status_todo.template 8 Feb 2005 18:49:16 -0000
@@ -53,8 +53,8 @@
<pre>
Regedit]
- * Allow display and editting of binary (REG_BINARY) values.
- * Allow display and editting of multi-string (REG_SZ_MULTI) values.
+ * Allow display and editing of binary (REG_BINARY) values.
+ * Allow display and editing of multi-string (REG_SZ_MULTI) values.
* Import registry files regerated by Windows 2000 regedit.
[winecfg]
Index: wwn/wn20040903_238.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040903_238.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20040903_238.xml
--- wwn/wn20040903_238.xml 7 Sep 2004 16:14:19 -0000 1.2
+++ wwn/wn20040903_238.xml 8 Feb 2005 18:49:35 -0000
@@ -448,7 +448,7 @@ it:</p>
I'm going to play with the richedit control to try get it to draw RTF
documents with formatting. My plan is to write a program that can
-display but not edit, then let somebody else add the editting
+display but not edit, then let somebody else add the editing
functionality afterwards :) Once I can get the attached program to
work, the plan is to change the code in text-writer.c to add the
formatting information to the richedit control via standard richedit
Index: wwn/wn20050128_259.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20050128_259.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20050128_259.xml
--- wwn/wn20050128_259.xml 28 Jan 2005 21:03:46 -0000 1.1
+++ wwn/wn20050128_259.xml 8 Feb 2005 18:27:39 -0000
@@ -167,7 +167,7 @@ somewhere? Francois Gouget pointed out:
has access to the things you as a user have access to. Since a normal
user can't erase a hard drive, a virus running under Wine isn't
going to be able to either. However, Hiji pointed out this is still a
-real problem for people using Sun's JDS since currently mounts
+real problem for people using Sun's JDS since it currently mounts
Windows partitions as read/write for regular users. </p>
<p>Okay, so say a virus does manage to insert itself on your
@@ -327,7 +327,7 @@ and replied to Mike's bullet points:</p>
<ul>
It is easy, but not as easy a regular Wiki. By a long shot. Moreover
a Wiki like MoinMoin is so common on the web that people know it,
-and they don't have to lear yet another markup format. And you can not
+and they don't have to learn yet another markup format. And you cannot
compare the click-to-edit--edit--click-to-save ease of using a Wiki
with the procedure to change this one (mentioning svk, diff, mail, etc,
and you've lost 95% of people, right there).</ul></p>
@@ -347,7 +347,7 @@ This has been a non-argument from the be
by the silly FAQ-O-Matic, but that wasn't really a Wiki. There are so
many Wikis on the web that work just fine and are useful (see the Arch
Wiki, and so many others) that this has no support whatsoever. In fact,
-the lack of control (and the associated ease of editting) are the very
+the lack of control (and the associated ease of editing) are the very
reason to use Wikis, and we are giving these up for some irrational
fears.</ul></p><p>
Index: wwn/wn20050204_260.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20050204_260.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20050204_260.xml
--- wwn/wn20050204_260.xml 7 Feb 2005 07:19:11 -0000 1.1
+++ wwn/wn20050204_260.xml 8 Feb 2005 07:57:36 -0000
@@ -142,7 +142,7 @@ window. The loose ends are mostly relate
exported functions in user32.spec can give you a rough idea of what
remains to be done. For OpenGL what we need is to implement proper
clipping when drawing to a child window. There are also a number of
-window management hacks in the Crossover tree that need to be cleaned
+window management hacks in the CrossOver tree that need to be cleaned
up and brought over.</p></quote>
<p>Lionel Ulmer described some of issues with OpenGL:</p>
@@ -239,7 +239,7 @@ completed riched20 code.
</p><p>
Code review notes:
</p><p>
-You've writen the code to deal with unicode as default, which is good,
+You've written the code to deal with unicode as default, which is good,
but you need to deal with both ASCII and unicode messages in the window
procedure.
</p><p>
@@ -253,7 +253,7 @@ Similarly, you'll need to use "winbase.h
From what I can see in the old riched32 code, the rtf parser looks
quite good, so don't try rewrite that (which from my quick check you
haven't). We can merge the parser into the riched20 code quite
-easily... it's just enters the text into the existing control using
+easily... it just enters the text into the existing control using
EM_SETSEL and some formatting messages.
</p><p>
I have a test I can send to you if you wish. Again, my preference is to
@@ -286,7 +286,7 @@ not what I want it to be, but it's bette
<p>Rob Shearman had some suggestions concerning "undo" functionality:</p>
<quote who="Robert Shearman"><p>
-Undo should be pretty easy as long as you can represent easily represent
+Undo should be pretty easy as long as you can easily represent
user actions in a transactions stack.
A user doing something will then cause an action to be pushed onto the
stack (although you would probably want some coalescing so that you
@@ -322,7 +322,7 @@ it. Is that OK ?
</p><p>
It's not like everything is done the way it should be (for instance,
-coordinate system is still pixel-based and not twips-based), but in this
+coordinate system is still pixel-based and not twips-based), but at this
stage the risk of having to constantly rewrite everyone else's code is
much lower.</p></quote>
@@ -344,7 +344,7 @@ any problem. The only things missing are
MS-RichEdit emulation (Data types and message translations). But it
looks like these two are what above patch and existing code has. I am
almost positive that if such a parser (And emulation layer) is submitted
-to the Scintilla project it will be farther maintained by the project.
+to the Scintilla project it will be further maintained by the project.
One more thing good about it, that makes a lot of sense, is its
popularity, which means there are a lot of people that know this
code-base and can help fix problems. (And it does compile under wine out
@@ -500,7 +500,7 @@ easier on the eyes:</p>
Not really related to the actual wine development but more to the
make/build/install environment.
</p><p>
-Remembering the most wine users will not necessarily be developers we should
+Remembering that most wine users will not necessarily be developers we should
consider improving the output of running (./configure && make) to make it
more user friendly. Hopefully it should also be less confronting and
confusing to non developers. I propose something similar to the way the
More information about the wine-patches
mailing list