Issue 85567

Summary: I/O Error - Opening StarImpress 5.0 sdd files
Product: Impress Reporter: Dave Barton <bmcs>
Component: open-importAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 2.3.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
Zip Compressed Eight Slide StarOffice Impress File none

Description Dave Barton 2008-01-25 02:02:59 UTC
Opening some StarImpress 5.0 sdd files fail to open in OOo 2.3.1 and generate a
"General I/O Error". The same files open without error in SO 5.2 and OOo 2.0.x
Comment 1 Dave Barton 2008-01-25 02:11:04 UTC
Created attachment 51145 [details]
Zip Compressed Eight Slide StarOffice Impress File
Comment 2 kami911 2008-01-25 04:51:34 UTC
2.4.0 M2 on linux (our build) - CONFIRMED
Comment 3 christian.guenther 2008-01-25 11:03:48 UTC
Set to new and change the target.
Comment 4 christian.guenther 2008-01-25 11:13:10 UTC
I can reproduce the bug in src680m243.
Please have a look.
Comment 5 noop 2008-01-25 19:37:14 UTC
I can also reproduce the "General I/O Error" on StarOffice 8 ver 9.

Comment 6 clippka 2008-06-06 14:09:29 UTC
I have to retarget this one
Comment 7 Martin Hollmichel 2008-12-10 11:03:00 UTC
move to next target due to limited time frame for 3.1
Comment 8 clippka 2009-02-09 16:55:09 UTC
the problem is with ole object 274. It is a StarMath 5 that has problems during
loading in binfilter. ( I don't know what the difference to the other hundreds
for StarMath 5 ole objects is)

in Content::insert() (e:\cws\impress168\ucb\source\ucp\package\pkgcontent.cxx )

the lines (1652)

		// Required: Title
		if ( !m_aProps.aTitle.getLength() )
			m_aProps.aTitle = m_aUri.getName();

cause titles that start with a 0x01 (f.e. "%01Ole")

The title with the 0x01 as the first name is later used as a file name inside
the zip storage, that gives some assertion.

What finaly fails is the export of the manifest xml where we get a sax exception
because a 0x01 inside an attribute value is not valid xml.


@cl->mav : I debuged that far but I don't know what the cause is and at which
place "%01Ole" should/could be converted. please take over
Comment 9 Marcus 2017-05-20 11:11:19 UTC
Reset assigne to the default "issues@openoffice.apache.org".