<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> <span class="fn">Justin L</span></a>
</span> changed
<a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Fileopen: DOC with Lock Tracking (Protect changes) opens in LO as read-only to unlock edit with password, instead of password to remove Protect"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132637">bug 132637</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;">Status</td>
<td>NEW
</td>
<td>ASSIGNED
</td>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
<td>jluth@mail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Fileopen: DOC with Lock Tracking (Protect changes) opens in LO as read-only to unlock edit with password, instead of password to remove Protect"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132637#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Fileopen: DOC with Lock Tracking (Protect changes) opens in LO as read-only to unlock edit with password, instead of password to remove Protect"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132637">bug 132637</a>
from <span class="vcard"><a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> <span class="fn">Justin L</span></a>
</span></b>
<pre>In Word 2003, Lock.doc opens in read-write mode.
In Word 2013, it opens in read-only mode. You need to View - Edit document to
get started (but of course with no password).
So, the question is how far do we want to take this for the DOC format?
Currently, when LO round-trips the file, ALL of this information is lost.
Laszlo has implemented most of this for DOCX - import and export. But is it
worth doing it for the old DOC format? Opening up as read-only (like DOCX)
seems very stupid to me, so my recommendation would be to just ignore the
password completely in this case (since it is lost anyway) and open in
read-write mode (just like sensible Word 2003). Otherwise we also need to map
it to the correct document security functions, and export it. That seems like
unnecessary effort at this stage in the game.
[For completeness, I also looked at the fourth lock option, which allow
comments only. I don't think Writer has support for that, so it should be
treated the same as a read-only protection - requiring the password to unlock
to edit.]
In all cases - including read-only, all of the protection is lost just by
round-tripping. So if a password is defeating you, just save-as and reload - no
password, no protection (except forms, which protects the section, but without
a password).
Proposed fix (which just ignores LockRev/password) at
<a href="https://gerrit.libreoffice.org/c/core/+/93551">https://gerrit.libreoffice.org/c/core/+/93551</a></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>