Issue 37386 - Hebrew in embeded document displayed wrong on import
Summary: Hebrew in embeded document displayed wrong on import
Status: CLOSED DUPLICATE of issue 49930
Alias: None
Product: Impress
Classification: Application
Component: open-import (show other issues)
Version: 680m62
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Mathias_Bauer
QA Contact: issues@graphics
URL:
Keywords: ms_interoperability, oooqa
Depends on:
Blocks:
 
Reported: 2004-11-18 11:14 UTC by sforbes
Modified: 2013-08-07 15:21 UTC (History)
2 users (show)

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


Attachments
Problem PPT file- see slide #4 (485.00 KB, application/vnd.ms-powerpoint)
2004-11-18 11:16 UTC, sforbes
no flags Details
screenshot of garbled text (328.84 KB, image/png)
2004-11-18 11:18 UTC, sforbes
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description sforbes 2004-11-18 11:14:48 UTC
The attached file is a PowerPoint presentation, which contains an embedded
wordproccesing file.

The Hebrew in the file displays wrong:
Some charachters are missing, other overlap, and the font is wrong.

I have all the options in tools--options--load/save- microsoft- marked.

Double clicking the embedded object openes it for editing, and then it looks ok.
Comment 1 sforbes 2004-11-18 11:16:34 UTC
Created attachment 19465 [details]
Problem PPT file- see slide #4
Comment 2 sforbes 2004-11-18 11:18:03 UTC
Created attachment 19466 [details]
screenshot of garbled text
Comment 3 Dieter.Loeschky 2005-07-11 08:12:25 UTC
DL-> WG: Could you please handle this?
Comment 4 wolframgarten 2005-07-11 08:40:57 UTC
Seems to be the OLE on slide 4. Reproducible. Reassigned.
Comment 5 sven.jacobi 2005-07-29 15:55:51 UTC
reassigned
Comment 6 sven.jacobi 2005-07-29 16:03:54 UTC
sj: This issue is double to i49930. OOo does not have a problem to load and
display the original replacement graphic that is provided within the original
ppt format. 

So it is a problem that happens after refetching the replacement graphic, -> 49930

*** This issue has been marked as a duplicate of 49930 ***
Comment 7 Mathias_Bauer 2005-08-01 14:39:57 UTC
Thanks for finding this out! Closing.