Created attachment 138486 [details] Video of described behavior SUMMARY Filename field refuses to type more than one dot. STEPS TO REPRODUCE 1. Open a music folder to work with. 2. Try to type a dot after [track number] or apply [%{track}. %{title}] formatting from tags OBSERVED RESULT Filename field stubbornly refuses to type a dot. Other punctuation characters works okay. A dot before extension suffix stays untouched, but there are quirks too. See add. info. EXPECTED RESULT Apply as many dots as I want to. SOFTWARE/OS VERSIONS OS: Solus 4.2 with KDE Plasma DE Kid3 (3.8.6) is installed from vendor-provided eopkg repositories KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION My first time reporting a bug, correct me if I'm doing something wrong. Re: quirks: if I try to type a dot AFTER the extension suffix, it automatically deletes the existing one and type another one. Only works after existing dot, not before. If I try to remove existing dot between the filename and suffix, it allows me to type a dot anywhere, but just one. See attached video.
Also tried this in Windows 10 (dual-booted) - works absolutely fine. Can it be a text encoding issue?
Could it be that you have checked "Automatically apply format" in the section "Filename Format" of the "Files" tab in the preferences? This would automatically apply the "String replacement" (in the same section, enabled by default), which has a replacement from "." to "" defined. This was done because there are players which get confused by files with more than one dot in it. To fix this, you could either uncheck the "Automatically apply format" checkbox or remove the replacement for "." in the "String replacement" table.
(In reply to Urs Fleisch from comment #2) > Could it be that you have checked "Automatically apply format" in the > section "Filename Format" of the "Files" tab in the preferences? This would > automatically apply the "String replacement" (in the same section, enabled > by default), which has a replacement from "." to "" defined. This was done > because there are players which get confused by files with more than one dot > in it. To fix this, you could either uncheck the "Automatically apply > format" checkbox or remove the replacement for "." in the "String > replacement" table. That's exactly what happened, thank you very much. Case closed. Suggestion: maybe make this more apparent, I can see how some future users may also struggle with that. Maybe add as troubleshooting section in handbook? I scrolled through it before posting, wasn't obvious where to look.