Re: [qa-dev] No TCM update data?

[Clytie Siddall]

Hi everyone :)




I'll answer this thread altogether. I hope that's OK.

On 04/01/2007, at 6:22 PM, André Schnabel wrote:

I'm very sorry I haven't been able to respond to your mails sooner. Things have been happening, including a hurricane. A stimulating start to the year.

Clytie Siddall schrieb:

So, if anyone here would be willing to run testtool for my build on Linux or Windows, or if you know someone who would do it, the help would be very much appreciated. :) I think my community is just sitting back and expecting the project to fail again. I would really like to prove them wrong.

Please send the exact URL of the builds to test ;-)

André, thankyou for offering to help.

Shaun replied:

Please the last line on the Vietnamese row of
http://www.qatrack.org/ooo/view.php

Thanks for answering that, Shaun. Yes, those are our builds awaiting QA.

André then answered my original post in further detail:

Clytie Siddall schrieb:

I'm still trying to find someone who will run testtool on Windows or Linux for my build.

Started for Linux/rpm (I think I can start tests for Windows later today).

Great! :D

but please be aware, that I don't have Vietnamese environment (and I have no idea how a Vietnamese Office Suite should look like).

I only can see, that I have no Vietnamese fonts installed.

Yes, I understand that. But we have had plenty of anecdotal testing: we know in general how OpenOffice.org Việt behaves on Windows (and Linux). testtool will supply systematic details.

....

So at least some manual testing should be done (by native Vietnamese users).

Absolutely. The more, the merrier. ;)

Your testing will be a great help. Nam (previous project lead) has agreed to run testtool on Windows XP, if I would provide translated instructions. I appreciate his offer very much. I only hope my translation of Maho's instructions is useful to him.

I know I am not the only person who has found this release difficult, protracted and especially hard to handle if you are new to the project. I do not give up easily: I am far too stubborn to have enough sense to see when I'm beaten. But I have even considered giving up on OpenOffice.org. It's just too much work for too little results to my community.

I know this situation :-( But is it really better to skip the tests and hope "someone else" will find the errors? Just an example, why we propagate the idee to test each binary that will be officially released: Mozilla had to remove full installation packs for FireFox 2.0.0.1 Windows and Linux , German Localization. If you install this package, your local profile will be write protected (causing several problems). This does not happen on other localizations, not on Max OS X and not if you use the update. Now ... OOo is far more complex than FF and therefore needs even more testing :-(

Thorsten then said:

I agree with you. I haven't given up. I was getting very discouraged when I wrote the original email. I was overloaded, getting nowhere and generally feeling sorry for myself. So, in between natural disasters and other demands, I spent some time working on my translations for other projects. I needed to remind myself why I'm here. So now I'm back and ready to keep trying. :)

as Andre wrote some mails ago, here are the release process and the
testing of a localized build are mixed up.

Yes, especially when you have to do both at once.

and localization testing) on a new language. And in the same way you
want to release that version. This isn't possible in a timeframe for
a release testing cycle. The testing of a new language takes much more
time.

As I could read out of your mails you want to make testing (translation

Yes, indeed. I'm fortunate that our project has actually been around for several years, so I didn't have to create a new project, and there have been plenty of unofficial builds of our translations, getting used and discussed. But there was a lot left to do, to achieve an official release, an important goal for our community in promoting free software and empowerment through access to technology.

And what should be the result of such a release? If the translated
version is build first the qa team (perhaps only one person) will find

released with 10, 20 or 100 of such errors? Nobody can answer these

many localization bugs.

many bugs in translation, localization and other things. So could it be questions. So first testing (will take some weeks/months) has to be done and after that the the major issues have to be fixed. And then the language builds can be release in perhaps the next version without major issues problem. On the other hand, the TestTool scripts have to be adapted for each new language. If this isn't done, the tests will throw

Oh, yes... ;)

So why not make testing on OOo2.1 builds, report and/or fix all major

(check fixed issues and make a sanity check) of OOo2.2? The release
schedule is End of February.

translation issues until end of January and make a small release testing

At this stage, I'll be lucky if I have time to submit a translation at all for 2.2. But I hope to do so. Translations for OpenOffice.org 2.2 have to be submitted by January 18th !

As a new member of QA on OOo, your feedback on broken or difficult

processes and bad information on the web sites or anything else is still needed, useful and welcome. So do not stop posting it.

Thanks for your encouragement, Thorsten. :)

André reported:

first and topten tests are ok on Linux.

Yay!

Testtool reports errors for the Filter Names in File Open dialoges, it doesn't know the translated names. But this would not affect regular users.

Maybe someone can give a hint how to teach testtool the vietnames filter names?

I will do the work if someone can tell me how.

Clytie: do you have an issue or any other place where I could leave my results?

"VI: track QA for 2.1" (thanks to Shaun earlier on)

http://www.openoffice.org/issues/show_bug.cgi?id=72816

André added:

Same results on Windows: first and topten tests are fine (except the filter names).

Good. :)

But the windows Installer (NSIS-wrapper) is not fully localized. E.g. some of the Buttons (like "< Back") are not translated.

http://groups-beta.google.com/group/vi-VN



http://www.openoffice.org/issues/show_bug.cgi?id=72905
http://www.openoffice.org/issues/show_bug.cgi?id=73103
http://www.openoffice.org/issues/show_bug.cgi?id=73192

This is a known bug [1], which we think we may have fixed. Hopefully, Pavel can build the fix soon. I won't release until it's fixed, since it's already caused users to give up on trying the program. :( I appreciate your help very much. I would like to update qatrack to show our progress in testing. André, which Linux build are you testing? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) [1] NSIS does not support Unicode. This problem has been reported for a long time, affecting many languages and a great deal of translated material, but NSIS developers aren't doing anything about it. However, due to the expertise here at OpenOffice.org, we have an interim fix, using decomposed Unicode and legacy encodings:

PGP.sig
Description: This is a digitally signed message part