IntenseFinance/gnucash
3
0
Fork 0
mirror of https://github.com/Gnucash/gnucash.git synced 2025-02-25 18:55:30 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'maint'

Browse Source 
Resolved conflicts:
	gnucash/report/report-system/html-document.scm
This commit is contained in:
Geert Janssens
2017-08-21 21:53:02 +02:00
parent f28896fbde a783c8e38f
commit 4b3db97ba1
7 changed files with 8478 additions and 3681 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
libgnucash/doc/prices.txt
View File

@@ -15,12 +15,12 @@ both the register entry and the price must have links to each other
This is needed because if the user enters an incorrect amt or value
or date in the transaction register, and then corrects it later,
piossibly weeks or months later, the corresponding price in the
possibly weeks or months later, the corresponding price in the
priceDB must be fixed as well.
Similarly, if a user deletes a transaction (possibly because it
contains an error in date/amt/value), then it is adviasable that
the correpsonding priceDB entry must be deleted as well (since
contains an error in date/amt/value), then it is advisable that
the corresponding priceDB entry must be deleted as well (since
it is not safe to assume that the price is 'correct').
\section Rounding errors
@@ -30,7 +30,7 @@ round-off errors can make 'obvious' math inaccurate. Note that if
we define price as (value/amt), then we will find that
value != price * amt due to roundoff handling. One must be careful
and consistent in handling this in the register, as otherwise
users will be driven crazy by inconsitent behaviour.
users will be driven crazy by inconsistent behaviour.
(Linas Vepstas April 2003)