|
|
How to Report Problems with NeoOffice
From NeoWiki
| Revision as of 22:18, 24 February 2009 (edit) ( | contribs) (→Reporting Problems with NeoOffice - Changed references to filing a bug in Bugzilla to filing a bug in the forums.) ← Previous diff |
Revision as of 17:51, 25 February 2009 (edit) (undo) ( | contribs) m (Changed one reference to Bugzilla guide) Next diff → |
||
| Line 16: | Line 16: | ||
| ==Reporting Problems with NeoOffice== | ==Reporting Problems with NeoOffice== | ||
| - | If you want to report problems, please submit them to the [http://trinity.neooffice.org/modules.php?name=Forums NeoOffice Support forum]. For more detailed information about how to properly report a bug, attach a crash log, sample of a hang, or problematic document to a bug post, and what happens next with your bug, please visit the [[ | + | If you want to report problems, please submit them to the [http://trinity.neooffice.org/modules.php?name=Forums NeoOffice Support forum]. For more detailed information about how to properly report a bug, attach a crash log, sample of a hang, or problematic document to a bug post, and what happens next with your bug, please visit the [[Bugzilla_Guide|Guide to NeoOffice Bugs]]. |
| The forum [http://trinity.neooffice.org/modules.php?name=Forums&file=viewforum&f=7 on trinity] can also be used to discuss problems. | The forum [http://trinity.neooffice.org/modules.php?name=Forums&file=viewforum&f=7 on trinity] can also be used to discuss problems. | ||
Revision as of 17:51, 25 February 2009
Contents |
Known Issues with NeoOffice
Patrick Luby maintains a brief list of "known problems." That page covers features found in OpenOffice.org that are still missing from NeoOffice.
Other known issues with NeoOffice can be found in
- NeoOffice Installation Issues - issues with installation, patch updates, and first launch of the application
- Troubleshooting Tips - causes of common Mac OS X-related problems that affect NeoOffice
- NeoOffice Bugzilla (be sure to select NeoOffice from the Project menu when querying the bug database)
- NeoOffice Support forum
- NeoOffice Testing forum
Please search for your issues before posting to the Support forum. The Testing forum is used for providing feedback on new patches and alpha and beta versions of NeoOffice; issues with released versions are handled in the Support forum.
N.B. NeoOffice shares all the bugs and limitations of OpenOffice.org, so any issue in the OpenOffice.org IssueZilla will also be a known issue with NeoOffice.
Reporting Problems with NeoOffice
If you want to report problems, please submit them to the NeoOffice Support forum. For more detailed information about how to properly report a bug, attach a crash log, sample of a hang, or problematic document to a bug post, and what happens next with your bug, please visit the Guide to NeoOffice Bugs.
The forum on trinity can also be used to discuss problems.
Bugs in OpenOffice.org code
If Patrick or another developer replies that the problem is with the underlying OpenOffice.org code, report the problem in the OpenOffice.org IssueZilla to ensure the OpenOffice.org coders fix the problem! See here for details. For purposes of the Found in version: field in IssueZilla, NeoOffice 2.1 is the equivalent of OpenOffice.org 2.1 and NeoOffice 2.2.1 is the equivalent of OpenOffice.org 2.2.1.
After you file a bug in the OOo IssueZilla, please paste its URL into the comments of your NeoOffice forum post; the developers and QA will often follow the progress of the OOo bug.
Bugs in WordPerfect import
Similarly, if you have an issue with the result of the import of a WordPerfect document—bold is missing, table messed up, etc.—this is a problem with the libwpd and WriterPerfect libraries and should be reported in the libwpd Bugzilla.
Bug Filing Guide
We are developing a guide to filing a good bug in the forums. If you have suggestions, please contribute on the Guide to NeoOffice Bugs page.
