Google Git
Sign in
apache / openoffice / bab44dcac0296df22024f3f10e7997de78ed4094 / . / AOO410 / main / readlicense_oo / docs / readme / readme.xrm
blob: 333a2f92a18117bf289d04a23ba16b13725c4056 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!--***********************************************************
*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*
***********************************************************-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
<title id="title" xml:lang="en-US">${PRODUCTNAME} Readme File</title>
<style type="text/css">
#Copyright_Trademark * {font-size: .7em;}
.note {border: 1px solid #993333; padding: 3px;}
p { margin-top: .1em; margin-bottom: .1em;}
.code {font-family: monospace;}
</style>
</head>
<body>
<div id="Intro">
<h1 id="Welcome" xml:lang="en-US">${PRODUCTNAME} ${PRODUCTVERSION} ReadMe</h1>
<p id="LatestUpdates" xml:lang="en-US">For latest updates to this readme file, see <a href="http://www.openoffice.org/welcome/readme.html">http://www.openoffice.org/welcome/readme.html</a></p>
<p id="A6" xml:lang="en-US">This file contains important information about this program. Please read this information very carefully before starting work.</p>
<p id="A7" xml:lang="en-US">The Apache OpenOffice 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 ${PRODUCTNAME} community site with helpful information at <a href="http://openoffice.apache.org">http://openoffice.apache.org</a></p>
<p id="A9" xml:lang="en-US">Also read the sections below about getting involved in the Apache OpenOffice project.</p>
<h3 id="A10" xml:lang="en-US">Is ${PRODUCTNAME} really free for any user? </h3>
<p id="A11" xml:lang="en-US">${PRODUCTNAME} is free for use by everybody. You may take this copy of ${PRODUCTNAME} 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 ${PRODUCTNAME} or <a href="http://www.openoffice.org/license.html">http://www.openoffice.org/license.html</a></p>
<h3 id="A12" xml:lang="en-US">Why is ${PRODUCTNAME} free for any user?</h3>
<p id="A13" xml:lang="en-US">You can use this copy of ${PRODUCTNAME} 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 ${PRODUCTNAME} what it is today - the world's leading open-source office software.</p>
<p id="A13b" xml:lang="en-US">If you appreciate their efforts, and would like to ensure Apache OpenOffice continues into the future, please consider contributing to the project - see <a href="http://openoffice.apache.org/get-involved.html">http://openoffice.apache.org/get-involved.html</a> for details on contributing time and <a href="http://www.apache.org/foundation/contributing.html">http://www.apache.org/foundation/contributing.html</a> for details on donations. Everyone has a contribution to make.</p>
</div>
<div id="Installation">
<h2 id="rr3fgf42r" xml:lang="en-US">Notes on Installation</h2>
<p class="note" id="javaneeded" xml:lang="en-US">${PRODUCTNAME} requires a recent version of JAVA for full functionality; JAVA can be downloaded from <a href="http://java.com">http://java.com</a>.</p>
<h3 id="sdfsdfgf42r" xml:lang="en-US">System Requirements</h3>
<div class="MAC" id="SystemRequirements_OSX">
<ul>
<li>
<p id="macxiOSX" xml:lang="en-US">MacOSX 10.7 (Lion) or higher</p>
</li>
<li>
<p id="macxicpu" xml:lang="en-US">Intel processor</p>
</li>
<li>
<p id="macxiRAM" xml:lang="en-US">512 MB RAM</p>
</li>
<li>
<p id="macxHardDiksSpace" xml:lang="en-US">Up to 1.5 GB available hard disk space</p>
</li>
<li>
<p id="macxivideo" xml:lang="en-US">1024 x 768 graphic device with 256 colors (higher resolution recommended)</p>
</li>
</ul>
</div>
<div class="WIN" id="SystemRequirements_WIN">
<ul>
<li>
<p id="s2s3sdf2" xml:lang="en-US">Microsoft Windows XP, Vista, Windows 7 or Windows 8</p>
</li>
<li>
<p id="utzu6" xml:lang="en-US">Pentium III or later processor</p>
</li>
<li>
<p id="ghuj67" xml:lang="en-US">256 MB RAM (512 MB RAM recommended)</p>
</li>
<li>
<p id="jzjtzu6" xml:lang="en-US">Up to 1.5 GB available hard disk space</p>
</li>
<li>
<p id="jtzu56" xml:lang="en-US">1024x768 resolution (higher resolution recommended), at least 256 colors</p>
</li>
</ul>
<p class="note" id="edssc3d" xml:lang="en-US">Please be aware that administrator rights are needed for the installation process.</p>
<p id="MSOReg1" xml:lang="en-US">Registration of ${PRODUCTNAME} as default application for Microsoft Office formats can be forced or suppressed by using the following command line switches with the installer:</p>
<ul>
<li>
<p id="MSOReg2" xml:lang="en-US"><tt>/msoreg=1</tt> will force registration of ${PRODUCTNAME} as default application for Microsoft Office formats.</p>
</li>
<li>
<p id="MSOReg3" xml:lang="en-US"><tt>/msoreg=0</tt> will suppress registration of ${PRODUCTNAME} as default application for Microsoft Office formats.</p>
</li>
</ul>
<p id="DLLA1" xml:lang="en-US">If you perform an administrative installation using setup /a, you need to make sure that the file msvcr100.dll is installed on the system. This file is required for ${PRODUCTNAME} to start after an administrative installation. You can get the file from <a href="http://www.microsoft.com/en-us/download/details.aspx?id=5555">http://www.microsoft.com/en-us/download/details.aspx?id=5555</a></p>
<p class="note" id="AdminNeeded" xml:lang="en-US">Please be aware that administrator rights are needed for the installation process.</p>
</div>
<div class="SOLSPARC" id="Sols2">
<ul>
<li>
<p id="s2335" xml:lang="en-US">Solaris 10 operating system (SPARC platform) or higher</p>
</li>
<li>
<p id="s253" xml:lang="en-US">256 MB RAM (512 MB RAM recommended)</p>
</li>
<li>
<p id="s23seg" xml:lang="en-US">Up to 1.55 GB available hard disk space</p>
</li>
<li>
<p id="s2s43gfe" xml:lang="en-US">X Server with 1024x768 resolution (higher resolution recommended), with at least 256 colors</p>
</li>
<li>
<p id="n4234rw" xml:lang="en-US">Window Manager</p>
</li>
<li>
<p id="wd2dff2" xml:lang="en-US">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)</p>
</li>
</ul>
</div>
<div class="SOLX86" id="Solia2">
<ul>
<li>
<p id="s23h" xml:lang="en-US">Solaris 10 operating system (x86 platform) or higher</p>
</li>
<li>
<p id="s24f" xml:lang="en-US">256 MB RAM (512 MB RAM recommended)</p>
</li>
<li>
<p id="fgheg" xml:lang="en-US">Up to 1.55 GB available hard disk space</p>
</li>
<li>
<p id="fghfgh" xml:lang="en-US">X Server with 1024x768 resolution (higher resolution recommended), with at least 256 colors</p>
</li>
<li>
<p id="mgjfg" xml:lang="en-US">Window Manager</p>
</li>
<li>
<p id="wd2dff1" xml:lang="en-US">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)</p>
</li>
</ul>
</div>
<div class="LINUX" id="Linuxi2">
<ul>
<li>
<p id="s2we35" xml:lang="en-US">Linux Kernel version 2.6.18 or higher</p>
</li>
<li>
<p id="s253we" xml:lang="en-US">glibc2 version 2.5 or higher</p>
</li>
<li>
<p id="s256we" xml:lang="en-US">gtk version 2.10.4 or higher</p>
</li>
<li>
<p id="s2etfseg" xml:lang="en-US">Pentium III or later processor</p>
</li>
<li>
<p id="s2ssdfe" xml:lang="en-US">256 MB RAM (512 MB RAM recommended)</p>
</li>
<li>
<p id="n42dfgf" xml:lang="en-US">Up to 1.55 GB available hard disk space</p>
</li>
<li>
<p id="ghjhhr" xml:lang="en-US">X Server with 1024x768 resolution (higher resolution recommended), with at least 256 colors</p>
</li>
<li>
<p id="fhrtz5" xml:lang="en-US">Window Manager</p>
</li>
<li>
<p id="wd2dff" xml:lang="en-US">Gnome 2.16 or higher, with the gail 1.8.6 and the at-spi 1.7 packages, required for support of assistive technology tools (AT tools)</p>
</li>
</ul>
<p id="Linuxi3a" xml:lang="en-US">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 ${PRODUCTNAME}, which may have different features from this Community ${PRODUCTNAME}. Sometimes you can install the Community ${PRODUCTNAME} 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.</p>
<p class="note" id="Linuxi4a" xml:lang="en-US">It is recommended that you always backup your system before you remove or install software.</p>
</div>
<p id="Precautions" xml:lang="en-US">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.</p>
</div>
<div class="LINUX WIN" id="StartupProblems">
<h2 id="naso01" xml:lang="en-US">Problems During Program Startup</h2>
<div class="LINUX" id="GnomeStartupProblems">
<p id="naso02" xml:lang="en-US">If you experience ${PRODUCTNAME} startup problems (most notably while using Gnome) please 'unset' the <tt>SESSION_MANAGER</tt> environment variable inside the shell you use to start ${PRODUCTNAME}. This can be done by adding the line "<tt>unset SESSION_MANAGER</tt>" to the beginning of the soffice shell script found in the "<tt>[office folder]/program</tt>" directory.</p>
</div>
<p id="abcdef" xml:lang="en-US">Difficulties starting ${PRODUCTNAME} (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 - ${PRODUCTNAME} - View - 3D view'.</p>
</div>
<div class="WIN" id="Scroll">
<h2 id="naso" xml:lang="en-US">ALPS/Synaptics notebook touchpads in Windows</h2>
<p id="naso2" xml:lang="en-US">Due to a Windows driver issue, you cannot scroll through ${PRODUCTNAME} documents when you slide your finger across an ALPS/Synaptics touchpad.</p>
<p id="naso6" xml:lang="en-US">To enable touchpad scrolling, add the following lines to the "<tt>C:\Program Files\Synaptics\SynTP\SynTPEnh.ini</tt>" configuration file, and restart your computer:</p>
<p class="code" id="naso7">[${PRODUCTNAME}]</p>
<p class="code" id="naso3">FC = "SALFRAME"</p>
<p class="code" id="naso4">SF = 0x10000000</p>
<p class="code" id="naso5">SF |= 0x00004000</p>
<p class="note" id="naso8" xml:lang="en-US">The location of the configuration file might vary on different versions of Windows.</p>
</div>
<div class="SOLSPARC SOLX86" id="NetscapeAdressBook">
<h2 id="sdfsd32asrc" xml:lang="en-US">Mozilla Address Book Driver</h2>
<p id="sdcc32asrc" xml:lang="en-US">The Mozilla address book driver requires the <tt>SUNWzlib</tt> package. This package is not part of the minimum Solaris operating system installation. If you require access to the Mozilla address book, then add this package to your Solaris operating system using the command "<tt>pkgadd</tt>" from the installation CD.</p>
</div>
<div id="Keyboard">
<h2 id="awe1" xml:lang="en-US">Shortcut Keys</h2>
<p id="w32e1" xml:lang="en-US">Only shortcut keys (key combinations) not used by the operating system can be used in ${PRODUCTNAME}. If a key combination in ${PRODUCTNAME} does not work as described in the ${PRODUCTNAME} 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 ${PRODUCTNAME}. For more information on this topic, refer to the ${PRODUCTNAME} Help or the Help documention of your operating system.</p>
<div class="MAC" id="MACKeysBETA">
<p id="mackeys1" xml:lang="en-US">The application help of ${PRODUCTNAME} may use shortcut combinations for PC keyboards only.</p>
</div>
</div>
<div class="LINUX MAC SOLSPARC SOLX86" id="FileLocking">
<h2 id="gfh6w" xml:lang="en-US">File Locking</h2>
<p id="pji76w" xml:lang="en-US">File locking is enabled by default in ${PRODUCTNAME}. On a network that uses the Network File System protocol (NFS), the locking daemon for NFS clients must be active. To disable file locking, edit the <tt>soffice</tt> script and change the line "<tt>export SAL_ENABLE_FILE_LOCKING</tt>" to "<tt># export SAL_ENABLE_FILE_LOCKING</tt>". If you disable file locking, the write access of a document is not restricted to the user who first opens the document.</p>
<p class="note" id="pji76wsdf" xml:lang="en-US">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, ${PRODUCTNAME} will hang when you try to open a file from a NFS mounted directory from a Linux computer.</p>
</div>
<div class="WIN" id="Mapi">
<h2 id="gfh6w1" xml:lang="en-US">Problems When Sending Documents as E-mails From ${PRODUCTNAME}</h2>
<p id="pji76w1" xml:lang="en-US">When sending a document via 'File - Send - Document as E-mail' or 'Document as PDF Attachment' problems might occur (program crashes or hangs). This is due to the Windows system file "Mapi" (Messaging Application Programming Interface) which causes problems in some file versions. Unfortunately, the problem cannot be narrowed down to a certain version number. For more information visit <a href="http://www.microsoft.com">http://www.microsoft.com</a> to search the Microsoft Knowledge Base for "mapi dll".</p>
</div>
<div id="A11y">
<h2 id="aw22" xml:lang="en-US">Important Accessibility Notes</h2>
<p id="access7" xml:lang="en-US">For more information on the accessibility features in ${PRODUCTNAME}, see <a href="http://www.openoffice.org/access/">http://www.openoffice.org/access/</a></p>
</div>
<div id="UserSupport">
<h2 id="support" xml:lang="en-US">User Support</h2>
<p id="support1" xml:lang="en-US">The main support page <a href="http://support.openoffice.org/">http://support.openoffice.org/</a> offers various possibilities for help with ${PRODUCTNAME}. Your question may have already been answered - check the Community Forum at <a href="http://forum.openoffice.org">http://forum.openoffice.org</a> or search the archives of the 'users@openoffice.apache.org' mailing list at <a href="http://openoffice.apache.org/mailing-lists.html">http://openoffice.apache.org/mailing-lists.html</a>. Alternatively, you can send in your questions to <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>. How to subscribe to the list (to get an email response) is explained on this page: <a href="http://openoffice.apache.org/mailing-lists.html">http://openoffice.apache.org/mailing-lists.html</a>.</p>
<p id="faq" url="ahead" xml:lang="en-US">Also check the FAQ section at <a href="http://wiki.openoffice.org/wiki/Documentation/FAQ">http://wiki.openoffice.org/wiki/Documentation/FAQ</a>.</p>
</div>
<div id="ReportBugsIssues">
<h2 id="reportbugs" xml:lang="en-US">Reporting Bugs &amp; Issues</h2>
<p id="reportbugs1" xml:lang="en-US">The ${PRODUCTNAME} Web site hosts <a href="https://issues.apache.org/ooo/">BugZilla</a>, 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.</p>
</div>
<div id="GettingInvolved">
<h2 id="gettinginvolved1" xml:lang="en-US">Getting Involved</h2>
<p id="gettinginvolved2" xml:lang="en-US">The ${PRODUCTNAME} Community would very much benefit from your active participation in the development of this important open source project.</p>
<p id="gettingimvolved3" xml:lang="en-US">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 <a href="http://openoffice.apache.org/get-involved.html">http://openoffice.apache.org/get-involved.html</a></p>
<h3 id="howtostart" xml:lang="en-US">How to Start</h3>
<p id="howtostart1" xml:lang="en-US">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 ${PRODUCTNAME} 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.</p>
<h3 id="subscribe" xml:lang="en-US">Subscribe</h3>
<p id="subscribe1" xml:lang="en-US">Here are a few of the ${PRODUCTNAME} mailing lists to which you can subscribe at <a href="http://openoffice.apache.org/mailing-lists.html">http://openoffice.apache.org/mailing-lists.html</a></p>
<ul>
<li>
<p id="subscribelist1" xml:lang="en-US">News: announce@openoffice.apache.org *recommended to all users* (light traffic)</p>
</li>
<li>
<p id="subscribelist2" xml:lang="en-US">Main user forum: users@openoffice.apache.org *easy way to lurk on discussions* (heavy traffic)</p>
</li>
<li>
<p id="subscribelist4" xml:lang="en-US">General project development and discussion list: dev@openoffice.apache.org (heavy traffic)</p>
</li>
</ul>
<h3 xml:lang="en-US">Joining the Project</h3>
<p id="joining" xml:lang="en-US">You can make major contributions to this important open source project even if you have limited software design or coding experience. Yes, you!</p>
<p id="joining1" url="ahead" xml:lang="en-US">At <a href="http://openoffice.apache.org/get-involved.html">http://openoffice.apache.org/get-involved.html</a> you will find a first overview where you can start with, ranging from Localization, QA, user support to some real core coding projects. If you are not a developer, you can help with Documentation or Marketing, for example. The ${PRODUCTNAME} marketing 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.</p>
<p id="joining3" xml:lang="en-US">You can help by joining the marketing mailing list marketing@openoffice.apache.org 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.</p>
</div>
<div id="Credits">
<p id="credits" xml:lang="en-US">We hope you enjoy working with the new ${PRODUCTNAME} ${PRODUCTVERSION} and will join us online.</p>
<p id="credits2" xml:lang="en-US">The Apache OpenOffice Community</p>
</div>
<div id="ModifiedSourceCode">
<h2 id="ModifiedSourceCodeHeading" xml:lang="en-US">Used / Modified Source Code</h2>
<p id="ModifiedSourceCodePara" xml:lang="en-US">For detailed information about used and/or modified source code, see the NOTICE file which is part of the installation.</p>
</div>
</body>
</html>