54
Packaging Extensions with Extension Manager CS5
<menuitem id="DWMenu_Commands_Dog_Dog3" name="Insert Dog _Again Again"
file="commands dog.htm" />
</menu-insert>
<insertbar-changes>
<insertbar-insert>
<category folder="Cat" id="DW_Inserbar_Cat">
<button file="cat/cat.htm" id="DW_Inserbar_Cat_Cat1" image="cat
cat.gif" />
</category>
</insertbar-insert>
</insertbar-changes>
</configuration-changes>
</macromedia-extension>
You can get more examples here:
http://help.adobe.com/en_US/extensionmanager/cs/using/sample.zip.
The sample.zip file contains three examples, including MXI files and other necessary files.
■
<sample.zip>/Samples/html illustrates how to use an HTML file for extension description.
■
<sample.zip>/Samples/multilingual combines multiple language versions of files in one
extension.
■
<sample.zip>/Samples/net update demonstrates an updateable extension.
Creating multilingual extension packages (version 2.1 and later)
Since version 2.1, Extension Manager supports multilingual extension packages, which let you
combine multiple language versions in one ZXP/MXP file. During installation, the appropriate
language is determined by the process outlined in
defaultLanguage
on
page
12
. Then,
language-specific files and text strings are identified using attributes you’ve included in the MXI
file.
Enabling multilingual support in an MXI file
To enable multilingual support in an MXI file, you need to specify the attribute
ismultilingual="true"
to load strings from external files. If you want to localize the name of
the extension, you can specify a
name_resid
attribute in the
<macromedia-extension>
tag. If
no corresponding language tag is found for the id, "name_ID", Extension Manager falls back to
the name in the name attribute.
<macromedia-extension
name="Extension Name"
name_resid="name_ID"
version="1.0.0"
ismultilingual="true" >
<defaultLanguage>en_US</defaultLanguage>
<author name="FooBar" author_resid="author_ID"/>
<description resid="description_ID">
<![CDATA[ Inline Description ]]>
</description>