Patch by Jeff Kletsky:
At least for the online OFX sources I use in the US, downloaded
transactions are populated with memos of
"Account unknown Bank unknown"
Past being annoying, this can cause improper "matches" when comparing
transactions.
The root cause is found in src/import-export/aqbanking/gnc-ab-utils.c
in the function gnc_ab_memo_to_gnc where the code seems to check for
the existence of a remote account number from the aqbanking
transaction
if (ab_other_accountid && *ab_other_accountid)
and appears to intend to return the empty string if one is not present.
However, an earlier line in the code sets ab_other_accountid to
"unknown" so that the test always returns true.
This patch should return:
* "Account <account number> Bank <bank number>" if both are present
* "Account <account number>" if only the account is present
* "Bank <bank number>" if only the bank is present
* "" if neither is present
Additionally, ordering of trimming was changed to handle the
possibility that the leading and/or trailing character(s) were stripped
as invalid UTF-8, resulting in an untrimmed string.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20144 57a11ea4-9604-0410-9ed3-97b8803252fd
languages (e.g., Portugues (Portugal). Add po/en.po so that english
doesn't have to be special-cased to the C locale.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20142 57a11ea4-9604-0410-9ed3-97b8803252fd
svnversion without options returns the most recent revision in the repo
at the time of the last svn update/checkout even if that revision
didn't hold any changes in the current path. Not very useful as a
reference. Better is to ask for the last changed revision with -c.
BUT: -c option for some reason always considers svn working copy
as having mixed sources. We're only interested in the last part so
we strip the beginning revision if it's there.
As a result if your WC really has mixed sources, that will not be
visible in the version number...
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20140 57a11ea4-9604-0410-9ed3-97b8803252fd
that looks like this:
Date Completion
When a date is entered without year, it should be taken:
(*) In the current calendar year
( ) In a sliding 12-month window starting this many months before the
current month: [ 6 ]
Patch by Peter Selinger with minor modifications
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20132 57a11ea4-9604-0410-9ed3-97b8803252fd
Patch by Bert Claesen:
The attached patch (against r20122) tries to solve bug #535774 and:
*Introduces Option naming consistent with report title (e.g. Customer Report
shows Customer in the Option screen)
*Removes the printf() default string in case no arguments where given
*Moves the docname up to a higher level for easy of overview
Cases default to a GNC-OWNER-VENDOR.
Note on the patch:
*As indicated in the comments, two functions are nearly identical, where in the
Vendor report the use of Vendor/Company is mixed. This can easily be moved into
one function as the footprint is the same.
cstim: I've clarified which ones of the functions returns translated vs.
untranslated strings, too.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20131 57a11ea4-9604-0410-9ed3-97b8803252fd
Patch by Christoph Holtermann:
1) I decided to let the methods return "Division by Zero" for denom()==0.
2) As proposed in
http://stackoverflow.com/questions/1307014/python-str-versus-unicode i created
both __str__ and __unicode__.
3) I use format to fix the decimal places to 2. It would be nice if the number
would be configurable.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20128 57a11ea4-9604-0410-9ed3-97b8803252fd
This caused online price quotes to fail for anything other than a currency.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20126 57a11ea4-9604-0410-9ed3-97b8803252fd
* Add a macro GNC_RESAVE_VERSION which holds an svn revision number.
* When fully saving a database put this number in versions with
table_name Gnucash-Resave.
* On database load, compare the current GNC_RESAVE_VERSION with the
Gnucash revision and Gnucash-Resave revision saved when the database
was created.
* If the current GNC_RESAVE_VERSION > the saved Gnucash
version, then emit ERR_SQL_DB_TOO_OLD.
* If GNC_RESAVE_VERSION < the saved Gnucash-Resave, emit ERR_SQL_DB_TOO_NEW.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20123 57a11ea4-9604-0410-9ed3-97b8803252fd
tables out of the way, writing new tables, and then dropping the old
tables once everything has been saved.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20119 57a11ea4-9604-0410-9ed3-97b8803252fd
This patch makes this feature available as button "Duplicate" in the search window.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20115 57a11ea4-9604-0410-9ed3-97b8803252fd
The newer "import-export/aqbanking" has been in use since aqbanking-3.0.0.
As it turned out, we require aqbanking-4.0.0 now anyway, which was
release 2009-05-30. Consequently, the old module isn't being maintained
by us and so needs to be removed.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20106 57a11ea4-9604-0410-9ed3-97b8803252fd
qof_instance_begin_edit. Add qof_session_safe_save. Add unit tests for
these changes.
QofBook read-only attribute is to prevent starting an edit when the
version of Gnucash which created a dataset is newer than the one
currently running. This is to prevent writing records of an old format
into an existing data set. The user can use File>Save As to create a new
QofSession which will write a completely new dataset in the current
format. This is an important safety feature for future versions of
Gnucash which will not bring all of a dataset into memory, instead
loading only what is immediately needed.
Safe-save is the Qof access to allow writing out a dataset to an
existing server database (i.e., postgresql or mysql) while maintaining
the ability to both transaction-protect saving individual records while
maintaining the ability to rollback the entire save if something goes
wrong.
The unit test framework is added to enable testing these components.
More tests will be added in a later commit.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20103 57a11ea4-9604-0410-9ed3-97b8803252fd
While $HOME is fine on linux, on Windows the most sensible location is "My Documents"
(or its translated equivalent).
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20101 57a11ea4-9604-0410-9ed3-97b8803252fd
and add a hint for translators to the error message string
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20100 57a11ea4-9604-0410-9ed3-97b8803252fd
Old state files are still read (if no new equivalent exists yet)
but will never be written to again.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20098 57a11ea4-9604-0410-9ed3-97b8803252fd
No version GnuCash 2.2.x version will produce state files with
spaces in their key names, and we don't need to worry about older
compatibility (migrating from 2.0.x should always happen via 2.2.x).
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20096 57a11ea4-9604-0410-9ed3-97b8803252fd
This version uses 2 separate sentences,
mentions currencies and
gives a clue for the account type.
Add enable basic doxygen output.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20089 57a11ea4-9604-0410-9ed3-97b8803252fd
The INVOICE_TYPE string unfortunately is
stored in translated form due to the usage of gncInvoiceGetType()
for user-visible strings as well. Hence, as an exception we
must also search for the translated here even though it's an
internal flag.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20087 57a11ea4-9604-0410-9ed3-97b8803252fd
Additional: explain alternatives and optional parts
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20086 57a11ea4-9604-0410-9ed3-97b8803252fd
Get the bi_import plugin building on Windows by including missing libc functions
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20085 57a11ea4-9604-0410-9ed3-97b8803252fd
