r20109 - gnucash-docs/trunk/guide/C - A bunch of <acronym> tags.
Cristian Marchi
cmarchi at code.gnucash.org
Sat Jan 15 15:57:19 EST 2011
Author: cmarchi
Date: 2011-01-15 15:57:19 -0500 (Sat, 15 Jan 2011)
New Revision: 20109
Trac: http://svn.gnucash.org/trac/changeset/20109
Modified:
gnucash-docs/trunk/guide/C/appendixa.xml
gnucash-docs/trunk/guide/C/ch_basics.xml
gnucash-docs/trunk/guide/C/ch_bus_ar.xml
gnucash-docs/trunk/guide/C/ch_cc.xml
gnucash-docs/trunk/guide/C/ch_oview.xml
gnucash-docs/trunk/guide/C/fdl-appendix.xml
Log:
A bunch of <acronym> tags.
Modified: gnucash-docs/trunk/guide/C/appendixa.xml
===================================================================
--- gnucash-docs/trunk/guide/C/appendixa.xml 2011-01-15 20:33:28 UTC (rev 20108)
+++ gnucash-docs/trunk/guide/C/appendixa.xml 2011-01-15 20:57:19 UTC (rev 20109)
@@ -30,7 +30,7 @@
</sect1>
<sect1 id="appendixa_qif1">
- <title>Organization of QIF Files (Discussion)</title>
+ <title>Organization of <acronym>QIF</acronym> Files (Discussion)</title>
<para>
</para>
</sect1>
@@ -40,17 +40,17 @@
</para>
</sect1>
<sect1 id="appendixa_enterpay1">
- <title>Checking QIF Data (Discussion)</title>
+ <title>Checking <acronym>QIF</acronym> Data (Discussion)</title>
<para>
</para>
</sect1>
<sect1 id="appendixa_xmlconvert1">
-<title>Converting XML <application>&app;</application> File</title>
- <para>The <application>&app;</application> XML data file can be tranformed to almost any other data
-format (e.g., QIF, CSV...) quite easily if one is familiar with XSLT.
-The <application>&app;</application> data file is well-formed XML, and it can therefore be run
-through an XSLT parser with an associated stylesheet. This allows one
+<title>Converting <acronym>XML</acronym> <application>&app;</application> File</title>
+ <para>The <application>&app;</application> <acronym>XML</acronym> data file can be transformed to almost any other data
+format (e.g., <acronym>QIF</acronym>, <acronym>CSV</acronym>...) quite easily if one is familiar with <acronym>XSLT</acronym>.
+The <application>&app;</application> data file is well-formed <acronym>XML</acronym>, and it can therefore be run
+through an <acronym>XSLT</acronym> parser with an associated stylesheet. This allows one
to transform the file to just about any format that can be designed,
given a properly written stylesheet.</para>
@@ -89,12 +89,12 @@
</literallayout>
</listitem>
<listitem>
- <para>Create an XSLT stylesheet containing the transformation your desire,
+ <para>Create an <acronym>XSLT</acronym> stylesheet containing the transformation your desire,
or obtain one that’s already written (AFAIK, there aren’t any, but I'm
-working on a CSV one).</para>
+working on a <acronym>CSV</acronym> one).</para>
</listitem>
<listitem>
-<para>Install an XSLT processor such as Saxon
+<para>Install an <acronym>XSLT</acronym> processor such as Saxon
(http://saxon.sourceforge.net/) or Xalan-J (http://xml.apache.org/).
Any conforming processor will do, really...</para>
</listitem>
@@ -106,14 +106,14 @@
<para>You will now have a file in the desired output format. An
enterprising individual could go so far as to write a stylesheet to
transform the <application>&app;</application> data file to an OpenOffice spreadsheet (or
-vice-versa, for that matter). Such things as QIF ought to be a little
+vice-versa, for that matter). Such things as <acronym>QIF</acronym> ought to be a little
less work.</para>
</listitem>
</orderedlist>
<para>Benefits are that you don’t need to write a Scheme module or a new C
-routine to do this transformation. Anyone who knows or can learn XML
-and XSLT can perform this task. Not much harder, really, than writing a
+routine to do this transformation. Anyone who knows or can learn <acronym>XML</acronym>
+and <acronym>XSLT</acronym> can perform this task. Not much harder, really, than writing a
Web page....</para>
<para>Anyhow, I just wanted this tidbit to be captured somewhere permanently.
Modified: gnucash-docs/trunk/guide/C/ch_basics.xml
===================================================================
--- gnucash-docs/trunk/guide/C/ch_basics.xml 2011-01-15 20:33:28 UTC (rev 20108)
+++ gnucash-docs/trunk/guide/C/ch_basics.xml 2011-01-15 20:57:19 UTC (rev 20109)
@@ -744,7 +744,7 @@
as your primary data file. What each of these files does is presented below.</para>
<note>
- <para>The following sections are relevant only if you are saving your financial data in the xml format</para>
+ <para>The following sections are relevant only if you are saving your financial data in the <acronym>XML</acronym> format</para>
</note>
<programlisting>
Modified: gnucash-docs/trunk/guide/C/ch_bus_ar.xml
===================================================================
--- gnucash-docs/trunk/guide/C/ch_bus_ar.xml 2011-01-15 20:33:28 UTC (rev 20108)
+++ gnucash-docs/trunk/guide/C/ch_bus_ar.xml 2011-01-15 20:57:19 UTC (rev 20109)
@@ -796,7 +796,7 @@
<para>You can change the starting invoice number if it is important you.
There is no user interface to change the number at this time. You have
- to hand edit your XML data file. The relevant entry is in the "counters"
+ to hand edit your <acronym>XML</acronym> data file. The relevant entry is in the "counters"
section near the beginning of the file. The file must be re-opened after
editing.</para>
@@ -1009,7 +1009,7 @@
<para>You must select the <guilabel>Fancy</guilabel> style sheet template,
and choose a name for your new style sheet. When you click the
- <guibutton>OK</guibutton> button, the HTML Style Sheet editor window is
+ <guibutton>OK</guibutton> button, the <acronym>HTML</acronym> Style Sheet editor window is
displayed. This window contains four tabs, Colors, General, Images, and
Tables. The Colors tab allows you to change the colors of various sections
of the invoice. The General tab allows you to set the Preparer and
@@ -1035,7 +1035,7 @@
<phrase>HTML Style Sheets example</phrase>
</textobject>
- <caption><para>The HTML Style Sheets window with an example Background
+ <caption><para>The <acronym>HTML</acronym> Style Sheets window with an example Background
Tile, Heading Banner, and Logo.</para></caption>
</mediaobject>
</screenshot>
Modified: gnucash-docs/trunk/guide/C/ch_cc.xml
===================================================================
--- gnucash-docs/trunk/guide/C/ch_cc.xml 2011-01-15 20:33:28 UTC (rev 20108)
+++ gnucash-docs/trunk/guide/C/ch_cc.xml 2011-01-15 20:57:19 UTC (rev 20109)
@@ -155,7 +155,7 @@
unauthorized transactions during your monthly reconciliation.</para>
<para>Another way is to import a credit card statement directly into your
- account. If your credit card company supports a QIF file format for its
+ account. If your credit card company supports a <acronym>QIF</acronym> file format for its
statements, you have the option of directly importing the statement. This
type of import is covered in the <application>&app;</application> manual,
and it is a
Modified: gnucash-docs/trunk/guide/C/ch_oview.xml
===================================================================
--- gnucash-docs/trunk/guide/C/ch_oview.xml 2011-01-15 20:33:28 UTC (rev 20108)
+++ gnucash-docs/trunk/guide/C/ch_oview.xml 2011-01-15 20:57:19 UTC (rev 20109)
@@ -96,7 +96,7 @@
<itemizedlist>
<listitem>
<para><emphasis>Quicken Import File (QIF)</emphasis>: Import
- Quicken QIF style files, a popular file format with many
+ Quicken <acronym>QIF</acronym> style files, a popular file format with many
commercial personal finance software packages.</para>
</listitem>
@@ -124,7 +124,7 @@
Transaction Report, Balance Sheet, Profit&Loss, Portfolio
Valuation, and many others. Reports support graphical views of the
data, including pie charts, bar charts, and scatter plots. The
- reports can be exported to HTML files, and are easily
+ reports can be exported to <acronym>HTML</acronym> files, and are easily
customized.</para>
</listitem>
@@ -503,7 +503,7 @@
<itemizedlist>
<listitem>
<para><xref linkend="appendixa"></xref> - Guide for former <trademark
- class="registered">Quicken</trademark>, MS Money or other QIF
+ class="registered">Quicken</trademark>, MS Money or other <acronym>QIF</acronym>
users</para>
</listitem>
@@ -549,7 +549,7 @@
<para>Easy import</para>
<para><application>&app;</application> allows you to import data from on-line bank statements
- and software packages using QIF (<trademark
+ and software packages using <acronym>QIF</acronym> (<trademark
class="registered">Quicken</trademark> Interchange Format), OFX and
HBCI files. An easy-to-use <quote>assistant</quote> walks you through
reviewing resulting changes and actually importing them into
Modified: gnucash-docs/trunk/guide/C/fdl-appendix.xml
===================================================================
--- gnucash-docs/trunk/guide/C/fdl-appendix.xml 2011-01-15 20:33:28 UTC (rev 20108)
+++ gnucash-docs/trunk/guide/C/fdl-appendix.xml 2011-01-15 20:57:19 UTC (rev 20109)
@@ -128,13 +128,13 @@
<para>
Examples of suitable formats for Transparent copies include
plain ASCII without markup, Texinfo input format, LaTeX input
- format, SGML or XML using a publicly available DTD, and
- standard-conforming simple HTML designed for human
+ format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available <acronym>DTD</acronym>, and
+ standard-conforming simple <acronym>HTML</acronym> designed for human
modification. Opaque formats include PostScript, PDF,
proprietary formats that can be read and edited only by
- proprietary word processors, SGML or XML for which the DTD
+ proprietary word processors, <acronym>SGML</acronym> or <acronym>XML</acronym> for which the <acronym>DTD</acronym>
and/or processing tools are not generally available, and the
- machine-generated HTML produced by some word processors for
+ machine-generated <acronym>HTML</acronym> produced by some word processors for
output purposes only.
</para>
More information about the gnucash-changes
mailing list