=?UTF-8?Q?Fr=C3=A9d=C3=A9ric=20Delanoy=20?=: winelib: Use valid values for 'filename' tag attributes.

Alexandre Julliard julliard at winehq.org
Mon Jul 22 15:10:04 CDT 2013


Module: docs
Branch: master
Commit: f4f1d0ef4d4963520a06bbf73bb85d0a5b60edcb
URL:    http://source.winehq.org/git/docs.git/?a=commit;h=f4f1d0ef4d4963520a06bbf73bb85d0a5b60edcb

Author: Frédéric Delanoy <frederic.delanoy at gmail.com>
Date:   Mon Jul 22 14:20:19 2013 +0200

winelib: Use valid values for 'filename' tag attributes.

---

 en/winelib-bindlls.sgml |    4 ++--
 en/winelib-intro.sgml   |    4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/en/winelib-bindlls.sgml b/en/winelib-bindlls.sgml
index 596c112..304a3fe 100644
--- a/en/winelib-bindlls.sgml
+++ b/en/winelib-bindlls.sgml
@@ -45,7 +45,7 @@
         extremely simple and leads into the subject in "baby steps".  The
         second example is the ODBC interface proxy in Wine.  The files to which
         we will refer for the ODBC example are currently in the 
-        <filename class="Directory">dlls/odbc32</filename> directory of the
+        <filename class="directory">dlls/odbc32</filename> directory of the
         Wine source.
       </para>
       <para>
@@ -170,7 +170,7 @@ signed short WINAPI MyProxyWinFunc (unsigned short a, void *b, void *c,
       <para>
         For a more extensive case we can use the ODBC example.  This is
         implemented as a header file 
-        (<filename class="HeaderFile">proxyodbc.h</filename>) and the actual
+        (<filename class="headerfile">proxyodbc.h</filename>) and the actual
         C source file (<filename>proxyodbc.c</filename>).  Although the file
         is quite long it is extremely simple in structure.
       </para>
diff --git a/en/winelib-intro.sgml b/en/winelib-intro.sgml
index 8a6fe38..0f85543 100644
--- a/en/winelib-intro.sgml
+++ b/en/winelib-intro.sgml
@@ -208,8 +208,8 @@
                 can help it guess what it is that your project is
                 trying to build. Otherwise, it is able to understand
                 Visual C++ projects. Usually the executables and libraries are
-                in a <filename class="Directory">Release</filename> or
-                <filename class="Directory">Debug</filename> subdirectory of the
+                in a <filename class="directory">Release</filename> or
+                <filename class="directory">Debug</filename> subdirectory of the
                 directory where the sources are. So it's best if you can
                 transfer the source files and either of these directories to
                 Linux. Note that you don't need to transfer the




More information about the wine-cvs mailing list