Bank statement import fails when using CR as EOL indicator (affects Mac OS X import files)

[Peter Herre]

The bank statement import works fine as long as the delimiting character is a semicolon. However, when importing a file where the delimiting character of a semicolon has been replaced by a tabulator (but the rest remaining the same!), nothing is imported at all. Clearly, the import has been done with exactly the same settings, but with specifying the TAB character as delimiter. The module reports the following result:

The bank statement file has been imported
Errors:
------

Sum up:
Number of statements: 0
Number of error: 0

The tabulator delimited format is created by a bank statement export from the HBCI banking software Bank X (for Mac OS X). So it would be fine if a tabulator delimited import works as fine as the semicolon delimited input. It is worth to be noted that text in the imported format has NOT been marked with quotes.

[Peter Herre (o-info-j)]

It turned out that the error was **not** caused because of the different delimiter, but because of different end-of-line (EOL) encoding: The original import file used CR to indicate EOL, as it is usually done on Mac OS X side. However, after transcoding the file that uses LF to indicate EOL, each line was properly detected.

However, it would be useful to accept both CR and LF as valid EOL indicators.