docs: manual, news updates
This commit is contained in:
		
							parent
							
								
									329cdeda0e
								
							
						
					
					
						commit
						61547445f4
					
				@ -1012,17 +1012,14 @@ managing memory growth.
 | 
			
		||||
### File format compatibility
 | 
			
		||||
 | 
			
		||||
hledger's file format is mostly identical with that of c++ ledger, with
 | 
			
		||||
some features being accepted but ignored. (Eg modifier entries, periodic
 | 
			
		||||
entries, metadata, per-posting cleared flags). There are also some subtle
 | 
			
		||||
differences in parser behaviour (eg comments may be permissible in
 | 
			
		||||
different places.)
 | 
			
		||||
some features being accepted but ignored (eg, modifier entries and
 | 
			
		||||
periodic entries). There are subtle differences in parser behaviour, eg
 | 
			
		||||
comments may be permissible in different places. hledger does not allow
 | 
			
		||||
separate dates for individual postings, or AMT1=AMT2 or { } syntax.
 | 
			
		||||
 | 
			
		||||
Generally, it's easy to keep a journal file that works with both hledger
 | 
			
		||||
and c++ledger if you avoid the more esoteric syntax.  Occasionally you'll
 | 
			
		||||
need to make small edits to restore compatibility for one or the other.
 | 
			
		||||
 | 
			
		||||
hledger does not allow separate dates for individual postings, unlike c++
 | 
			
		||||
ledger.
 | 
			
		||||
and c++ledger if you avoid these.  Occasionally you'll need to make small
 | 
			
		||||
adjustments to restore compatibility for one or the other.
 | 
			
		||||
 | 
			
		||||
(See also [usage issues](#usage-issues))
 | 
			
		||||
 | 
			
		||||
@ -1244,14 +1241,9 @@ Here are some issues you might encounter when you run hledger:
 | 
			
		||||
        $ echo "export LANG=en_US.UTF-8" >>~/.bash_profile
 | 
			
		||||
        $ bash --login
 | 
			
		||||
 | 
			
		||||
- **hledger fails to parse some ledger syntax**
 | 
			
		||||
- **hledger fails to parse some valid ledger files**
 | 
			
		||||
 | 
			
		||||
    There are still some valid c++ ledger journals we don't parse. Here's
 | 
			
		||||
    the current list of things we know we don't parse (see also
 | 
			
		||||
    [file format compatibility](#file-format-compatibility):
 | 
			
		||||
 | 
			
		||||
    - AMOUNT1 = AMOUNT2 (balance assertion/price specification ?)
 | 
			
		||||
    - ... AMOUNT {...}
 | 
			
		||||
    See [file format compatibility](#file-format-compatibility).
 | 
			
		||||
 | 
			
		||||
## Examples and recipes
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
@ -4,6 +4,18 @@ title: hledger news
 | 
			
		||||
 | 
			
		||||
# hledger news
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
  * installing: don't specify process version after all, too many problems
 | 
			
		||||
  * parsing: better international number format support, allowing comma as decimal point and flexible digit groups (#32)
 | 
			
		||||
  * parsing: support @@ syntax specifying total price
 | 
			
		||||
  * parsing: infer a conversion price in unpriced two-commodity transactions
 | 
			
		||||
  * parsing: support per-posting cleared status
 | 
			
		||||
  * parsing: more reporting interval syntax: biweekly, bimonthly, every N days/weeks/months/quarters/years, every Nst/nd/rd/th day of month/week
 | 
			
		||||
  * convert: support custom date formats
 | 
			
		||||
  * histogram: honour the specified start or end dates
 | 
			
		||||
  * print: don't show a trailing space when description is blank
 | 
			
		||||
  * web: allow filter patterns with spaces if quoted, like command line
 | 
			
		||||
 | 
			
		||||
## 2010/12/6 hledger 0.13
 | 
			
		||||
 | 
			
		||||
  * move web, vty, chart commands into separate hledger-web, hledger-vty,
 | 
			
		||||
 | 
			
		||||
		Loading…
	
		Reference in New Issue
	
	Block a user