https://bugs.kde.org/show_bug.cgi?id=515546
--- Comment #1 from pc <[email protected]> --- I realised that there is a flaw in the suggested logic in my original description. This is because KMyMoney does allow the creation of categories with case sensitivity, such that a case insensitive match could actually, though probably not in practice unless there had been a "mistake", match multiple category names. So, for example, all of the following names could exist as indivdiual category entries: Insurance insurance inSurance InSurance etc. I still believe from a "it just works" user point of view the use of a case insensitive match for an existing category is still an idea worth considering. However, the "logic" for existing category name check might need to be something along the lines of: If case sensitive match of <WORD>: Use <WORD> as the category name If exactly one case insensitive match of <WORD>: Use case insensitive match of <WORD> as the category name If >1 case insensitive match of <WORD>: Write message "There is no exact, and there are more than 1 case insensitive, match of <WORD> in the existing Category names" If zero case insensitive match of <WORD>: Write message "There is no match of <WORD> in the existing Category names" -- You are receiving this mail because: You are watching all bug changes.
