account matching in generic import

[Benoit Grégoire]

> Hm... of course debugging is another issue. But in this question I somewhat
> distinguished the "machine-readable" account id versus the "human-readable"
> account id. To identify an account for a human, I would write "Bank code:
> 123 455 78, Country: Utopia, Account code: 26 984 09 27". For a machine, I
> would of course write something different... So my point was to have one
> argument for the machine-readable account id which also gets stored in the
> kvp frame, and having the other argument be the human-readable account
> identification.

Ok, now I see.  Well, I dont have such information in OFX, but I think I 
figured an elegant solution.  What if the text remains generic at the top, 
and on the second line, the function adds the human readable description if 
not NULL, or the machine readable online_id otherwise?

Note that this function will eventually be extended to include as parameters 
the default account name, type and currency as parameters (all optionnal) so 
that if the user creates a new account, these will be filled in for him.  
I'll try to put them all in the declaration tomorow so they won't change 
anymore.
-- 
Benoit Grégoire
LibOFX http://step.polymtl.ca/~bock/libofx/