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 108166

Summary: should use nroff on KNROFF
Product: [Fedora] Fedora Reporter: David Joo <djoo>
Component: manAssignee: Eido Inoue <havill>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: eng-i18n-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.5m2-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-01-27 00:49:03 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: 100644    

Description David Joo 2003-10-28 08:20:57 UTC
Description of problem:
Because we have two locale to deal with (new UTF-8 for ko_KR and EUC-KR), KNROFF
path should run  /usr/bin/nroff -c -mandoc instead of /usr/bin/groff -Tkorean
-mandoc to detect charset correctly and use the proper dev for groff

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

How reproducible:
everytime

Steps to Reproduce:
1. LANG=ko_KR.UTF-8 man man
    
Actual results:
does not show man

Expected results:
should show man in UTF-8

Additional info:
probably just s/KNROFF         /usr/bin/groff -Tkorean -mandoc/KNROFF         
/usr/bin/nroff -c -mandoc/ will be fine

Comment 1 Leon Ho 2003-12-08 00:32:19 UTC
Does this solution okay to you? Anything that we can do on our end to
resolve this bug?

Comment 2 Eido Inoue 2003-12-08 17:26:53 UTC
Looks ok. Will push the changes to fc2 first.

Comment 3 Eido Inoue 2004-01-27 00:49:03 UTC
Korean will use the nroff script front-end as mentioned. There won't
be a separate knroff variable, though, because everything will be
unified to use one nroff (korean and japanese can both use nroff
because it checks the locale)