So quite apparently, the problem is in MSW2007, where it opens the files to
the last version prior to the changes, and you then have to deliberately
display the final version, and the only way to get a clean version in
MSW2007 is apparently to accept the changes there.
I've now tried it a few times, but MSW2007 stubbornly keeps opening up docs
in which all changes were accepted in LibreOffice (and I just went to 3.5),
to display showing markup, which you then have to either switch off, or
accept all the changes in order to display a clean version in MSW2007.
In a collaboration like I'm having it means that in practice I must accept
the changes twice, once in LO, and then once again in MSW2007, before I
hand it off to colleagues using MSW2007
On Sun, Feb 19, 2012 at 7:56 PM, Brian Barker <b.m.barker@btinternet.com>wrote:
At 19:33 19/02/2012 -0500, Rogier F. van Vlissingen wrote:
During a book project where some are using LibreOffice and some are using
MSWord, we're noticing that if corrections are processed in Libre office
3.4.4 and the file looks totally clean, when you open it up in Word, they
are still there, and you end up having to delete them a second time.
What settings are you using for tracking changes? If you have Edit |
Changes > | Record ticked in LibreOffice, you will be preserving the
original along with the changes. If you have Edit | Changes > | Show
unticked, you will see just the edited version and not the hidden originals
(so your document will look "clean").
When you open a document that includes tracked changes in Word, the
original items will be there along with the changes. What you see will
depend on your Review setting in Word. In particular, if you have this set
to Original, you will not see any of the changes.
o If you don't want to track changes, untick Edit | Changes > | Record in
LibreOffice.
o If you want to track changes but then want to see in Word what you have
done, change the Review setting in Word.
I trust this helps.
Brian Barker
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.**
org <users%2Bhelp@global.libreoffice.org>
Problems? http://www.libreoffice.org/**get-help/mailing-lists/how-to-**
unsubscribe/<http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/>
Posting guidelines + more: http://wiki.**documentfoundation.org/**
Netiquette <http://wiki.documentfoundation.org/Netiquette>
List archive:
http://listarchives.**libreoffice.org/global/users/<http://listarchives.libreoffice.org/global/users/>
All messages sent to this list will be publicly archived and cannot be
deleted
--
Rogier F. van Vlissingen, NY
(917) 549 0959
www.acimnthomas.com
www.securitybitbybit.com
www.dabxdemandsidesolutions.com <http://www.dabxenergymanagement.com>
Making Green Power financially rewarding
** Independent Representative **
*sign up for power here www.napower.com/124436*
*sign up for American wind here
www.napower.com/132240/renewable-<http://www.napower.com/132240/renewable-wind>
**wind <http://www.napower.com/132240/renewable/wind>*
*
*
And grow some glutathione while you're at it:
http://vliscony.max4u.com
--
For unsubscribe instructions e-mail to: users+help@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.