Test Day:2012-03-07 L10N Desktop

Click here to set up this language box

Fedora Test Days
L10n Desktop
Date	2012-03-07
Time	all day
Website	QA/Fedora_17_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)

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 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. The specific live image for L10N tests can be found here (need update).
• Unless otherwise noted, you may use nightly Fedora 17 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.

Nice to test

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

• (as_IN)(gtk)(Translation) - Translation Error with "????" appearing
• (te_IN) Disk format message is out of screen during installation
• No translation on Login-Page of the reboot-menu
• (all languages) yum untranslated words
• Semi-translated messages (translated strings missing)

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.

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 lang_CODE	Indicates a test that has passed	{{result|pass|lang_CODE}}
inprogress lang_CODE	Indicates a test currently assigned and inprogress	{{result|inprogress|lang_CODE}}
warn lang_CODE	Indicates a test that needs further review	{{result|warn|lang_CODE}}<ref>some comments here.</ref>
fail lang_CODE	Indicates a failed test ... see Comment/Bug(s) for details	{{result|fail|lang_CODE}}