Bug 435021 - Rename does not support both comma and semicolon
Summary: Rename does not support both comma and semicolon
Status: RESOLVED INTENTIONAL
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-file (other bugs)
Version First Reported In: 7.2.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-27 15:09 UTC by Antonio
Modified: 2022-01-31 21:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 7.3.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio 2021-03-27 15:09:38 UTC 
SUMMARY
Rename no more allows comma (,) and semicolon (;)

STEPS TO REPRODUCE
1. Select an image
2. Right-click, Rename
3. Edit name inserting comma and/or semicolon

OBSERVED RESULT
Both comma and semicolon are replaced by underscore.
The same problem arises with replace command such as: [file]{replace:"_",";",i}
In this case OK button remains disabled until replace char contains ; or ,

EXPECTED RESULT
Both comma and semicolon should be inserted or replaced without any problem (such as in ver. 7.1.0).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 18.04.5 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2021-03-27 15:22:21 UTC 
This is not a bug but completely intentional. On a FAT*, NTFS*, or FUSE* file system are "," or ";" prohibited characters in the filename. digiKam allows these special characters in the file name on an EXT* or other native Linux file system. We had bug reports that these characters lead to errors on the Windows file system.

Maik
Comment 2 Maik Qualmann 2021-03-27 19:27:37 UTC 
I checked again, since digiKam-6.0.0 with Bug 391312 there is a query of the file system and the suppression of not allowed file characters on Windows file systems.

Maik