Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 105762 - japanese man page of nkf is not UTF-8 encoded
Summary: japanese man page of nkf is not UTF-8 encoded
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nkf
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-09-27 04:24 UTC by Kazutoshi Morioka
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: 2.03-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-09-30 07:18:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Kazutoshi Morioka 2003-09-27 04:24:29 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030702
Galeon/1.3.9

Description of problem:
At Fedora Core, japanese man pages should be encoded with UTF-8.
But man page for nkf, "/usr/share/man/ja/man1/nkf.1.gz" is encoded with EUC-JP.
So, japanese man page of nkf cannot be read in default ja_JP.UTF-8 locale.

I suspect another japanese man pages not included in man-pages-ja are also
encoded with EUC-JP.

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

How reproducible:
Always

Steps to Reproduce:
1. Set language to japanese (normaly, ja_JP.UTF-8 is selected)
2. Open gnome-terminal.
3. Type this command.
man nkf

Actual Results:  man page for nkf is shown in corrupted characters and not readale.

Expected Results:  man page for nkf is shown in japanese.

Additional info:

I suspect another japanese man pages not included in man-pages-ja are also
encoded with EUC-JP.
Comment 1 Akira TAGOH 2003-09-30 07:18:08 UTC 
fixed in 2.03-1
Note You need to log in before you can comment on or make changes to this bug.