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)
Best regards,
Wouter van Vugt
MVP Visual Studio Tools for Office
|
|
|
|
|
+31 6 438 317 12 |
|
|
|
|
|
|
|
Code
Counsel |
Critical Path Training |
|
|
|
Sharing
Knowledge with Passion |
Your fastest way up the SharePoint learning curve! |
|||
