Hi Milos,
Milos Sramek schrieb:
Hi,
thank you all for your answers. In fact I take part in a larger scale
testing of interoperability of formats, since open source software is
currently considered by Slovak administration as and alternative to the
standard MS stuff.
Then you might be interested in the work of
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=oic
http://www.ecis.eu/intraoperability/
http://www.fokus.fraunhofer.de/en/elan/publikationen/infomaterial/white_paper/documentinteroperability/index.html
And Plugfest
http://plugfest.opendocsociety.org/doku.php?id=start
Do you want to host a Plugfest?
If everything goes really well, there will be a
transition period when open source (say, LO) and proprietary
applications will be used in parallel and documents in various formats
will be interchanged. Therefore, we want to understand the situation and
prepare a guide (use this feature, avoid that feature), which would help
in creating documents which can safely be opened by the other tool.
I'm very interested in a comparison. Perhaps you can start a page on the
Wiki to collect all the problems?
I am aware of the fact that "open" standards like OOXML, which are
more-or-less in hands of only one company (even if it is an ISO
standard) will always be a problem. Simultaneously, MS support of ODF
will probably never be perfect. But a state administration does not need
complex features and formatting - therefore we want to prepare the guide
which would tell them, what is safe to use.
The discrepancies between rendering of odt and docx files by the other
applications are really big. Jean-Francois pointed to "Styles. Or lack
of. " I've heard this also from other people. So, is it really possible,
that a program, when opening a document, applies some additional
formating, which can change appearance in comparison to the original?
Should this be considered as a bug, or is it a feature (which can be
eventually switched off) ?
There are some features, which are available in one format and not in
the other. Therefore it is no good idea to keep both formats parallel.
I prefer ODF ;)
The support for ODF in MS Office 2013 is already good. MS has an
overview, what is not supported yet.
http://msdn.microsoft.com/en-us/library/jj680136%28v=office.12%29.aspx
As an example I created a simple document in LO40 (MS2013), stored as
odt (docx) and opened and printed in MS2013 (LO40) :
http://ubuntuone.com/1lkbhsT9veT24B9a9jPUpr
In the pdf (overlay of rendering in bork applications) you can see that
the major difference resides in interline spacing. Do you have and idea,
where is the reason?
Yes :) MS Word adds space after the paragraph in a list in docx. In Word
open the context menu of a paragraph of the list. Click on 'Paragraph'.
You can see, that Spacing after and you will find a checkbox for not
adding the space. Let read MS Word the ODF 1.2 version of your document,
you will notice a better layout.
ODF 1.1 and OOXML transitional were used, the used fonts were available
on both computers. Line spacing does not seem to be a big issue, but one
can see inconsistent line spacing nearly everywhere. So, from the point
of view of interoperability it is perhaps a blocker, since the
displacement is sometimes a couple of lines per page.
Do not use ODF 1.1. ODF 1.1 has no namespace for formulas in Calc.
Therefore Excel do not import the formulas, but only the values. Use ODF
1.2 and MS Office 2013. If you will go with ODF, one Windows PC with MS
Office 2013 should be sufficient to analyze and transform documents with
broken layout.
If this is a bug in LO I will file a bug in its Bugzilla. If it is a bug
in MS2013, we will ask MS to correct that (there is a guy from Microsoft
in our team who promised to do that). If they do not correct it, it will
be a nice argument against using MSO at all.
It need not be a bug, but different default settings and missing features.
I will be grateful for each advice on how to analyze the problem and how
to sort out the reason.
If you provide examples, it is much easier to find the reasons.
Missing feature is a large problem. Very difficult is for example the
handling of tables. Word knows "floating tables", which LO does not.
Therefore LO converts a "floating table" by putting as normal table into
a frame. But a frame cannot extend a page and therefore the table does
not break to the next page. But in Word this table breaks to the next page.
Similar problems exists with anchor and wrap settings of objects.
Kind regards
Regina
--
To unsubscribe e-mail to: [email protected]
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
