Hi :)
It is great when it does work and yes it's really good to be able to be
highly responsive and adaptable to clients. It's certainly something that
LibreOffice strives for and that is one of the reasons i enjoy using it so
much.
When it doesn't work, even slightly it's all the more annoying because it's
so close and some of the issues that block it from being perfect are outside
of our control. MS tries to stack things in it's own favour (obviously) and
who wouldn't when profit is the main reason for producing anything?
Regard from
Tom :)
jdh111 wrote:
A client asked me the other day to send him an .rtf version
<snip />
I then opened the new .rtf file in LO: flawless.
My client, too, confirmed that the .rtf file was perfect for his purposes.
It felt good being able to help him with this.
<snip />
jdh
--
View this message in context:
http://nabble.documentfoundation.org/LO-3-4-3-Writer-cannot-handle-RTF-document-tp3485447p3496710.html
Sent from the Users mailing list archive at Nabble.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
- [libreoffice-users] RE: LO 3.4.3 Writer cannot handle RTF document (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.