Bug 134045 - the gu_IN locale improvements
Summary: the gu_IN locale improvements
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: Indic
TreeView+ depends on / blocked
 
Reported: 2004-09-29 07:38 UTC by Jatin Nansi
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-04 09:03:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
updates to gu_IN locale data (4.07 KB, patch)
2004-09-29 07:40 UTC, Jatin Nansi 		no flags Details | Diff
updated patch (5.59 KB, patch)
2004-10-04 08:09 UTC, Jatin Nansi 		no flags Details | Diff
Show Obsolete (1) View All

Description Jatin Nansi 2004-09-29 07:38:35 UTC 
Description of problem:
the localedata for gu_IN in glibc has some missing fields and some
spelling mistakes. I am attaching a patch to correct those.

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

How reproducible:
Every time

Steps to Reproduce:
1. this data is used in several places. No steps to reproduce tho.
2.
3.
  
Actual results:
missing data, and spelling mistakes

Expected results:
correct data

Additional info:
Comment 1 Jatin Nansi 2004-09-29 07:40:23 UTC 
Created attachment 104491 [details]
updates to gu_IN locale data
Comment 2 Jatin Nansi 2004-09-29 07:44:59 UTC 
submitted upstream:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=413
Comment 3 Ulrich Drepper 2004-09-30 10:18:35 UTC 
I cannot  judge the patch much but is wrong, for instance, that
yesexpr and noexpr do not recognize yY and nN as well.  This is common
practice in all locales.
Comment 4 Jatin Nansi 2004-10-04 08:08:46 UTC 
Attaching patch with yesexpr and noexpr corrected.
Comment 5 Jatin Nansi 2004-10-04 08:09:40 UTC 
Created attachment 104707 [details]
updated patch
Comment 6 Ulrich Drepper 2004-10-04 09:03:50 UTC 
I've added the patch upstream.  It'll find its way into FC3 with the
next update.
Note You need to log in before you can comment on or make changes to this bug.