Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 164813

Summary: Numeric Character for Punjabi Locale AM|PM
Product: Red Hat Enterprise Linux 4 Reporter: Elena Zannoni <ezannoni>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2005-678 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-05 16:42:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 158715    
Bug Blocks: 156322    

Description Elena Zannoni 2005-08-01 16:10:15 UTC
+++ This bug was initially created as a clone of Bug #158715 +++

Description of problem:
for Punjabi locale in Time (AM|PM) on desktop, Punjabi locale has a Numeric
character (5) instead of proper Punjabi Character.

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

How reproducible:

Steps to Reproduce:
1.Login into Punjabi Locale
2. check Time in panel in 12 hour format
Actual results:
string is like "ਸ5à©à¨°à©"

Expected results:
It should be "ਸਵà©à¨°à©"

Additional info:
1)refer to bug 622
there is patch on 27Dec04, which was wrongly applied
2) <U035> should be replaced with <UA035>, but did with <U0035>

Comment 2 Red Hat Bugzilla 2005-10-05 16:42:42 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.