Bug 441331 – no local code id for fedora localization

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 441331 - no local code id for fedora localization

Summary:	no local code id for fedora localization

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora Localization
Classification:	Fedora
Component:	l10n-requests (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Dimitris Glezos
QA Contact:	A S Alam
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-04-07 12:12 EDT by Teguh DC
Modified:	2013-07-02 20:49 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-04-07 19:13:45 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Teguh DC 2008-04-07 12:12:23 EDT

Description of problem:
local code for indonesian (id) doest not appear in component list for the
product "Fedora Localization".

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dimitris Glezos 2008-04-07 12:28:49 EDT

You can take a look at the following FAQ entry on instructions to get your
component registered:

  http://fedoraproject.org/wiki/L10N/FAQ#bugzilla-team

This is a part of the set of steps needed to create a new Fedora translation
team, as noted at /wiki/L10N/Maintainer.

If you need someone else to commit the file for you, please copy-paste the
appropriate line from the owners.list file here, and someone will commit it for you.

Comment 2 Teguh DC 2008-04-07 19:13:45 EDT

Ok, thanks for giving this clue. just update the owners.list

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