How to Report Problems with NeoOffice

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 16:57, 12 December 2008 (edit)
Sardisson (Talk | contribs)
(Reporting Problems with NeoOffice - point to the bugzilla guide explicitly in this section)
← Previous diff
Revision as of 22:18, 24 February 2009 (edit) (undo)
( | contribs)
(Reporting Problems with NeoOffice - Changed references to filing a bug in Bugzilla to filing a bug in the forums.)
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 NeoOffice [http://bugzilla.neooffice.org/ Bugzilla]. You should first search to see if your bug has already been reported (is a "duplicate"); click "Query Bugs" and then "advanced query page" to search for a keyword you think might apply. (Make sure to select '''NeoOffice''' from the '''Project''' menu, since that menu defaults to '''NeoLight'''.) 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, and what happens next with your bug, please visit the [[Bugzilla Guide]].+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]].
-Additionally, there is a forum [http://trinity.neooffice.org/modules.php?name=Forums&file=viewforum&f=7 on trinity] to discuss problems. But your best bet is to use the bugzilla system so that the developers do not miss your bug or issue submission.+The forum [http://trinity.neooffice.org/modules.php?name=Forums&file=viewforum&f=7 on trinity] can also be used to discuss problems.
====Bugs in OpenOffice.org code==== ====Bugs in OpenOffice.org code====
If Patrick or another developer replies that the problem is with the underlying [[OpenOffice.org|OpenOffice.org]] code, report the problem in the OpenOffice.org IssueZilla to ensure the OpenOffice.org coders fix the problem! See [http://qa.openoffice.org/issue_handling/pre_submission.html 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<!-- (and NeoOffice/J 1.1 was equivalent to OpenOffice.org 1.1.4)-->. If Patrick or another developer replies that the problem is with the underlying [[OpenOffice.org|OpenOffice.org]] code, report the problem in the OpenOffice.org IssueZilla to ensure the OpenOffice.org coders fix the problem! See [http://qa.openoffice.org/issue_handling/pre_submission.html 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<!-- (and NeoOffice/J 1.1 was equivalent to OpenOffice.org 1.1.4)-->.
-After you file a bug in the OOo IssueZilla, please paste its URL into the comments of your NeoOffice Bugzilla report; the developers and QA will often follow the progress of the OOo bug.+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==== ====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 [http://bugzilla.abisource.com/enter_bug.cgi?product=libwpd libwpd Bugzilla]. 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 [http://bugzilla.abisource.com/enter_bug.cgi?product=libwpd libwpd Bugzilla].
-=== Bugzilla Guide ===+=== Bug Filing Guide ===
-We are developing a guide to filing a good bug in Bugzilla. If you have suggestions, please contribute on the [[Bugzilla_Guide|Guide to the NeoOffice Bugzilla]] page.+We are developing a guide to filing a good bug in the forums. If you have suggestions, please contribute on the [[Bugzilla_Guide|Guide to NeoOffice Bugs]] page.
{{botlangbarEN|[[Fr:Comment_rapporter_des_problèmes_rencontrés_avec_NeoOffice|Français]] [[De:Probleme_melden|Deutsch]] [[It:Come_segnalare_i_problemi_incontrati|Italiano]] [[Es:Como reportar problemas|Español]] [[nl:Hoe problemen met NeoOffice melden|Nederlands]]}} {{botlangbarEN|[[Fr:Comment_rapporter_des_problèmes_rencontrés_avec_NeoOffice|Français]] [[De:Probleme_melden|Deutsch]] [[It:Come_segnalare_i_problemi_incontrati|Italiano]] [[Es:Como reportar problemas|Español]] [[nl:Hoe problemen met NeoOffice melden|Nederlands]]}}
[[Category:NeoOffice]][[Category:Contributing]] [[Category:NeoOffice]][[Category:Contributing]]

Revision as of 22:18, 24 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

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 Bugzilla Guide.

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.


This article in other languages: Français Deutsch Italiano Español Nederlands
Personal tools