Test Day:2011-08-30 L10n Desktop

Click here to set up this language box

Fedora Test Days
L10n Desktop
Date	2011-08-30
Time	all day
Website	QA/Fedora_16_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 - IgorSoares (igorps), Rhe (rhe), 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.
• Unless otherwise noted, you may use nightly Fedora 16 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.

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}}

Test Matrix

Package	Steps	Result [language code]	Bug	Comment
example	Issue command example	fail pt_BR	RHBZ #678583
abrt	Issue command abrt-gui
anaconda	Issue command liveinst			Perform this first to install onto hard drive. Also test the keyboard layout behavior according to [1]
audit-viewer	Issue command audit-viewer
authconfig	Issue command authconfig
chkconfig	Issue command chkconfig
certmonger	Check .PO file
comps	n/a (this can be checked through anaconda test using the install media)
fedora-desktop-backgrounds	Go to System -> Settings -> Appearance
fedora-initscripts	This can be checked by pressing Esc during system boot-up
fedora-preupgrade	Issue command preupgrade and preupgrade-cli
desktop-effects	Issue command desktop-effects
firstboot	As root ("su -" or "sudo"), issue command firstboot
libreport	Check .PO file
im-chooser	Issue command im-chooser
iok	Issue command iok
kexec-tools	Issue command kexec -h
libuser	Check .PO file
liveusb-creator	Issue command liveusb-creator
mlocate	Issue command locate -h
multimedia-menus	Go to Application -> Sound & Video -> Output Generation
newt	Check .PO file
passwd	Issue command passwd -?
policycoreutils	Issue command system-config-selinux and selinux-polgengui
pykickstart	Check .PO file
python-meh	Check .PO file
redhat-menus	Check desktop menu
setroubleshoot	Issue command sealert -b
setuptool	Issue command setup
smolt	Issue command smoltGui and as root, issue command firstboot and check the section of 'Hardware Profile'
smoon	Check .PO file
sos	Become root using either su - or sudo), issue command sosreport
switchdesk	Issue command switchdesk
system-config-audit	Issue command system-config-audit
system-config-bind	Issue command system-config-bind
system-config-boot	Issue command system-config-boot
system-config-date	Issue command system-config-date
system-config-firewall	Issue command system-config-firewall
system-config-httpd	Issue command system-config-httpd
system-config-kdump	Issue command system-config-kdump
system-config-keyboard	Issue command system-config-keyboard
system-config-kickstart	Issue command system-config-kickstart
system-config-language	Issue command system-config-language
system-config-lvm	Issue command system-config-lvm
system-config-netboot	Issue command system-config-netboot
system-config-network	Issue command system-config-network
system-config-nfs	Issue command system-config-nfs
system-config-printer	Issue command system-config-printer
system-config-rootpassword	Issue command system-config-rootpassword
system-config-samba	Issue command system-config-samba
system-config-services	Issue command system-config-services
system-config-users	Issue command system-config-users
system-switch-java	Issue command system-switch-java
system-switch-mail	Become root using either su - or sudo, issue command system-switch-mail
usermode	Become root using either (su - or sudo), issue command usermode