Hi Ming Fei,
Looking in the spec I found this sentence:
All XML streams have the media type
"text/xml".
Another thing to address IMHO. It makes no sense at all to make
all XML files use the same media-type in a format where most things are stored
as XML.
Best regards,
Wouter van Vugt
MVP Visual Studio Tools for Office
From: Ming Fei Jia [mailto:jiamingf@cn.ibm.com]
Sent: maandag 22 juni 2009 17:18
To: Wouter van Vugt
Cc: office-comment@lists.oasis-open.org
Subject: Re: [office-comment] embedding images in ODF
Wouter,
Seems the question you asked are implementation specific. For Symphony, you had
better raise you issue in Symphony support forum. For OpenOffice, you had
better raise you issue in OpenOffice issuezilla.
I tried for both Symphony 1.3 and OpenOffice3.1. They have the same result like
you said for the 2 items. So these depend on OpenOffice code base
implementation. For the first, the file name is GUID like structure, that may
be a problem for someone, but may be not a problem for someone else. Also, ODF
spec does not define how the picture file name should be like. For the second,
does not specify the media type for wmf file, this also an implementation
specific issue. In the wikimedia(http://en.wikipedia.org/wiki/Internet_media_type),
does not list wmf as common media type. If we think wmf is a common use media
type, that needs implementation improvement, not the standard issue. Anyway,
thanks report the issues.
"Wouter van Vugt"
<wouter@code-counsel.net> wrote on 06/19/2009 02:52:53 PM:
> 06/19/2009 02:53 PM
>
> Subject:
>
> [office-comment] embedding images in ODF
>
> When adding an image into an ODF document using Lotus Symphony I
> noticed that the manifest contains the following information:
>
> <manifest:file-entry
manifest:media-type="" manifest:full-
> path="Pictures/2000006A00000E3F0000107325797BF2.wmf"/>
> <manifest:file-entry
manifest:media-type="" manifest:full-
> path="Pictures/2000067F0000136800001363D5B042F0.wmf"/>
>
> Two things can be noticed here. First
the file name was mangled into
> a GUID like structure, while that is technically unnecessary. Next,
> and even more amazing, is that the media-type is left unspecified.
> The only way I can now recognize this image as a WMF, is to use the
> file extension. This poses unnecessary difficulties for processing
> applications. Given my guess that Symphony generates conformant ODF,
> the spec should be adapter to require the media-type attribute when
> a decent value can be chosen.
>
> Proposed changes:
> -
Demand that file names are not mangled when embedding
> into a package.
> -
Demand that media-types be specified whenever possible
> (WMF is surely possible)