Hi,
while trying to run the automated tests for the Vietnamese localization
I came across several errors and warings, because the testtool
environment does not know about the new localization.
Thanks to Vito's hints I was able to get initially support for
vietnamese, so that first and topten tests run without problems (I'll
provide the files / patch).
The next step was to get full suppot for all tests in ooo_releasetes.sh.
But after a while, I wonder if this work would be usefull at all.
The problem is, that testtool scripts look for several localized strings
(e.g. file filter names, Object names ...). These are defined in several
filter??.txt files across the environment (afaik no complete list exists
what files are used). Considereing the time I have at the moment for
OOo, it would take about a month to find all these files and apply
patches. But I get the feeling the approach of testtool is wrong in this
case - why:
The only way for me to define the strings for testtool is to extract
them from the application (or ask Clytie to provide the strings). The
testtool then would check if the current string in the application
mathces the one that has been extrcted from the application - what
sounds a little strange to me. Next problem is - when the translation is
wrong, a translator does not only need to change the translation in OOo
but in the testtool environment as well (she needs to change sevral
files in this case). This is a lot of work and providing translation for
the testtool environment might be even more work than providing
translation for the application.
We have no "Reference" strings for most of our languages. Only English
and German strings are provided in the specifications. So for all those
languages, testtool would check one possible translation against another
possible translation.
The testool scripts internally use the old Phone-number system to
identify a language. This works at the moment .. but we have languages
where no code can be applied. So if we like to extend the testtool
environment to those languages we get probelems :-(
During recent discussion we learned, that functionality is not
localization dependent in most cases. Given the problems named above,
I'd rather use the testtool scripts for testing of functionality .. and
do not mix this up with thesting some of the translated strings.
So my idea is to check for translated strings only in first and topten
tests. All other scripts should be changed, so that a missing language
is ignored and only a notice is written instead of a warning. This is
still a lot of work but would be done only once per script and not once
per script and language, if we need to add the localized strings.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
