;doc: csv: amount decimal places: edits

This commit is contained in:
Simon Michael 2024-04-24 16:02:15 -10:00
parent 2a67aa327b
commit 7920b0b9ac

View File

@ -3838,7 +3838,7 @@ When you are reading CSV data, eg with a command like `hledger -f foo.csv print`
hledger will infer each commodity's decimal precision (and other [commodity display styles](#commodity-display-styles)) from the amounts - hledger will infer each commodity's decimal precision (and other [commodity display styles](#commodity-display-styles)) from the amounts -
much as when reading a journal file without `commodity` directives (see the link). much as when reading a journal file without `commodity` directives (see the link).
But note these commodity styles are not inferred from the numbers in the original CSV data; Note, the commodity styles are not inferred from the numbers in the original CSV data;
rather, they are inferred from the amounts generated by the CSV rules. rather, they are inferred from the amounts generated by the CSV rules.
When you are importing CSV data with the `import` command, eg `hledger import foo.csv`, there's another step: When you are importing CSV data with the `import` command, eg `hledger import foo.csv`, there's another step:
@ -3849,7 +3849,7 @@ So for each commodity - let's say it's EUR - `import` will choose:
2. otherwise, the style inferred from EUR amounts in the journal 2. otherwise, the style inferred from EUR amounts in the journal
3. otherwise, the style inferred from EUR amounts generated by the CSV rules. 3. otherwise, the style inferred from EUR amounts generated by the CSV rules.
TLDR: if `import` is not generating the precisions or styles you want, add a `commodity` directive specifying them. TLDR: if `import` is not generating the precisions or styles you want, add a `commodity` directive to specify them.
### Referencing other fields ### Referencing other fields