Issue 8114 - MS Word file with outline numbering created inside Lotus does not import properly
Summary: MS Word file with outline numbering created inside Lotus does not import prop...
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-10-07 09:48 UTC by Unknown
Modified: 2013-08-07 14:43 UTC (History)
2 users (show)

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


Attachments
File attached for this bug. (8.00 KB, application/octet-stream)
2002-10-07 09:52 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-10-07 09:48:43 UTC
Open the Doc file.  The bullets in the document do not show up.  Will attach 
the file once I figure out how to do it.
Comment 1 Unknown 2002-10-07 09:52:25 UTC
Created attachment 3076 [details]
File attached for this bug.
Comment 2 prgmgr 2002-10-13 17:10:44 UTC
Thank you for using and supporting OOo.

Was the Word file created in OOo or Word?
Comment 3 Unknown 2002-10-16 10:36:05 UTC
The file was created from the Lotus SmartSuite Product: Word Pro.  It 
is capable of exporting to the DOC file format.  
Should have mentioned that earlier.  Will do that in the future.  
Comment 4 Unknown 2002-10-16 10:39:00 UTC
Some more information - File opens fine in MS Word.
Comment 5 prgmgr 2002-10-18 03:11:35 UTC
Thanks for the attachment.

The question for the developers is, should this be considered a valid 
MS doc test case?  I don't think it should be.

User summary
All bullets are lost in the attached Word Document.

Dropping priority to P4.  I think this is related to how Lotus is 
exporting the outline numbering.

Workaround is to open the file in Word 2000 and save.  OOo then 
recognizes the outline numbering list.
Comment 6 caolanm 2002-10-18 09:32:49 UTC
I'm comfortable with considering as valid bugs docs that open in word
fine but not in writer, despite being created with a different 3rd
party suite. They can be better than normal word docs by testing our
assumptions about how word works.
Comment 7 stefan.baltzer 2002-11-26 17:14:47 UTC
Reassigned to Michael.
Comment 8 michael.ruess 2002-11-28 10:56:22 UTC
MRU->CMC: Could you please have a look, if this is a valid Word file?
Means, wether Writer should be able to import not.
If it's not, reassign and I'll close the issue.
Thank you very much!
Comment 9 caolanm 2002-12-03 12:01:45 UTC
I see what is happening, 

a) the style names are supposed to be in unicode with a 16bit count at
the beginning and a 16bit 0 at the end. The lotus people have stuck 8
bit strings with an 8bit count and 8bit 0 at the end! (slap, bold
lotus). We can check the belt and braces nature of the strings to see
if they are valid and if not try 8 bit mode for them to work around
this. This much be similiar to what word does to recover from this
crud seeing as it ends up with the right style names.

b) The lists in use are winword 7- lists, these are valid to use in
winword 8+ documents. But you can't easily create a document that
contains them as a user. I have rarely seen them in action to
determine what is supposed to occur when the appear in a ww8+ doc. So
this is a very neat example of what is supposed to happen.

Will all work in SRX644s
Comment 10 caolanm 2002-12-06 13:11:55 UTC
Working SRX644s
Comment 11 michael.ruess 2002-12-06 14:55:14 UTC
Looks good in srx644s.
Comment 12 michael.ruess 2002-12-06 14:55:46 UTC
Will be able to read these kind of documents with OpenOffice 1.1 beta