Is missing trn:currency clause legal?

Donald Allen donaldcallen at
Tue Feb 23 11:01:50 EST 2010

On Tue, Feb 23, 2010 at 10:23 AM, Derek Atkins <warlord at> wrote:
> Donald Allen <donaldcallen at> writes:
>>> Agreed, it should be more vocal about failures!  In particular it should
>>> at LEAST output something to gnucash.trace!
>> It already announces the assertion failure in gnucash.trace. That's
>> great for debugging, pretty useless for an ordinary user. The user
>> needs to be told about this via the UI.
> Yeah, that's true too.  Certain errors need to get propagated up to the
> user.
>>> Can you try to run a Check & Repair to see if it fixes the issue?
>> I did and it did (with gnucash 2.2.9). It didn't take very long,
>> either, and my xml file is over 20 Mb uncompressed. Perhaps you should
>> consider automatically running Check & Repair after N restarts of
>> gnucash, just as fsck is run after N clean reboots that mount an
>> ext2/ext3 filesystem.
> Not a bad idea.  Or perhaps it should get run prior to a Save-As?

My preference would be to run it periodically, rather than prior to a
save-as. An xml file may get improperly structured, as mine did, due
to problems in gnucash. Even if the bad structure doesn't cause
trouble immediately, it could do so in later, more correct versions of
gnucash, perhaps in subtle ways, even if the user never uses the
database backend. And if Check & Repair can fix the structure, as it
did in my case, why not use it? It's cheap to run, I don't think users
will typically do it on their own unless things are obviously broken,
and if they don't use the database backend, they are unlikely to do a


>> /Don
> -derek
> --
>       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>       Member, MIT Student Information Processing Board  (SIPB)
>       URL:    PP-ASEL-IA     N1NWH
>       warlord at MIT.EDU                        PGP key available

More information about the gnucash-devel mailing list