Bug 129736 - emacs doesn't detect utf8 encoding of file
emacs doesn't detect utf8 encoding of file
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: emacs (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jens Petersen
:
Depends On:
Blocks: FC5Target
  Show dependency treegraph
 
Reported: 2004-08-12 08:32 EDT by Alexander Larsson
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-28 04:34:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The textfile, in utf8. (241.47 KB, text/plain)
2004-08-12 08:32 EDT, Alexander Larsson
no flags Details
Other text file (14.35 KB, text/plain)
2004-08-30 09:26 EDT, Alexander Larsson
no flags Details

  None (edit)
Description Alexander Larsson 2004-08-12 08:32:18 EDT
Unless i add a local coding variable defining the file as utf8 emacs
doesn't autodetect the file as utf8, so when you save the utf8
characters in the file are changed.
Comment 1 Alexander Larsson 2004-08-12 08:32:49 EDT
Created attachment 102645 [details]
The textfile, in utf8.
Comment 2 Miloslav Trmač 2004-08-12 09:29:29 EDT
$ LC_MESSAGES=C iconv -f utf-8 -t utf-8 < eel-changelog  > /dev/null
iconv: illegal input sequence at position 8181
Comment 3 Jens Petersen 2004-08-13 08:22:22 EDT
Well spotted: the second "Tomasz K" is different from the first -
so it looks like the file corrupted.
Comment 4 Alexander Larsson 2004-08-30 09:26:11 EDT
Created attachment 103246 [details]
Other text file

Ok, what about this one. It passes iconv and has the same problem.
Comment 5 Matthew Miller 2005-04-26 11:14:06 EDT
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Comment 6 Jens Petersen 2005-09-28 04:34:07 EDT
AFAICT this is ok now with cvs emacs (ie emacs22)
which has improved upstream support.

Note You need to log in before you can comment on or make changes to this bug.