Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index




Last time I had a read-only document, I used Save As and made sure it was not saved as read-only. You have to use a different file name to get it to work, or at least it did the last time I needed to do that. I think that was during the 4.0.4 or .5 version of LO.



On 02/19/2014 12:04 PM, edo1 wrote:
I saved a small (14 page) styled part of a large project as read-only to
protect
against accidents while I did something else. Later wanting to check a
style, I
unchecked read-only and reopened the file. Yet it still opens as read-only
and
"styles and formatting" is grayed out. Does anyone know how this can happen
and how I can prevent it?

The best I could do was copy the contents into a new file from which I could
retrieve the styles. That work-around will be a great pain with the rest of
the
project. I'm running LO 4.2.0.4 in Win7 x64. Thanks for any help! - edo1



--
View this message in context: http://nabble.documentfoundation.org/read-only-problem-tp4097968.html
Sent from the Users mailing list archive at Nabble.com.



--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.