content/marketing/ooocon2005/schedule/thursday_community.html - openoffice-org - Git at Google

 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <head>
   <meta content="text/html; charset=ISO-8859-1"
  http-equiv="content-type">
   <title>OOoCon 2005 Community</title>
   <style type="text/css">
 h3 { background-color: rgb(255, 192, 90) ! important;
 color: rgb(255, 255, 255);
 }
   </style>
 </head>
 <body>
 <div id="startpage" class="app">
 <div class="h3" id="myprojects">
 <h2>Abstracts
 of
 Conference Papers
 - Community Stream<br>
 </h2>
 <h3><a name="c1"></a>Community
 RE (report from the Bleeding Edge)</h3>
 </div>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Pavel Jan&iacute;k -
 independent consultant<br>
       </td>
     </tr>
     <tr class="b">
       <td>Developers' life is much
 easier now than it was in 1.x times. Much
 easier. We have EIS, child workspaces, we can do QA etc. The
 development process is open in several aspects. There are dark places
 though.<br>
 In his presentation, Pavel will talk about his experiences with
 developer milestones, his build system and about his findings about
 processes of Hamburg RE. He will bring several interesting (and
 potentially conflicting) questions. Could public tinderbox help Sun
 engineers identify potential conflicts between Sun build environment
 and community environment? Can community member change the community
 build environment without changes in Sun build environment? How can the
 member of community fix P1 build issues effectively? More milestones a
 week: can we follow them at all? Master fixes and moving tags after the
 milestone is ready: should it be announced?<br>
 Sun only child workspaces and their effect on the development process
 (bugs in Sun internal bug tracking system, description of child
 workspace vs. every change in CVS).<br>
       <br>
 Target: developers from both Sun RE and the community
 interesting in experiences from the hell^H^H^H^Hbleeding edge, problems
 and proposed solutions<br>
       </td>
     </tr>
     <tr style="font-style: italic;" class="a">
       <td>Biography: Pavel
 Jan&iacute;k is long time user and developer of GNU/Linux and free
 software applications, member of GNU project. He is a member of
 OpenOffice.org Community Council, OpenOffice.org Engineering Steering
 Committee, co-lead of l10n project and lead of Czech Native-Language
 project. He provides regular builds of development milestones for more
 than 20 languages and GNU/Linux, Microsoft Windows and MacOS X
 operating systems.<br>
 In his other life, he is an independent consultant working for various
 public and government companies, agencies and institutions in Czech
 republic and EU.<br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a><br>
 <h3><a name="c2"></a>Entering
 the OOo Community</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td> Andre
 Schnabel<br>
       </td>
     </tr>
     <tr class="b">
       <td>The aim of this session
 is to give a general overview of the projects
 and its organization, but also tips to enter into a project. <br>
 This session will have 3 axes in a first time :<br>
       <ul>
         <li>the overall project
 structure (Accepted, Incubator, NLC, CC) and its communication flow</li>
         <li>the organization
 inside a project and how the NLC could be a bridge
 between the development project and the NL project, keeping people in
 touch and introducing people to those projects.</li>
         <li>the
 documents&nbsp; (like specs template and features described in IZ)
 and tools used for collaboration (Licenses, JCA, CVS, EIS)</li>
       </ul>
 NL projects are not independent&nbsp; entities, they are the first
 step to
 belong to a community and learn how to behave in it. For those who
 wants to go further, the need of picturing the OOo community is a
 requirement. Aside the structure, there are general principles that are
 available in any FOSS community like: aiming dialog and consensus,
 sharing knowledge and power, personal responsibility, confidence. <br>
 This means for example that competencies are promoted and recognized
 not as personal contributions but for what they bring to the project.
 In the same way some are projects leads, but only contributors in other
 projects. <br>
 In conclusion, contributing to a project is based on an ethic of
 discussion and respect for others.<br>
       <br>
 Target audience: All people from NLC (or not :-) willing to contribute
 to a project in OOo community for the first time. <br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a>
 <h3><a name="c3"></a>The
 State of the Project Year 5</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Louis Suarez-Potts -
 Community Manager, OpenOffice.org/CollabNet</td>
     </tr>
     <tr class="b">
       <td>This talk recapitulates
 the events of the last year and then looks
 forward to what the next year and beyond might hold for
 OpenOffice.org.&nbsp; Topics include:<br>
       <ul>
         <li>What the past year has
 produced and how the project has evolved;</li>
         <li>What we can do to
 enhance developer contributions:</li>
         <li>Changing license is
 but one measure</li>
         <li>Improving the build
 process</li>
         <li>Re-architecting OOo to
 make it more modular</li>
         <li>License change</li>
       </ul>
 And then there is 3.0 and beyond.&nbsp; How can OOo capture more
 attention?
 There is the well-known proposal for OpenOffice.org Lite, which would
 require a re-architecting of the code.&nbsp; But it may be done if
 mobile
 phone companies and others get involved, for it is a very popular
 notion, one that merits more investigation.<br>
       <br>
 Target audience: General <br>
       </td>
     </tr>
     <tr class="a">
       <td><span style="font-style: italic;">Biography: Louis
 Suarez-Potts has been the community manager of OpenOffice.org
 since close to its beginning.&nbsp; He is also the chair of the
 Community
 Council and the lead of several projects on OpenOffice.org. He lives in
 Toronto.</span><br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a><br>
 <h3><a name="c4"></a>Localizing
 OpenOffice.org</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Monica Badia
 - Italian Language Lead, Sun Microsystems<br>
       </td>
     </tr>
     <tr class="b">
       <td>In June 2004, Sun
 Microsystems Inc. and OO.o started a Localization
 Pilot Process with the aim of improving the collaboration effort both
 in translation and localization testing (see:
 http://l10n.openoffice.org/localization/L10n_pilotprocess.html). Now
 that the short term goals have been reached, we would like to<br>
       <ol style="list-style-type: lower-alpha;">
         <li>share our experience
 during this pilot in the specific areas Translation and Testing</li>
         <li>consolidate and set up
 the long term localization process.</li>
       </ol>
 The Globalization team of SMI would like to present in a BOF session
 the following topics:<br>
       <ul>
         <li>the general
 Localization Pilot Process</li>
         <li>the Italian Success
 Story which will provide the audience with detailled information on the
 Translation process</li>
         <li>the linguistic review
 process</li>
         <li>the translation tools</li>
         <li>the Localization
 Testing and TCM tool</li>
         <li>OO.o 2.0 Dutch
 localization:an example of how Sun&nbsp; / Sun appointed vendors /
 and NL OO.o Communities can work together.</li>
         <li>the translation
 process automation &ndash; how Sun is setting up a process to
 automate the file exchange with the OO.o and how the OO.o Community
 will benefit from the future automation.</li>
       </ul>
 Target audience: All members of the communities interested in the L10N
 of OO.o and in a collaboration with SMI<br>
       </td>
     </tr>
     <tr style="font-style: italic;" class="a">
       <td>Biographies:<br>
       <br>
 Dott. Monica Badia: Italian Language Lead at Sun Microsystems. She is
 responsible for the quality control of Sun localized products in
 Italian. She is also lead of the linguistic QA Matrix and linguistic
 review process for the European languages.&nbsp; She counts a 6
 year
 experience at Sun Microsystems in the field of localization. From
 1999to 2003 she was assigned to the translation&nbsp; and L10N
 testing of
 StarOffice in Italian.
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a><br>
 <h3><a name="c5"></a>The
 Lingucomponent Project &ndash; linguistic tools in OpenOffice.org</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Daniel Naber - Software
 developer, IntraFind Software AG, Munich, Germany<br>
       </td>
     </tr>
     <tr class="b">
       <td>The Lingucomponent
 project is responsible for spell checking, thesauri,
 and grammar checking inside OpenOffice.org. I will show where OOo's
 spell checking and thesaurus features stand today, how they differ from
 those in StarOffice and how the community can enhance them. One
 important thing is of course extending these features to new languages.
 This is a fair amount of work, but it doesn't require programming
 skills and I'll demonstrate the approaches that make these tasks
 feasible.<br>
       <br>
 New thesauri can be built using OpenThesaurus, a PHP-driven website
 that allows the community to work on a new thesaurus or to maintain an
 existing one. &nbsp;Writing dictionaries is a task that's not well
 supported by tools, but
 I'll show the basic ideas behind MySpell &ndash; OOo's integrated
 spell
 checker &ndash; and how to get started writing your own spelling
 dictionary. For grammar checking, I will show what is still missing to
 integrate a grammar checking into OOo.<br>
       <br>
 Also, the concept of a programming interface for spell checking and
 thesauri will be explained which allows everybody to plug in his own
 spell checkers and thesauri.<br>
       <br>
 Targeted audience: developers, but not necessarily programmers<br>
       </td>
     </tr>
     <tr class="a">
       <td><span style="font-style: italic;">Biography: Daniel Naber
 studied computer science and linguistics at the
 University of Bielefeld, Germany. He now works at a software company in
 Munich that specializes in enhancing fulltext search with linguistic
 methods. He's author of OpenThesaurus, a web application that's used to
 maintain the German (www.openthesaurus.de), Polish, and Spanish
 thesaurus for OpenOffice.org. He also wrote LanguageTool, an English
 grammar checker that can be adapted for other languages. </span><br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a><a href="thursday.html"></a><br>
 <h3><a name="b5b"></a>The
 Localization Process</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr class="a">
       <td><span style="font-style: italic;">Alessandro Cattelan</span><br>
       </td>
     </tr>
     <tr class="b">
       <td>The Italian OpenOffice
 project is reorganizing the
 localization process
 in order to improve the quality of the translation and to keep it as
 up-to-date as possible. <br>
 We would like to propose the organization of a BOF where translators
 could discuss how to best carry out the translation process. We would
 like to focus on the following issues:<br>
       <ul>
         <li>the importance of
 Translation Memories (TM) and glossaries;</li>
         <li>CAT tools (which CAT
 tool is best for the OOo localization);</li>
         <li>how to work with a CAT
 tool;</li>
         <li>workflow (how to
 organize the work of the translators
 &ndash; structure of a
 translation team, mailing lists, TM and glossaries repositories,
 stylistic guides, etc.);</li>
         <li>coordination of the
 various national groups.</li>
       </ul>
 Target audience: &nbsp;Translators and people interested in the
 localization process.<br>
       </td>
     </tr>
     <tr style="font-style: italic;" class="a">
       <td>Biography: Currently
 specializing in translation at the
 Advanced School
 of Modern Languages for Interpreters and Translators (SSLMIT), Trieste,
 Italy.<br>
 Working as a freelance translator and language teacher.<br>
 I am currently&nbsp; co-operating with the Italian OpenOffice
 project
 team for the localization into Italian of the suite.</td>
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a>
 <h3><a name="b5a"></a>Localization &ndash; the tools and the people</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Adam Rambousek -&nbsp;Faculty of Informatics, Masaryk
 University
       </td>
     </tr>
     <tr class="b">
       <td>This session will present the localization framework used by
 many
 native language projects with brief overview of tools available for
 translators and project leaders. In addition to technical aspects, also
 people are important for successful localization. I will present the
 experiences in attracting, choosing and retaining project contributors,
 organizing them to cooperate on translation and evaluating their work.
 And also, I will talk about collaboration with users on finding bugs in
 localized texts. <br>
 Target audience:
 Anyone interested in localization process
       </td>
     </tr>
     <tr style="font-style: italic;" class="a">
       <td>Biography:
 I'm the member of Czech native language project for a few years and
 from the beginning of this year I'm the translation co-lead. Also, I'm
 a student at the Faculty of Informatics, Masaryk University in Brno and
 I'm developing dictionary writing system in the Natural Language
 Processing Laboratory at FI MU. <br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a><br>
 <h3><a name="b6"></a>Bug
 hunting Party</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr class="a">
       <td><span style="font-style: italic;">Andr&eacute; Schnabel</span><br>
       </td>
     </tr>
     <tr class="b">
       <td>To give the daily work
 of our QA team a boost, the best way
 is to come together and do the job.<br>
 There have been some virtual bug hunting days within the recent years,
 organized via IRC. We want to do the same but invite people to meet
 each other, talk to each other, spread their knowledge and go for a bug
 hunt. <br>
 After a short introduction of the daily work of a qu member, we would
 simply start doing it. That means searching issuezilla for unconfirmed
 issues, try to confirm them, look for duplicates or even already
 resolved issues.<br>
 People should bring a notebook with them, if possible. <br>
 For the session we will need wired / wireless internet access.<br>
       <br>
 Target audience: Community members, current and future members of the
 QA team<br>
       </td>
     </tr>
     <tr class="a">
       <td><span style="font-style: italic;">Biography: I'm member of
 the OpenOffice.org project since May 2002, mainly doing documentation,
 user support and QA. </span><br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="thursday.html">Back</a><br>
 </div>
 </body>
 </html>
	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
	<html>
	<head>
	<meta content="text/html; charset=ISO-8859-1"
	http-equiv="content-type">
	<title>OOoCon 2005 Community</title>
	<style type="text/css">
	h3 { background-color: rgb(255, 192, 90) ! important;
	color: rgb(255, 255, 255);
	}
	</style>
	</head>
	<body>
	<div id="startpage" class="app">
	<div class="h3" id="myprojects">
	<h2>Abstracts
	of
	Conference Papers
	- Community Stream<br>
	</h2>
	<h3><a name="c1"></a>Community
	RE (report from the Bleeding Edge)</h3>
	</div>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Pavel Janík -
	independent consultant<br>
	</td>
	</tr>
	<tr class="b">
	<td>Developers' life is much
	easier now than it was in 1.x times. Much
	easier. We have EIS, child workspaces, we can do QA etc. The
	development process is open in several aspects. There are dark places
	though.<br>
	In his presentation, Pavel will talk about his experiences with
	developer milestones, his build system and about his findings about
	processes of Hamburg RE. He will bring several interesting (and
	potentially conflicting) questions. Could public tinderbox help Sun
	engineers identify potential conflicts between Sun build environment
	and community environment? Can community member change the community
	build environment without changes in Sun build environment? How can the
	member of community fix P1 build issues effectively? More milestones a
	week: can we follow them at all? Master fixes and moving tags after the
	milestone is ready: should it be announced?<br>
	Sun only child workspaces and their effect on the development process
	(bugs in Sun internal bug tracking system, description of child
	workspace vs. every change in CVS).<br>
	<br>
	Target: developers from both Sun RE and the community
	interesting in experiences from the hell^H^H^H^Hbleeding edge, problems
	and proposed solutions<br>
	</td>
	</tr>
	<tr style="font-style: italic;" class="a">
	<td>Biography: Pavel
	Janík is long time user and developer of GNU/Linux and free
	software applications, member of GNU project. He is a member of
	OpenOffice.org Community Council, OpenOffice.org Engineering Steering
	Committee, co-lead of l10n project and lead of Czech Native-Language
	project. He provides regular builds of development milestones for more
	than 20 languages and GNU/Linux, Microsoft Windows and MacOS X
	operating systems.<br>
	In his other life, he is an independent consultant working for various
	public and government companies, agencies and institutions in Czech
	republic and EU.<br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a><br>
	<h3><a name="c2"></a>Entering
	the OOo Community</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td> Andre
	Schnabel<br>
	</td>
	</tr>
	<tr class="b">
	<td>The aim of this session
	is to give a general overview of the projects
	and its organization, but also tips to enter into a project. <br>
	This session will have 3 axes in a first time :<br>
	<ul>
	<li>the overall project
	structure (Accepted, Incubator, NLC, CC) and its communication flow</li>
	<li>the organization
	inside a project and how the NLC could be a bridge
	between the development project and the NL project, keeping people in
	touch and introducing people to those projects.</li>
	<li>the
	documents  (like specs template and features described in IZ)
	and tools used for collaboration (Licenses, JCA, CVS, EIS)</li>
	</ul>
	NL projects are not independent  entities, they are the first
	step to
	belong to a community and learn how to behave in it. For those who
	wants to go further, the need of picturing the OOo community is a
	requirement. Aside the structure, there are general principles that are
	available in any FOSS community like: aiming dialog and consensus,
	sharing knowledge and power, personal responsibility, confidence. <br>
	This means for example that competencies are promoted and recognized
	not as personal contributions but for what they bring to the project.
	In the same way some are projects leads, but only contributors in other
	projects. <br>
	In conclusion, contributing to a project is based on an ethic of
	discussion and respect for others.<br>
	<br>
	Target audience: All people from NLC (or not :-) willing to contribute
	to a project in OOo community for the first time. <br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a>
	<h3><a name="c3"></a>The
	State of the Project Year 5</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Louis Suarez-Potts -
	Community Manager, OpenOffice.org/CollabNet</td>
	</tr>
	<tr class="b">
	<td>This talk recapitulates
	the events of the last year and then looks
	forward to what the next year and beyond might hold for
	OpenOffice.org.  Topics include:<br>
	<ul>
	<li>What the past year has
	produced and how the project has evolved;</li>
	<li>What we can do to
	enhance developer contributions:</li>
	<li>Changing license is
	but one measure</li>
	<li>Improving the build
	process</li>
	<li>Re-architecting OOo to
	make it more modular</li>
	<li>License change</li>
	</ul>
	And then there is 3.0 and beyond.  How can OOo capture more
	attention?
	There is the well-known proposal for OpenOffice.org Lite, which would
	require a re-architecting of the code.  But it may be done if
	mobile
	phone companies and others get involved, for it is a very popular
	notion, one that merits more investigation.<br>
	<br>
	Target audience: General <br>
	</td>
	</tr>
	<tr class="a">
	<td><span style="font-style: italic;">Biography: Louis
	Suarez-Potts has been the community manager of OpenOffice.org
	since close to its beginning.  He is also the chair of the
	Community
	Council and the lead of several projects on OpenOffice.org. He lives in
	Toronto.</span><br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a><br>
	<h3><a name="c4"></a>Localizing
	OpenOffice.org</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Monica Badia
	- Italian Language Lead, Sun Microsystems<br>
	</td>
	</tr>
	<tr class="b">
	<td>In June 2004, Sun
	Microsystems Inc. and OO.o started a Localization
	Pilot Process with the aim of improving the collaboration effort both
	in translation and localization testing (see:
	http://l10n.openoffice.org/localization/L10n_pilotprocess.html). Now
	that the short term goals have been reached, we would like to<br>
	<ol style="list-style-type: lower-alpha;">
	<li>share our experience
	during this pilot in the specific areas Translation and Testing</li>
	<li>consolidate and set up
	the long term localization process.</li>
	</ol>
	The Globalization team of SMI would like to present in a BOF session
	the following topics:<br>
	<ul>
	<li>the general
	Localization Pilot Process</li>
	<li>the Italian Success
	Story which will provide the audience with detailled information on the
	Translation process</li>
	<li>the linguistic review
	process</li>
	<li>the translation tools</li>
	<li>the Localization
	Testing and TCM tool</li>
	<li>OO.o 2.0 Dutch
	localization:an example of how Sun  / Sun appointed vendors /
	and NL OO.o Communities can work together.</li>
	<li>the translation
	process automation – how Sun is setting up a process to
	automate the file exchange with the OO.o and how the OO.o Community
	will benefit from the future automation.</li>
	</ul>
	Target audience: All members of the communities interested in the L10N
	of OO.o and in a collaboration with SMI<br>
	</td>
	</tr>
	<tr style="font-style: italic;" class="a">
	<td>Biographies:<br>
	<br>
	Dott. Monica Badia: Italian Language Lead at Sun Microsystems. She is
	responsible for the quality control of Sun localized products in
	Italian. She is also lead of the linguistic QA Matrix and linguistic
	review process for the European languages.  She counts a 6
	year
	experience at Sun Microsystems in the field of localization. From
	1999to 2003 she was assigned to the translation  and L10N
	testing of
	StarOffice in Italian.
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a><br>
	<h3><a name="c5"></a>The
	Lingucomponent Project – linguistic tools in OpenOffice.org</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Daniel Naber - Software
	developer, IntraFind Software AG, Munich, Germany<br>
	</td>
	</tr>
	<tr class="b">
	<td>The Lingucomponent
	project is responsible for spell checking, thesauri,
	and grammar checking inside OpenOffice.org. I will show where OOo's
	spell checking and thesaurus features stand today, how they differ from
	those in StarOffice and how the community can enhance them. One
	important thing is of course extending these features to new languages.
	This is a fair amount of work, but it doesn't require programming
	skills and I'll demonstrate the approaches that make these tasks
	feasible.<br>
	<br>
	New thesauri can be built using OpenThesaurus, a PHP-driven website
	that allows the community to work on a new thesaurus or to maintain an
	existing one.  Writing dictionaries is a task that's not well
	supported by tools, but
	I'll show the basic ideas behind MySpell – OOo's integrated
	spell
	checker – and how to get started writing your own spelling
	dictionary. For grammar checking, I will show what is still missing to
	integrate a grammar checking into OOo.<br>
	<br>
	Also, the concept of a programming interface for spell checking and
	thesauri will be explained which allows everybody to plug in his own
	spell checkers and thesauri.<br>
	<br>
	Targeted audience: developers, but not necessarily programmers<br>
	</td>
	</tr>
	<tr class="a">
	<td><span style="font-style: italic;">Biography: Daniel Naber
	studied computer science and linguistics at the
	University of Bielefeld, Germany. He now works at a software company in
	Munich that specializes in enhancing fulltext search with linguistic
	methods. He's author of OpenThesaurus, a web application that's used to
	maintain the German (www.openthesaurus.de), Polish, and Spanish
	thesaurus for OpenOffice.org. He also wrote LanguageTool, an English
	grammar checker that can be adapted for other languages. </span><br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a><a href="thursday.html"></a><br>
	<h3><a name="b5b"></a>The
	Localization Process</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr class="a">
	<td><span style="font-style: italic;">Alessandro Cattelan</span><br>
	</td>
	</tr>
	<tr class="b">
	<td>The Italian OpenOffice
	project is reorganizing the
	localization process
	in order to improve the quality of the translation and to keep it as
	up-to-date as possible. <br>
	We would like to propose the organization of a BOF where translators
	could discuss how to best carry out the translation process. We would
	like to focus on the following issues:<br>
	<ul>
	<li>the importance of
	Translation Memories (TM) and glossaries;</li>
	<li>CAT tools (which CAT
	tool is best for the OOo localization);</li>
	<li>how to work with a CAT
	tool;</li>
	<li>workflow (how to
	organize the work of the translators
	– structure of a
	translation team, mailing lists, TM and glossaries repositories,
	stylistic guides, etc.);</li>
	<li>coordination of the
	various national groups.</li>
	</ul>
	Target audience:  Translators and people interested in the
	localization process.<br>
	</td>
	</tr>
	<tr style="font-style: italic;" class="a">
	<td>Biography: Currently
	specializing in translation at the
	Advanced School
	of Modern Languages for Interpreters and Translators (SSLMIT), Trieste,
	Italy.<br>
	Working as a freelance translator and language teacher.<br>
	I am currently  co-operating with the Italian OpenOffice
	project
	team for the localization into Italian of the suite.</td>
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a>
	<h3><a name="b5a"></a>Localization – the tools and the people</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Adam Rambousek - Faculty of Informatics, Masaryk
	University
	</td>
	</tr>
	<tr class="b">
	<td>This session will present the localization framework used by
	many
	native language projects with brief overview of tools available for
	translators and project leaders. In addition to technical aspects, also
	people are important for successful localization. I will present the
	experiences in attracting, choosing and retaining project contributors,
	organizing them to cooperate on translation and evaluating their work.
	And also, I will talk about collaboration with users on finding bugs in
	localized texts. <br>
	Target audience:
	Anyone interested in localization process
	</td>
	</tr>
	<tr style="font-style: italic;" class="a">
	<td>Biography:
	I'm the member of Czech native language project for a few years and
	from the beginning of this year I'm the translation co-lead. Also, I'm
	a student at the Faculty of Informatics, Masaryk University in Brno and
	I'm developing dictionary writing system in the Natural Language
	Processing Laboratory at FI MU. <br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a><br>
	<h3><a name="b6"></a>Bug
	hunting Party</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr class="a">
	<td><span style="font-style: italic;">André Schnabel</span><br>
	</td>
	</tr>
	<tr class="b">
	<td>To give the daily work
	of our QA team a boost, the best way
	is to come together and do the job.<br>
	There have been some virtual bug hunting days within the recent years,
	organized via IRC. We want to do the same but invite people to meet
	each other, talk to each other, spread their knowledge and go for a bug
	hunt. <br>
	After a short introduction of the daily work of a qu member, we would
	simply start doing it. That means searching issuezilla for unconfirmed
	issues, try to confirm them, look for duplicates or even already
	resolved issues.<br>
	People should bring a notebook with them, if possible. <br>
	For the session we will need wired / wireless internet access.<br>
	<br>
	Target audience: Community members, current and future members of the
	QA team<br>
	</td>
	</tr>
	<tr class="a">
	<td><span style="font-style: italic;">Biography: I'm member of
	the OpenOffice.org project since May 2002, mainly doing documentation,
	user support and QA. </span><br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="thursday.html">Back</a><br>
	</div>
	</body>
	</html>