Does anyone know where to find an authoritative specification for the manifest.xml file included in LO extensions, one that lists all possible elements and explains them?
I asked the AI chatbot this question and it gave me a list and explanations, but I’d like to compare an authoritative source.
The closest thing I can find appears to be the Manifest File section of the Open Document specification.
https://wiki.documentfoundation.org/Documentation/DevGuide/Extensions#File_Format
The subsections of the File Format all discuss the specific entries in the manifest.xml, and the introductory text specifies that manifest.xml ... lists all items and their media-type. As simple as that.
Thank you for your answer. It is correct that the File Format article provides information on the <manifest:file-entry> element and its attributes <manifest:media-type> and <manifest:full-path>.
However, some information seems to be missing:
<manifest:manifest> is mentioned. I gather that this is the root element from looking at examples, but the File Format article does not mention it.<!DOCTYPE manifest:manifest PUBLIC "-//OpenOffice.org//DTD Manifest 1.0//EN" "Manifest.dtd"> is mentioned. Again, I assume this is the right declaration, but the File Format article does not say this.manifest.dtd, I see that <manifest:file-entry> element is not the only element that can be found under <manifest:manifest>. For example, there is <manifest:encryption-data>. Is this used for anything? Where is this described?The File Format article provides useful information, but it seems to make the assumption that developers already know certain things or can reasonably be expected to put together a complete picture for themselves by delving into multiple sources or trial-and-error. This seems to be an unnecessary hurdle. Is there a document that defines, in simple terms, the correct structure / contents of the manifest.xml file for a LibreOffice extension?
I am in the same situation. I’ve been seaching some files to see what is going n. I ended up finding what you’ve mentioned aboput ,!DOCTYPE … in one of the files I’ve searched.
But I keep getting an error
… error on line 3 at column 122: Namespace prefix manifest for full-path on file-entry is not defined
this occur in the fiest line after the <!DOCTIPE…
Here the line:
<manifest:file-entry manifest:full-path=“MyCounterLibrary/” manifest:media-type=“application/vnd.sun.star.basic-library”/>
Sometimes I feel like in a maze created to make things difficult to those not learned.
I copied this from here
And nobody answered your claim…
@RayCulp Note that you and Mike refer to extensions. The manifest.xml file in extensions seems to use a subset of all the elements specified in the ODF.
Thus no manifest:manifest element is present (at least, I never found any in all my extensions endeavours). The same goes for the <!DOCTYPE thing.
As for the encryption, I don’t know.
This is why I’d think that, for extensions, you’d only find xmlns, manifest:file-entry and manifest:full-path elements. And perhaps some encryption information (/note for self: check this).
Perhaps someone with more in-depth knowledge will jump in.
They are straight double quotes, in the file I copied from to paste, even if they look curled, like these here " " " " " " "
Yes, I am trying to create an extension using LO Macro with all the expected resources (I can do it just using the option “Export as an Extension” from “Export Basic Library”). I am following the directions from the link I’ve posted earlier.
The manifest.xml in this source seems to miss the Namespace in the item
manifert:manifest
Then I uses the item that appears in RayCulp post…
and also
Didn’t work!
Then I found a .oxt file in one of my extension folders and looked for the manifest.xml in there. I copied the item, which is like this:
<manifest:manifest xmlns:manifest=“http://openoffice.org/extensions/description/2006”>
(which, by the way, appears in the post of mikekaganski
This one seems to work. At adding the extension, it shows the software Licence Agreement, the icon appears in the “Display Extensions” with Extension name, version, and email (which means the description.xml is OK), the Library with module and dialog are properly loaded, and the extension runs as expected. It also shows the Extension name in the Calc Toolbar (after the icon to export pdf, but with no icon
Is there any way to add an icon instadr of showing the extension name?
Sorted out. I had not used the correct icon filename in the Addons.xcu.
changed to a 32x32 png icon. works perfectly.
Thanks for that info. Sounds plausible, but it would still be good to know if this is formally defined somewhere.