From 63b9f288f5a2448de30153786bbe5327e02bfab8 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Thu, 21 Jul 2016 19:47:34 -0700 Subject: [PATCH] doc: csv: small rewordings --- hledger-lib/doc/hledger_csv.5.m4.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hledger-lib/doc/hledger_csv.5.m4.md b/hledger-lib/doc/hledger_csv.5.m4.md index ccc99eae1..6d8b5886a 100644 --- a/hledger-lib/doc/hledger_csv.5.m4.md +++ b/hledger-lib/doc/hledger_csv.5.m4.md @@ -82,7 +82,7 @@ date-format %-m/%-d/%Y %l:%M %p `fields `*`FIELDNAME1`*, *`FIELDNAME2`*... -This (a) names the CSV fields, in order (names may not contain whitespace, but may be omitted), +This (a) names the CSV fields, in order (names may not contain whitespace; uninteresting names may be left blank), and (b) assigns them to journal entry fields if you use any of these standard field names: `date`, `date2`, `status`, `code`, `description`, `comment`, `account1`, `account2`, `amount`, `amount-in`, `amount-out`, `currency`. Eg: @@ -127,7 +127,7 @@ Field assignments can be used instead of or in addition to a field list. This applies one or more field assignments, only to those CSV records matched by one of the PATTERNs. The patterns are case-insensitive regular expressions which match anywhere within the whole CSV record (it's not yet possible to match within a -specific field). When there are multiple patterns they should be written +specific field). When there are multiple patterns they can be written on separate lines, unindented. The field assignments are on separate lines indented by at least one space. Examples: