Bug 193958 - Kwrite doesn't open files without an extension
Summary: Kwrite doesn't open files without an extension
Status: RESOLVED DUPLICATE of bug 188355
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdecore (show other bugs)
Version: 4.2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-24 23:26 UTC by Wojciech Ryrych
Modified: 2009-05-25 00:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
affected and unaffected files (20.00 KB, application/octet-stream)
2009-05-24 23:30 UTC, Wojciech Ryrych
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wojciech Ryrych 2009-05-24 23:26:51 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Gentoo Packages

KWrite has problem with opening plain text without an extension. I have many files with translation in Polish from dot.kde.org and don't use extensions.

usually:

1. I create a new text file without an extension
2. Open it with Kwrite
3. KWrite opens it
4. Put some text in Polish and save the file
5. The next time the preview on right sidebar shows that the text contains binary data (icon) or it is an unknown type of the file

What is strange that other files open normally (also without the extension). I can provide 2 similar files both affected and unaffected. The discussion about this was here: http://forum.kde.org/kwrite-doesnt-open-plain-text-files-without-an-extension-t-56727.html#pid77004

hope it might help :)
Comment 1 Wojciech Ryrych 2009-05-24 23:30:04 UTC
Created attachment 33981 [details]
affected and unaffected files

one file can be open in KWrite and the other doesn't - both have no extension
Comment 2 Wojciech Ryrych 2009-05-24 23:30:53 UTC
ok, I've just added an attachment
Comment 3 Dario Andres 2009-05-25 00:23:18 UTC
This was fixed recently on KDE4.3 code. Bug 188355. Thanks

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