[Libreoffice-bugs] [Bug 49046] FORMATTING: Incorrect Display of Bullets Points, Table Borders and Heading Underlining when Reading doc/docx Documents
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun May 13 02:21:54 PDT 2012
--- Comment #15 from Roman Eisele <bugs at eikota.de> 2012-05-13 02:21:54 PDT ---
I am sorry if my remark (comment #13) has irritated you; I did not mean to
criticize you! On the contrary, your bug report is a good sample of accuracy
and care; I (and I think I can say also the other QA people) would be happy if
all or at least most bug reports would be so clear, well-written and
well-documented with example files and screenshots.
I also completely understand that you have taken all care to make up a good and
precise bug report, and I appreciate the work this must have made for you very
> Are the range of documents and/or output I uploaded useful,
> or just overkill?
The count of attachments may be a matter of taste, but again, most bug reports
have not enough documentation (sample files, screenshots ...), so I think that
too much is always better than not enough.
There is just a single point I wanted to make with my remark. If we have three
issues in one report, the handling of this report becomes a bit harder. For
example, I said that issue (1) in your report is more or less identical to bug
34814. This is not intented as criticism of your report (I know it is hard to
find specific issues or duplicates in this database!); it is just an
observation which, if right, makes the handling of the specific issue far
easier: if a new report is about a known and already well-documented issue, I
can just mark the new report as a duplicate of the old one. This allows to go
on fast and to concentrate on the new or not yet identified issues ... But if
there is more than one issue in a report, I can't use this easy solution, as
marking the report as a duplicate would hide the other, still valid issues.
There are more similar problems in the further process. When a developer has
fixed a bug, he (or someone else) marks the bug report as RESOLVED/FIXED; but
if the report contains more than one issue, it is unlikely that all issues are
fixed at once. Therefore, the 'Status' field, which is important for finding
the bugs needing confirmation and bug fixes, becomes difficult when there is
more than one issue in a bug report.
Therefore, your report is already (as said above) a good sample of accuracy and
very helpful; but if you report more bugs in future, the reports would be even
more helpful if you could make a separate bug report for each issue. I know
that this means even more work for you, and feel sorry for that, but it would
help a lot to prevent us from making mistakes, overseeing issues, etc.
> It is a bit of a pain having to load documents up one at a time,
> and most of the up loaded documents go with all the multiple "bugs".
You are right, addding attachments is annoying in this bugtracker, and adding
one attachment more than once is even more annoying. You can, of course, try to
upload an attachment only to one bug report and then just make references in
the text of the next reports to it, without adding the attachment again. For
example, it should be posible to link your 1st screenshot for this report via
just typing 'attachment 60432' (you see the number of an already added
attachment when you move the mouse over or click on the desired attachment in
the 'Attachments' table at the top of a bug report), or via copying the link
from the same 'Attachments' table. In this way, you can add an attachment only
once, but link it from the text of other bug reports. This is still not easy to
use, but maybe a bit easier/faster.
Thank you very much again for your report and your patience!
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Libreoffice-bugs