Bug 77130 - cannot set utf-8 as preferred encoding
cannot set utf-8 as preferred encoding
Product: Red Hat Linux
Classification: Retired
Component: xemacs (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jens Petersen
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2002-11-01 11:00 EST by diego.santacruz
Modified: 2015-01-07 19:01 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-19 04:42:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description diego.santacruz 2002-11-01 11:00:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
Tried setting the preferred encoding in xemacs to utf-8, but I get the error
"Can't prefer the 'utf-8' coding system". Since now UTF-8 is the default
encoding in Red Hat 8.0, it should be possible to set UTF-8 in xemacs as the
preferred coding.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Set the preferred coding to UTF-8 with 'Esc-x prefer-coding-system' anb then

Actual Results:  xemacs refuses to set the coding to UTF-8 with the message
"Can't prefer the 'utf-8' coding system"

Expected Results:  Be able to set UTF-8 as the preferred coding so that new
files are written in UTF-8.

Additional info:

Currently one has to manually set the coding to UTF-8 before opening each file,
which is a pain.
Not using UTF-8 creates all types of problems when attempting to read the file
with more or less (since they will assume UTF-8).
Comment 1 Jens Petersen 2002-11-11 01:28:50 EST
Yes, I have also noticed this.

Comment 2 Jens Petersen 2003-04-17 08:58:59 EDT
Utf-8 coding configuration should be improved in xemacs-21.4.12-8
in rawhide shortly.
Comment 3 Jens Petersen 2003-05-19 04:42:17 EDT
Closing for now.

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