[1/3] [docs] winedev: Use 'quote' tags instead of double quotes
Frédéric Delanoy
frederic.delanoy at gmail.com
Sat Aug 17 02:28:38 CDT 2013
This way they can be adapted e.g. for translations.
Also use single quotes for individual characters
---
en/winedev-architecture.sgml | 16 ++++++++--------
en/winedev-coding.sgml | 21 ++++++++++-----------
en/winedev-debugger.sgml | 36 ++++++++++++++++++------------------
en/winedev-documentation.sgml | 34 ++++++++++++++++------------------
en/winedev-kernel.sgml | 14 +++++++-------
en/winedev-ole.sgml | 32 ++++++++++++++++----------------
en/winedev-opengl.sgml | 16 ++++++++--------
en/winedev-otherdebug.sgml | 6 +++---
en/winedev-testing.sgml | 12 ++++++------
en/winedev-windowing.sgml | 8 ++++----
10 files changed, 96 insertions(+), 99 deletions(-)
diff --git a/en/winedev-architecture.sgml b/en/winedev-architecture.sgml
index 84082ee..b9169a4 100644
--- a/en/winedev-architecture.sgml
+++ b/en/winedev-architecture.sgml
@@ -9,8 +9,8 @@
<title>Foreword</title>
<para>
Wine is often used as a recursive acronym, standing for
- "Wine Is Not an Emulator". Sometimes it is also known to be
- used for "Windows Emulator". In a way, both meanings are
+ <quote>Wine Is Not an Emulator</quote>. Sometimes it is also known to be
+ used for <quote>Windows Emulator</quote>. In a way, both meanings are
correct, only seen from different perspectives. The first
meaning says that Wine is not a virtual machine, it does not
emulate a CPU, and you are not supposed to install
@@ -23,9 +23,9 @@
closely.
</para>
<note>
- <title>"Emulator"</title>
+ <title><quote>Emulator</quote></title>
<para>
- The "Emulator" perspective should not be thought of as if
+ The <quote>Emulator</quote> perspective should not be thought of as if
Wine is a typical inefficient emulation layer that means
Wine can't be anything but slow - the faithfulness to the
badly designed Windows API may of course impose a minor
@@ -388,7 +388,7 @@
</para>
<para>
- Wine must at least completely replace the "Big Three" DLLs
+ Wine must at least completely replace the <quote>Big Three</quote> DLLs
(<filename>KERNEL</filename>/<filename>KERNEL32</filename>,
<filename>GDI</filename>/<filename>GDI32</filename>, and
<filename>USER</filename>/<filename>USER32</filename>),
@@ -621,7 +621,7 @@
into Win32 code by substituting the addresses of the Wine
handlers directly without any thunking layer in
between. This eliminates the overhead most people
- associate with "emulation", and is what the applications
+ associate with <quote>emulation</quote>, and is what the applications
expect anyway.
</para>
<para>
@@ -629,7 +629,7 @@
</parameter>, a thunk layer is inserted between the
application imports and the Wine handlers (actually the
export table of the DLL is modified, and a thunk is
- inserted in the table); this layer is known as "relay"
+ inserted in the table); this layer is known as <quote>relay</quote>
because all it does is print out the arguments/return
values (by using the argument lists in the DLL
descriptor's entry point table), then pass the call on,
@@ -771,7 +771,7 @@
the easily recognizable code of
<constant>0xC0000005</constant>. Any page can be mapped to
any frame, therefore you can have multiple addresses which
- actually "contain" the same memory. Pages can also be mapped
+ actually <quote>contain</quote> the same memory. Pages can also be mapped
to things like files or swap space, in which case accessing
that page will cause a disk access to read the contents into
a free frame.
diff --git a/en/winedev-coding.sgml b/en/winedev-coding.sgml
index 83998bd..8c9b0b7 100644
--- a/en/winedev-coding.sgml
+++ b/en/winedev-coding.sgml
@@ -158,9 +158,8 @@ code
<listitem>
<para>
Make sure that <filename>.diff</filename> files have
- \r\n line ends, because if OE detects that there is no
- \r\n line endings it switches to quoted-printable format
- attachments.
+ <quote>\r\n</quote> line endings, because if OE detects that
+ there are none it switches to quoted-printable format attachments.
</para>
</listitem>
<listitem>
@@ -197,8 +196,8 @@ code
<title>Quality Assurance</title>
<para>
- (Or, "How do I get Alexandre to apply my patch quickly so I
- can build on it and it will not go stale?")
+ (Or, <quote>How do I get Alexandre to apply my patch quickly so I
+ can build on it and it will not go stale?</quote>)
</para>
<para>
Make sure your patch applies to the current Git HEAD
@@ -245,7 +244,7 @@ code
<filename>foo.h</filename> is there.
</para>
<para>
- Furthermore, operating systems change names or "fork" into
+ Furthermore, operating systems change names or <quote>fork</quote> into
several ones. An <symbol>#ifdef MyOs</symbol> will break
over time.
</para>
@@ -287,8 +286,8 @@ code
to configure Wine to their system.
</para>
<para>
- There <emphasis>are</emphasis> exceptions to the "avoid
- <symbol>#ifdef MyOS</symbol>" rule. Wine, for example, needs
+ There <emphasis>are</emphasis> exceptions to the <quote>avoid
+ #ifdef MyOS</quote> rule. Wine, for example, needs
the internals of the signal stack -- that cannot easily be
described in terms of features. Moreover, you cannot use
<filename>autoconf</filename> <symbol>HAVE_*</symbol>
@@ -311,7 +310,7 @@ code
This first step is to make <command>autoconf</command> check
for this header. In <filename>configure.ac</filename> you
add a segment like this in the section that checks for
- header files (search for "header files"):
+ header files (search for <quote>header files</quote>):
</para>
<programlisting>
AC_CHECK_HEADER(foo.h, AC_DEFINE(HAVE_FOO_H))
@@ -473,10 +472,10 @@ AC_CHECK_HEADER(foo.h, AC_DEFINE(HAVE_FOO_H))
</para>
<para>
- In menus, the character "&" means that the next
+ In menus, the character '&' means that the next
character will be highlighted and that pressing that
letter will select the item. You should place these
- "&" characters suitably for your language, not just
+ '&' characters suitably for your language, not just
copy the positions from English. In particular,
items within one menu should have different highlighted
letters.
diff --git a/en/winedev-debugger.sgml b/en/winedev-debugger.sgml
index 22b3051..b67fd01 100644
--- a/en/winedev-debugger.sgml
+++ b/en/winedev-debugger.sgml
@@ -1086,7 +1086,7 @@ winedbg myprog.exe
<variablelist>
<varlistentry>
<term>
- Win32/"normal" Wine addresses/Linux: linear addresses.
+ Win32/<quote>normal</quote> Wine addresses/Linux: linear addresses.
</term>
<listitem>
<para>
@@ -1101,20 +1101,20 @@ winedbg myprog.exe
</varlistentry>
<varlistentry>
<term>
- Win16 "enhanced mode": segmented addresses.
+ Win16 <quote>enhanced mode</quote>: segmented addresses.
</term>
<listitem>
<para>
- These are the "normal" Win16 addresses, called SEGPTR.
+ These are the <quote>normal</quote> Win16 addresses, called SEGPTR.
They have a segment:offset notation, e.g. 0x01d7:0x0012.
- The segment part usually is a "selector", which
- <emphasis>always</emphasis>
+ The segment part usually is a <quote>selector</quote>, which
+ <emphasis>always</emphasis>
has the lowest 3 bits set. Some sample selectors are
0x1f7, 0x16f, 0x8f. If these bits are set except for
the lowest bit, as e.g. with 0x1f6,xi then it might be a
handle to global memory. Just set the lowest bit to get
the selector in these cases. A selector kind of
- "points" to a certain linear (see above) base address.
+ <quote>points</quote> to a certain linear (see above) base address.
It has more or less three important attributes: segment
base address, segment limit, segment access rights.
</para>
@@ -1132,12 +1132,12 @@ winedbg myprog.exe
</varlistentry>
<varlistentry>
<term>
- DOS/Win16 "standard mode"
+ DOS/Win16 <quote>standard mode</quote>
</term>
<listitem>
<para>
They, too, have a segment:offset notation. But they are
- completely different from "normal" Win16 addresses, as
+ completely different from <quote>normal</quote> Win16 addresses, as
they just represent at most 1MB of memory: The segment
part can be anything from 0 to 0xffff, and it's the same
with the offset part.
@@ -1145,7 +1145,7 @@ winedbg myprog.exe
<para>
Now the strange thing is the calculation that's behind
these addresses: just calculate segment*16 + offset in
- order to get a "linear DOS" address. So
+ order to get a <quote>linear DOS</quote> address. So
e.g. 0x0f04:0x3628 results in 0xf040 + 0x3628 = 0x12668.
And the highest address you can get is 0xfffff (1MB), of
course.
@@ -1462,9 +1462,9 @@ set $BreakAllThreadsStartup = 1
<term><registers></term>
<listitem>
<para>
- All CPU registers are also available, using $ as a
- prefix. You can use <command>info regs</command> to
- get a list of available CPU registers
+ All CPU registers are also available, using '$' as a
+ prefix. You can use <command>info regs</command> to
+ get a list of available CPU registers.
</para>
</listitem>
</varlistentry>
@@ -1559,7 +1559,7 @@ set $BreakAllThreadsStartup = 1
</msgtext>
</entry>
<entry>
- continue execution until next 'C' line of code
+ continue execution until next <quote>C</quote> line of code
(enters function call)
</entry>
</row>
@@ -1573,7 +1573,7 @@ set $BreakAllThreadsStartup = 1
</msgtext>
</entry>
<entry>
- continue execution until next 'C' line of code
+ continue execution until next <quote>C</quote> line of code
(doesn't enter function call)
</entry>
</row>
@@ -2315,7 +2315,7 @@ set $BreakAllThreadsStartup = 1
<entry>
<command>set - fixme</command>
</entry>
- <entry>turn off the 'fixme' class</entry>
+ <entry>turn off the <quote>fixme</quote> class</entry>
</row>
</tbody>
</tgroup>
@@ -2463,8 +2463,8 @@ set $BreakAllThreadsStartup = 1
kdbg -r localhost:32878 wine
</screen>
localhost:32878 is not a fixed value, but has been
- printed in step 1/. 'wine' should also be the full
- path to the Wine executable.
+ printed in first step. <quote>wine</quote> should also be the full
+ path to the Wine executable.
</para>
</listitem>
</orderedlist>
@@ -2486,7 +2486,7 @@ kdbg -r localhost:32878 wine
<para>
You need to attach the unix debugger to the correct unix
process (representing the correct windows thread) (you can
- "guess" it from a <command>ps fax</command> for example:
+ <quote>guess</quote> it from a <command>ps fax</command> command for example.
When running the emulator, usually the first two
<varname>upids</varname> are for the Windows application
running the desktop, the first thread of the application is
diff --git a/en/winedev-documentation.sgml b/en/winedev-documentation.sgml
index 26f4b57..98aa8a1 100644
--- a/en/winedev-documentation.sgml
+++ b/en/winedev-documentation.sgml
@@ -303,8 +303,8 @@
</para></listitem>
<listitem><para>
- <command>BUGS</command>. Any bugs in the function that exist 'by design', i.e.
- those that will not be fixed or exist for compatibility with Windows.
+ <command>BUGS</command>. Any bugs in the function that exist <quote>by design</quote>,
+ i.e. those that will not be fixed or exist for compatibility with Windows.
</para></listitem>
<listitem><para>
@@ -385,7 +385,7 @@
</para>
<para>
- Similarly, any interface name starting with a capital I and followed by the
+ Similarly, any interface name starting with a 'I' and followed by the
words "reference" or "object" become a link to that objects documentation.
</para>
@@ -438,7 +438,7 @@
</para>
<para>
- Any line starting with a single word followed by a colon (<command>:</command>)
+ Any line starting with a single word followed by a colon (':')
is assumed to be case listing and is emphasized and put in its own paragraph. This
is most often used for return values, as in the example section below.
</para>
@@ -449,8 +449,8 @@
</screen>
<para>
- Any line starting with a (<command>-</command>) is put into a paragraph by itself.
- this allows lists to avoid being run together.
+ Any line starting with a '-' is put into a paragraph by itself.
+ This allows lists to avoid being run together.
</para>
<para>
@@ -504,8 +504,9 @@
difference is the use of curly brackets to mark this documentation as supplemental.
The generator will output this documentation using the name given before the
DLL name, and will link to it from the main DLL page. In addition, if you have
- referred to the comment name in other documentation using "IExample interface",
- "IExample object", or "IExample()", those references will point to this documentation.
+ referred to the comment name in other documentation using <quote>IExample interface</quote>,
+ <quote>IExample object</quote>, or <quote>IExample()</quote>, those references will point to
+ this documentation.
</para>
<para>
@@ -846,7 +847,7 @@
</para>
<para>
An SGML attribute appears inside the start tag, between
- the < and > brackets. For example, if you wanted to
+ the '<' and '>' brackets. For example, if you wanted to
set the <sgmltag class="attribute">id</sgmltag> attribute
of the <sgmltag class="starttag">book</sgmltag> element to
<quote>mybook</quote>, you would create a start tag like
@@ -876,18 +877,15 @@
</para>
<para>
An entity in your document is always surrounded by the
- <quote>&</quote> and <quote>;</quote> characters. One
- entity you'll need sooner or later is the one for the
- <quote><</quote> character. Since SGML expects all
- tags to begin with a <quote><</quote>, the
- <quote><</quote> is a reserved character. To use it in
+ '&' and ';' characters. One entity you'll need sooner or later is the one
+ for the '<' character. Since SGML expects all tags to begin with a '<',
+ the '<' is a reserved character. To use it in
your document (as I am doing here), you must insert it
with the <literal><</literal> entity. Each time
the SGML processor encounters <literal><</literal>,
- it will place a literal <quote><</quote> in the output
- document. Similarly you must use the <literal>></literal>
- and <literal>&</literal> entities for the
- <quote>></quote> and <quote>&</quote> characters.
+ it will place a literal '<' in the output
+ document. Similarly you must use the <literal>></literal>
+ and <literal>&</literal> entities for the '>' and '&' characters.
</para>
<para>
The final term you'll need to know when writing simple
diff --git a/en/winedev-kernel.sgml b/en/winedev-kernel.sgml
index 20222c5..fd4d206 100644
--- a/en/winedev-kernel.sgml
+++ b/en/winedev-kernel.sgml
@@ -870,8 +870,8 @@ if (res != ERROR_SUCCESS) return res;
<sect1>
<title>File management</title>
<para>
- With time, Windows API comes closer to the old Unix paradigm "Everything
- is a file". Therefore, this whole section dedicated to file management
+ With time, Windows API comes closer to the old Unix paradigm <quote>Everything
+ is a file</quote>. Therefore, this whole section dedicated to file management
will cover firstly the file management, but also some other objects like
directories, and even devices, which are manipulated in Windows in a
rather coherent way. We'll see later on some other objects fitting
@@ -916,8 +916,8 @@ if (res != ERROR_SUCCESS) return res;
Well later on (with Windows 95), Microsoft decided to overcome some
little details in file names: this included being able to get out of
the 8+3 format (8 letters for the name, 3 letters for the
- extension), and so being able to use "long names" (that's the
- "official" naming; as you can guess, the 8+3 format is a short
+ extension), and so being able to use <quote>long names</quote> (that's the
+ <quote>official</quote> naming; as you can guess, the 8+3 format is a short
name), and also to use very strange characters in a file name (like
a space, or even a '.'). You could then name a file
<filename>My File V0.1.txt</filename>, instead of
@@ -1403,7 +1403,7 @@ if (res != ERROR_SUCCESS) return res;
When we say that most systems in NT are case insensitive, this
has to be understood for looking up for a file, where the
matches are made in a case insensitive mode. This is different
- from VFAT or NTFS "case preservation" mechanism, which stores
+ from VFAT or NTFS <quote>case preservation</quote> mechanism, which stores
the file names as they are given when creating the file, while
doing case insensitive matches.
</para>
@@ -2016,7 +2016,7 @@ if (res != ERROR_SUCCESS) return res;
<entry>
No specific Win32 object is used in this case. The
handles manipulated for the standard Win32 streams are in
- fact "bare handles" to their corresponding Unix streams.
+ fact <quote>bare handles</quote> to their corresponding Unix streams.
The mode manipulation functions
(<function>GetConsoleMode()</function> /
<function>SetConsoleMode()</function>) are not supported.
@@ -2424,7 +2424,7 @@ if (res != ERROR_SUCCESS) return res;
</para>
<para>
Windows, for a 16-bit process, defines a few selectors to access the
- "real" memory (the one provided) by DOS. Basically, Wine also
+ <quote>real</quote> memory (the one provided) by DOS. Basically, Wine also
provides this area of memory.
</para>
</sect3>
diff --git a/en/winedev-ole.sgml b/en/winedev-ole.sgml
index 528c718..cc6f950 100644
--- a/en/winedev-ole.sgml
+++ b/en/winedev-ole.sgml
@@ -405,8 +405,8 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
</para>
<para>
- For now, suffice it to say that COM lets you "marshal" interfaces into
- other "apartments". An apartment (you may see it referred to as a
+ For now, suffice it to say that COM lets you <quote>marshal</quote> interfaces into
+ other apartments. An apartment (you may see it referred to as a
context in modern versions of COM) can be thought of as a location, and
contains objects.
</para>
@@ -466,7 +466,7 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
<para>
RPC packets contain a buffer containing marshalled data in NDR format.
- NDR is short for "Network Data Representation" and is similar
+ NDR is short for <quote>Network Data Representation</quote> and is similar
to the XDR
format used in SunRPC (the closest native equivalent on Linux to DCE
RPC). NDR/XDR are all based on the idea of graph serialization and were
@@ -494,7 +494,7 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
Manually marshalling and unmarshalling each method call using the NDR
APIs (NdrConformantArrayMarshall etc) is very tedious work, so the
Platform SDK ships with a tool called "midl" which is an IDL compiler.
- IDL or the "Interface Definition Language" is a tool designed
+ IDL or the <quote>Interface Definition Language</quote> is a tool designed
specifically for describing interfaces in a reasonably language neutral
fashion, though in reality it bears a close resemblance to C++.
</para>
@@ -607,9 +607,9 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
</para>
<para>
- You may be wondering what the word "buffer" is doing in those interface
+ You may be wondering what the word <quote>buffer</quote> is doing in those interface
names. I'm not sure either, except that a running theme in DCOM is that
- interfaces which have nothing to do with buffers have the word Buffer
+ interfaces which have nothing to do with buffers have the word <quote>Buffer</quote>
appended to them, seemingly at random. Ignore it and <emphasis>don't let it
confuse you</emphasis> :) This stuff is convoluted enough ...
</para>
@@ -734,8 +734,8 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
<para>
Remember that I said our DCOM doesn't use RPC? Well, you might be
- thinking "but we use IRpcStubBuffer like we're supposed to ... isn't
- that provided by MIDL which generates code that uses the NDR APIs?". If
+ thinking <quote>but we use <type>IRpcStubBuffer</type> like we're supposed to ... isn't
+ that provided by MIDL which generates code that uses the NDR APIs?</quote>. If
so pat yourself on the back, you're still with me. Go get a cup of
coffee.
</para>
@@ -758,15 +758,15 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
<para>
So, type libraries were invented. Actually they were invented as part of
- a parallel line of COM development known as "OLE Automation", but let's
+ a parallel line of COM development known as <quote>OLE Automation</quote>, but let's
not get into that here. Type libraries are basically binary IDL files,
except that despite there being two type library formats neither of them
can fully express everything expressible in IDL. Anyway, with a type
library (which can be embedded as a resource into a DLL) you have
another option beyond compiling MIDL output - you can set the
ProxyStubClsId32 registry entry for your interfaces to the CLSID of the
- "type library marshaller" or "universal marshaller". Both terms are
- used, but in the Wine source it's called the typelib marshaller.
+ <quote>type library marshaller</quote> or <quote>universal marshaller</quote>. Both terms
+ are used, but in the Wine source it's called the typelib marshaller.
</para>
<para>
@@ -785,7 +785,7 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
actually use a mix of MIDL and typelib marshalling. In order to cover up
for the fact that we don't really use RPC they're all forced to go via
the typelib marshaller - that's what the 1 || hack is for and what the
- "Registering non-automation type library!" warning is about (I think).
+ <quote>Registering non-automation type library!</quote> warning is about (I think).
</para>
</sect2>
@@ -858,9 +858,9 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
used by the system provided standard marshaling. A STDOBJREF (standard object
reference) consists of the magic signature 'MEOW', then some flags, then the IID
of the marshaled interface. Quite what MEOW stands for is a mystery, but it's
- definitely not "Microsoft Extended Object Wire". Next comes the STDOBJREF flags,
- identified by their SORF_ prefix. Most of these are reserved, and their purpose
- (if any) is unknown, but a few are defined.
+ definitely not <quote>Microsoft Extended Object Wire</quote>. Next comes the
+ STDOBJREF flags, identified by their SORF_ prefix. Most of these are reserved,
+ and their purpose (if any) is unknown, but a few are defined.
</para>
<para>
@@ -873,7 +873,7 @@ static ICOM_VTABLE(IDirect3D) d3dvt = {
only want to unmarshal an object once. Therefore, if we strengthen the rules to say
when marshaling that we will only unmarshal once, then we no longer have to know when
it is unmarshaled. Therefore, we can give out an arbitrary number of references when
- marshaling and basically say "don't call me, except when you die."
+ marshaling and basically say <quote>don't call me, except when you die</quote>.
</para>
<para>
diff --git a/en/winedev-opengl.sgml b/en/winedev-opengl.sgml
index a4bb913..478a85c 100644
--- a/en/winedev-opengl.sgml
+++ b/en/winedev-opengl.sgml
@@ -67,7 +67,7 @@
<title>OpenGL library itself</title>
<para>
- To check for the presence of 'libGL' on the system, the
+ To check for the presence of <quote>libGL</quote> on the system, the
script checks if it defines the
<function>glXCreateContext</function> function.
</para>
@@ -98,8 +98,8 @@
<listitem>
<para>
the interface to the windowing system is different for
- each OS. It's called 'GLX' for Linux (well, for X Window)
- and 'wgl' for Windows. Thus, one need first to emulate one
+ each OS. It's called <quote>GLX</quote> for Linux (well, for X Window)
+ and <quote>wgl</quote> for Windows. Thus, one need first to emulate one
(wgl) with the other (GLX).
</para>
</listitem>
@@ -108,7 +108,7 @@
the calling convention between Windows (the 'Pascal'
convention or 'stdcall') is different from the one used on
Linux (the 'C' convention or 'cdecl'). This means that
- each call to an OpenGL function must be 'translated' and
+ each call to an OpenGL function must be <quote>translated</quote> and
cannot be used directly by the Windows program.
</para>
</listitem>
@@ -132,7 +132,7 @@
<para>
At GDI level for all pixel format selection routines (i.e.
choosing if one wants a depth / alpha buffer, the size
- of these buffers, ...) and to do the 'page flipping' in
+ of these buffers, ...) and to do the <quote>page flipping</quote> in
double buffer mode. This is implemented in
<filename>dlls/winex11.drv/opengl.c</filename>.
</para>
@@ -162,7 +162,7 @@
The script is located in <filename>dlls/opengl32</filename>
and is called <command>make_opengl</command>. It requires
Perl5 to work and takes an OpenGL version as argument.
- It's the version to 'simulate'. This fixes the list of functions
+ It's the version to <quote>simulate</quote>. This fixes the list of functions
that the Windows application can link directly to without having
to query them from the OpenGL driver.
</para>
@@ -202,7 +202,7 @@
</para>
<para>
In fact, before using one of these thunks, the Windows
- program first needs to 'query' the function pointer. At
+ program first needs to <quote>query</quote> the function pointer. At
this point, the corresponding thunk is useless. But as
we first query the same function in libGL and store the
returned function pointer in the thunk, the latter
@@ -243,7 +243,7 @@ Please report (lionel.ulmer at free.fr) !
<listitem>
<para>
Use of obsolete extensions that are not supported
- anymore by SGI or of 'private' extensions that are not
+ anymore by SGI or of <quote>private</quote> extensions that are not
registered. An example of the former are
<function>glMTexCoord2fSGIS</function> and
<function>glSelectTextureSGIS</function> as used by
diff --git a/en/winedev-otherdebug.sgml b/en/winedev-otherdebug.sgml
index e8dba3c..d34465b 100644
--- a/en/winedev-otherdebug.sgml
+++ b/en/winedev-otherdebug.sgml
@@ -131,8 +131,8 @@
<title>How to do regression testing using Git</title>
<para>
- A problem that can happen sometimes is 'it used to work
- before, now it doesn't anymore...'. Here is a step by step
+ A problem that can happen sometimes is <quote>it used to work
+ before, now it doesn't anymore...</quote>. Here is a step by step
procedure to try to pinpoint when the problem occurred. This
is <emphasis>NOT</emphasis> for casual users.
</para>
@@ -164,7 +164,7 @@ git bisect bad wine-1.1.44
<listitem>
<para>
Having told Git when things were working and when they broke,
- it will automatically "position" your source tree to the middle.
+ it will automatically <quote>position</quote> your source tree to the middle.
So all you need to do is build the source:
<screen>
./configure && make clean && make depend && make
diff --git a/en/winedev-testing.sgml b/en/winedev-testing.sgml
index 9095166..5e04b71 100644
--- a/en/winedev-testing.sgml
+++ b/en/winedev-testing.sgml
@@ -9,9 +9,9 @@
applications to crash or misbehave in some way.
</para>
<para>
- The question becomes, "How do we ensure compliance with that standard?".
- The answer is, "By using the API documentation available to us and
- backing that up with conformance tests." Furthermore, a conformance
+ The question becomes, <quote>How do we ensure compliance with that standard?</quote>.
+ The answer is, <quote>By using the API documentation available to us and
+ backing that up with conformance tests.</quote> Furthermore, a conformance
test suite is the most accurate (if not necessarily the most complete)
form of API documentation and can be used to supplement the Windows
API documentation.
@@ -301,7 +301,7 @@ Kit</ulink>.
headers, and the other uses the Microsoft headers.
</para></listitem>
<listitem><para>
- If you choose the "Win32 MSVC Headers" configuration, most of the
+ If you choose the <quote>Win32 MSVC Headers</quote> configuration, most of the
tests will not compile with the regular Visual Studio headers. So
to use this configuration, download and install a recent
<ulink url="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/">Platform SDK</ulink>
@@ -343,8 +343,8 @@ Kit</ulink>.
<title>With MinGW</title>
<para>
Wine build system already has support for building tests with a MinGW
- cross-compiler. See the section above called 'Setup of the MinGW
- cross-compiling environment' for instructions on how to set things up.
+ cross-compiler. See the section above called <quote>Setup of the MinGW
+ cross-compiling environment</quote> for instructions on how to set things up.
When you have a MinGW environment installed all you need to do is rerun
configure and it should detect the MinGW compiler and tools. Then run
'make crosstest' to start building the tests.
diff --git a/en/winedev-windowing.sgml b/en/winedev-windowing.sgml
index c977eff..50ff636 100644
--- a/en/winedev-windowing.sgml
+++ b/en/winedev-windowing.sgml
@@ -61,14 +61,14 @@
Another fairly important concept is
<firstterm>z-order</firstterm>. It is derived from the
ancestor/child hierarchy and is used to determine
- "above/below" relationship. For instance, in the example
+ <quote>above/below</quote> relationship. For instance, in the example
above, z-order is
</para>
<screen>
child1->popup->child2->child3->wnd1->child4->wnd2->desktop.
</screen>
<para>
- Current active window ("foreground window" in Win32) is
+ Current active window (<quote>foreground window</quote> in Win32) is
moved to the front of z-order unless its top-level
ancestor owns popup windows.
</para>
@@ -236,7 +236,7 @@ child1->popup->child2->child3->wnd1->child4->wnd2->desktop.
<para>
First the system looks for sent messages, then for posted
messages, then for hardware messages, then it checks if
- the queue has the "dirty window" bit set, and, finally, it
+ the queue has the <quote>dirty window</quote> bit set, and, finally, it
checks for expired timers. See
<filename>windows/message.c</filename>.
</para>
@@ -247,7 +247,7 @@ child1->popup->child2->child3->wnd1->child4->wnd2->desktop.
system message queue and then they either sit there until
<function>Get/PeekMessage</function> gets to process them
or, as in Win95, if system queue is getting clobbered, a
- special thread ("raw input thread") assigns them to the
+ special thread (<quote>raw input thread</quote>) assigns them to the
private queues. Sent messages are queued separately and
the sender sleeps until it gets a reply. Special messages
are generated on the fly depending on the window/queue
--
1.8.3.4
More information about the wine-patches
mailing list