Hi Hong, 1. In the Office however, we talk about "input and output Filters". Because the Office Works with ODF as a file-format. But if you want to save your file in a Microsoft-format, you will have to use a filter to save the information in the right way for the file to be readable by a Microsoft Office.
With other words, when you open a file, a Filter is used to read / translate the data into the Office. And when you save the file, a Filter is also used to save it into the type of file you want to save. (ODF, PDF, DOC, PPT, XML, HTML etc) 2. For Automatic Testers, this is important when we want to test if the office loads and saves the files as it should (with the right filter). The problem with Filternames, is that they are called different things in different languages, and the OpenOffice.org -filters all starts with "OpenOffice.org 3.0" while the StarSuite -filters all start with "StarSuite" etc. Since DEV300 the Filternames are retrieved from the API automatically. ( http://blogs.sun.com/GullFOSS/entry/qa_automation_filter_names_for ) So you don't have to bother with those. However, you might have to create the OLE Object names manually. Best wishes / Fredrik zhang Hong wrote: > Hi Fredrik, > > Thank you for your answer :-) > > I think I don't understand filter well, could you give some information about > it? > 1. what is filter? > 2. what is the role of filter in automation testing? > > Best Wishes > Zhang Hong > > > > Zhang Hong > Beijing Redflag Chinese 2000 Software CO.,LTD > Email:[EMAIL PROTECTED] > 2008-04-18 > > > > 发件人： Fredrik Haegg > 发送时间： 2008-04-17 23:11:13 > 收件人： [email protected] > 抄送： > 主题： Re: [qa-dev] [Automation]Filters > > zhang Hong wrote: >> Hi all, >> >> Who can tell me some details about filters in Testtool? >> If I want to add RedOffice (our product) into the filterlist, are the >> following steps right? >> >> 1.Running "qa\qatesttool\global\tools\getnames.bas" based on RedOffice; >> 2.Adding ole_86.txt (created in first step) into the directory >> "\global\input\olenames\" + gProductName >> I think gProductName = RedOffice, But I don't know where and how to add >> "gProductName" in scripts? > > > Could be very difficult. > > What you have written is right, but it might just be the first you need > to do. > > As far as I've found myself, there is a file under global/system/inc/ > called "iniinfo.inc". > In it you'll find the function "getSofficeNative". > This is one of the places where you'll find lines like these: > > sOffice(iOfficeEntries) = "StarOffice" : inc (iOfficeEntries) > sOffice(iOfficeEntries) = "StarSuite" : inc (iOfficeEntries) > sOffice(iOfficeEntries) = "OpenOffice.org": inc (iOfficeEntries) > > and adding the line > sOffice(iOfficeEntries) = "RedOffice" : inc (iOfficeEntries) > > should get you a bit closer to your goal. But you will have to search > for "OpenOffice.org", "StarOffice" and "StarSuite" to see if you > find any more lines like that. > > > Best wishes > / Fredrik > > > >> Thank you very much! >> >> Best Regards >> Zhang Hong >> >> >> >> >> Zhang Hong >> Beijing Redflag Chinese 2000 Software CO.,LTD >> Email:[EMAIL PROTECTED] >> 2008-04-17 >> > > -- Sun Microsystems GmbH Fredrik Haegg Nagelsweg 55 Software 20097 Hamburg Phone: +49 (0)40 23646 634 Germany Fax: +49 (0)40 23646 650 http://www.sun.de mailto:[EMAIL PROTECTED] Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer Vorsitzender des Aufsichtsrates: Martin Haering --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
