Caio Tiago Oliveira wrote:
On 7/26/07, Thorsten Ziehm <[EMAIL PROTECTED]> wrote:
> Translation is here a different part. Checking the
>> translation in new features, does not need test cases for
functionality.
>> It is only needed to know, where the changes were done in UI.
> Where we get this information compressed for testing?
The Office is too complex. I cannot tell you, where changes were made.
This is a big problem, but I do not know how this can be solved.
I might to be oversimplifying this, but...
there are a lot of new strings or dialogs.
~30.000 as I know for UI and help in 43 CWS which are flagged as UI/help
relevant. I cannot say, where you can find these changes. Perhaps
somebody is possible to identify it.
[...]
Even if the l10n responsible run pofilter on the files, may occur errors.
If not, he could even submit strings partially translated, for
instance (gsicheck would catch only when missing tags or so, it can't
find too short strings).
So... would be nice to someone look at these dialogs and say they are
correctly translated before integrating.
l10n tests on TCM would help to find these cases.
How should the test case look like?
In general, it's nice to review the new strings before releasing.
+1
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
