[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Pre string freeze release for GCompris
From:       Alexander Potashev <aspotashev () gmail ! com>
Date:       2018-11-20 10:51:53
Message-ID: CADMG6+9V-rb_zB7EabmBj+frvoTMPfSSB6-9s3hDZVbORoucgA () mail ! gmail ! com
[Download RAW message or body]

пн, 19 нояб. 2018 г. в 21:11, Johnny Jazeix <jazeix@gmail.com>:
> So the aim to introduce a pre-string freeze period is to check and improve the strings.

Hi Johnny,

You may want to fix these problems:

 1. "A letter is spoken. Click on the matching letter in the main area. You
can "
"listen to the letter again, by clicking on the mouth icon."

There is no mouth icon.

 2. "A letter is spoken. Click on the matching letter in the main area. You
can "
"listen to the letter again, by clicking on the mouth icon in the bottom box."

Same.

 3. "Guide the Number Muncher to all the factors of the number at the top of
the "
"screen."

Wrong: the note is on the bottom of the screen.

 4. "Guide the Number Muncher to the all the expressions that do not equal the
"
"number at the top of the screen."

Wrong: the note is on the bottom of the screen.

 5. "Guide the Number Muncher to all the multiples of the number at the top of
"
"the screen."

Wrong: the note is on the bottom of the screen.

 6. "<font color=\"#373737\">Check if the word<br/><b><font
color=\"#315AAA\">%1</"
"font></b><br/><font color=\"#373737\">is displayed"

Unpaired HTML tags <font ...>.


Thanks!

-- 
Alexander Potashev
[prev in list] [next in list] [prev in thread] [next in thread]