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


Hi :)
The older MS formats (Doc, Xls etc) have stopped changing around so much in
the MS Office 2007, 2010, 2013 and 365 releases, ie since they stopped
being the default formats in MS Office.  Before 2007 the older MS formats
were a bit of a nightmare but for the last 7 or more years they have been
quite stable.

MS are apparently focussing on developing their newer format more, which
might be what makes it so problematic at the moment.  While there is a
"strict" format that is possible to use in MS Office 2013 it is not the
default.  To use it people have to use
File - "Save As ..."
and that seem to be beyond the skill level of most MS Office users.  Also
have you actually tried using "strict" rather than the various
"transitional" defaults?  When you try to open a "strict" OOXML file then
2010 and 2007 pop-up an alert warning allegeding that the file is a
security risk and probably contains malware.  This might be a left-over
from when non-MS programs were able to implement the OOXML ISO format
before MS were able to implement it themselves!  Since then non-MS programs
and suites have had to try to add-in compatibility with all the proprietary
or binary blobs and stuff that isn't in their ISO specification.

The Doc, Xls and other older formats are only good for file-sharing right
now.  The specification is not properly documented so creating programs to
read it in the future is unlikely.  Similarly with the Rtf format
apparently.

Document storage is safer if ODF is used but for sharing and working with
people right now the older MS format seems to be about the only one that
everyone, even MS Office, can read fairly consistently.
Regards from
Tom :)



On 14 September 2014 04:04, Owen Genat <owen.genat@gmail.com> wrote:

Luuk wrote
They talk about 'Office 2007', not about the versions after that one....

The article was written late 2010. MS Office 2010 is mentioned (four
times).


Luuk wrote
The last 2 years of revisions (2nd link) are all "No changes to the
meaning...." effectively making the specs old, and making it hard to
make a piece of software capable of reading/writing office 2013
documents.

[MS-OE376] is a document referencing the standard (EMCA-376 4th Ed. /
ISO/IEC 29500:2012 3rd Ed.). It is mainly notes with some examples designed
to accompany the specification. Naturally it is not going to change that
much as the specification is what contains the technical detail.

Unfortunately, none of this is going to assist with the original (or
follow-up) query.

Best wishes, Owen.



--
View this message in context:
http://nabble.documentfoundation.org/Table-presented-totally-wrong-tp4121993p4122207.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



-- 
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.