By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1954 - kate/kwrite - no UTF-16 Unicode text, with CRLF, CR line terminators
Summary: kate/kwrite - no UTF-16 Unicode text, with CRLF, CR line terminators
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeutils (show other bugs)
Version: R14.0.x [Trinity]
Hardware: All Linux
: P5 enhancement
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2969
  Show dependency tree / graph
 
Reported: 2014-02-21 21:41 CST by David C. Rankin
Modified: 2018-08-30 02:24 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Example file for UTF-16 text (attachment corrupted) (3.44 KB, text/x-csrc)
2014-02-21 21:42 CST, David C. Rankin 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David C. Rankin 2014-02-21 21:41:29 CST 
kate/kwrite fail to open any UTF-16 Unicode text, with CRLF, CR line terminators that can be easily opened in vim or (DOS/Windows) editors. All TDE editors (save and except kedit) should be able to easily handle any and all common text formats from Linux or otherwise.
Comment 1 David C. Rankin 2014-02-21 21:42:54 CST 
Created attachment 1943 [details]
Example file for UTF-16 text (attachment corrupted)

This is an example of a text file kate/kwrite cannot handle and attempt to open it as a binary file.
Comment 2 Timothy Pearson 2014-03-02 18:06:10 CST 
Comment on attachment 1943 [details]
Example file for UTF-16 text (attachment corrupted)

Can you please resubmit this attachment?  It was corrupted in the Bugzilla upgrade.

Thanks!