<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Formatting of simple .RTF one page A4 document completely screwed up" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135079#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Formatting of simple .RTF one page A4 document completely screwed up" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135079">bug 135079</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to robert from <a href="show_bug.cgi?id=135079#c4">comment #4</a>) > Stop adding new "new shiny and whiter than white" features to the suite, and > concentrate on removing bug like these, you know, that 80/20 rule! People > needing the most complicated functions work in environments where the price > of an office suite is 0.001% of their daily turnover, and nobody gives an > (fill in your favourite expletive) about it! -> For my curiosity: is there also a rule where to start with 'bug like these'. There are a quite a number of those, sadly, IMHO (not talking about RTF specifically) So is there also a rule on how to set priority's. All those bug more or less 'trivial' in some way. Don't think that RTF is the most used format these day's (but of course depending on system; user case etc). So rather hard to define what's important or not. Especially with a suite with quite some functionality FWIW: on the RTF format: <a href="https://bugs.documentfoundation.org/showdependencytree.cgi?id=81234&hide_resolved=1">https://bugs.documentfoundation.org/showdependencytree.cgi?id=81234&hide_resolved=1</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>