Bug 798640 - Whats the need of TA-IN?
Summary: Whats the need of TA-IN?
Status: CLOSED NOTABUG
Alias: None
Product: Fedora Localization
Classification: Fedora
Component: l10n-requests
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dimitris Glezos
QA Contact: A S Alam
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 13:22 UTC by Arun Prakash
Modified: 2013-07-03 01:10 UTC (History)
5 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2012-04-03 17:22:20 UTC


Attachments (Terms of Use)

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.


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