User: jpmcc Date: 2007-07-27 20:25:53+0000 Added: marketing/www/ooocon2007/programme/wednesday_abstracts.html marketing/www/ooocon2007/programme/images/abstract.gif
Log: Add abstracts File Changes: Directory: /marketing/www/ooocon2007/programme/ =============================================== File [added]: wednesday_abstracts.html Url: http://marketing.openoffice.org/source/browse/marketing/www/ooocon2007/programme/wednesday_abstracts.html?rev=1.1&content-type=text/vnd.viewcvs-markup Added lines: 719 ---------------- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <title>OpenOffice.org Conference 2007 - Abstracts - Wednesday</title> <!-- Include the common CSS stylesheet --> <link rel="stylesheet" type="text/css" href="../default.css" /> <link rel="stylesheet" type="text/css" href="programme.css" /> <style type="text/css"> .abstract .header { background-color: rgb(255, 240, 181); padding-left: 0.5em; } </style> </head> <body> <h2>Abstracts of Conference Papers - Wednesday</h2> <!-- This is the template for each abstract Note that the abstracts should be sequentially numbered g1, g2 ... etc You should also change the 'Back' link to point to the correct Conference day.. <div class="abstract" name="a1" id="a1"> <div class="header"> <p class="title">This is the title of the Abstract</p> <p class="by">Name of Author</p> </div> <div class="content"> <p>Abstract goes here</p> </div> <div class="bio"> <p><strong>Name of Author</strong>, Biography</p> </div> <p><a href="wednesday.html">Back</a></p> </div> --> <div class="abstract" name="a105" id="a105"> <div class="header"> <p class="title"> Contributing to OpenOffice.org </p> <p class="by"> Martin Hollmichel (Program Manager / Project Lead / Sun Microsystems, Inc. / tools.openoffice.org)</p> </div> <div class="content"> <p><i>Abstract:</i> The session will introduce on how to contribute to OpenOffice.org and how the OpenOffice.org Development process work. There are many different way on how to contribute to the project, we will look on different aspects: code/patch contributions, legal aspects access to resources of the Projects (Website, Issue Tracker, etc) CVS access and branches, Tinderboxes, build-bots The OpenOffice.org development process differs in several aspects from usual Open Source habits of other projects. The session will explain the OpenOffice.org development style. In detail we will have a look onto different roles of contributors, especially at the of core-developers, UserExperience, QA folks and add-on-developers. </p> </div> <div class="bio"> <p><i>Biography:</i> Working on OpenOffice.org and its predecessor StarOffice since 1994 and working as release manager for OpenOffice.org now. Since 2003 member of the OpenOffice.org community council. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a178" id="a178"> <div class="header"> <p class="title"> State of the Project </p> <p class="by"> Louis Suarez-Potts (Community Lead / OpenOffice.org)</p> </div> <div class="content"> <p><i>Abstract:</i> An account of the state of the OOo project. </p> </div> <div class="bio"> <p><i>Biography:</i> Louis is the Community Manager of OpenOffice.org, a role he has held for the last seven years. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a71" id="a71"> <div class="header"> <p class="title"> Marketing ODF to the OpenOffice.org project </p> <p class="by"> Charles-H. Schulz (Lead of the Native-Language Confederation / Ars Aperta / Native-Language Confederation)</p> </div> <div class="content"> <p><i>Abstract:</i> This session is aimed at explaining and discovering the benefits of ODF for the OpenOffice.org community. The community itself is pretty much unaware of ODF, its importance to the worldwide communities, because ODF and Open Standards were never explained to them in "their own words" and in a way the reality of open standards can be expressed clearly to them. This session will thus attempt to integrate arguments and facts about ODF inside the framework of native-language projects, marketing project, etc. </p> </div> <div class="bio"> <p><i>Biography:</i> Charles-H. Schulz, graduated in the ISEG Paris, has a Master of International Trade and Negociation, Ars Aperta co-founder. He worked in many FLOSS companies including Mandriva and Novell. He is the lead of the Native-Lang Confederation of Openoffice.org. He works at fostering the international development of this successful project. He is in charge of the worldwide coordination of the communities of users, developers and documentation teams of the OpenOffice.org project. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a108" id="a108"> <div class="header"> <p class="title"> On-Site Requirements Engineering for OpenOffice.org - A Practical Approach </p> <p class="by"> Matthias Müller-Prove, Christian Jansen, Sabine Özalp, Ronald Hartwig, Maren Mäuselein (User Experience Engineer / Co-Lead of the User Experience Project / Sun Microsystems / User Experience Project)</p> </div> <div class="content"> <p><i>Abstract:</i> The user experience project (ux.openoffice.org) started in January 2007 with the intention to improve the usefulness and usability of OpenOffice.org for our users. Therefore we need to learn and understand how OpenOffice.org is actually used. We took the opportunity to meet with employees of VBG (a large accident insurance company in Germany which migrated to Linux and OpenOffice.org) and conducted several workshops to gain unfiltered insights into real life working contexts. The requirements engineering was done using a synergy effect with a parallel usability project between VBG and UID, in which more than 200 on-site interviews were done and served as initial input for our research. </p> </div> <div class="bio"> <p><i>Biography:</i> Matthias Müller-Prove played a significant role in designing the user interface of the web editor Adobe GoLive before he joined Sun Microsystems to work on OpenOffice.org in 2002. He is now co-lead of the OpenOffice.org User Experience Project. Matthias holds a BSc. and diploma in Computer Science from the University of Hamburg with special focus on human-computer interaction and the history of hypertext and graphical user interfaces. Christian Jansen is a User Experience Engineer of the StarOffice User Experience team at Sun Microsystems. During the last 8 years, he played a major role in specifying the graphical user interface of OpenOffice.org. He holds a degree in Communication Design from the 'Hamburger Akademie für Kommunikationsdesign und Art Direction' (Hamburg Academy for Communication Design and Art Direction) Dr. Ronald Hartwig works in the area of Usability Engineering for more than 10 years. He never encountered an ideal project with respect to usability engineering. But his flexible attitude and the ability for pragmatic decisions let him contribute to the success of the projects. As Manager Consulting & Training at UID it is his mission to bridge the gap between theory and reality. Maren Mäuselein works as Usability Consultant at User Interface Design GmbH. She holds a Diploma in Media Science with a focus on Media Informatics. Maren has studied at the University of Paderborn, Germany and Jönköping International Business School, Sweden. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a26" id="a26"> <div class="header"> <p class="title"> How to fix an issue in OpenOffice.org </p> <p class="by"> Michel Loiseleur (Open Source Software Engineer / Linagora)</p> </div> <div class="content"> <p><i>Abstract:</i> When you take the source of OpenOffice, you discover the pleasure of 200 modules dispatched for a total of 1 billions of bytes of plain text of source code, sometimes commented in german. This session will teach you how to get into OpenOffice pragmatically and efficiently, in order to fix a precise issue. You will learn how to find quickly the source code directly attached to a particular functionality and how to use efficiently the majority of APIs. The session will be supported by full and concrete examples. </p> </div> <div class="bio"> <p><i>Biography:</i> A small contributor who find its way in the source code. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a76" id="a76"> <div class="header"> <p class="title"> Across the Great Wall </p> <p class="by"> Peter Junge (Program Manager, QA Developer / Beijing Redflag Chinese 2000 Software Co., Ltd.)</p> </div> <div class="content"> <p><i>Abstract:</i> This session should be basically a case study about my current job, integrating my employer, Chinese company 'Beijing Redflag CH2000', into the OOo community. The term 'Great Wall' should not only be a synonym for China, but also for other barriers as language and differently approaching communication. I want to show pitfalls and lessons learned to easy the integration of upcoming contributers from different cultures. </p> </div> <div class="bio"> <p><i>Biography:</i> Born 1963 Diplom-Geophysiker (Master of Geophysics) 2000 - 2006 Employee of Sun Microsystems, QA Engineer StarOffice/OpenOffice.org development Since 2006 Employee of Beijing Redflag Chinese 2000 Software Co., Ltd., Program Manager and Senior Engineer Open Source Technology Department </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a147" id="a147"> <div class="header"> <p class="title"> ODF Interoperability </p> <p class="by"> Robert Weir (Software Architect / IBM)</p> </div> <div class="content"> <p><i>Abstract:</i> We'll look at interoperability from several angles, with an emphasis on OpenOffice.org and how its output can be interchanged with other applications. We'll look at what works well, what doesn't, and what we need to do to improve interoperability. </p> </div> <div class="bio"> <p><i>Biography:</i> Born, 1969. Not dead yet, 2007. Member of various standards committees related to ODF, including the OASIS ODF TC, the ODF Adoption TC, the ODF Metadata Subcommittee, the ODF Formula Subcommittee, INCITS V1 (JTC1/SC34 mirror committee in the US). </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a133" id="a133"> <div class="header"> <p class="title"> ODF in Russia. Status, problems and future trends. </p> <p class="by"> Rail Aliev (CTO / Russian and Turkish Native Language Project co-lead, Technical Coordinator of Eurasia Native Language Confederation / Infra-Resource)</p> </div> <div class="content"> <p><i>Abstract:</i> This talk will be based on the analytic report made for Ministry for Economic Development and Trade of the Russian Federation. It will cover the following aspects: - analysis of international experience of ODF migration - analysis of known and possible migration problems - pilot project results (public and federal objects in of the regions of the Russian Federation) - ODF migration results of one of the departments of Ministry for Economic Development and Trade of the Russian Federation </p> </div> <div class="bio"> <p><i>Biography:</i> Born (1975) in Ukraine, graduated from Business Management Faculty of Istanbul University (Turkey), moved to Moscow (Russia) in 1999. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a106" id="a106"> <div class="header"> <p class="title"> Improving the modularity of OpenOffice.org </p> <p class="by"> Mathias Bauer (OOo Project Lead Word Processing, CoLead Application Framework / Sun Microsystem Inc. )</p> </div> <div class="content"> <p><i>Abstract:</i> I will try to explain the different meanings and aspects of "modularity", how we can describe them and how good they are implemented in OpenOffice.org. I will give an overview of what we have done already to improve modularity, what we are currently doing and where we are aiming at. </p> </div> <div class="bio"> <p><i>Biography:</i> I work on OpenOffice.org and StarOffice since 1995. In the past I mainly worked on the application framework, but in the past years also on programmability and API. Since November 2006 I'm the Project Lead of the OOo "word processing" project. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a54" id="a54"> <div class="header"> <p class="title"> Case Study: OpenOffice.org Guerrilla Advertising in the New York Metro Newspaper </p> <p class="by"> Benjamin Horst (Marketing Volunteer / Freelance)</p> </div> <div class="content"> <p><i>Abstract:</i> In the summer of 2006, I emulated the Firefox advertising campaign in a major NYC publication. Raising donations online and working with the Metro newspaper, we created a back page ad promoting OOo to New York City readers. Small projects like this can be replicated around the world, with little central coordination, to raise brand awareness and usage of OpenOffice.org. We maintained a project website and archive at (an excerpt follows): http://homepage.mac.com/bhorst/ Following the trail blazed by Firefox, we posted an advertisement for OpenOffice.org in the free daily newspaper "Metro" in New York City. We qualified for non-profit prices and therefore got a lot of bang for the buck. Each weekday, 330,000 free copies of Metro are distributed to commuters in the five boroughs. Roughly 450,000 people read it, and they represent a young, affluent and savvy demographic. 1. Discussion is carried out in the OpenOffice Ads Action Google Group. 2. Collection was completed successfully, and the ad ran on Monday, July 31, 2006. You can download a PDF of the Metro issue, and see the ad on the back page. (Click on July 31 in the calendar, then press the "Get Your Metro" button, and it'll download for you.) 3. You can still donate directly to OpenOffice.org. </p> </div> <div class="bio"> <p><i>Biography:</i> Horst is a 1999 graduate of Vassar College, with a BA in Geography. He received his Master in Urban Planning from Harvard University Graduate School of Design in 2001, and now lives in New York City, working in the field of internet startups. Horst has spoken about OpenOffice.org, open source software and Free Culture on a number of occasions: * Vassar College Media Cloisters  ÂGaming and Virtual Words Panel * Comdex 2003 * University of Southern California Linux User Group * National Hispanic WomenÂs Leadership Conference * Vassar College Media Cloisters  ÂFree Culture and the University * Free Culture National Summit 2006 at Swarthmore College * Westchester (NY) PC Users Group Complete CV available here: http://www.solidoffice.com/about/benjamin-horst-cv/ </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a83" id="a83"> <div class="header"> <p class="title"> Chinese Office Software Standards UOF and Inter-operation of OpenOffice.org ODF </p> <p class="by"> Xiuzhi Cheng (ESC member / Beijing RedFlag Chinese2000 Software Co. Ltd.)</p> </div> <div class="content"> <p><i>Abstract:</i> UOF which stands for Unified Document Format is the proposed document format of Chinese office software. XML-based Chinese Office Software Document Format Working Group was set up by China National IT Standardization Technical Committee in 2002. It consists of 4 parts£¬they are UOF document format£¬UOF storage format£¬Application program Interface (API)and User interface of Chinese office software¡£The converter between UOF and ODF had been embeded into Openoffice.org now and will be submitted to OpenOffice.org by RedFlag Ch2000 Company.We will introduce the history , features and structure of UOF as well as the inter-operation between UOF and ODF. </p> </div> <div class="bio"> <p><i>Biography:</i> I have experience on OpenOffice.org for more than five years and major on UOF and ODF for more than three years. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a101" id="a101"> <div class="header"> <p class="title"> Redoffice ¨C Creating a More Friendly Operating Style and Using Experience </p> <p class="by"> ShaoLiang Yang (Director of Product Dept. / Beijing Redflag Chinese 2000 Software Technology CO.,LTD)</p> </div> <div class="content"> <p><i>Abstract:</i> Redoffice, with the foundation of OpenOffice, is a commercial Office Suite from China. It is authored with a sensation of toppling over the tradition and pursuing higher level of ideal. With the innovative user interface, more object-oriented templates and ClipArt resources, the user is encouraged to get more involved with the product design and interaction. Armed with the tight connection with Internet, Redoffice is capable of real-time update and instant version renewal. Redoffice will make full use of the excellent technical architecture and powerful community force of OpenOffice to explore and improve the end-user¡¯s operating experience, extending the Internet-based service mode to attract more and more users to join in. </p> </div> <div class="bio"> <p><i>Biography:</i> 2000Ä꿪ʼ´ÓÊÂOpenOfficeµÄÑо¿£¬¸ºÔðRedOfficeµÄ²úÆ·¹æ»®ºÍÉè¼Æ¹¤×÷¡£ Embarking on the research of OpenOffice since year 2001 and currently being responsible for the product planning and architechture design of RedOffice. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a138" id="a138"> <div class="header"> <p class="title"> Split OOo into smaller pieces </p> <p class="by"> Petr Mládek (Package maintainer / Novell, Inc)</p> </div> <div class="content"> <p><i>Abstract:</i> OpenOffice.org is huge piece of software and this brings lots problems to both developers and users. Developers need to create the whole build tree even if they want to fix a simple bug. The users are often forced to download the whole installation set or all packages to get this fix. I will discuss possible solutions for splitting OpenOffice.org. I will compare them with the other huge projects, such as GNOME, KDE, X.Org. I will show how it could help both developers and customers and what problems might appear. In the end I will summarize what has already been done in this area, what are the plans and schedules. </p> </div> <div class="bio"> <p><i>Biography:</i> Petr Mládek, 31, has been working for SUSE Linux as the package maintainer since March 2001. He started to work on the OpenOffice.org package in spring 2002. He has been member of the OpenOffice.org security team since June 2006. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a79" id="a79"> <div class="header"> <p class="title"> Political struggles in Denmark - My experiences </p> <p class="by"> Leif Lodahl (Language coordinator in Denmark / )</p> </div> <div class="content"> <p><i>Abstract:</i> Presentation of my experiences in the democratical process in Denmark moving towards the use of open standards in the public sector. How to talk to members of the Parliament, journalists and public servants. Latest news and progress. </p> </div> <div class="bio"> <p><i>Biography:</i> I has been working as project manager, consultant and instructor at Symfoni Software Denmark for seven years. The company is IBM Business Partner and I work in the Lotus Notes department. I started working with OpenOffice.org as volounteer about five years ago. First translation of OOo 2.0 and then as coordinator for translation of the written manuals. Since March this year I have been the LangCoord in Denmark. I am 42 years old, married and with two boys aged 12 and 14. I live some 10 kilometers noth of Copenhagen, Denmark. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a25" id="a25"> <div class="header"> <p class="title"> Integrating OpenOffice.org with Web Content Management Systems </p> <p class="by"> Bård Farstad (Co-Founder & V.P. Business Development / eZ Systems)</p> </div> <div class="content"> <p><i>Abstract:</i> While the OpenOffice.org Writer application provides a simple yet powerful writing environment, the underlying OpenDocument XML format (ODF) in which the documents are stored provides opportunities for document portability, reuse and integration with other systems and workflows. By supporting integration with the ODF format, the eZ Publish content management system (CMS) enables collaborative document production, simple website updates and multi-channel publishing (including XHTML, RDF and PDF). This talk will describe the eZ Publish ODF import / export extension, demonstrate how the OpenOffice.org Writer application can be used to generate standards-compliant website content, and show some cool tips and tricks (such as how to migrate from Microsoft Word documents to ODF automagically by using OpenOffice.org macro support in a CMS application). </p> </div> <div class="bio"> <p><i>Biography:</i> Bård Farstad is one of the co-founders of eZ systems, the software company behind the Open Source Enterprise CMS system eZ publish. He has been working professionally with Open Source since 1999 and is currently living in Porsgrunn, Norway. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a17" id="a17"> <div class="header"> <p class="title"> Automating a Production Publishing System </p> <p class="by"> Jonathan Eunice (Founder and Principal IT Advisor / Illuminata, Inc.)</p> </div> <div class="content"> <p><i>Abstract:</i> Illuminata is a small IT advisory firm with a long-standing publishing business. Over the past several years, we have shifted from FrameMaker to OpenOffice.org as the basis for our publishing process, substantially increasing the degree of automation in the process. This case study talk will describe how we did it, and explain many lessons learned along the way. </p> </div> <div class="bio"> <p><i>Biography:</i> Jonathan Eunice is a prominent information technology analyst. He has advised Global 2000 businesses and government agencies on IT strategies for nearly twenty years. In this time he has authored hundreds of publications and client inquiry responses on a broad range of IT topics, including system and software architectures, operating environments, and development tools. He is also the principal author and caretaker of Illuminata's backend publishing systems. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a158" id="a158"> <div class="header"> <p class="title"> Aqua OpenOffice.org : the Light </p> <p class="by"> Eric Bachard (Porting project Co Lead / Mac OS X Lead / Porting project)</p> </div> <div class="content"> <p><i>Abstract:</i> 3rd part of Native Mac OS X port of OpenOffice.org In this presentation, the status of native Mac OS X port of OpenOffice.org will be presented : - evolution since last year - description of the technical points solved/ remaining - live presentation of the Aqua version (work in progress) - Objectives / work in progress and future of Mac OS X port </p> </div> <div class="bio"> <p><i>Biography:</i> Professor of Applied Physics at University of Technology of Belfort Montbeliard ( UTBM , http://www.utbm.fr ) 43, married, 2 children,French </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a165" id="a165"> <div class="header"> <p class="title"> The price is high! Is it too high? </p> <p class="by"> Juergen Schmidt (Software Engineer / Sun Microsystems)</p> </div> <div class="content"> <p><i>Abstract:</i> When we have decided to keep the UNO (the C++ and Java runtime) and the office API compatible, we were probably not really aware of the long term influence on our daily development work and especially the quality and the usability of the API. The experiences of the last years have shown that is impossible to design perfect API's in the first shot. Well we have introduced some help mechanism like the Âpublished keyword to mark API's as potential candidates for changes. But even with this mechanism the compatibility statement is a huge burden. The price is high and the costs are on the side of the project. The question is if the price is maybe to high and if this compatibility statement prevent us to be flexible enough in the future. This session should try to answer this question or at least should inspire to think about it. Potential ways for the future should be analyzed in consideration of costs for our customers and our developers on one side and innovation and better, simpler and more intuitive programmability features on the other side. </p> </div> <div class="bio"> <p><i>Biography:</i> Juergen Schmidt is working for Sun Microsystems in the StarOffice group for 10 years. He was deeply involved in the development of the UNO component model which is the foundation for the OpenOffice.org/StarOffice API. The OpenOffice.org community is one aspect of his daily work. He is involved in the OpenOffice.org project since the beginning, he is the project lead of the OpenOffice.org API project and the co-lead of the Extensions and ODF Toolkit project. His main goal is to spread the knowledge around the programmability features of OpenOffice.org around the world and to show that it is more than only an office productivity suite. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a182" id="a182"> <div class="header"> <p class="title"> Who is using OpenOffice.org </p> <p class="by"> Erwin Tenhumberg (Open Source Group / Sun Microsystems)</p> </div> <div class="content"> <p><i>Abstract:</i> In this BoF the latest OpenOffice.org user survey data will be presented and discussed. </p> </div> <div class="bio"> <p><i>Biography:</i> Erwin Tenhumberg is a member of the Open Source Group at Sun Microsystems which is led by Sun's Chief Open Source Officer Simon Phipps. Among his roles and responsibilities are community development, marketing and evangelism for OpenOffice.org. In addition, Erwin Tenhumberg focuses on open source business models and open source in the public sector. Besides his role in the Open Source Group, Erwin is also co-chairing the OASIS OpenDocument Format (ODF) Adoption TC (Technical Committee). </p> </div> <p><a href="wednesday.html">Back</a></p> </div> <div class="abstract" name="a30" id="a30"> <div class="header"> <p class="title"> Releasing OpenOffice.org: translation and QA process </p> <p class="by"> Rafaella Braconi and Joost Andrae (Rafaella: project lead (l10n), Joost: project co-lead (QA) / Sun Microsystems)</p> </div> <div class="content"> <p><i>Abstract:</i> This informal presentation aims at giving an overview of the major steps that need to be performed to release a native version of OpenOffice.org. Well established processes are the baseline used to provide clearer instructions on what is really important to do in order to make sure that the translated product gets also distributed. A discussion about technical experiences gathered from the last releases especially by native language communities is welcome. </p> </div> <div class="bio"> <p><i>Biography:</i> Joost: Working for StarDivision/Sun Microsystems since 12.5 years now Joost is nowerdays working as StarOffice / OpenOffice.org Program Manager within the StarOffice development team in Hamburg. As a co-lead of the OpenOffice.org QA project he helps to coordinate all activities and additionally tests (QA), releases, announces and uploads OpenOffice.org builds to the mirror network. Rafaella: As Globalization Program Manager at Sun Microsystems, Inc., Rafaella Braconi is responsible for delivering localized quality products back to Sun to internal customers. She counts a 9 year experience at Sun Microsystems in the field of localization. She was previously acting as Translation Manager of the StarOffice Translation Department and worked in the Translation and Language Information Services (TLIS) and had a key role in designing and setting up an internal linguistic quality assurance process among others. </p> </div> <p><a href="wednesday.html">Back</a></p> </div> </body> </html> Directory: /marketing/www/ooocon2007/programme/images/ ====================================================== File [added]: abstract.gif Url: http://marketing.openoffice.org/source/browse/marketing/www/ooocon2007/programme/images/abstract.gif?rev=1.1&content-type=text/vnd.viewcvs-markup --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
