Bug 798640

Summary: Whats the need of TA-IN?
Product: [Fedora] Fedora Localization Reporter: Arun Prakash <arunprakash.pts>
Component: l10n-requestsAssignee: Dimitris Glezos <dimitris>
Status: CLOSED NOTABUG QA Contact: A S Alam <aalam>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: diegobz, fedora, mshao, piotrdrag, trans
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-03 17:22:20 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:

Description Arun Prakash 2012-02-29 13:22:37 UTC 
I recently noticed that we have TA-IN (Tamil India) as one of the languages, also it doesnot have any teams yet. 
In india we use the tamil code as TA and most very less frequently as TA-IN. For srilanka tamil they use TA-LK. So it is highly unnecessary to have TA-IN branch.
Comment 1 Piotr Drąg 2012-02-29 20:00:54 UTC 
You are right that ta_IN should not be used, as glibc only works with 'ta' code. It's here probably because of the convention that Publican-based documentation use. As long as there is no team created, no actual translations can be send for this invalid (for software anyway) language code, so we're fine.