[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libreoffice-users] Re: rtf import broken in 3.5.1?
[Thread Prev] | [Thread Next]
- Subject: Re: [libreoffice-users] Re: rtf import broken in 3.5.1?
- From: Tom Davies <tomdavies04@yahoo.co.uk>
- Date: Fri, 27 Apr 2012 11:30:23 +0100 (BST)
- To: users@global.libreoffice.org
Hi :)
It takes a lot of digging to find stuff like that. Also it's a bit negative and "old" so people ignore it. It's better to join in with something positive and fairly new
http://www.fsf.org/campaigns/opendocument
From a quick google search i found the Pdf of the Novell complaint; in Rtf format (click on the link in note 63 to download the pdf document)
http://en.wikipedia.org/wiki/Rich_Text_Format#cite_note-63
or in html form
http://gl.scofacts.org/gl-20041115214025458.html
Perhaps GrokLaw has a note of the outcomes?
Pointing out that MS may have lost a lot of legal cases about "Anti-trust" and questionable business practices seldom sways people's minds. Bill Gates is now seen as a philanthropist due to investing in charitable concerns that generate enough profit to at least be self-sustainable. Try reading "The Emperor's New Clothes" (folktale) and "The Prince" (politic satire(?) by Machiavelli).
Personally i think the best way to turn the tanker around is to go with it but keep gently nudging. Introduce people to LibreOffice and Google-docs or whichever suits a person and their machine better. Show how it can support MS formats but is better with the better (native) format (ODF). Direct action from groups such as FSF is vital too but there needs to be a softer approach from other people at the same time to make sure the infrastructure is there as things start to change. People can't move from Rtf, DocX or even Doc until they are familiar with and comfortable with programs other than MS Office.
The original question was about converting Rtf to something else? If so this link might help
http://www.gnu.org/software/unrtf/unrtf.html
Regards from
Tom :)
--- On Fri, 27/4/12, Milos Sramek <sramek.milos@gmail.com> wrote:
From: Milos Sramek <sramek.milos@gmail.com>
Subject: Re: [libreoffice-users] Re: rtf import broken in 3.5.1?
To: users@global.libreoffice.org
Date: Friday, 27 April, 2012, 8:13
Dňa 26.04.2012 21:28, Tom Davies wrote / napísal(a):
> Hi :)
> What!! An "agreed" 'Open' Standard that MS never quite implemented in the way they had promised but still managed to push as the unifying standard that all other companies had to follow. The format they promised would have long term support so that historical archives and such could reliably store documents for the long-term future in much the way that books have lasted. The one that no-one other than MS (hmm, not even MS) managed to implement because MS never quite got around to publishing how they had messed up the format in any particular release. The format that resulted in court actions which MS apparently lost. The one that MS is quietly dropping support for and not developing any further so that all existing problems remain.
Dear Tom,
do you have any references to those court cases? Sounds very interesting. RTF is in Slovakia one of the officialy approved standards to be used by public administration (besides pdf, odf and HTML). Of course, since MS is everywhere and everybody uses RTF. Information about those court trials would be a nice argument against RTF, the compatibility of which in LO/OO/OOO is really pain. This would show why is it so.
Milos
>
> Luckily we have all learned our lesson and anyway MS wouldn't try to fool us the same way again, right? lol ;)
> Regards from
> Tom :)
>
>
>
> --- On Thu, 26/4/12, Andreas Säger<villeroy@t-online.de> wrote:
>
> From: Andreas Säger<villeroy@t-online.de>
> Subject: [libreoffice-users] Re: rtf import broken in 3.5.1?
> To: users@global.libreoffice.org
> Date: Thursday, 26 April, 2012, 20:06
>
> RTF never really worked in OOo nor LibO and there are reasons why:
> http://diaryproducts.net/for/geek/microsoft_rtf_specification_nightmare
>
> --
> View this message in context: http://nabble.documentfoundation.org/rtf-import-broken-in-3-5-1-tp3877445p3942245.html
> Sent from the Users mailing list archive at Nabble.com.
>
-- email& jabber: sramek.milos@gmail.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
--
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
| Re: [libreoffice-users] Re: rtf import broken in 3.5.1? | Ma Xiaojun <damage3025@gmail.com> |
| Re: [libreoffice-users] Re: rtf import broken in 3.5.1? | Milos Sramek <sramek.milos@gmail.com> |
- Prev by Date: Re: [libreoffice-users] quickstarter in Windows
- Next by Date: Re: [libreoffice-users] quickstarter in Windows
- Previous by thread: [libreoffice-users] Re: rtf import broken in 3.5.1?
- Next by thread: Re: [libreoffice-users] Re: rtf import broken in 3.5.1?
- Index(es):
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 GNU Lesser General Public License (LGPLv3). "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.