import Word doc to FrameMaker 11 as an OLE Object!

[samehme]

Hi,

I am trying to import an Arabic MS Word document, with more than 1 page, into FrameMaker 11 as an OLE Object. Well, it does import the 1st page of the Word file, but not the rest of the other pages in the Word file.

Thanks,

Sameh

[Arnis_Gubins]

FM doesn't support right-to-left languages and using OLE isn't a best practice, so you have at least a couple of things that aren't going to work very well in your scenario. What happens when you try to simply import (by reference) the Word file?

[samehme]

Thanks, Arnis,

Could you please tell me what are these couple of things:

"you have at least a couple of things that aren't going to work very well in your scenario."

I am aware that FM doesn't have RTL support, that is why the Word OLE.

[Arnis_Gubins]

The "couple of things" are: OLE and right-to-left content.

Sorry, I'm not trying to be facetious here, but that's what you're up against. If you import as OLE, FM treats the file as a clipboard graphic and drops the entire content into a single anchored frame. Turn on your FM View > Borders, and Symbols as well, and you'll see a solid black line at the bottom of the frame holding your imported OLE content. This is telling you that the content has overflowed the container (i.e. FM can't show you any more that what the frame size allows).

If you just want to publish exising Arabic content in a composite FM document, then you could try creating a PDF from Word and then import the PDF (one page at a time) into FM. Just keep in mind that like the OLE content, FM is treating this as a graphic.

Alternatively, you could just try importing the Word file into FM by reference. If you tell FM to keep the source formatting, then it might look correct in FM. As long as you don't edit the content (but you can format it) in FM, you might be able to get away with it.

I tried this approach and this what I got (Apologies, since I can't read Arabic, I don't know what the content is, but it does look more or less correct in FM - though I don't know if the font is distorted or some characters aren't being interpreted properly).