From Fedora Project Wiki


Fedora Language Testing Group [FLTG] is a SIG group of Fedora contributors taking care of language testing in Fedora.

Our mission is to test and review language support in Fedora and act as a bridge between translation team, i18n team and users to aid in testing languages in Fedora.

What do we do

  • Test the new fedora releases for our respective languages using different test cases we have prepared.
  • File the bugs and provide reference for other translators/testers.
  • Add new test cases based on new bugs filed and new packages.
  • Prepare the ISO for testing in consultation with the release-engineering team.
  • Coordinate and conduct both i18n (with the help of Fedora i18n team) and 110n test days.
  • Based on the ISO selected for testing, review the test cases.
  • Keep informed the l10n team about new issues, helping them to improve the testing.
  • Submit the report on test days and collect feedback from testers.

Types of Test Days

Fedora L10N Test Day


  • To improve the quality of Fedora in our native languages.
  • To develop more test cases for easy and planned testing.
  • To help the translators/testers find the common bugs.
  • To have a collective testing platform where all translators can be together and test to improve their product with less bugs and errors.
  • A point of contact for all testers to get more information on testing events, test cases and common bugs.

Joining FLTG

IRC Channel

#fedora-g11n[?] on Freenode

Test days : #fedora-test-day on Freenode

Mailing Lists

  • g11n list - Discussions about Language Testing activities, bugs filed, test cases, feedback on testing


Meetings are held bi-weekly on Wednesdays 04:30:00 UTC.


Fedora Language Test Days

Fedora 24

Fedora 23

Current status:

Fedora 22

Fedora 20

Ticket - i18n testing date

Ticket - l10n testing date

ISO Request Ticket

Other important links:-

Previous Test Days

Fedora 19 **

Fedora i18n Test Days

Ticket - i18n testing date

Ticket - l10n testing date

Test Day Reports

Feedbacks Collected

Fedora 18 **

  • L10n/i18n Installation Test Day - Due to issues with anaconda, no installation test day was conducted for F18.

Fedora i18n Test Days

Ticket to follow

Test Day Reports

Feedbacks Collected

Fedora 17 **

Fedora 17 Test Days

Ticket discussion

Feedbacks Collected

** Note: FLTG started testing from Fedora 17 release.

Fedora 16

Test Days

Ticket discussion

Fedora 15

Fedora 12

Bug Reporting

Filing a bug is the most important task in testing as reporting the problems you encounter help developers to fix the issue and make the product for best use. Each project has its own way to file bugs and bug reporting process for Fedora and Gnome is explained below.

Instructions to file bugs in Fedora

  • To file l10n bugs in Fedora, please visit here.
  • To file i18n bugs in Fedora, please visit here.

Instructions to file bugs in Gnome

Bugs pertaining to Gnome must be filed in Gnome Bugzilla. To file l10n bugs in Gnome, please follow the instructions mentioned here.

Language Bug Triage

List need to create in Bugzilla 'TODO'

New i18n Features to be included for testing

Fedora 18

- Fontconfig 2.0

- Gnome Ibus Integration

- ibus-libpinyin

- Typing Booster

- Gnome Initial Experience

- Liberation Fonts 2

- New Installer (anaconda)

Fedora 17

- Indian Language Unicode 6

- Gnome Input Integration ibus

- libpinyin

- Inscript2

- Font Configuration Tool

- Eekboard


Reports give you all the details like languages participated in testing, number of applications tested, no of bugs filed etc. Reports for l10n and i18n test days are available below :

Fedora 19

Fedora 18


After every test event FLTG makes sure that all feedback and suggestions are collected from the community. This helps us to improve our future testing events and make things easy for our testers. All feedbacks from community are recorded here.

Check-list for FLTG Members

This list explains the step-by-step tasks executed by the FLTG group before every testing event. Each members choose their tasks and work collectively towards making the testing event successful. To view the list click here.