Issue 84216 - Text flow goes astray in OLE writer tables
Summary: Text flow goes astray in OLE writer tables
Alias: None
Product: Impress
Classification: Application
Component: ui (show other issues)
Version: OOo 2.3
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-12-04 09:23 UTC by scagni
Modified: 2013-02-07 22:02 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Problems with text in tables in Impress (18.78 KB, application/vnd.sun.xml.impress)
2007-12-04 09:24 UTC, scagni
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description scagni 2007-12-04 09:23:12 UTC
I found another problem with using ole Writer objects containing tables in
impress presentations.
In the file attached you will find a table in an Impress file where text
visualization went wrong when I formatted some words in bold and changed a
little the table size.
As you can see some words appear over other , making the text completely
unreadable. If you double click on the object to open and edit it, text is shown
correctly, but when you exit from the edit operation it goes berserk again.
I fiddled around a bit with the object but could not figure out a sure way to
"cure" this problem. It really seems that the least editing of the OLE object
you do in Impress the highest are the chances of it not degenerating as in the
example file.
I also noticed that, even apart from the gravest cases like the one in the file,
very often text in a table pasted in Impress appear differently when the OLE
object is opended than when it is closed. For example it was easy to have the
text partially "hidden" beyond the right border of a cell (as if it was too long
to fit) while it looked correctly fitting when you open the same object.
All this of course makes editing tables in Impress a time consuming, rather
unpredictable and somewhat frustrating activity.
This does not depend on a SPECIFIC FONT, since is alas the same with Arial and
Times new roman as well as other fonts.
Thanks for the attention.
Comment 1 scagni 2007-12-04 09:24:17 UTC
Created attachment 50082 [details]
Problems with text in tables in Impress
Comment 2 kpalagin 2008-01-10 10:42:23 UTC
Confirming with 2.4.m241 on WinXP - as described.

please note that if you double-click OLE object and then exit you get correct 
display (at least with build m241).
Comment 3 scagni 2008-01-10 10:58:24 UTC
Do you mean with the writer table in the attached file here?
Alas, with OO231 right now I tried a lot of times to "exit" after opening the
object in as many ways I could think of (clicking somewhere else, pressing ESC
key, altogether closing the doc,....) but could not obtain a "correct display".
For example, the final "o" in "livello was always overimosed on the rectangular
characters following, while in truth there is even a space between them.
In general the wrong display was exactly the same after as many opening and
closing of the object without modifying anything as you want.
But perhaps I did not grasp the exact meaning of your writing?
Comment 4 kpalagin 2008-01-10 11:37:50 UTC
I ESCaped or clicked out (do not remember exactly) of the object.
Please try dev build from
Comment 5 scagni 2008-01-10 12:28:12 UTC
I see. I will try, but please consider that, although it could sound amateurish,
it is more difficult - or at least requires more effort - for me to try
development builds. 
I use OO everyday to work and the flow of bug reporting is just a byproduct of
the working process.
The business of downloading, installing, trying, and disinstalling devbuilds is
instead an independent effort that must be planned and pursued independently,
and I rarely have time for it.
I hope to be able to give some news before next week.
Comment 6 kpalagin 2008-01-10 12:56:15 UTC
Instead of trying dev build you could just wait for release, but that is 3 
month away (or some release candidate before that), so it is up to you to 
decide which rout to take.