| NeoOffice |
|
| NeoOffice® is Mac OS X office software funded entirely by the time and money donated by our users | |
|
|
||||
| Home | Downloads | Support | Características |
| FAQ | NeoWiki | Trinity Forums | Bugzilla | Build Instructions |
| Donativos | Early Access Program |
NeoOffice is a reasonably stable version of the OpenOffice.org office suite that has been engineered to run natively on Mac OS X.
NeoOffice is not perfect. Although we try very hard to make NeoOffice free of bugs and crashes, our users still find new bugs and new cases that cause NeoOffice to crash. So, if you feel that you need software that has been heavily tested, we recommend that you use a commercially-supported product like Microsoft Office or Apple iWork.
NeoOffice can open, edit, print, and save all OpenOffice.org and most Microsoft Office documents.
I am having problems installing or running NeoOffice. Where can I go for support?
If you have questions, your best bet is to browse around the NeoWiki and the Trinity Forums.
NeoOffice is an open source development project staffed entirely by volunteers. What this means is that there is no formal user support. Instead, we have the NeoWiki and Trinity Forums so that users can post questions or search for answers. Please note that these sites are run by users just like you so please be patient. If you do not get an immediate response to your question, it probably means that either no one knows the answer to your question or there are not many other users online. So please be patient and, if you have time, help other users by posting answers to any questions that you know the answer to.
Will NeoOffice be updated in the future?
Since this project is staffed entirely by volunteers and is funded entirely by donations, future updates will only happen if there are enough volunteers who donate their spare time and enough users who donate funds.
If you would like to volunteer time or donate funds to NeoOffice, please read our Donations page.
I found a bug in NeoOffice. Will it ever be fixed?
First, check if the bug has already been fixed by downloading and installing the latest NeoOffice patch.
If the latest patch does not fix your bug, file a bug report in Bugzilla. Your bug report should describe the bug in detail and should provide the steps to reproduce the bug. Also, if NeoOffice is crashing, provide the Mac OS X crash log as this really helps the developers locate the cause of crashes.
Please note that NeoOffice has all of the same bugs that are in OpenOffice.org. So if we find that the bug is an OpenOffice.org bug, most likely we will not fix the bug as we do not have enough volunteers or funds to fix OpenOffice.org bugs.
I have patches for NeoOffice. How can I contribute them?
Please read our instructions for submitting patches.
Since NeoOffice is distributed under the GNU General Public License (GPL), you can copy it as much as you like and give it to whomever you want provided that you copy the source along with the binaries.
Note that if you modify any of the NeoOffice code, you must release your modifications under the GPL. In other words, you cannot make proprietary modifications to NeoOffice and we aggressively enforce the terms of the GPL against anyone who does not GPL their modifications.
Also, since providing user support consumes much of our donations, there are some restrictions on when you can use the NeoOffice trademark. So, if you are selling NeoOffice or distributing your own custom NeoOffice builds, you must comply with the NeoOffice CD Distribution and Trademark Usage policy.
Using the full GPL ensures that anyone who makes improvements to NeoOffice will share them with the community.
Why is NeoOffice separate from OpenOffice.org?
When we started the NeoOffice project, our primary reason for being separate was that we did not like OpenOffice.org's SISSL license. However, now that the NeoOffice project has been active for a few years, license issues are no longer the primary reason that keeps us separate. The primary reason that we stay separate is that we can develop, release, and support a native Mac OS X office suite with much less time and money than we could if we worked within the OpenOffice.org project.
Why would running a separate project be so much more efficient than using OpenOffice.org's infrastructure? Basically, the reason is that OpenOffice.org's processes and infrastructure are designed to handle the tens (or maybe hundreds) of millions of users on three very different platforms. This is a huge job that requires a huge amount of infrastructure and processes. Furthermore, OpenOffice.org is paid for by Sun Microsystems so its paid staff are most concerned with completing whatever goals Sun Microsystems sets. In comparison, NeoOffice averages less than a million downloads per month and NeoOffice only runs on a platform that Sun Microsystems has rarely released software for. Because of these differences, any Mac OS X work must be coordinated with the OpenOffice.org paid staff to ensure that the Mac OS X work does not conflict with any work on the Windows, Linux, or Solaris platforms.
Both Ed Peterlin and Patrick Luby have worked within the OpenOffice.org project in the past and, in our experience, this coordination requires a significant amount of time. Since we are volunteers, we have very limited time and such coordination can quickly use up most of it. By running a separate project, we have eliminated most of this coordination time and have used that time savings on things that are important to NeoOffice users such as frequent bug fixes and responsive support.