Hi Vito,
indeed there are some efforts to make it easier localizing automated
scripts for writer component. Have a look in the directory
../writer/tools and you'll find a test 'w_get_locale_strings.bas'.
Running this test returns the strings needed for w_fields.bas,
w_table.bas, and loadsave tests. Just copy and paste them into the
needed tests....this is from my point of view a fast method to get these
tests localized.
Further on there is a file called 'w_locale_strings1.inc' that holds all
relevant strings for testcase 'tTableNumberFormat' in table test that
needed some string comparing. This is the first step to have
localizations in writer centralized....and yes it is in some cases
essential to have strings compared....hard work. But as you see we are
on our way and help is always appreciated ;-)
I will update the wiki-page with this information.....hope this helps!
--
Regards
Helge
Vito Smolej wrote:
Regarding test routines for writer, the wiki page (*) tells what to do
with the file writer/update/inc/w_002_.inc and then suggests:
* In the "Writer"-directory: Search for "iSprache".*
There were 39 hits (**). Thirtynine separate files to edit, expand
with localized strings (again) etc. Any plans to localize (pun
intended)? And/or bootstrap the situation by using tool scripts that
create (like in other parts of the system) the required information in
the form of xxxxxxxxxx_NN.txt files?
--
===============================================================
Sun Microsystems GmbH Helge Delfs
Nagelsweg 55 Quality Assurance Engineer
20097 Hamburg OOo Team Lead Automation
http://qa.openoffice.org mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
