Hi Vito,
if you have a good idea on how we might improve our localization testing please
do not hesitate to make suggestions.
But you must be aware that the test scripts have a long history - once designed
for exactly one language (German), the StarOffice brand only and iirc with only
a Writer and Calc application on OS/2 and Windows.
Since that time a lot has changed - more applications were added, the suite
became OpenSource and now ships in God knows how many brandings and languages -
and if that weren't enough - even on multiple platforms. I believe OOo is
probably one of the most challenging projects of this sort worldwide.
We've done our best to cope with the many changes and we are constantly trying
to simplify things without sacrificing functionality. However, no one managed to
turn up with the ultimate solution yet. So we do what we believe makes
localizing as simple as possible.
I just exchanged almost the entire extras/input/formats tree in favor for a
slightly simpler solution which generates the reference files automatically - i
can hardly imagine how to simplify on that. The logfile (.res-file) even prints
out the differences. If you are happy with the newer set of strings you just
have to copy the file from your local work directory over the old one and check
it into CVS. Sounds pretty simple to me.
From your post (below) i think you know all that.
If someone would turn up with a promising concept on how to handle versioning,
branding and all the other stuff involved we would be more than happy to discuss
it and try to implement it - if it is superior to the current solutions. But i
bet you'll find it pretty difficult to come up with "one size fits all" solution.
Best regards,
Joerg
Vito Smolej wrote:
"Have a look in the directory ../writer/tools..." - lieber Helge, you
can be sure I did that (can provide the res file as a proof;) before I
called in here..
The script is no big help - it just lists the localized expressions
which I should know by heart by now - after all it was me (with a few
other dogs), who dug these bones into the code. What the script does not
do, however, is create a (say) w_locale_strings_50.txt, that would be
used by all those 36 cases, where the code branches into different
locales. That is, a file like some older parts of the testtool system
use...
I am ready to help - no doubt - however I would probably be a nuisance
if I tried to dig into the code. Ill probably skip the writer tests
altogether - theres so much there that reminds me of tests in the
framework.Regards and please this is no critique, its just plain common
sense - my way. Ill probably bring up the subject on one of the IRC
meetings.
Vito
Helge Delfs wrote:
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 ;-)
--
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?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
