r19898 - gnucash-docs/trunk/guide/C - Use double quotes instead of single quotes for id names.

[Cristian Marchi]

Author: cmarchi
Date: 2010-11-30 14:35:23 -0500 (Tue, 30 Nov 2010)
New Revision: 19898
Trac: http://svn.gnucash.org/trac/changeset/19898

Modified:
   gnucash-docs/trunk/guide/C/appendixb.xml
   gnucash-docs/trunk/guide/C/appendixd.xml
Log:
Use double quotes instead of single quotes for id names.

Modified: gnucash-docs/trunk/guide/C/appendixb.xml
===================================================================
--- gnucash-docs/trunk/guide/C/appendixb.xml	2010-11-30 19:31:36 UTC (rev 19897)
+++ gnucash-docs/trunk/guide/C/appendixb.xml	2010-11-30 19:35:23 UTC (rev 19898)
@@ -13,7 +13,7 @@
   <appendix id="appendixb">
     <title>Frequently Asked Questions</title>
     <para>This is a list of questions asked on the mailing lists for which there really is no section in the documentation covering the subject.</para>
-    <sect1 id='appendixb_info'>
+    <sect1 id="appendixb_info">
       <title>Sources of Information</title>
 
       <sect2 id="appendixb_info_where">

Modified: gnucash-docs/trunk/guide/C/appendixd.xml
===================================================================
--- gnucash-docs/trunk/guide/C/appendixd.xml	2010-11-30 19:31:36 UTC (rev 19897)
+++ gnucash-docs/trunk/guide/C/appendixd.xml	2010-11-30 19:35:23 UTC (rev 19898)
@@ -12,10 +12,10 @@
   <appendix id="appendixd">
     <title>Auxiliary File Formats</title>
     <para>These are the formats of some auxiliary files used by <application>&app;</application>.</para>
-    <sect1 id='check_format_info'>
+    <sect1 id="check_format_info">
       <title>Check Format Files (*.chk)</title>
 
-      <sect2 id='check_format_overview'>
+      <sect2 id="check_format_overview">
         <title>Overview</title>
         <para>The check format file is used to tell <application>&app;</application> how to print a check or checks onto a page of paper.  This file first describes the overall layout of a page (number of checks, orientation, etc) and then describes the layout of the specific items on a single check.  The file is organized as a typical Key/Value file used by many Linux applications.  Keys/values pairs are grouped into sections that begin with the group name enclosed in square brackets.</para>
         <para><application>&app;</application> looks for check format files in two different locations when you bring up the check printing dialog.  The first location is typically /usr/share/gnucash/checks, where check files distributed with the application can be found.  The second location is the user private ~/.gnucash/checks directory.  Users may add check formats at any time (even while <application>&app;</application> is running) simply by dropping a new *.chk file in this directory.  The next time the check printing dialog is opened the new check format will appear in the list of available check formats.</para>
@@ -63,7 +63,7 @@
         <sect3>
           <title>Top Group</title>
           <para>This section of the check file describes the overall layout of a page of checks (or check) that goes into the printer.</para>
-          <table id='check_table_top'>
+          <table id="check_table_top">
             <title>Overall Page Description Fields</title>
             <tgroup cols="4">
               <thead>
@@ -137,7 +137,7 @@
         <sect3>
           <title>Check Positions Group</title>
           <para>This group of items specifies how multiple checks are laid out on the same sheet of paper, and gives names to each of these check locations so that a user can specify which check location that <application>&app;</application> should print.  This entire group of key/value pairs is optional, and should be omitted if the format file only specifies a single check per page of paper.</para>
-          <table id='check_table_positions'>
+          <table id="check_table_positions">
             <title>Multiple Checks Per Page Fields</title>
             <tgroup cols="4">
               <thead>
@@ -170,7 +170,7 @@
           <para>This section specifies the individual items that are printed on the check.  There is no limit to the number of items that may be present in this section, and any given type of item can be repeated multiple times.  This allows for the printing of checks that have a side stub, or for the one-per-page business checks that have both the check and multiple check stubs on the same page.  For example, to print the payee name on a business check and on both stubs, simply specify three payee items with differing print coordinates.</para>
           <para>Each key names in this section explicitly includes the item number to which it applies.  E.G. The key named <guilabel>Type_1</guilabel> applies to the first item to be printed, and the key <guilabel>Coords_3</guilabel> applies to the third item to be printed.  Item numbers start at one and increase sequentially.  Any gap in the numbering sequence is interpreted by <application>&app;</application> as the end of the item list.  Items are printed in the order of their item numbers, not in the order in which they appear in the file.</para>
           <para>Each item specified must include a type declaration.  The rest of the parameters for that item depend upon the particular type of that item.  See <xref linkend="check_table_types"></xref> for a list of valid item types and their required parameters.</para>
-          <table id='check_table_items'>
+          <table id="check_table_items">
             <title>Individual Check Item Fields</title>
             <tgroup cols="4">
               <thead>
@@ -234,7 +234,7 @@
             </tgroup>
           </table>
           <para>These are the individual items that can be printed on a check.  All items require the coordinates on the page where the item should be printed.  The majority of these items result in text being printed on the page, and these items may have individual font and alignments specified.  For example, the numerical amount of a check could be printed right justified while everything else is printed left justified.  Other types may have unique parameters.</para>
-          <table id='check_table_types'>
+          <table id="check_table_types">
             <title>Individual Check Item Types</title>
             <tgroup cols="4">
               <thead>
@@ -402,7 +402,7 @@
           <note><para>SPLIT items include all split entries for the transaction except for the split that applies to the current account register.  This is usually the last split listed when splits are displayed in the register.  The coordinate location defines the lower left location for the split information.</para></note>
         </sect3>
       </sect2>
-      <sect2 id='check_format_notes'>
+      <sect2 id="check_format_notes">
         <title>Creating Check Format Files</title>
         <para>Creating your own check format file is a fairly simple task.  The easiest way to start is to copy an existing check format file from the application directory (typically /usr/share/gnucash/checks) to the directory ~/.gnucash/checks.  Make sure to change the guid so the new file will be accepted by gnucash, and change the title to something descriptive.  Then change or add individual item fields as necessary.  You can also create a new check file by clicking the <guilabel>Save Format</guilabel> button on the "Custom format" page of the check printing dialog.</para>
         <note>