svn commit - mysqldoc@docsrva: r12927 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0

[jon]

Author: jstephens
Date: 2008-12-12 01:01:47 +0100 (Fri, 12 Dec 2008)
New Revision: 12927

Log:

Fixed invalid indexterms



Modified:
   trunk/refman-4.1/internationalization.xml
   trunk/refman-5.0/internationalization.xml
   trunk/refman-5.1/internationalization.xml
   trunk/refman-6.0/internationalization.xml


Modified: trunk/refman-4.1/internationalization.xml
===================================================================
--- trunk/refman-4.1/internationalization.xml	2008-12-11 20:59:54 UTC (rev 12926)
+++ trunk/refman-4.1/internationalization.xml	2008-12-12 00:01:47 UTC (rev 12927)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 642 bytes

@@ -7477,7 +7477,7 @@
 
     <indexterm>
       <primary>time zones</primary>
-      <primary>support</primary>
+      <secondary>support</secondary>
     </indexterm>
 
     <para>

@@ -7777,7 +7777,7 @@
 
       <indexterm>
         <primary>time zones</primary>
-        <primary>upgrading</primary>
+        <secondary>upgrading</secondary>
       </indexterm>
 
       <para>


Modified: trunk/refman-5.0/internationalization.xml
===================================================================
--- trunk/refman-5.0/internationalization.xml	2008-12-11 20:59:54 UTC (rev 12926)
+++ trunk/refman-5.0/internationalization.xml	2008-12-12 00:01:47 UTC (rev 12927)
Changed blocks: 5, Lines Added: 110, Lines Deleted: 108; 10907 bytes

@@ -7535,11 +7535,12 @@
   <section id="time-zone-support">
 
     <title>MySQL Server Time Zone Support</title>
-<indexterm>
-<primary>time zones</primary>
-<primary>support</primary>
-</indexterm>
 
+    <indexterm>
+      <primary>time zones</primary>
+      <secondary>support</secondary>
+    </indexterm>
+
     <para>
       The MySQL server maintains several time zone settings:
     </para>

@@ -7828,78 +7829,78 @@
       please see <xref linkend="replication-features"/>.
     </para>
 
-  <section id="time-zone-upgrades">
+    <section id="time-zone-upgrades">
 
-      <title>Staying Current with Time Zone
-      Changes</title>
-<indexterm>
-<primary>time zones</primary>
-<primary>upgrading</primary>
-</indexterm>
+      <title>Staying Current with Time Zone Changes</title>
 
+      <indexterm>
+        <primary>time zones</primary>
+        <secondary>upgrading</secondary>
+      </indexterm>
 
-    <para>
-      As mentioned earlier, when the time zone rules change,
-      applications that use the old rules become out of date. To stay
-      current, it is necessary to make sure that your system uses
-      current time zone information is used. For MySQL, there are two
-      factors to consider in staying current:
-    </para>
+      <para>
+        As mentioned earlier, when the time zone rules change,
+        applications that use the old rules become out of date. To stay
+        current, it is necessary to make sure that your system uses
+        current time zone information is used. For MySQL, there are two
+        factors to consider in staying current:
+      </para>
 
-    <itemizedlist>
+      <itemizedlist>
 
-      <listitem>
-        <para>
-          The operating system time affects the value that the MySQL
-          server uses for times if its time zone is set to
-          <literal>SYSTEM</literal>. Make sure that your operating
-          system is using the latest time zone information. For most
-          operating systems, the latest update or service pack prepares
-          your system for the time changes. Check the Web site for your
-          operating system vendor for an update that addresses the time
-          changes.
-        </para>
-      </listitem>
+        <listitem>
+          <para>
+            The operating system time affects the value that the MySQL
+            server uses for times if its time zone is set to
+            <literal>SYSTEM</literal>. Make sure that your operating
+            system is using the latest time zone information. For most
+            operating systems, the latest update or service pack
+            prepares your system for the time changes. Check the Web
+            site for your operating system vendor for an update that
+            addresses the time changes.
+          </para>
+        </listitem>
 
