summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Michlmayr <tbm@cyrius.com>2014-10-19 10:20:31 -0400
committerMartin Michlmayr <tbm@cyrius.com>2014-10-19 10:20:31 -0400
commit085596ae0ed077fb3d10e58159508a936601de41 (patch)
treef0371a4995e6391991aa2010a51ee3c02241b8b1
parent325f8cb6442118c38121991bb76e03fd95ffcafc (diff)
parent5df0788ba20f3b9a8f37827b92d18c92f37827c6 (diff)
downloadfork-ledger-085596ae0ed077fb3d10e58159508a936601de41.tar.gz
fork-ledger-085596ae0ed077fb3d10e58159508a936601de41.tar.bz2
fork-ledger-085596ae0ed077fb3d10e58159508a936601de41.zip
Merge pull request #327 from myqlarson/patch-1
Update ledger3.texi
-rw-r--r--doc/ledger3.texi18
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/ledger3.texi b/doc/ledger3.texi
index e52aff2b..e9b0f552 100644
--- a/doc/ledger3.texi
+++ b/doc/ledger3.texi
@@ -4547,8 +4547,8 @@ Transaction Number,Date,Description,Memo,Amount Debit,Amount Credit,Balance,Chec
Unfortunately, as it stands Ledger cannot read it, but you can. Ledger
expects the first line to contain a description of the fields on each
-line of the file. The fields ledger can recognize are called
-@code{date}, @code{posted}, @code{code}, @code{payee} or @code{desc},
+line of the file. The fields ledger can recognize contain these case-insensitive strings
+@code{date}, @code{posted}, @code{code}, @code{payee} or @code{desc} or @code{description},
@code{amount}, @code{cost}, @code{total}, and @code{note}.
Delete the account description lines at the top, and replace the first
@@ -4582,17 +4582,17 @@ transid,date,payee,note,amount,,,code,
@end smallexample
Ledger will include @samp{; transid: 767718} in the first transaction
-is from the file above.
+from the file above.
@findex --invert
@findex --account @var{STR}
@findex --rich-data
-The @command{convert} command accepts three options. The most important
-ones are @option{--invert} which inverts the amount field, and
+The @command{convert} command accepts three options. They are
+@option{--invert} which inverts the amount field,
@option{--account @var{STR}} which you can use to specify the account to
-balance against and @option{--rich-data}. When using the rich-data
-switch, additional metadata is stored as tags. There is, for example,
+balance against, and @option{--rich-data} which stores
+additional metadata as tags. There is, for example,
a UUID field. If an entry with the same UUID tag is already included in
the normal ledger file (specified via @option{--file @var{FILE} (-f)} or
via the environment variable @env{LEDGER_FILE}) this entry will not be
@@ -4613,7 +4613,7 @@ account Aufwand:Einkauf:Lebensmittel
Note that it may be necessary for the output of @samp{ledger convert}
to be passed through @code{ledger print} a second time if you want to
-match on the new payee field. During the @code{ledger convert} run
+match on the new payee field. During the @code{ledger convert} run,
only the original payee name as specified in the csv data seems to be
used.
@@ -5239,7 +5239,7 @@ report the values used by each tag.
@findex entry
@findex xact
-The @command{xact} command simplify the creation of new transactions.
+The @command{xact} command simplifies the creation of new transactions.
It works on the principle that 80% of all postings are variants of
earlier postings. Here's how it works: