Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 82517 - perl doesn't know 'GB18030' encoding
perl doesn't know 'GB18030' encoding
Product: Red Hat Linux
Classification: Retired
Component: perl (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-01-22 19:33 EST by Bernd Groh
Modified: 2014-06-18 04:21 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-11 06:53:39 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 Bernd Groh 2003-01-22 19:33:28 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
When using the module Encode and trying to convert either from or to 'GB18030',
using Encode::from_to, I'll get the message:

Unknown encoding 'GB18030'

Since I believe 'GB18030' should be supported, I thought that this might be a bug.


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

How reproducible:

Steps to Reproduce:
1. write following perl-script:
use Encode;
$string = $ARGV[0];
Encode::from_to($string, 'GB18030', 'UTF8');
print "$string\n";
2. make it executable and execute it

Actual Results:  Follwing Error-Message appears:
Unknown encoding 'GB18030' at <path to script>/<script> line 4

Expected Results:  The GB18030-encoded string provided as argument to the script
should have been displayed (assuming STDOUT is screen) in UTF8-encoding.

Additional info:
Comment 1 Warren Togami 2005-05-28 03:25:37 EDT
Is this still an issue in RHEL4, FC3, or FC4?
Comment 2 Warren Togami 2005-09-11 06:53:39 EDT
Closing due to lack of response and RH8 is not a supported product.

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