Bug 380220 - On windows cannot use shared folders with non-ascii name
Summary: On windows cannot use shared folders with non-ascii name
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Bundle-Windows (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-26 08:23 UTC by enboig
Modified: 2022-01-07 05:22 UTC (History)
2 users (show)

See Also:
Latest Commit: https://commits.kde.org/digikam/8490cd2b9c459b549753563274d8a7d630567395
Version Fixed In: 5.9.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 enboig 2017-05-26 08:23:54 UTC 
When I try to add a network folder named "R:\Comunicació\FOTOS" it is added, but returns an error and is not scanned. When returning to edit it the name has become "R:\Comunicaci?\FOTOS"; and "?" is not just a plain "?", its is inside a rhombus, as it is a unknown char.
Comment 1 Maik Qualmann 2018-03-12 20:06:34 UTC 
Git commit 8490cd2b9c459b549753563274d8a7d630567395 by Maik Qualmann.
Committed on 12/03/2018 at 20:05.
Pushed by mqualmann into branch 'master'.

fix access to non-ascii character in the network share path
Related: bug 391744
FIXED-IN: 5.9.0

M  +3    -1    NEWS
M  +1    -1    libs/database/collection/collectionmanager.cpp

https://commits.kde.org/digikam/8490cd2b9c459b549753563274d8a7d630567395
Comment 2 caulier.gilles 2018-03-13 10:11:12 UTC 
The 5.9.0 pre-release installer is updated with last fix from Maik. Please try and report :

https://files.kde.org/digikam/
Comment 3 hardy.public 2018-03-30 15:09:33 UTC 
This is fixed.