Bug 189660 - unicode plain text files aren't opened with $editor by default, but ascii ones do
Summary: unicode plain text files aren't opened with $editor by default, but ascii one...
Status: RESOLVED DUPLICATE of bug 188355
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-15 00:08 UTC by Marcel B.
Modified: 2009-05-21 18:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel B. 2009-04-15 00:08:25 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

This applies not only to the plasma desktop but also to dolphin, but I didn't find a more general "application" to assign the report to. Additionally, I noticed this behaviour with windows-1258-encoded files, too.

How to reproduce:
- Create two text files with $texteditor, save one with f.e. ascii encoding and one with unicode/utf-8.
- Try to open them by clicking on them on the desktop or within dolphin. The ascii-encoded one will be handed over to kwrite as expected, the unicode one won't and kde will ask with which program you want to open it.

Expected behaviour:
Both files should be opened with $texteditor by default.
Comment 1 Beat Wolf 2009-04-15 12:59:45 UTC
isn't this a mimetype bug?
Comment 2 Marcel B. 2009-04-15 13:09:18 UTC
The "application list" of bugzilla just contains kmail/kdepim-related components when searching for mime, but in general that seems plausible.
Comment 3 Dario Andres 2009-04-17 17:59:30 UTC
I guess this should be reassigned to kdelibs. I remember a related bug: in Dolphin the ascii-only files are shown(preview) as text files, but the files that contain non-ascii chars are shown as binary data (their text preview is not generated). This may be related to the fact that the textthumbnail protocol only uses ascii characters (weird and old). I can't find the related bug number.
Comment 4 Christoph Feck 2009-05-21 18:19:35 UTC

*** This bug has been marked as a duplicate of bug 188355 ***