Am Dienstag, den 08.02.2011, 03:04 -0800 schrieb cdfleischmann:
> Thanks Marc unfortunately, I have already gone down that route, thus far,
> have tried the following:
> 
> Inserting the picture (not linked but embedded) as the backgroundURL for the
> TextFrame. Inside the textFrame, I insert an image (any image), again
> embedded, and set the size. When I save it to MS Word, I hit bug
> http://www.openoffice.org/issues/show_bug.cgi?id=32638 That is, I get an
> error, There is not enough memory when opening the file in Word.
> 
> A sample ODT file: 
> http://openoffice.2283327.n4.nabble.com/file/n3275734/test.odt test.odt 
> And the resultant MS Word doc file 
> http://openoffice.2283327.n4.nabble.com/file/n3275734/test.doc test.doc 
> 
> However, when I link the images rather than embed, ie., I use file:/// to
> link to an absolute filename (with absolute). The document opens correctly
> and the scaling/sizing works as it should. However the file is then not
> portable, ie., refers to locations on my machine.
> 
> If however, I try to host the images (on a server), and try to include
> images via URL hyperlinks (http://...) rather than to local files, (files:/
> / /) The images don't seem to scale no matter what I try and remain 100% of
> the original file size...
> 
> Is there a known workaround to insert images via hyperlinks and have the
> resultant image load, and correctly (re)size? 

If you're hit by an API bug the only workaround I can think of is to
unpack the document zip file, fix the paths or what is wrong and not
settable correctly by API using sed/awk/perl/java/whatever and pack
things up again.

Since you're building docs by using the sdk that would only be one -
although ugly - additional step. And you caan omit it when the bug is
fixed.

Good luck,
Marc

-- 
Ihr Suchbegriff >OO.o<  könnte fehlerhaft oder unbekannt sein: Ob Zoo
besser ist? (Suchmaschine)


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org

Reply via email to