Bug 190042 - Reasonable default character encoding for new FTP folder
Summary: Reasonable default character encoding for new FTP folder
Status: RESOLVED FIXED
Alias: None
Product: knetattach
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-19 11:50 UTC by Unknown
Modified: 2010-05-29 13:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2009-04-19 11:50:33 UTC
Version:            (using KDE 4.2.2)
Installed from:    Ubuntu Packages

When I add a new FTP folder with the network folder dialogue available in "Networks", the default encoding is "Arabian (ISO 8859-6)". While Dolphin of course can not know which encoding is used, I don't think this is a reasonable default encoding since it is quite unlikely for a German user (and I set KDE to German) to use that encoding. People not knowing about encodings, or not knowing which encoding their FTP server uses (me being one of the latter) might just leave it that way and experience problems when using special characters. The default should either be an international encoding like UTF-8 (if that is often used for FTP - as I said, I don't know) or the local encoding depending on the setting of the user.
Comment 1 Gabriel Magno de Oliveira Silva 2009-10-29 02:28:42 UTC
It occurs adding SSH folder as well. In my case, the default is "Báltico (ISO 8859-13)", that is the first in the list.
Comment 2 Unknown 2009-11-14 10:38:59 UTC
The issue is still there in KDE 4.3.2 (Kubuntu)
Comment 3 Unknown 2010-05-29 13:14:40 UTC
This is fixed in KDE 4.4, thank you very much :)