Quote from gnucash-devel:
"I think this introduced a "might be used uninitialized" warning in
src/gnome/top-level.c with my particular version of gcc.
Initializing *file_guid with NULL in gnc_restore_all_state() fixes
the warning, see below."
Author: Herbert Thoma <herbert.thoma@iis.fraunhofer.de>
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23621 57a11ea4-9604-0410-9ed3-97b8803252fd
Yet another case this could happen: when using Actions->New Account Hierarchy
on an already open book.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23619 57a11ea4-9604-0410-9ed3-97b8803252fd
This is the former content of plugins-example.tgz, mentioned in the
wiki documentation.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23615 57a11ea4-9604-0410-9ed3-97b8803252fd
This reverts commit 5305c7909e.
This was incomplete and not meant to be pushed yet.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23612 57a11ea4-9604-0410-9ed3-97b8803252fd
Ensure that all strings coming in from OFX are checked for being
valid UTF-8.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23599 57a11ea4-9604-0410-9ed3-97b8803252fd
to avoid writing broken unparseable XML.
This checks for both bad UTF8 and for invalid control characters
that libxml2 doesn't convert to entities.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23598 57a11ea4-9604-0410-9ed3-97b8803252fd
These resulted in message translations not being found:
gnc-warnings.c is generated from these strings using xsltproc
the *.po files are generated from these strings using gettext
gettext collapses whitespace. xlstproc doesn't at least not in the
way we use it. So when gnucash needs to look up a translation for
a warning, it won't find it due to the mismatch in message id.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23589 57a11ea4-9604-0410-9ed3-97b8803252fd
Add price database entry for accounts (e.g., stock accounts) which don't have a price cell
in their register tables.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23583 57a11ea4-9604-0410-9ed3-97b8803252fd
The gschema.xml.in.in pathnames were too long for versions with more than
5 characters, e.g. 2.5.10, so tar was rejecting them. aqbanking, csv-import,
csv-export, and qif-import are now aqb, csv-imp, csv-exp, and qif-imp,
respectively.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23567 57a11ea4-9604-0410-9ed3-97b8803252fd
- Added conditional to grey-out/disable 'Open File/Link' when association is unset
- Converted 'Open Location' dialog to gtk_dialog_new_with_buttons
- fixed invalid options from last submitted patch
- made dialog modal
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23563 57a11ea4-9604-0410-9ed3-97b8803252fd
- move the swig version check after the guile checks
this allows us to check for a different version of swig
based on the guile version that was detected
- use more recent autoconf macros for swig (from the autotools archive)
this give us more flexible error reporting
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23560 57a11ea4-9604-0410-9ed3-97b8803252fd
- guile 1.8 doesn't need the swig patch
- make sure all swig interface files include guile-mappings.h
for the *utf8_string to *locale_string mappings
but only load it when building guile modules
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23559 57a11ea4-9604-0410-9ed3-97b8803252fd
This is actually a bug in swig.
This commit works around it by patching the swig
generated source files until swig itself has been fixed.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23557 57a11ea4-9604-0410-9ed3-97b8803252fd
