# Welcome

# OOo-dev 3.1 ReadMe

For latest updates to this readme file, see http://www.openoffice.org/welcome/readme.html

Dear User

This file contains important information about this program. Please read this information very carefully before starting work.

The OpenOffice.org Community, responsible for the development of this product, would like to invite you to participate as a community member. As a new user, you can check out the OOo-dev site with helpful user information at

http://www.openoffice.org/about_us/introduction.html

Also read the sections below about getting involved in the OpenOffice.org project.

### Is OOo-dev really free for any user?

OOo-dev is free for use by everybody. You may take this copy of OOo-dev and install it on as many computers as you like, and use it for any purpose you like (including commercial, government, public administration and educational use). For further details see the license text delivered together with OOo-dev or http://www.openoffice.org/license.html

### Why is OOo-dev free for any user?

You can use this copy of OOo-dev today free of charge because individual contributors and corporate sponsors have designed, developed, tested, translated, documented, supported, marketed, and helped in many other ways to make OOo-dev what it is today - the world's leading open-source office software.If you appreciate their efforts, and would like to ensure OpenOffice.org continues into the future, please consider contributing to the project - see http://contributing.openoffice.org for details. Everyone has a contribution to make.

## Notes on Installation

System Requirements:

- Linux Kernel version 2.4 or higher
- glibc2 version 2.3.2 or higher
- gtk version 2.2.0 or higher
- Pentium compatible PC (Pentium III or Athlon recommended)
- 256 MB RAM (512 MB RAM recommended)
- 440 MB available hard disk space
- Chinese, Japanese and Korean versions: 440 MB available hard disk space
- X Server with 1024x768 resolution (higher resolution recommended), with at least 256 colors
- Window Manager
- Gnome 2.6 or higher, with the gail 1.8.6 and the at-spi 1.7 packages, required for support of assistive technology tools (AT tools)

There is a wide variety of Linux distributions, and even within the same distribution there may be different installation options (KDE vs Gnome, etc.). Some distributions ship with their own ‘native’ version of OOo-dev, which may have different features from this Community OOo-dev. Sometimes you can install the Community OOo-dev alongside the ‘native’ version. However, it’s usually safer to remove the ‘native’ version before installing this Community version. Consult the documentation for your distribution for details of how to do this.

It is recommended that you always backup your system before you remove or install software.

### Problems During Program Startup

If you experience OOo-dev startup problems (most notably while using Gnome) please 'unset' the SESSION_MANAGER environment variable inside the shell you use to start OOo-dev. This can be done by adding the line "unset SESSION_MANAGER" to the beginning of the soffice shell script found in the "[office folder]/program" directory.

Difficulties starting OOo-dev (e.g. applications hang) as well as problems with the screen display are often caused by the graphics card driver. If these problems occur, please update your graphics card driver or try using the graphics driver delivered with your operating system. Difficulties displaying 3D objects can often be solved by deactivating the option "Use OpenGL" under 'Tools - Options - OOo-dev - View - 3D view'.

Please note that copy and paste via clipboard between OOo-dev 1.x and OOo-dev 3.1 might not work in OpenOffice.org format. If that happens, choose 'Edit - Paste Special' and choose a format other than OOo-dev, or open the document in OOo-dev 3.1 directly.

Please make sure you have enough free memory in the temporary directory on your system and that read, write and run access rights have been granted. Close all other programs before starting the installation.

### Shortcut Keys

Only shortcut keys (key combinations) not used by the operating system can be used in OOo-dev. If a key combination in OOo-dev does not work as described in the OOo-dev Help, check if that shortcut is already used by the operating system. To rectify such conflicts, you can change the keys assigned by your operating system. Alternatively, you can change almost any key assignment in OOo-dev. For more information on this topic, refer to the OOo-dev Help or the Help documentation of your operating system.

Due to a conflict with input method switching on multiple platforms, the following shortcut keys required to be changed at last minute:

- Ctrl-Space is now Ctrl-Shift-Space
- Ctrl-Shift-Space is now Ctrl-M

### File Locking

In the default setting, file locking is turned on in OOo-dev. To deactivate it, you have to set the appropriate environment variables SAL_ENABLE_FILE_LOCKING=0 and export SAL_ENABLE_FILE_LOCKING. These entries are already in enabled form in the soffice script file.

