OpenOffice2

Differences between revisions 1 and 7 (spanning 6 versions)
Revision 1 as of 2005-04-26 03:14:12
Size: 850
Editor: intern146
Comment: New page
Revision 7 as of 2005-04-28 10:38:42
Size: 3055
Editor: intern146
Comment: set high priority, set breezy goal
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * Priority: NeedsPriority
 * People: MatthiasKloseLead, NeedsSecond
 * Priority: HighPriority
 * People: MatthiasKloseLead, DanielHolbachSecond
Line 12: Line 12:
 * Status: BrainDump, UduBof  * Status: DraftSpecification, BreezyGoal
Line 23: Line 23:
Determine the OpenOffice version, which builds with build tools from main on all release architectures and ships on the breezy desktop.
Line 24: Line 26:

The OpenOffice version in hoary (1.1.3) will be outdated by the breezy release date. Either switch to 1.1.4 or to 2.0.
Line 27: Line 31:
We need it for the desktop. One stable version.

Either:

 * Go with 1.1.4:
   * Stable release.
   * Builds with free tools.
   * Doesn't build on amd64 (hoary amd64 currently uses the i386 binaries).

 * Go with 2.0:
   * Release scheduled for June, recently a delay was announced (timeframe?).
   * Currently doesn't build with free tools. Needs evaluation with recent free java vm's and newer snapshots.
   * Building without Java support doesn't seem an option. Components like Base (database), docbook format, etc. rely on a Java runtime.
   * Better upstream report.
   * More translations will be ready upstream, less bugs in the translation tools/framework.
   * Doesn't build on amd64 (yet).
   * Have a chance to integrate new translations.
Line 28: Line 50:

Either:

 * Go with 1.1.4:
   * Update to 1.1.4 packages

 * Go with 2.0:
   * Update to recent milestone, after g++-4.0 is the default.
   * Update the existing translations (xh) for 2.0
   * See OpenofficeLocalization for localization stuff.
   * native amd64 build?
   * move spell checking support to OOo2, or share spell checking support with OOo1.

Write a test plan, mainly for LocoTeams to test OOo for their language

 * Write one or more test documents, which can be used for testing fonts in documents
   * Each document should have a paragraph for one language with (all?) the local characters
   * Test document imports, which were created on Windows with other office products
   * Test document imports for documents created with OOo1 versions in warty and breezy.
Line 37: Line 78:
 * 2.0:
   * The packagaging currently doesn't build all the language packs.
   * Spell checking needs to be integrated and/or separated out from OOo1.
   * amd64 builds
   * Handling of new translations.
   * Misc. bug fixing targeted for breezy
Line 44: Line 92:
.
 * OpenOffice 2.0 beta release on i386 and powerpc in hoary (without Java support, english only).

OpenOffice2

Status

Introduction

Determine the OpenOffice version, which builds with build tools from main on all release architectures and ships on the breezy desktop.

Rationale

The OpenOffice version in hoary (1.1.3) will be outdated by the breezy release date. Either switch to 1.1.4 or to 2.0.

Scope and Use Cases

We need it for the desktop. One stable version.

Either:

  • Go with 1.1.4:
    • Stable release.
    • Builds with free tools.
    • Doesn't build on amd64 (hoary amd64 currently uses the i386 binaries).
  • Go with 2.0:
    • Release scheduled for June, recently a delay was announced (timeframe?).
    • Currently doesn't build with free tools. Needs evaluation with recent free java vm's and newer snapshots.
    • Building without Java support doesn't seem an option. Components like Base (database), docbook format, etc. rely on a Java runtime.
    • Better upstream report.
    • More translations will be ready upstream, less bugs in the translation tools/framework.
    • Doesn't build on amd64 (yet).
    • Have a chance to integrate new translations.

Implementation Plan

Either:

  • Go with 1.1.4:
    • Update to 1.1.4 packages
  • Go with 2.0:
    • Update to recent milestone, after g++-4.0 is the default.
    • Update the existing translations (xh) for 2.0
    • See OpenofficeLocalization for localization stuff.

    • native amd64 build?
    • move spell checking support to OOo2, or share spell checking support with OOo1.

Write a test plan, mainly for LocoTeams to test OOo for their language

  • Write one or more test documents, which can be used for testing fonts in documents
    • Each document should have a paragraph for one language with (all?) the local characters
    • Test document imports, which were created on Windows with other office products
    • Test document imports for documents created with OOo1 versions in warty and breezy.

Data Preservation and Migration

Packages Affected

User Interface Requirements

Outstanding Issues

  • 2.0:
    • The packagaging currently doesn't build all the language packs.
    • Spell checking needs to be integrated and/or separated out from OOo1.
    • amd64 builds
    • Handling of new translations.
    • Misc. bug fixing targeted for breezy

UDU BOF Agenda

  • OpenOffice default for Breezy (1.1.4, or 2.0)

  • Packaging and bug fixing assignments
  • Localization Work

UDU Pre-Work

  • OpenOffice 2.0 beta release on i386 and powerpc in hoary (without Java support, english only).

OpenOffice2 (last edited 2008-08-06 16:38:23 by localhost)