From Fedora Project Wiki

Revision as of 09:56, 3 September 2012 by Kparal (talk | contribs)

Fedora Test Days
L10n Desktop

Date 2012-09-20
Time all day

Website QA/Fedora_18_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on translations availability and accuracy in desktop applications

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

  • Development -
  • Quality Assurance - Aalam (alam)
  • Localization -

Prerequisite for Test Day

  • Bare metal or virtual machine.
  • Usb key, a virtualized guest or a burned CD/DVD with the test image

How to test?

Prepare Your System

  • Tests requiring physical media (e.g. DVD or CD images)
  • You may download a non-destructive Fedora 18 live image for your architecture. The specific live image for L10N tests can be found (ADD HERE). Tips on using a live image are available at FedoraLiveCD
  • Unless otherwise noted, you may use nightly Fedora 18 branch install images. Review for information on downloading and installing Branched.
  • If you are using a Alpha or pre-Alpha installation please keep in mind to update your system before running the tests.

How to run desktop in your language?

After booting from Live iso:
1. On desktop top right corner click on "Live System User"
2. From menu, select "System Settings"
3. In "System Settings" window, select "Region and Language"
4. Then in "Region and Language" window, under "Language", to add your language click plus (+) sign at the bottom.
5. In "Select a Language" window select your language, then click "select" button.
6. Close "Region and Language" window
7. Click "Live System User" at top right corner and select "Log Out..."
8. In confirmation box click on "Log Out" Button.
9. On gdm screen just click on user name "Live System User"
10. It will ask you to update folder name to your language, try your choice.

And start testing your language...

Nice to test

Bugs you might hit or additional situations that are nice to test:

Test Results

Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at Bugzilla against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

How to file bugs

The following links helps you to guide to file both l10n and i18n related bugs:-

Fill one bug report by component and issue
You should fill only one bug report by component and by issue.Be sure to link the report here quickly then, to let people re-use it.

Translation teams are free to prioritize packages they find more important to test. Please use the following format when posting results to this page:

Example Explanation Wiki text
none
Untested {{result|none}}
Pass pass lang_CODE
Indicates a test that has passed {{result|pass|lang_CODE}}
Inprogress inprogress lang_CODE
Indicates a test currently assigned and inprogress {{result|inprogress|lang_CODE}}
Warning warn lang_CODE
[1]
Indicates a test that needs further review
  1. some comments here.
{{result|warn|lang_CODE}}<ref>some comments here.</ref>
Fail fail lang_CODE
Indicates a failed test ... see Comment/Bug(s) for details {{result|fail|lang_CODE}}

Test Matrix

Only Fedora component are tested
This time, we only test Fedora components, the one following the Fedora release cycle. Therefor, you should not report here GNOME issues for example.

NOTE:- If you find any strings in English, kindly confirm whether its 100% translated in upstream. Link for upstream is provided along with each packages. Accordingly please file your bugs, as in some cases latest translations might not be imported.

Package Steps L10n resource Tracker Result [language code] Bug Comment
example Run command example
Fail fail pt_BR
Fail fail ja
RHBZ #678583 This is a result example.