m (Pravins moved page FLTG/Test Day:2015-08-18 Translation (l10n) to FLTG/Test Day:2015-08-18 L10N: Removing Translation and brackets from name.) |
|
(No difference)
| |
Revision as of 06:40, 13 August 2015
| Fedora Test Days | |
|---|---|
| |
| L10n Desktop | |
| Date | 2015-08-18 |
| Time | all day |
| Website | QA/Fedora_23_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 -
- Localization -
Prerequisite for Test Day
- Bare metal or virtual machine. Start with Virtualization
- 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 20 live image for your architecture. The specific live image for L10N tests can be found here soon. Please note we are providing only x84_64 image for this testing. Tips on using a live image are available at FedoraLiveCD
- Unless otherwise noted, you may use nightly Fedora 20 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 "Settings"
3. In "Settings" window, select "Region and Language"
4. Then in "Region and Language" window, Click on "Language", to add your language click ... (more) sign at the bottom.
5. In window select your language (start type name in English), then select language name and Click Done
6. enable INPUT method, in "Region and Language" window, Click on "Input Method", to add keyboard you want, click on plus ('+') and (more) sign at the bottom.
7. In window select your keyboard (start type name in English), then select keyboard name and Click Add
8. Click on 'Restart Now' bar will appear as in screen-shot
9. click on "Log Out" Button to logout
10. On gdm screen just click on user name "Live System User"
11. 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:
- (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.
How to file bugs
The following links helps you to guide to file both l10n and i18n related bugs:-
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. We have made introduced a new test matrix from Fedora 18 l10n testing. Feel free to provide feedback/comments/suggestions to fltg mailing list.
- The applications have been divided into Frequently Used Applications (FUAs) and non Frequently Used Applications (non-FUAs) for translation teams to prioritize packages for testing.
- Further, both FUA and non-FUA lists are subdivided into project wise sections into Fedora applications, Gnome applications and Firefox.
- The test matrix table below takes you to individual pages application-wise for testing.
- Each test page contains test cases for each application where you can provide the test results for that application in a table format like earlier.
- Click on the link in the second column in the below test matrix, which directs you to the test result page where you can enter your language name, code (fail/pass), bug filed and comments, if any.
Test Matrix
Both FUA and non-FUA will have Fedora and Gnome sections
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.
FUAs Application List
FEDORA Applications
GNOME Applications
FIREFOX
| Package | Provide Results | L10n Resource | Comments |
|---|---|---|---|
|
QA-L10N:firefox | firefox teams |