From Fedora Project Wiki
(Move long comments to a separate section at end of page) |
|||
| (6 intermediate revisions by 5 users not shown) | |||
| Line 9: | Line 9: | ||
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] with i18n keyword. For instance file a bug report against the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=20&component=firefox&keywords=i18n firefox] if you have problems testing the Firefox Web Browser. adding ''i18n'' keyword to '''Keywords''' field in bugzilla is important part in order to keep it on track. 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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be language you tested, the third should be the list of testers' name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line. | If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] with i18n keyword. For instance file a bug report against the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=20&component=firefox&keywords=i18n firefox] if you have problems testing the Firefox Web Browser. adding ''i18n'' keyword to '''Keywords''' field in bugzilla is important part in order to keep it on track. 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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be language you tested, the third should be the list of testers' name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line. | ||
== Long comments == | |||
<references group="long" /> | |||
{| class="wikitable sortable" style="width: 100%" rowbgcolor="#3074c2" rowstyle="color: white; font-weight: bold;" 55% | {| class="wikitable sortable" style="width: 100%" rowbgcolor="#3074c2" rowstyle="color: white; font-weight: bold;" 55% | ||
| Line 17: | Line 20: | ||
|- | |- | ||
| ll-cc (language-country) | | ll-cc (language-country) | ||
| {{result|pass}} or {{result|fail}} <ref>if failing one of test cases in the category, then the result should be {{result|fail}}. also leave a comment with bz reference like {{bz|12345}}</ref> | | {{result|pass}} or {{result|fail}} <ref group="long">if failing one of test cases in the category, then the result should be {{result|fail}}. also leave a comment with bz reference like {{bz|12345}}</ref> | ||
| [[User:Sample User1|Sample User1]] [[User:Sample User2|Sample User2]] <ref>Add you here and update the result with the reference as needed when the result is different to what others did.</ref> | | [[User:Sample User1|Sample User1]] [[User:Sample User2|Sample User2]] <ref>Add you here and update the result with the reference as needed when the result is different to what others did.</ref> | ||
| <references/> | | <references/> | ||
|-} | |- | ||
| bn_IN | |||
| {{result|pass}} <ref> yum-langpack:running fine. </ref> <ref group="long"> dnf-langpacks: dnf is installed. The dnf-langpacks will not work if dnf-plugins-core is not already installed. {{bz|1136172}}. All 3 langpacks commands works fine after installing dnf-plugins-core.</ref> <ref> PyGTKDeprecationWarning messages on terminal {{bz|1136177}} </ref><ref> fonts-tweak-tool able to write configuration file and its used by gedit </ref> <ref group="long"> 'fc-match sans-serif:lang=bn' gave 'Lohit-Bengali.ttf' , 'fc-match serif:lang=bn' and 'fc-match monospace:lang=bn' gave ' Lohit-Bengali.ttf', where as fc-match sans-serif:lang=bn-in' gave 'Lohit-Bengali.ttf', 'fc-match serif:lang=bn-in' gave 'Lohit-Bengali.ttf'and 'fc-match monospace:lang=bn-in gave 'Lohit-Bengali.ttf' font.</ref> | |||
| [[User:smaitra|Satya]] | |||
| <references/> | |||
|- | |||
| ja-JP | |||
| {{result|pass}} <ref>yum-langpacks works.</ref> | |||
| [[User:Tagoh|tagoh]] | |||
| <references/> | |||
|- | |||
| ja_JP | |||
| {{result|pass}} <ref>yum install @kde-desktop worked correctly</ref> | |||
| [[User:Petersen|juhp]] | |||
| <references/> | |||
|- | |- | ||
| mr_IN | | mr_IN | ||
| {{result|pass}} <ref> yum-langpack: Lang packs is picked and installed automatically for the libreoffice/tesseract package. </ref> <ref> dnf-langpacks: dnf is installed. The dnf-langpacks will not work if dnf-plugins-core is not already installed. {{bz|1136172}}. All 3 langpacks commands works fine after installing dnf-plugins-core.</ref> <ref> fonts-tweak-tool able to write configuration file | | {{result|pass}} <ref> yum-langpack: Lang packs is picked and installed automatically for the libreoffice/tesseract package. </ref> <ref group="long"> dnf-langpacks: dnf is installed. The dnf-langpacks will not work if dnf-plugins-core is not already installed. {{bz|1136172}}. All 3 langpacks commands works fine after installing dnf-plugins-core.</ref> <ref> PyGTKDeprecationWarning messages on terminal {{bz|1136177}} </ref><ref> fonts-tweak-tool able to write configuration file and its used by gedit </ref> <ref group="long"> 'fc-match sans-serif:lang=mr' gave 'Lohit-Devanagari.ttf' , 'fc-match serif:lang=mr' and 'fc-match monospace:lang=mr' gave ' Lohit-Devanagari.ttf', where as fc-match sans-serif:lang=mr-in' gave 'Lohit-Devanagari.ttf', 'fc-match serif:lang=mr-in' gave 'Lohit-Devanagari.ttf'and 'fc-match monospace:lang=mr-in gave 'Lohit-Devanagari.ttf' font.</ref> | ||
| [[User:Pnemade|Parag]] | | [[User:Pnemade|Parag]] | ||
| <references/> | |||
|- | |||
| zh_CN | |||
| {{result|pass}} <ref>tested works as expect for Langpack Yum Application</ref> <ref>tested works as expect for Langpack Dnf Application</ref> <ref>tested works as expect for fonts-tweak-tool </ref> | |||
| [[User:lijli|Lijun Li]] | |||
| <references/> | | <references/> | ||
|-} | |-} | ||
|} | |} | ||
Latest revision as of 06:01, 26 December 2014
I18N Test Day - Other[edit]
Test cases[edit]
Results[edit]
If you have problems with any of the tests, report a bug to Bugzilla with i18n keyword. For instance file a bug report against the component firefox if you have problems testing the Firefox Web Browser. adding i18n keyword to Keywords field in bugzilla is important part in order to keep it on track. 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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be language you tested, the third should be the list of testers' name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.
Long comments[edit]
| Language | Result | Testers | Comments/Ref. |
|---|---|---|---|
| ll-cc (language-country) |   |
Sample User1 Sample User2 [1] |
|
| bn_IN | |
Satya | |
| ja-JP | |
tagoh |
|
| ja_JP | |
juhp |
|
| mr_IN | |
Parag | |
| zh_CN | |
Lijun Li |
Cite error: <ref> tags exist for a group named "long", but no corresponding <references group="long"/> tag was found