For example, in LibreOffice 3.4.3 Impress, create a dashed line and save it
in MS PowerPoint 97 format. Close then reopen it. When I did that just now
under Windows 7 x64, the line style was lost and it displayed solid.
just checked it in both LO 3.3.4 and 3.4.3.'97 format (ie,ppt) showing the
dashed line as dashed line when opened in LO.when the file is saved into
.pptx,the dashed line is getting converted into a solid one.
so,for me,'97 format is working properly.
anybody else having difficulty with '97 format????????
regards,
On 11 September 2011 21:01, Spencer Graves <spencer.graves@prodsyse.com>wrote:
For me, the answer is NOT obvious, because of (a) the occasional
incompatibilities and (b) the things that are easier in MS Office than
LibreOffice. I've had problems with LibreOffice where I save something in
*.doc format or *.ppt and reopen it, and it's different. Also, I've been
using Open Office / LibreOffice regularly for 1.5 years now, and I still
cannot find how to control bullets and numbering as easily as I could with
MS Office. For any document I have to send to a collaborator who uses MS
Office, I need to keep it primarily in the MS format to increase the chances
that I will at least know what is being changed without warning!
For example, in LibreOffice 3.4.3 Impress, create a dashed line and
save it in MS PowerPoint 97 format. Close then reopen it. When I did that
just now under Windows 7 x64, the line style was lost and it displayed
solid. If I do NOT have to share it with an MS Office user, then I keep it
in Open Office format. Otherwise, I must convert at some point to MS
format, and I should do that regularly at least until I identify at least
one incompatibility problem.
Best Wishes,
Spencer
On 9/11/2011 7:54 AM, Tinkerer wrote:
The answer is obvious. Save in odf and get used to using odf.
When there is a requirement to use an MS suffix,use Save As to do a copy
in
doc or docx, but keep your copy in odf.
Tink.
--
View this message in context: http://nabble.**
documentfoundation.org/Should-**LibreOffice-even-support-**
Microsoft-secret-formats-**tp3325743p3326996.html<http://nabble.documentfoundation.org/Should-LibreOffice-even-support-Microsoft-secret-formats-tp3325743p3326996.html>
Sent from the Users mailing list archive at Nabble.com.
--
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
--
Dr soumalya ray <http://drsoumalya.blogspot.com> <drsoumalya@gmail.com>
MBBS,MD(PGT-C.Medicine),Ex-HousePhysician(Medicine)
Skype: som3776 | Twitter: @docbkp <http://twitter.com/docbkp>
--
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
- Re: [libreoffice-users] Should LibreOffice even support Microsoft secret formats? (continued)
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.