svn commit - mysqldoc@docsrva: r5996 - trunk/mysqldoc-guide

[stefan]

Author: shinz
Date: 2007-04-19 12:28:47 +0200 (Thu, 19 Apr 2007)
New Revision: 5996

Log:
Intermediate commit

Modified:
   trunk/mysqldoc-guide/overview.de.xml
   trunk/mysqldoc-guide/overview.xml


Modified: trunk/mysqldoc-guide/overview.de.xml
===================================================================
--- trunk/mysqldoc-guide/overview.de.xml	2007-04-18 23:59:37 UTC (rev 5995)
+++ trunk/mysqldoc-guide/overview.de.xml	2007-04-19 10:28:47 UTC (rev 5996)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 16; 2908 bytes

@@ -170,45 +170,42 @@
     </table>
 
     <para>
-      The remaining directories hold the documentation itself, either in
-      DocBook XML format or in a format that can be built and translated
-      into DocBook XML for publishing. These directories also contain
-      any additional files required for the document, such as the entity
-      definitions (including some common files), and the graphics files
-      used for illustrations and screenshots. In each case, there is
+      Die sonstigen Verzeichnisse enthalten die Dokumentation selbst,
+      zumeist im Format DocBook XML, teilweise aber auch in einem
+      anderen XML-Format, das durch Transformation in DocBook XML
+      umgewandelt werden kann. Zusätzlich enthalten diese Verzeichnisse weitere
für die Dokumentation benötigte Dateien, beispielsweise
Entitätsdefinitionen und Grafikdateien (Diagramme und Bildschirmfotos).
+      <remark>I've asked MC about the following sentence.</remark>
+      In each case, there is
       typically only one document target in each directory, but each
       document can be translated into any one of the desired formats.
     </para>
 
     <table id="mysqldoc-guide-overview-dirent-docs">
-      <title>Documentation directories in mysqldoc</title>
+      <title>Dokumentationsverzeichnisse in mysqldoc</title>
       <tgroup cols="2">
         <thead>
           <colspec colwidth="30*"/>
           <colspec colwidth="70*"/>
           <row>
-            <entry>Directory</entry>
-            <entry>Description</entry>
+            <entry>Verzeichnis</entry>
+            <entry>Beschreibung des Inhalts</entry>
           </row>
         </thead>
         <tbody>
           <row>
             <entry><filename>administrator</filename></entry>
-            <entry>The files specific to the Administrators guide.</entry>
+            <entry>Dateien für das Handbuch zum GUI-Tool MySQL
Administrator.</entry>
           </row>
           <row>
             <entry><filename>arbitrary</filename></entry>
-            <entry>The directory which holds specifications for arbitrary
documentation.
-              See
-
+            <entry>Enthält die Spezifikationen für die
<quote>beliebige Dokumentation</quote>, siehe
 <!--<xref
-            linkend="mysqldoc-guide-tools-arby"/>-->
-
+            linkend="mysqldoc-guide-tools-arby"/>-->.
               .</entry>
           </row>
           <row>
             <entry><filename>common</filename></entry>
-            <entry>Files common to all documents.</entry>
+            <entry>Für alle Dokumente benutzte Dateien.</entry>
           </row>
           <row>
             <entry><filename>dynamic-docs</filename></entry>


Modified: trunk/mysqldoc-guide/overview.xml
===================================================================
--- trunk/mysqldoc-guide/overview.xml	2007-04-18 23:59:37 UTC (rev 5995)
+++ trunk/mysqldoc-guide/overview.xml	2007-04-19 10:28:47 UTC (rev 5996)
Changed blocks: 4, Lines Added: 3, Lines Deleted: 9; 2227 bytes

@@ -13,7 +13,7 @@
     Somewhere we should mention that the whole documentation system is
     based on open source components or free software (MS Help Workshop).
   </remark>
-
+<remark>Generally, you're using the term "translate" quite often to talk about
transformations. This can be confusing considering that a lot of our docs stuff is about
translations (of human language). I'd suggest to use "transform" for the former.
/SH</remark>
   <para>
     MySQL develops all of the documentation internally. This includes
     the various version specific reference manuals, the documentation

@@ -116,17 +116,11 @@
     <remark>
       "In addition ... also ..." sounds redundant /SH
     </remark>
-
-
-
     <remark>
       Also, I'd suggest to give an example or two for "enhanced
       functionality" because otherwise this sounds like marketing buzz.
       :-) /SH
     </remark>
-
-
-
     <remark>
       Might also make sense to point out that all tools (including those
       "additional tools and utilities" are either XSLT or Perl.

@@ -236,7 +230,7 @@
       definitions (including some common files), and the graphics files
       used for illustrations and screenshots. In each case, there is
       typically only one document target in each directory, but each
-      document can be translated into any one of the desired formats.
+      document can be translated into any one of the desired formats. <remark>I
don't understand the last sentence; can you elaborate or give an example?</remark>
     </para>
 
     <table id="mysqldoc-guide-overview-dirent-docs">

@@ -253,7 +247,7 @@
         <tbody>
           <row>
             <entry><filename>administrator</filename></entry>
-            <entry>The files specific to the Administrators guide.</entry>
+            <entry>The files specific to the MySQL Administrator guide.
<remark>Can we stick to "manual" or "documentation"?
/SH</remark></entry>
           </row>
           <row>
             <entry><filename>arbitrary</filename></entry>