<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><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#c10">Comment # 10</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 <span class="vcard"><a class="email" href="mailto:robert@prino.org" title="robert@prino.org">robert@prino.org</a>
</span></b>
<pre>(In reply to Telesto from <a href="show_bug.cgi?id=135079#c7">comment #7</a>)
<span class="quote">> (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</span >
There is very obviously no hard and fast rule to classify "bug(s) like these",
but what confidence does it instil in people if even a single one A4-sized
document that only uses the most basic of RTF features cannot be rendered
correctly in Writer.
Hell, if it uses a font that's not on the system, why not open a pop-up that
asks the user which font to substitute. I still use the Word XP freebie that
came with my old AD 2003 PC, and I've set it up to show me a pop-up whenever I
open something non-.DOC. How hard would it be to add a similar feature to
Writer, when opening a non-.ODT format file, with a warning that it may not
render correctly, just as there is one when saving in non-.ODT formats?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>