Regarding KtoBlzCheck GSoC project

[Prasun Kumar]

Dear Sir,
Thank you for answering the questions. I have some more.
For the API part, should I use the KMyMoney implementation suggested by you(
https://cgit.kde.org/kmymoney.git/tree/kmymoney/payeeidentifier/ibanandbic?h=4.8)
as a reference?
Secondly, for adding support for additional countries, should these come
under iban or should I create separate files and classes for each country?

Thanks,
Prasun

On Sun, 22 Mar 2020 at 19:32, Ralf Habacker <ralf.habacker at freenet.de>
wrote:

> Am 20.03.20 um 19:28 schrieb Prasun Kumar:
> > Dear Sir,
> > I am drafting a project proposal for GSoC and I have a few questions
> > regarding the project.
> >
> > In the KtoBlzCheck cmdline tool, there is an option of taking the
> > bankdata file as an input from the user. In this case, should we use
> > the text file format as being done right now if I am not mistaken
> > because the user should not be compelled to provide a sqllite db as an
> > input file?
>
> the text format file has some disadvantages:
>
> 1. It provides no date range (currently several text files are required
> to support valid date range and
>
> 2. it does support multiple languages as it is required by kmymoney
> https://cgit.kde.org/kmymoney.git/tree/kmymoney/plugins/ibanbicdata?h=5.0
>
> As this GSOC project is to replace raw bank data text files by an sqlite
> data base., the command line tool should get an option to use a sqlite
> database from a custom path.
>
> Regards
>
> Ralf
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-finance-apps/attachments/20200326/e45d046e/attachment.html>