Warning: The activated file locking feature can cause problems with Solaris 2.5.1 and 2.7 used in conjunction with Linux NFS 2.0. If your system environment has these parameters, we strongly recommend that you avoid using the file locking feature. Otherwise, OOo-dev will hang when you try to open a file from a NFS mounted directory from a Linux computer.

## Important Accessibility Notes

For information on the accessibility features in OOo-dev, see http://www.openoffice.org/access/.

## Registration

Please take a little time to complete the minimal Product Registration process when you install the software. While registration is optional, we encourage you to register, since the information enables the community to make an even better software suite and address user needs directly. Through its Privacy Policy, the OOo-dev Community takes every precaution to safeguard your personal data. If you missed the registration at installation, you can return and register at any time at by choosing "Help > Registration" from the main menu.

## User Survey

There is also a User Survey located online which we encourage you to fill out. The User Survey results will help OOo-dev move more rapidly in setting new standards for the creation of the next-generation office suite. Through its Privacy Policy, the OOo-dev Community takes every precaution to safeguard your personal data.

## User Support

The main support page http://support.openoffice.org/offers various possibilities for help with OOo-dev. Your question may have already been answered - check the Community Forum.http://user.services.openoffice.org or search the archives of the 'users@openoffice.org' mailing list at http://www.openoffice.org/mail_list.html. Alternatively, you can send in your questions to users@openoffice.org. How to subscribe to the list (to get an email response) is explained on this page: http://wiki.services.openoffice.org/wiki/Website/Content/help/mailinglists.

Also check the FAQ section at http://wiki.services.openoffice.org/wiki/Documentation/FAQ.

## Report Bugs & Issues

The OOo-dev Web site hosts IssueZilla, our mechanism for reporting, tracking and solving bugs and issues. We encourage all users to feel entitled and welcome to report issues that may arise on your particular platform. Energetic reporting of issues is one of the most important contributions that the user community can make to the ongoing development and improvement of the suite.

## Getting Involved

The OOo-dev Community would very much benefit from your active participation in the development of this important open source project.

As a user, you are already a valuable part of the suite's development process and we would like to encourage you to take an even more active role with a view to being a long-term contributor to the community. Please join and check out the user page at: http://www.openoffice.org

### Way to Start

The best way to start contributing is to subscribe to one or more of the mailing lists, lurk for a while, and gradually use the mail archives to familiarize yourself with many of the topics covered since the OOo-dev source code was released back in October 2000. When you're comfortable, all you need to do is send an email self-introduction and jump right in. If you are familiar with Open Source Projects, check out our To-Dos list and see if there is anything you would like to help with at http://development.openoffice.org/todo.html.

### Subscribe

Here are a few of the Project mailing lists to which you can subscribe at http://www.openoffice.org/mail_list.html

- News: announce@openoffice.org *recommended to all users* (light traffic)
- Main user forum: user@openoffice.org *easy way to lurk on discussions* (heavy traffic)
- Marketing project: dev@marketing.openoffice.org *beyond development* (getting heavy)
- General code contributor list: dev@openoffice.org (moderate/heavy)

### Join one or more Projects

You can make major contributions to this important open source project even if you have limited software design or coding experience. Yes, you!

At http://projects.openoffice.org/index.html you will find projects ranging from Localization, Porting and Groupware to some real core coding projects. If you are not a developer, try the Documentation or the Marketing Project. The OpenOffice.org Marketing Project is applying both guerrilla and traditional commercial techniques to marketing open source software, and we are doing it across language and cultural barriers, so you can help just by spreading the word and telling a friend about this office suite.

You can help by joining the Marketing Communications & Information Network here: http://marketing.openoffice.org/contacts.html where you can provide point communication contact with press, media, government agencies, consultants, schools, Linux Users Groups and developers in your country and local community.

We hope you enjoy working with the new OOo-dev 3.1 and will join us online.

The OpenOffice.org Community

## Used / Modified Source Code

Portions Copyright 1998, 1999 James Clark. Portions Copyright 1996, 1998 Netscape Communications Corporation.