Hi,
On 09.10.2014 23:53, Regina Henschel wrote:
(1)
I became aware of the problem with
https://issues.oasis-open.org/browse/OFFICE-3864. In the meantime the
developer found another way to track, whether the shape has "complex"
content. So the request for a new attribute has been (or will be?)
canceled. But he is not really satisfied with the solution.
(2)
When a custom shape contains a table then LibreOffice currently writes
e.g.
<draw:custom-shape ...>
<table:table...>
...
</table>
<text:p ...>
...
</text:p>
<draw:enhanced-geometry ...>
...
</draw:custom-shape>
This solution is not valid in ODF1.2. A construction of the kind
<draw:custom-shape>
...
<text:p>
<draw:frame>
<table:table>
...
</table:table>
</draw:frame>
</text:p>
...
</draw:custom-shape>
would be valid.
In normal texts <table:table> and <text:p> are both allowed as child
of <office:text>. Here a <table:table> element in a <draw:frame> has a
different meaning, because its outside the text flow. But inside a
shape the table is already outside the text flow and putting it into a
<draw:frame> would not add restrictions.
I would prefer this - it expresses what happens.
I see more problems in this solution being a 'special' solution for draw
objects in Writer only - because AFAIK (understood) it associates a draw
shape (SdrShape) with a writer frame pretty much directly internal. This
has some consequences:
- Will only work in Writer
- ODF parts describing shapes using this will not be copyable to ODF of
other apps
- copy/paste of those shapes between apps will be (very) problematic
Some years ago there was the general idea to use writer incarnations
instead of the EditEngine in general for text in text objects, with the
main goal to allow complex text content there. I would definitely prefer
such a more general solution which would work out of the box in all apps
with all shapes and would use a unified solutiuon for ODF (whichever
one, but a single one). I see the motivation to do a quick solution for
the problem which needs to be solved, but I recommend to think about the
more general possible solution. In the mid to long term this solution
may be in the way later.
From this perspective the most urgent requirement from my POV is that
the ODF solution should be usable for this more common case in the
future, too. It should/must be usable in general to embed Writer-styled
text to draw objects in all apps.
Just my 2 cents...
Sincerely,
Armin
The comment of the developer is in
https://bugs.freedesktop.org/show_bug.cgi?id=84714#c1. He suggests to
write loext:table till the proposal of <table:table> as child of
<draw:custom-shape> is accepted. He dislikes "fake" use of
<text:p><draw:frame> as wrapper. In addition he mentioned in the
discussion [4] on the mailing list, that because LibreOffice (and same
OpenOffice) use a SAX parser, it can not easily be detected, whether
elements exist or not exists in a sub-tree of the XML tree. I'm not
able to judge this.
Is the idea to allow <table:table> as child of <draw:custom-shape> and
other shapes worth supporting?
Kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
ALG
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