-      <listitem>
-        <para>
-          If you replace the system's
-          <filename>/etc/localtime</filename> timezone file with a
-          version that uses rules differing from those in effect at
-          <command>mysqld</command> startup, you should restart
-          <command>mysqld</command> so that it uses the updated rules.
-          Otherwise, <command>mysqld</command> might not notice when the
-          system changes its time.
-        </para>
-      </listitem>
+        <listitem>
+          <para>
+            If you replace the system's
+            <filename>/etc/localtime</filename> timezone file with a
+            version that uses rules differing from those in effect at
+            <command>mysqld</command> startup, you should restart
+            <command>mysqld</command> so that it uses the updated rules.
+            Otherwise, <command>mysqld</command> might not notice when
+            the system changes its time.
+          </para>
+        </listitem>
 
-      <listitem>
-        <para>
-          If you use named time zones with MySQL, make sure that the
-          time zone tables in the <literal>mysql</literal> database are
-          up to date. If your system has its own zoneinfo database, you
-          should reload the MySQL time zone tables whenever the zoneinfo
-          database is updated, using the instructions given earlier in
-          this section. For systems that do not have their own zoneinfo
-          database, check the MySQL Developer Zone for updates. When a
-          new update is available, download it and use it to replace
-          your current time zone tables. <command>mysqld</command>
-          caches time zone information that it looks up, so after
-          replacing the time zone tables, you should restart
-          <command>mysqld</command> to make sure that it does not
-          continue to serve outdated time zone data.
-        </para>
-      </listitem>
+        <listitem>
+          <para>
+            If you use named time zones with MySQL, make sure that the
+            time zone tables in the <literal>mysql</literal> database
+            are up to date. If your system has its own zoneinfo
+            database, you should reload the MySQL time zone tables
+            whenever the zoneinfo database is updated, using the
+            instructions given earlier in this section. For systems that
+            do not have their own zoneinfo database, check the MySQL
+            Developer Zone for updates. When a new update is available,
+            download it and use it to replace your current time zone
+            tables. <command>mysqld</command> caches time zone
+            information that it looks up, so after replacing the time
+            zone tables, you should restart <command>mysqld</command> to
+            make sure that it does not continue to serve outdated time
+            zone data.
+          </para>
+        </listitem>
 
-    </itemizedlist>
+      </itemizedlist>
 
-    <para>
-      If you are uncertain whether named time zones are available, for
-      use either as the server's time zone setting or by clients that
-      set their own time zone, check whether your time zone tables are
-      empty. The following query determines whether the table that
-      contains time zone names has any rows:
-    </para>
+      <para>
+        If you are uncertain whether named time zones are available, for
+        use either as the server's time zone setting or by clients that
+        set their own time zone, check whether your time zone tables are
+        empty. The following query determines whether the table that
+        contains time zone names has any rows:
+      </para>
 
 <programlisting>
 mysql&gt; <userinput>SELECT COUNT(*) FROM
mysql.time_zone_name;</userinput>

@@ -7910,45 +7911,45 @@
 +----------+
 </programlisting>
 
-    <para>
-      A count of zero indicates that the table is empty. In this case,
-      no one can be using named time zones, and you don't need to update
-      the tables. A count greater than zero indicates that the table is
-      not empty and that its contents are available to be used for named
-      time zone support. In this case, you should be sure to reload your
-      time zone tables so that anyone who uses named time zones will get
-      correct query results.
-    </para>
+      <para>
+        A count of zero indicates that the table is empty. In this case,
+        no one can be using named time zones, and you don't need to
+        update the tables. A count greater than zero indicates that the
+        table is not empty and that its contents are available to be
+        used for named time zone support. In this case, you should be
+        sure to reload your time zone tables so that anyone who uses
+        named time zones will get correct query results.
+      </para>
 
-    <para>
-      To check whether your MySQL installation is updated properly for a
-      change in Daylight Saving Time rules, use a test like the one
-      following. The example uses values that are appropriate for the
-      2007 DST 1-hour change that occurs in the United States on March
-      11 at 2 a.m.
-    </para>
+      <para>
+        To check whether your MySQL installation is updated properly for
+        a change in Daylight Saving Time rules, use a test like the one
+        following. The example uses values that are appropriate for the
+        2007 DST 1-hour change that occurs in the United States on March
+        11 at 2 a.m.
+      </para>
 
