Hi Jeongkyu, It seems your access right has been changed from MGR to SQA since the time I granted access to you. :-) We had given MGR rights to N-L community leads for the languages covered in the pilot process (http://l10n.openoffice.org/localization/L10n_pilotprocess.html).
As you might have seen in the http://l10n.openoffice.org/files/documents/9/2791/About_TCM.html MGR can grant TCM access to other community members and change test cases (including translating or updating them). Let me get back to you on this. greetings! Young Jeongkyu Kim wrote: > On 7/22/05, Andre Schnabel <[EMAIL PROTECTED]> wrote: > >>Hi, >> >> >>There actually is a way to download all texts, translate them offline >>and upload them again. It's some kind of plain text with tags for the >>case ID's. >>This was very easy to handle, if you had SQE privilegues. So I hope, >>those could be granted to you. > > > > I'll try to get the privileges. > > >>The general point of suggestion is about how much effective it is to test >> >>>localized software without localized test case. While I've been working >> >>on >> >>>translation, I've had to spent a while to figure out menus and options in >>>Korean version from the test cases. It does not make sense to ask every >>>testers to do the same thing. They may skip the test case if it is not >> >>easy >> >>>to figure out. I believe Sun should include the suggestion as policy of >>>their localized testing, at least with outside tester. >>> >>> >> >>I can only tell, what we (germanophone tem members) have done so far: >>- we did an initial translation of the test cases .. that means "only" >>translation, not localization in all cases >>- during the first tests, translation was reviewed, to mak test cases >>more easy to understand and to correct some mistakes that affect >>localization (e.g. in german environment you don't jump through words by >>pressing <ctrl>+<up> / <ctrl>+<down>) >> >>This could (more or less) easily be done, as almost all of our testers >>have SQE privileques. So anybody who sees a problem can change the >>translation. .. that's like open source projects should work. > > > > > Your way seems to be what Korean community has to follow. Actually, upcoming > TCM testing is the first one which Korean community members participate in. > I'd like to make use of this chance with community members to take more > control over Sun's TCM testing. > > >>.... >> >>>I meant the comments about tests that have been done. For example, there >> >>is >> >>>a test case about forbidden rule in Asian layout. I didn't know about the >>>details of the rule at all before I need to translate the case. It is >> >>kind >> >>>of professional knowledge about word processor. I just thought it would >> >>be >> >>>good if such a information can be shared within TCM. :-) >>> >>> >> >>Wel .. this should rather be discussed via Mail. TCM is used by testers, >>not by typographic experts .. so it is not of much use to keep the >>comments within TCM ;-) >>BTW: I've been the one to came across the same problem, when translating >>to german (but as this rule does not exist for european languages, my >>only comment is that we don't need to test this in a german localization) > > > > I thought sharing comments would be one of the ways to achieve the shape you > mentioned above. The test case about forbidden rule just states 'insert a > native language punctuation...'. It took a while for me to figure out what > is exactly forbidden punctuations for Korean document (They can be found in > one of the option dialogs). And I thought such kind of information should be > shared between testers. Now, I understand SQE + dedicated mailing list (or > forum) would be better way. > > Actually, when Sun introduce TCM to community, Young Song sent me a mail > with test TCM account. I regret I couldn't have a chance to play with it, > but better late than never. I will do my best to make it better for future > testing. :-) > > Thank you very much for your kind reply. > > Jeongkyu > -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
