| <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" |
| "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta content="text/html; charset=us-ascii" http-equiv="content-type" /> |
| <link rel="stylesheet" type="text/css" href="schedule.css" /> |
| <style type="text/css"> |
| /*<![CDATA[*/ |
| .abstract .header { |
| background-color: rgb(255, 240, 181); |
| padding-left: 0.5em; |
| } |
| /*]]>*/ |
| </style> |
| |
| <title>General streams</title> |
| </head> |
| |
| <body> |
| <h2>Abstracts of Conference Papers - General Streams</h2> |
| |
| <div class="abstract" name="g1" id="g1"> |
| <div class="header"> |
| <p class="title">VBA Interoperability & OpenOffice.org</p> |
| <p class="by">Noel Power</p> |
| </div> |
| <div class="content"> |
| <p>1.The Why: Describe the macro import problem, the need for a solution and the |
| potential wins in terms of Openoffice adoption.</p> |
| |
| <p>2.The How: Describe the origins of the incubator project, description of |
| architecture of the solution, the type of problems encountered and what we are |
| doing and what we have to do to solve them.</p> |
| |
| <p>3.The Present: Describe where we are at right now in terms of upstreaming |
| (hooks already integrated into upstream basic etc ), object Model, the approach |
| we are taking, what works right now.</p> |
| |
| <p>4.The Future: Describe whats next, the main areas that don't work, |
| whats required, why it is necessary to integrate the object model and more |
| basic enhancements upstream.</p> |
| |
| <p>Demo: Show some cool demos that demonstrate import of Excel macros</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Noel Power</strong>, Working as part of Novell's Openoffice |
| developement team. Responsible for improving VBA interoperability by enabling |
| Excel macros to run natively within Openoffice. Prior to joining Novell worked |
| as a Software developer with Sun, Lucent Technologies, Iona, Siemens, IBM, |
| Hewlett Packard & Motorola.</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g2" id="g2"> |
| <div class="header"> |
| <p class="title">Using OpenOffice.org as a redaction tool for office automation document</> |
| <p class="by">Garnett Yeatts & Boyd Fletcher</p> |
| </div> |
| |
| <div class="content"> |
| <p>The United States Joint Forces Command, USJFCOM, has developed an application |
| that leverages the Open Office technologies to assist in the redaction of office |
| automation documents. Redaction is the process of securely cleansing (or preparing) |
| a document for release and sharing. The solution also provides an automated (batch) |
| mechanism to convert MS Office to ODF and redact them. The redacted documents can be |
| stored in MS Office format, ODF, or PDF.</p> |
| |
| <p>Secure Save allows users to continue to use familiar tools while allowing an |
| organization to protect itself from external compromise due to malicious executable |
| code and from accidental release (leakage) of information due to unseen information |
| in documents. The Secure Save application can operate as either a OOo plugin for |
| individual document processing or as a standalone Java application for batching |
| processing. The secure save redaction options are controlled via site specific policy |
| configuration files.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Garnett Yeatts</strong> has thirteen years of experience developing and fielding custom |
| software systems. He holds a Bachelor's Degree in Computer Science from James Madison |
| University and a Master's Degree in Business Administration from Regis University.</p> |
| |
| <p><strong>Boyd Fletcher</strong> started his career in IT in the banking industry in 1986 and |
| graduated in 1993 from Old Dominion University with Bachelors in Computer Science. |
| He has spend most of the last 13 years working for the Department of Defense as a |
| software developer and systems engineer. First as a contractor with a variety of companies |
| and now as a civil servant with the Dept of Navys Space and Naval Warfare Command. As |
| deputy chief engineer at the United States Joint Forces Command Joint Experimentation |
| Directorate Joint Prototype Pathways Prototype Engineering branch, Boyd is responsible |
| for software architecture design</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g3" id="g3"> |
| |
| <div class="header"> |
| <p class="title">Mac OS X porting : the Next Step</p> |
| <p class="by">Eric Bachard</p> |
| </div> |
| |
| <div class="content"> |
| <p>As starting point, a brief description of last year objectives, will be completed |
| with current status.</p> |
| |
| <p>Negative points: visibility, native port speed, Apple changes, API knowledge. |
| Events how caused problems will be analysed in this part.</p> |
| |
| <p>Positive points: changes, vcl documentation writing. Progress made since last year |
| will be described in this part.</p> |
| |
| <p>Development: native port ( objectives, what is done, timeline, roadmap) Some more |
| “code oriented ” parts will be described in this part, including (if possible), |
| a running demonstration of changes.</p> |
| |
| <p>Propositions for improve Mac OS X porting project: a short analysis will present |
| what is needed to make the project do progress in "runtime" in resources management</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Eric Bachard</strong>, contributor since 2003, is Professor of applied physics |
| in Belfort Montbeliard University of Technology, contributes as co-lead for porting project |
| in OpenOffice.org porting project, and as mentor of Pierre de Filippis for the |
| Google Summer of Code 2006.</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g4" id="g4"> |
| <div class="header"> |
| <p class="title">Spreadsheet Compatibility. Forwards, Backwards ans Sideways</p> |
| <p class="by">Jody Goldberg</p> |
| </div> |
| |
| <div class="content"> |
| <p>Recent research into spreadsheet error rates are not enouraging (see Panko), |
| even experienced users make significant errors (off by over 5%) regularly. |
| Even slight variances in implementation between different applications and different |
| versions of applications compound the problem. Spreadsheet formulas are poor |
| documented functional programming languages. Despite the ongoing work in the |
| OpenDocument Formula subcommittee, and in Microsoft's ECMA TC45 standardization |
| effort the notion of one true standard to rule them all is a long way off.</p> |
| |
| <p>This discussion will deal with the extensions necessary in spreadsheet UI and |
| file formats to offer users a familiar syntax, and to allow different implementations |
| to at least know about the differences.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Jody Goldberg</strong> (Toronto Canada) has been involved with free |
| software for more than a decade. After spending years in various investment |
| banks developing analytics and talking to MS Excel support personnel, he discovered |
| Gnumeric and the GNOME project. Novell now employs him to work on |
| OpenOffice.org's Spreadsheet during business hours, and he continues to work |
| on Gnumeric once the kids go to sleep.</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g5" id="g5"> |
| |
| <div class="header"> |
| <p class="title">Discovering the New Chart Module</p> |
| <p class="by">Björn Milcke & Pierre-André Galmes</p> |
| </div> |
| |
| <div class="content"> |
| <p>Charts are used for visualizing data sets, e.g. numbers contained in the cells |
| of a spreadsheet. There are many kinds of charts to choose from (e.g. bar |
| chart, pie chart, scatter chart). As the current chart implementation has become |
| unmaintainable over the years, the chart team has decided to redesign the chart |
| module from scratch and create a usable base for further development and integration |
| of missing features.</p> |
| |
| <p>The new chart implementation is now gaining in maturity and is proving to be |
| a valuable tool. The purpose of this presentation is therefore to showcase this |
| brand new feature planned for one of the next releases. The presentation will focus |
| on the new chart as seen from two points of view: the user's (new features) |
| and the developer's (code design and API). Demos will be given to illustrate the |
| various features.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Björn Milcke</strong> graduated in Computer Science in Würzburg, Germany. |
| Working on StarOffice/OpenOffice.org Chart since 1999 (first for StarDivision then |
| for Sun Microsystems, Inc.)</p> |
| <p><strong>Pierre-André Galmes</strong> is working as a free-software consultant |
| at StarXpert in Paris since 2004. His work includes tasks like teaching to users OpenOffice.org |
| and C++ development. He recently started helping the chart team.</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g6" id="g6"> |
| <div class="header"> |
| <p class="title">WordForge - localisation infrastructure for everyone</p> |
| <p class="by">Dwayne Bailey</p> |
| </div> |
| |
| <div class="content"> |
| <p>Localisation is hard. It's made harder because there is a high technical |
| skill requirement to implement and integrate a localisation. A good translator, |
| who is technically skilled enough to localise software, is also difficult to find. |
| Now consider all this in relation to minority languages: no skilled resources and |
| few volunteer translators. Is this a recipe for mediocre localisations or an opportunity |
| for software to help elevate quality and help us produce localisations for very small languages?</p> |
| |
| <p>There are over 200 languages in Africa with more than 1 million speakers. If |
| we want to see those in OpenOffice.org we need to dramatically improve the process |
| of localisation so that we can reduce the barriers to entry.</p> |
| |
| <p>The WordForge project is delivering localisation infrastructure that helps |
| localisation teams effectively manage their localisations by ensuring good process |
| and by imporoving quality through glossary management and translation reuse.</p> |
| |
| <p>WordForge is focused on using the localisation formats developed by the localisation |
| industry including XLIFF, TMX and TBX. These standardised localisation formats add |
| large amounts of value to FOSS projects and translation teams, through the embeding and |
| managment of the localisation process, terminology and translation memory. WordForge's |
| existing translation management system, Pootle, is being extending to manage XLIFF files. |
| The present PO format does not allow effectively allow for this information to be |
| delivered to localisers.</p> |
| |
| <p>WordForge builds on the existing Translate Toolkit used by most OpenOffice.org |
| localisers and enhances the existing Pootle Translation Management Software. These |
| are real tools being expanded and enhanced by real localisers so that we can deliver |
| OpenOffice.org in many more languages.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Dwayne Bailey</strong> started Translate.org.za which has translated |
| OpenOffice.org into the 11 official languages of South Africa. This effort has played no small part in |
| getting Microsoft to localise into 3 South African languages. He is part of the |
| team that built the oo2po convertor used by most OpenOffice.org localisation teams. Dwayne, |
| together with Javier Sola from the KhmerOS team, founded the WordForge project as a means |
| to help improve the quality of localisations as well as to help more minority languages |
| translate FOSS.</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| |
| <div class="abstract" name="g6bis" id="g6bis"> |
| <div class="header"> |
| <p class="title">OpenOffice.org / RedOffice in China</p> |
| <p class="by">Cai Hong Hu</p> |
| </div> |
| |
| <div class="content"> |
| <p>This session is about how Beijing Bedflag Chinese 2000 Co. LTD., worked |
| hard to develop OpenOffice.org into a product RedOffice that would suit the |
| needs of Chinese business, including debugging OpenOffice.org, localizing the |
| information, Chinese typesetting, and developing lots of new fonctions for |
| the chinese customer.</p> |
| |
| <p>RedOffice has been excellent in government purchase from 2002 to now and its |
| bid-winning ratio is more than 30%. Until now, RedOffice products have spread over |
| more than twenty provinces and be widely used in various industries such as Water |
| Resource, Electrical Power, Tobacco, Mining, Iron and Steel Industry, etc.</p> |
| |
| <p>As an OpenOffice.org based software, RedOffice has a big market in China. Beijing |
| Redflag Chinese 2000 Co. LTD. helps to get support from China authority to support ODF |
| format in he passed ISO standard vote.</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g7" id="g7"> |
| <div class="header"> |
| <p class="title">OOo Documentation - Online Help and Beyond</p> |
| <p class="by">Frank Peters & Uwe Fischer</p> |
| </div> |
| |
| <div class="content"> |
| <p>This session will deal with multiple aspects of the OOo help system, and |
| documentation in general. It will encompass technological aspects, such as an |
| overview of OOo help system, information on how to write, modify, and build help, |
| how to localize or extend help. Common pitfalls when working with the help sources |
| will also be addressed. Further discussion will focus on community collaboration |
| aspects where the relation between the Sun-based help authors and the documentation |
| community will be discussed with the goal of highlighting existing and potential |
| collaboration paths and tools. Finally, we will try to collect ideas about the future |
| of OOo documentation and help, such as consolidation of documentation formats and the |
| feasibility of alternative delivery vehicles.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Uwe Fischer</strong> is a technical writer for StarOffice since 1995 and |
| has suffered from many team leads that gave different directions over time, yet |
| survived them all. He is a living fossil that proves that learning by doing can easily |
| lead nowhere.</p> |
| |
| <p><strong>Frank Peters</strong> is working on OOo and StarOffice documentation since |
| 2001 and is one of the many team leads that gave Uwe different directions. He worked |
| on implementing the help xml format and tools around it and helped making the help a |
| proper component in the product release process.</p> |
| </div> |
| <p><a href="tuesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g8" id="g8"> |
| <div class="header"> |
| <p class="title">Getting started with Automated GUI Testing - The VCL TestTool Application</p> |
| <p class="by">Thorsten Bosbach</p> |
| </div> |
| |
| <div class="content"> |
| <p>The VCL TestTool Application is used to test the functionality which is |
| available via the graphical user interface of OpenOffice.org.</p> |
| <p>Step by step hands on session: |
| <ul> |
| <li>Where is the VCL TestTool Application?</li> |
| <li>Where are the test scripts?</li> |
| <li>What steps are needed on using the VCL TestTool Application for the first time?</li> |
| </ul> |
| </p> |
| |
| <p>The test scripts make sure that the general functions of OOo are available |
| and working. Automated testing makes it easy to check if OOo behaves |
| equaly on different platforms and languages with a minimum manual effort.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Thorsten Bosbach</strong> is working at Sun Microsystems the last 6 years as |
| Quality Assurance Engineer in the StarOffice group, developing automated |
| GUI test scripts.</p> |
| </div> |
| <p><a href="wednesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g9" id="g9"> |
| <div class="header"> |
| <p class="title">Developing and improving OpenOffice.org dictionaries</p> |
| <p class="by">Németh László</p> |
| </div> |
| |
| <div class="content"> |
| <p>Overview of new features in OpenOffice.org spell checker, hyphenator and |
| thesaurus; and a practical guide to developing (much better) dictionaries for |
| these tools:</p> |
| |
| <ul> |
| <li>(semi)automated spell checking dictionary development (making, |
| extending and verifying spell checking dictionaries, developing affix |
| files for morphologically complex languages)</li> |
| |
| <li>using Hunspell (alias compression, complex prefixes for right-to-left |
| agglutinative languages, compound word support, pattern recognition for |
| numbers and number+letter combinations, forbidding taboo word suggestions etc.)</li> |
| |
| <li>making Unicode spell checking dictionaries, hyphenation patterns |
| and thesauri (not only for exotic writing systems)</li> |
| |
| <li>developing hyphenation patterns with discretionary and compound |
| word hyphenation support (need for Dutch, German, Hungarian, Norwegian, |
| Swedish etc.)</li> |
| |
| <li>handling morphological data for automatic stemming and affixation in thesaurus</li> |
| <li>moving to the standard writing (case study: supporting ligatures in French)</li> |
| <li>developing state-of-the-art language tools (case study: Hungarian |
| spell checking and hyphenation)</li> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Németh László</strong>, member of the Lingucomponent and |
| Hungarian language projects. Developed Unicode, compound word, morphological analysing |
| and agglutinative language support to OpenOffice.org Myspell spell checker (now Hunspell), and the |
| automatic discretionary and Unicode hyphenation patch to OpenOffice.org |
| AltLinux Libhnj hyphenator. Author of the Hungarian spell checking dictionary. |
| Lingucomponent co-lead.</p> |
| </div> |
| <p><a href="wednesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g10" id="g10"> |
| <div class="header"> |
| <p class="title">GStreamer in OpenOffice.org</p> |
| <p class="by">Cédric Bosdonnat & Radek Doulík</p> |
| </div> |
| |
| <div class="content"> |
| <p>This session will introduce the GStreamer media handling library and |
| its use in the OpenOffice.org. The talk will present the integration process |
| and the encountered problems as well as the work already done. It will also |
| mention possible future work in this area.</p> |
| |
| <p>The GStreamer integration includes these parts: |
| <ul> |
| <li>Enhancing media support in OpenOffice.org on Linux</li> |
| <li>Using the GStreamer framework to play multimedia files and streams</li> |
| <li>Creating macros handling GStreamer</li> |
| </ul> |
| </p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Cédric Bosdonnat</strong>, 22, graduated in INSA Lyon, has been |
| introduced to OpenOffice.org development during the Google Summer of Code 2005. |
| He works on an Eclipse plugin to help UNO component development. He has started |
| a UNO Component to use GStreamer free multimedia framework from OpenOffice.org.</p> |
| |
| <p><strong>Radek Doulík</strong>, 31, Graduated on Charles University in Prague, Worked |
| 6 years for Helixcode/Ximian/Novell in the Evolution project team. Today working |
| in the Open Office team, mainly on cairo canvas and Impress.</p> |
| </div> |
| <p><a href="wednesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g11" id="g11"> |
| <div class="header"> |
| <p class="title">Moving OOo to XCanvas, Step 2 - Draw and Impress</p> |
| <p class="by">Thorsten Behrens</p> |
| </div> |
| |
| <div class="content"> |
| <p>After having sucessfully converted the Impress slideshow to the new UNO |
| XCanvas rendering framework for OOo2.0, the next step in moving the whole |
| office suite to canvas-based rendering is the port of Draw and Impress</p> |
| |
| <p>This talk will show-case a working prototype of Impress, already rendering |
| the main edit view via XCanvas, displaying nicely anti-aliased graphics and |
| using the hardware-accelerated canvas sprite primitives while manipulating shapes.</p> |
| |
| <p>Furthermore, and overview is given about the underlying architectural rework |
| of the Impress drawing layer, which is now based on true MVC. Additionally, |
| the engine then offers an extensible display list of shape primitives, which |
| facilitates transparent switching of the rendering subsystem.</p> |
| |
| <p>The session concludes with an outlook on the port of Calc and Writer, and |
| the obstacles that have to be overcome beforehand.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>Thorsten Behrens</strong>, being a programmer since ages, he finished |
| a degree in computer science, and joined Sun's StarOffice/OpenOffice team |
| shortly thereafter. Since winter 2003, he's been busy redesigning and |
| implementing OOo's new rendering and slideshow components.</p> |
| </div> |
| <p><a href="wednesday.html">Back</a></p> |
| </div> |
| |
| <div class="abstract" name="g12" id="g12"> |
| <div class="header"> |
| <p class="title">OpenOffice.org and GNU/Linux distributions</p> |
| <p class="by">René Engelhard</p> |
| </div> |
| |
| <div class="content"> |
| <p>OpenOffice.org increasingly gets common and increasingly gets included |
| in GNU/Linux dustibutions. Unfortunately the working relationship with the |
| free software community at large and especially the GNU/Linux distributions |
| is not always as optimal as it can and there often are some stones in the |
| way for them when trying to package OpenOffice.org optimally.</p> |
| |
| <p>This Talk is intended to show those up and maybe to search ways for a |
| better working relationship in the future.</p> |
| </div> |
| |
| <div class="bio"> |
| <p><strong>René Engelhard</strong>, during his (aborted) studies of CS |
| at the University of Dortmund, Germany, he came in contact with Linux and |
| Free Software and not long after it joined the Debian Project. There he then |
| participated in the initial OpenOffice.org packaging efforts and now is |
| one of the two Debian OpenOffice.org Maintainers.</p> |
| </div> |
| <p><a href="wednesday.html">Back</a></p> |
| </div> |
| </body> |
| </html> |
