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 106051

Summary: need to convert Japanese manpages to UTF-8
Product: [Fedora] Fedora Reporter: Akira TAGOH <tagoh>
Component: shadow-utilsAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: eng-i18n-bugs, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 4.0.3-13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-22 16:28:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 100643    

Description Akira TAGOH 2003-10-02 09:23:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.2.1) Gecko/20030303

Description of problem:
Since we have decided to use UTF-8 locale, we can't look at EUC-JP manpages. so
basically it needs to be converted to UTF-8.

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


How reproducible:
Always

Steps to Reproduce:
1.LANG=ja_JP.UTF-8 man 5 shadow
2.
3.
    

Actual Results:  more warnings are output, and manpages is not readable.

Expected Results:  no warnings and readable.

Additional info:

I'm refiling this due to bugzilla issue.

Comment 1 Nalin Dahyabhai 2003-10-22 16:28:26 UTC
Fixing in 4.0.3-13.  Is there a systematic way of doing this sort of thing which
is preferred over one-off solutions like the one used this time?

Comment 2 Akira TAGOH 2003-10-24 13:02:19 UTC
Well, actually all manpages should has any information what encoding it is
using. e.g. .encoding UTF-8. and basically groff should converts it according to
that and current locale. but no such rules right now. so what we can do now is
just using iconv or something.