<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Make clear distinction on differences between "Export" and "Save As", and move items in those filters accordingly"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=116703">bug 116703</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>vstuart.foote@utsa.edu
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Make clear distinction on differences between "Export" and "Save As", and move items in those filters accordingly"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=116703#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Make clear distinction on differences between "Export" and "Save As", and move items in those filters accordingly"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=116703">bug 116703</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>Agree with Mike and Regina regards distinction to be made between what are
Export formats and what are Save-as.
The distinction here is less an issue of UX and Design and more an issue of ESC
and project management. If setting bounds (i.e. making distinctions in what
gets first-class effort) helps to focus dev efforts and the QA process it is a
good thing.
It can go too far, take GIMP XCF for example, but making the distinction helps
to constrain project scope. I've long held the subversive view that OOXML
should be an Export format, concentrate on ODF and SVG ;-)
IMHO citing HTML was just an unfortunate example. The Writer Web module is a
WYSIWYG mess held over from HTML 4.0 transitional with no support for inline
CSS nor any active content, essentially abandoned in place, with no movement on
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Writer Web -- rework HTML export and import filters to use HTML 5 and inline CSS3 styles"
href="show_bug.cgi?id=95861">bug 95861</a>. And the supporting Web wizard was stripped out at 5.4 (bug
99967)--good riddance.</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>