Created attachment 105353 [details] Separate extesions on both spaces and semicolons in mime setup The test in the GUI for the mime setup says, that one should use spaces to separate extensions. The actual parsing function accepts either semicolons or spaces (but not both). When the input fields are populated from database, the extensions are separated by semicolons. This can lead to the following problem: 1. Existing extensions: "ex1;ex2" 2. Add new extension separated by space as told: "ex1;ex2 ex3" Result: This is parsed to the extensions "ex1" and "ex2 ex3". Expected: Recognise "ex1", "ex2" and "ex3" separately. Patch: Separate string from user on both spaces and semicolons. Adjust the text in the GUI to that.
Hi Simon, There is extension of file with space separator ? I never seen something as "foo.jpg tar.gz". This will not work in source code which handle files. I understand well your description ? In my example "jpg tar.gz" is the expected extension. This is exactly what you want to manage with your patch ? The scheme for multiple extension is to use dot separator. exemple : jpg.tar.gz. This one is well supported by Qt de facto. Gilles Gilles
Hi Gilles, There was a misunderstanding. This is not about "composed" extensions like ".jpg.tar.gz" at all. This is about a present bug in the mime setup. When you enter "ex1;ex2 ex3" the internal result is a list containing "ex1" and "ex2 ex3" while it should be "ex1", "ex2" and "ex3".
Ah right, it's clear now. Patch is fine well (:=)))... Gilles
Git commit 8a8aeacc954671fe2c52f5e3672b4566a638d781 by Simon Frei. Committed on 06/05/2017 at 08:01. Pushed by sfrei into branch 'master'. Handle both semicolon and spaces in mime setup and use colored mime icons FIXED-IN: 5.6.0 M +2 -2 NEWS M +14 -5 libs/database/coredb/coredb.cpp M +7 -6 utilities/setup/album/setupmime.cpp https://commits.kde.org/digikam/8a8aeacc954671fe2c52f5e3672b4566a638d781