<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Save a Copy"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142476">142476</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Save a Copy
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>7.0.5.2 release
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Writer
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>luke.kendall@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>Steps:
1) Open a file.txt
2) Write some stuff. Maybe even use formatting that .txt format doesn't
support.
3) Save the file. (Leave it as plain text.)
4) Save a Copy and select HTML format.
Result:
Writer fails to change the extension to .html and instead offers the choice to
overwrite the existing file. This ignores the user's intention of saving an
alternate format version of the file.
Writer then changes the file type from what the user selected (e.g. HTML) back
to .txt.
Until the user manually deletes the file extension from the filename in the
Save a Copy text field, you cannot save the file as the file type you're trying
to.
This bug may relate to
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Saving file with a different LO-recognized file extension does not add correct extension"
href="show_bug.cgi?id=111070">https://bugs.documentfoundation.org/show_bug.cgi?id=111070</a>, but I think this
may be a different use case.
Note that this happens on Linux.
The reason for wanting to do this slightly odd operation is to prepare clean
source text for creating simple HTML. Using some formatting is a convenient
reminder to apply similar formatting in the target environment.
(Writer's HTML format is far too complex and unwieldy for many web platforms to
use as input markup - e.g. for Wordpress, or MailerLite newsletters, or blogs.
I mention this not to complain but merely to explain why the use case makes
sense. Writer is an excellent editor for plain text and most other formats, but
the underlying representation can cause problems due to the complexity caused
by 1) editing operations, and 2) by direct formatting. Plain text does not
capture any of those structural complexities from either of those causes.)</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>