I’m not sure Manager’s csv (comma separated value) import routine supports a comma as a decimal separator. The original csv standard only has text fields (without commas) with fields separated by commas. So does not support comas anywhere within numbers.
Various adaptions of “csv” have been made to some form of delimited separated values with some form of escape sequence to deal with values containing the delimiters. None of which is standard, which means no solution will uniformly work for the implementations chosen by different banks world wide.
Because of the lack of standardization in csv implementations (date format, number format, field delimiters, escape and quoting protocol), I believe Lubos is more interested in dropping it completely rather than having an inevitably partially incompatible implementation.
For a one off solution you can
- Open the bank statement in a spreadsheet program. This may involve customising the setting in the import graphical module to correctly parse you delimiter separated text file. LibreOffice delimiter separated values importer enables specification of date format and language / number setting.
- Format it as required. Within the spreadsheet the NUMBERVALUE() function enables converting text to numbers in a language independent fashion. Similarly the TEXT() converts a number to a language specific text string such as the format “#.##”.
- Export it as basic coma separated values (no commas in the numbers and “.” as a decimal separator).
A better solution for ongoing bank import is
- use a text processing utility which supports regular expression processing
- Write a regular expression to automate the conversion of your particular delimiter separated value file to a basic comma separated file compatible with Manager. This includes identifying number fields, removing the thousands separator (ie all character except digits, “-”, or your decimal separator), then replacing the decimal separator with “.”
- Use this tool to pre process your bank downloads prior to importing into Manager
Iff it really worked in earlier versions of Manager
Rerunning a test import in an older version may also help identify this a regression bug.
If it hasn’t worked in older versions, then you are suggesting a program enhancement. Probably to incorporate the RegEx functionality described above when importing numbers.