Saving a Word 97/2000/XP format document to the same format from within OOo
changes multiple aspects of the layout.  These changes *are not visible* from
within OOo, and may only be viewed with Word.  (I only have access to Word
97/98, someone please check if this happens with Word 2000/XP/etc.)


Steps to Reproduce: 

1. Generate complex document using Word 97/98 (or use the sample provided)
2. Open using OOo 1.1
3. Save to original .doc format, with same or different filename
4. Re-open in Word 97/98 to view layout issues, in OOo to view titlebar issue


Frequency: All the time


Expected Behavior: Original formatting, fonts, layouts, margins, etc should
remain the same.  


Actual Behavior: Formatting, fonts, layouts, margins, etc appear the same in
OOo, but are clearly changed when viewing the doc using Word 97/98.


Specifics:

-----
1. Titlebar
Docs opened in OOo should generally show the title of the document in the
titlebar of the app.  This is usually the case.  

Opening a Word doc in OOo shows the title in the titlebar.  Saving to original
Word format, then closing and re-opening in OOo shows "15 August 2001".  


2. Tables
"Space Between Columns" and "Indent from Left" (as shown in Word by Table ->
Cell Height and Width...) are both altered.  This is most noticeable on the
right of the first page of the sample documents, but occurs throughout.


3. Fields
Field fonts are changed.  In the sample file, the "Rating" field on the top of
the first page is changed from Arial 20 to Times New Roman 16.


4. Text Boxes vs Layout Frames
Word makes use of two distinct layout features, Frames and TextBoxes.  TextBoxes
are separate subdocuments (AFAICT), and text within them is separate from the
text in the main document.  Layout Frames look similar, except that the text
within them is *inline* -- manually clicking the right arrow key from the
paragraph previous to the Frame anchor will move the cursor through the Frame
contents, then back out into the following paragraph.  This can be important for
a number of applications, and is also convenient in that Frames can be included
as part of a paragraph style (as in the @Caption style of the ungoofed sample
document).

OOo appears to make an incomplete distinction between the two when saving a Word
Layout Frame, combining a Frame and a TextBox into an entity Word seems to view
as a hybrid, but goofing the original layout margins and positioning.  TextBoxes
in Word, however, appear correctly after saving in OOo and then viewing in Word.


5. Paragraph "Page break before" changed from paragraph property to manual page
break

"Page break before" is accessed in Word via Format -> Paragraph, selecting the
Line and Page Breaks tab.  In the ungoofed file, certain headings use Page Break
Before as a paragraph property.  In the goofed file, this property has been
turned off in the respective paragraphs, being replaced by a manual page break.
 It remains a paragraph property when viewed with OOo.  


6. Annotations

Annotations seem to work differently in Word than in OOo.  Word annotations
allow a selection to be highlighted, marking a specific section of the text for
annotation, much like the regular Highlighter.  Mousing over any portion of the
highlighted section then shows the annotation content in a popup window.  OOo
annotations seem to work more like footnotes, anchoring not to a range but
simply to a single point in the text.  This makes them much less useful for
reviewing/editing purposes, and can cause problems when editing (and then
saving) a Word document from within OOo.  


7. Pictures

The sample document contains two different pictures originally pasted in from
Excel.  The upper of the two was later edited within Word.  This seems to have
changed how OOo interprets the graphic, as is clear if one views the goofed file
from within Word -- line widths have changed in the upper graphic, but not in
the lower.  
-----


There may well be other issues at work as well, these are simply all those that
I am aware of right now.  I would love to recommend OOo to my boss, and use it
more in my own freelancing practice, but given the inconsistencies there is no
way I can do that.  Too many clients are MS-Word-only, and the changes wrought
by OOo would lose us business rather quickly.  

Thanks for everyone's work on this worthy project, and I hope to see these
issues resolved in a not-too-distant release.