On 05/16/2011 07:50 PM, Simon Vandyk wrote: > Hi, after extracting the files in the docx file that your fo converter > created i played with some of the open xml and i managed to get the > images to show in word 2008 for mac (this did not affect images > displaying in office 2007 for windows). > I added the following attribute to the v:shape tag that surrounds the > v:imagedata tag > > *type="#_x0000_t75"* > > Before (images showing if windows office 2007 and images *not* showing > on mac word 2008): > <v:shape filled="f" style="width:114.89pt;height:156.64pt"> > <v:imagedata r:id="r11" cropleft="0.00" croptop="-0.00" cropright="0.00" > cropbottom="-0.00" /> > </v:shape> > </w:pict> > > After adding attribute (images showing if windows office 2007 and images > *showing* on mac word 2008): > <v:shape *type="#_x0000_t75"* filled="f" > style="width:114.89pt;height:156.64pt"> > <v:imagedata r:id="r11" cropleft="0.00" croptop="-0.00" cropright="0.00" > cropbottom="-0.00" /> > </v:shape> > </w:pict> > > So a couple of questions: > 1. I'm not an open xml expert and does this attribute make sense?
A quick look at this reference http://msdn.microsoft.com/en-us/library/bb263897%28v=VS.85%29.aspx indicates that the type attribute is used to point to a shapeType element. XFC does not generate a shapeType element therefore, in principle, the type attribute should not be useful. Therefore adding type="#_x0000_t75" to v:shape seems to be just a (rather strange) workaround for basically what is a Microsoft bug. > 2. If this is the correct fix, would you be able to integrate it into a > new release that i could download and use. I'm sorry but we do not intend to release a minor release integrating your patch. I'm afraid you'll have to wait until we release XFC v4.5. As explained in my previous email, we intend to change the way images are generated in .docx files and we are confident that this will also fix your problem on the Mac. Of course, this time, we intend to thoroughly test the files generated by XFC on the Mac. If you cannot wait for a few weeks and have access to the source code of XFC (available if you own any of the following licenses: fc-site, fc-dev, fcn-site, fcn-dev), then may be you can patch the product yourself (without any assistance or support from XMLmind). The file of interest is: com/xmlmind/fo/converter/docx/Picture.java. > > The modified docx file is attached. > > Many Thanks > > Simon Vandyk > *Senior Developer* > Totally Communications > t: 020 7284 9731 > w: www.totallycommunications.com <http://www.totallycommunications.com> > tw: @totallycomms <http://tiny.cc/f5zm1> > fb: facebook <http://tiny.cc/icfd8> > > > > THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE LEGALLY > PRIVILEGED. If you are not the addressee, any disclosure, reproduction, > distribution or other use of this communication is strictly prohibited. > If you have received this transmission in error please notify the sender > immediately and then delete this e-mail. Any personal opinions or > statements contained in this e-mail are not authorised or endorsed by > Totally Plc or any of its subsidiaries. Totally Plc is not liable for > any viruses associated with this transmission. > > Hussein Shafie wrote: >> On 05/13/2011 04:04 PM, Simon Vandyk wrote: >>> Hi There, i am having problems with getting images to embed properly in >>> MS Word docs for Mac OSX after conversion to docx from an fo file. This >>> seems to be a problem for MS Word 2008 and 2011 for Mac OSX where images >>> wont display at all; in MS Word 2004 for Mac they show, but they overlay >>> other content. >> We don't have MS Word for the Mac. We have never tested the files that >> our product, XMLmind XSL-FO Converter, generates with this software. >> >> We naively thought that if it worked fine with all MS Word versions on >> Windows, then it would also work on the Mac. (This is for example the >> case with OpenOffice.) >> >> >> >> >>> The images display ok in MS Word 2007 for Windows. >> The .docx file you sent us also displays OK in MS Word 2010 for Windows. >> >> >> >>> My fo file is attached, along with one of the images used (all other >>> ones are referenced by url). >> Both the .fo file and the image file are just fine. >> >> >> >>> I am using version xslsrv_pro-4_4_2 i have >>> also attached one of the unmodified docx files generated. Please let me >>> know your suggestions. >> We don't have any suggestions, because this looks more like a limitation >> in MS Word for the Mac rather than a bug in our product. >> >> Anyhow, we are currently working on XMLmind XSL-FO Converter v4.5 >> (should be released at the end of June) and we'll *try* to reproduce and >> solve the problem you have described for this release. >> >> >> >> --- >> PS: The .fo file you sent us is indented, which is fine when debugging. >> However please do not generate indented .fo files in production. See >> FAQ: http://www.xmlmind.com/foconverter/faq.html#bad_vertical_space -- XMLmind FO Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xfc-support
