Michele Zarri wrote:
I do not have the number, but I know that this is a well known problem. I
have often had problems with images anchoring with documents written in MS
Word and opened with OOo so I expect the problem to exist also in the
opposite direction. My understanding is that the problem is with the way MS
Word manages the anchoring of figures. For example, MS Word does not allow
anchoring to or as character, so whenever this type of anchoring is defined
in a OOo document, the converter has to take some kind of decision on
how to "translate" this in a way MS word understands it. So I do not expect
a resolution any time soon.
Although I knew there are problems with images going from
Word->OOo or OOo->Word, I haven't been paying attention to the
details. From my limited sample (and Andrew's experience), it
seems to be the *frames* that are the problem, not the images
themselves, but I would have to test some more to be sure.
I hope someone else might know some issue numbers. I'll ask at
Docs as well.
On the other hand I wonder how common the scenario is. Besides the use case
Andrew presented, I expect that the reader of the OOo user guide will have
OOo installed and that OOo is used to view the document. If the anchoring
does not work, then there is always the pdf version that, as far as I am
aware does not suffer from this issue.
In summary I do not think we should worry too much about this.
I was thinking about the more general case: many users will be
trying to go between Word and OOo (one direction or the other or
both) with the documents they produce, and we should not only
warn them about the problem but suggest a workaround if possible.
--Jean
