Fix formatting and typos
This commit is contained in:
parent
34ed226c57
commit
3d90bfc4ad
1 changed files with 11 additions and 10 deletions
|
|
@ -1971,7 +1971,7 @@ account. For example:
|
||||||
capture Expenses:Deductible:Medical Medical
|
capture Expenses:Deductible:Medical Medical
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
Would cause any posting with @code{Medical} in it's name to be replaced with
|
Would cause any posting with @code{Medical} in its name to be replaced with
|
||||||
@code{Expenses:Deductible:Medical}.
|
@code{Expenses:Deductible:Medical}.
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -2889,9 +2889,9 @@ cannot appear in the Key:
|
||||||
@node Typed metadata, , Metadata values, Metadata
|
@node Typed metadata, , Metadata values, Metadata
|
||||||
@subsection Typed metadata
|
@subsection Typed metadata
|
||||||
|
|
||||||
If a metadata tag ends in ::, it's value will be parsed as a value expression
|
If a metadata tag ends in ::, its value will be parsed as a value
|
||||||
and stored internally as a value rather than as a string. For example,
|
expression and stored internally as a value rather than as a string.
|
||||||
although I can specify a date textually like so:
|
For example, although I can specify a date textually like so:
|
||||||
|
|
||||||
@smallexample
|
@smallexample
|
||||||
2012-03-10 * KFC
|
2012-03-10 * KFC
|
||||||
|
|
@ -2900,10 +2900,10 @@ although I can specify a date textually like so:
|
||||||
; AuxDate: 2012/02/30
|
; AuxDate: 2012/02/30
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
@noindent This date is just a string, and won't be parsed as a date unless its value is
|
@noindent This date is just a string, and won't be parsed as a date
|
||||||
used in a date-context (at which time the string is parsed into a date
|
unless its value is used in a date-context (at which time the string
|
||||||
automatically every time it is needed as a date). If on the other hand I
|
is parsed into a date automatically every time it is needed as a
|
||||||
write this:
|
date). If on the other hand I write this:
|
||||||
|
|
||||||
@smallexample
|
@smallexample
|
||||||
2012-03-10 * KFC
|
2012-03-10 * KFC
|
||||||
|
|
@ -2912,8 +2912,9 @@ write this:
|
||||||
; AuxDate:: [2012/02/30]
|
; AuxDate:: [2012/02/30]
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
@noindent Then it is parsed as a date only once, and during parsing of the journal file,
|
@noindent Then it is parsed as a date only once, and during parsing
|
||||||
which would let me know right away that it is an invalid date.
|
of the journal file, which would let me know right away that it is an
|
||||||
|
invalid date.
|
||||||
|
|
||||||
@node Virtual postings, Expression amounts, Metadata, Transactions
|
@node Virtual postings, Expression amounts, Metadata, Transactions
|
||||||
@section Virtual postings
|
@section Virtual postings
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue