Bug 772855 - en_US.utf8 locale doesn't seem to work correctly, e.g., when displaying man pages
Summary: en_US.utf8 locale doesn't seem to work correctly, e.g., when displaying man p...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 16
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jeff Law
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-10 06:51 UTC by Wayne Pollock
Modified: 2016-11-24 15:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 20:01:04 UTC
Type: ---


Attachments (Terms of Use)

Description Wayne Pollock 2012-01-10 06:51:07 UTC
Description of problem:

I use PuTTY SSH client v0.62, with UTF-8 translation.  I noticed some man pages looking strange:

LC_ALL=en_US.utf8 man iptables  # look at the hypens, e.g., in the "raw" paragraph

LC_ALL=C.utf8 man iptables  # compare with above; all looks correct.

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

Linux myservername 3.1.6-1.fc16.i686.PAE #1 SMP Wed Dec 21 23:01:09 UTC 2011 i686 i686 i386 GNU/Linux

man-pages-3.32-14.fc16.noarch
glibc-common-2.14.90-24.fc16.4.i686  # locale stuff

$ locale -V
locale (GNU libc) 2.14.90

How reproducible:

Always

Steps to Reproduce:
1. LC_ALL=en_US.utf8 man
2.
3.
  
Actual results:
squares or weird symbols

Expected results:
hyphens, curly-quotes, and other symbols should show as expected.

Additional info:

May be related to bug #98736.  This seems more a problem with en_US than with utf8.

Comment 1 Jeff Law 2012-02-14 20:01:04 UTC
I did a fresh F16 i686 install using the installation repo & updates repo and have been unable to reproduce this problem.

I've got the same glibc, glibc-common and man-pages.

I get the same man page results for en_US.utf8, C.utf8 and with no explicit locale.  In each case the "raw" paragraph looks fine.

I then installed putty and used that to ssh into the box and tried the same tests and again all the pages were fine.

I'm closing this as WORKSFORME.


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