-    <para>
-      The test uses these two queries:
-    </para>
+      <para>
+        The test uses these two queries:
+      </para>
 
 <programlisting>
 SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');
 SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');
 </programlisting>
 
-    <para>
-      The two time values indicate the times at which the DST change
-      occurs, and the use of named time zones requires that the time
-      zone tables be used. The desired result is that both queries
-      return the same result (the input time, converted to the
-      equivalent value in the 'US/Central' time zone).
-    </para>
+      <para>
+        The two time values indicate the times at which the DST change
+        occurs, and the use of named time zones requires that the time
+        zone tables be used. The desired result is that both queries
+        return the same result (the input time, converted to the
+        equivalent value in the 'US/Central' time zone).
+      </para>
 
-    <para>
-      Before updating the time zone tables, you would see an incorrect
-      result like this:
-    </para>
+      <para>
+        Before updating the time zone tables, you would see an incorrect
+        result like this:
+      </para>
 
 <programlisting>
 mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11
2:00:00','US/Eastern','US/Central');</userinput>

@@ -7966,9 +7967,9 @@
 +------------------------------------------------------------+
 </programlisting>
 
-    <para>
-      After updating the tables, you should see the correct result:
-    </para>
+      <para>
+        After updating the tables, you should see the correct result:
+      </para>
 
 <programlisting>
 mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11
2:00:00','US/Eastern','US/Central');</userinput>

@@ -7986,18 +7987,19 @@
 +------------------------------------------------------------+
 </programlisting>
 
-  </section>
+    </section>
 
-  <section id="time-zone-leap-seconds">
+    <section id="time-zone-leap-seconds">
 
-    <title>Time Zone Leap Second Support</title>
-<indexterm>
-<primary>time zones</primary>
-<primary>leap seconds</primary>
-</indexterm>
+      <title>Time Zone Leap Second Support</title>
 
-  </section>
+      <indexterm>
+        <primary>time zones</primary>
+        <secondary>leap seconds</secondary>
+      </indexterm>
 
+    </section>
+
   </section>
 
   <section id="locale-support">


Modified: trunk/refman-5.1/internationalization.xml
===================================================================
--- trunk/refman-5.1/internationalization.xml	2008-12-11 20:59:54 UTC (rev 12926)
+++ trunk/refman-5.1/internationalization.xml	2008-12-12 00:01:47 UTC (rev 12927)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 837 bytes

@@ -7455,7 +7455,7 @@
 
     <indexterm>
       <primary>time zones</primary>
-      <primary>support</primary>
+      <secondary>support</secondary>
     </indexterm>
 
     <para>

@@ -7752,7 +7752,7 @@
 
       <indexterm>
         <primary>time zones</primary>
-        <primary>upgrading</primary>
+        <secondary>upgrading</secondary>
       </indexterm>
 
       <para>

@@ -7912,7 +7912,7 @@
 
       <indexterm>
         <primary>time zones</primary>
-        <primary>leap seconds</primary>
+        <secondary>leap seconds</secondary>
       </indexterm>
 
       <para>


Modified: trunk/refman-6.0/internationalization.xml
===================================================================
--- trunk/refman-6.0/internationalization.xml	2008-12-11 20:59:54 UTC (rev 12926)
+++ trunk/refman-6.0/internationalization.xml	2008-12-12 00:01:47 UTC (rev 12927)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 837 bytes

@@ -8886,7 +8886,7 @@
 
     <indexterm>
       <primary>time zones</primary>
-      <primary>support</primary>
+      <secondary>support</secondary>
     </indexterm>
 
     <para>

@@ -9183,7 +9183,7 @@
 
       <indexterm>
         <primary>time zones</primary>
-        <primary>upgrading</primary>
+        <secondary>upgrading</secondary>
       </indexterm>
 
       <para>

@@ -9343,7 +9343,7 @@
 
       <indexterm>
         <primary>time zones</primary>
-        <primary>leap seconds</primary>
+        <secondary>leap seconds</secondary>
       </indexterm>
 
       <para>