Issue 582 - External framed graphic/text box spacing imported as internal spacing
Summary: External framed graphic/text box spacing imported as internal spacing
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 619
Hardware: PC Windows ME
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-21 21:59 UTC by issues@www
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

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


Attachments
word document (20.00 KB, application/octet-stream)
2003-12-06 14:52 UTC, issues@www
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2001-03-21 21:59:29 UTC
the attached document exhibits import problems.

the original (word) version shows the logo, top right, as white text in a black 
box with an inset white border.

when loaded into OOo 619:

1) the white box is absent - this appears to be because the white bordered 
rectangle is not imported
2) the frame associated with the logo appears to have been created witha "no 
fill" background; whereas the word frame appears to be black background
3) this is curious: The word box says it is "exactly 4.02cm" wide. In fact it 
appears to measure 4.75cm when you print out the original.  the OOo version is 
4.02cm wide but it is different from the version imported. (I can't see why the 
word version is wider than it says it is)
Comment 1 issues@www 2001-03-21 22:00:12 UTC
Created attachment 115 [details]
word document
Comment 2 stefan.baltzer 2001-04-03 13:18:13 UTC
Reassigned to Michael Ruess
Comment 3 michael.ruess 2001-04-03 17:01:38 UTC
To aspect...
1) This is a real Bug, I created a new one here so that the developer will not 
be conused by the other stuff which is inside this one. It is entered in 
Issuezilla with number #640.
2) That´s a bit strange in Word. Word stores the background color of a 
frame internally as the background of the paragraphs inside it. This is good to 
see when you have a big frame in Word with only one paragraph. Assign a 
background color to the frame and what you get is a whole black frame. So you 
see, that there is nothing we could change there which makes sense.
3) This is because Word and Writer have a different behaviour when frames have a 
spacing to the left or right. Word also fills the spacing to the wrapping text 
with the background color, Writer does not. We here think, that the way Writer 
it does, is the better one, because if you want a spacing between a frame and 
text, you don´t want it colored.

*** This issue has been marked as a duplicate of 640 ***
Comment 4 caolanm 2001-04-04 12:01:10 UTC
We do actually have another problem here. Looking at this closely we are
importing the "distance from text feature" of word as our "spacing" feature, but
our spacing feature is for the distance from inside the frame to the text inside
the frame, while word's is actually the distance from outside the frame to the
containing text, i.e. our "Borders setting feature". Set them to 0 in word and
the internal space remains while the surrounding text touches the frame

With this frame in word I cannot change that distance internally from the text
to the edge of the frame. The internal box that the text is clipped into is
exactly the size as reported as the dialog, so thats what the size relates to
but there is additional space that remains unaccounted for outside this
textclipping box. Perhaps this is a hardcoded default. And related to this is
the sad story that exporting one of our text frames to word and then attempting
to edit its properties causes word to crash!

So i'll call this one a bug to change our incorrect spacing import from internal
to external and to examine this seemingly hardcoded internal spacing. And see if
this misconception is why our exported boxes crash word on edit.

Note that this particular variety of textbox no longer exists in the standard ui
of word 2000, on choosing insert textbox now you get the new better varient. I
believe it only appears in legacy documents imported from earlier versions, this
sort of mess is perhaps why ms dropped them in favour of the new textboxes.


Comment 5 caolanm 2001-04-04 12:02:26 UTC
Reassign this to myself.

jonathan: as a matter of interest how did you create this document ? Am I
correct in my belief that its created in an earlier version of word and then
saved as 97/2000 rather than created from scratch in 97/2000 ? Or is there a
tricky way to make these.
Comment 6 caolanm 2001-04-05 14:55:37 UTC
Had the wrong of this. Michael was right about the margins, instead there was a
subtle layout issue with the positioning of the textbox. Fix for the positioning
of the external txtbox checked in, I also think that it makes sense to set the
background fill colour of an imported textbox to the colour of the last used
paragraph background colour. Thats how MS does it, and it makes the import as
the user expects.

Fix for textbox position and background colour checked in.
Comment 7 caolanm 2001-04-20 17:31:01 UTC
Good in 629a3
Comment 8 michael.ruess 2001-04-27 13:41:51 UTC
Looks pretty good in 630b.
Comment 9 michael.ruess 2001-06-25 14:35:05 UTC
Fix integrated in OO 632
Comment 10 jmills 2001-12-28 17:17:19 UTC
This isn't looking good in 641C - has something happened to cause 
this fix to fail?
Comment 11 michael.ruess 2002-01-11 15:43:15 UTC
In my opinion, it looks quite good... the only thing wrong is the
missing white rectangle. Jonathan, do you agree? If so, I´ll file an
internal bug for this, I don´t want to communicate in a bug, that has
already been closed/fixed and only a small thing of the original
description is still valid... Thank you for your patience.
Comment 12 michael.ruess 2002-01-14 11:13:56 UTC
I filed an internal bug for the problem with the missing rectangle.
This will be fixed in an OOo version >641.
Comment 13 michael.ruess 2002-01-14 11:14:48 UTC
So the remaining problem is processed seperately, I close this one here.
Thank you for your patience.