Adobe 29180248 User Guide - Page 55

Creating multilingual extension packages (version 2.1 and later)

55

Setting up the folder hierarchy for localized XML files

At the same location as your .mxi file, create a folder with the exact name of your .mxi file and

append "Resources" to it. For example if you have an .mxi file named "Calendar.mxi", create a

folder named "Calendar.mxi_Resources". In this folder, you add an XML file for each language

you are localizing the extension into. Each file will have a two-letter ISO language code followed

by an underscore character, and then the two-letter ISO country code in upper case. For example,

for English you specify "en_US.xml" and for French "fr_FR.xml".

If your extension needs to install localized files, you may want to create a subfolder for each of the

languages. The folder hierarchy should look as follows:

Calendar.mxi - MXI File

Calendar.mxi_Resources (folder)

en_US.xml - XML File containing English strings

fr_FR.xml - XML File containing French Strings

en_US (Folder Containing English files)

fr_FR (Folder Continaing French files)

Formatting XML for language-specific strings

The Extension Manager looks up localized strings from XML files that you provide for each

language. Each XML file should use Adobe's zstring format. Below is an example of the French

xml file. The locale (in this case,

"fr_FR")

should match the locale of the language. Extension

Manager looks up the localized strings based on the

name=""

attribute and subsitutes the localized

strings in the

<val>

tags. In the following example, we use

name_ID

for the localized Extension

Name, "French Extension Name". And

description_ID

will be used for the Description

displayed when you click the Extension in the Extension Manager.

Example

<?xml version="1.0" encoding="utf-8" standalone="no" ?>

<!DOCTYPE asf SYSTEM "http://ns.adobe.com/asf/asf_1_0.dtd">

<asf locale="fr_FR" version="1.0" xmlns="http://ns.adobe.com/asf">

<set name="DefaultSet">

<str name="name_ID">

<val>French Extension Name</var>

</str>

<str name="description_ID">

<val>

French Extension Description.

</val> </str> </set> </asf>

Installing localized files

To specify that a set of localized files get installed for a particular language, use the

xml:lang

attribute on the

files

tag containing files for that language.

Example

<files xml:lang="en_US">

<file source="en_US/Jacket.htm" destination="$dreamweaver/configuration"/>

</files>

<files xml:lang="fr_FR">

Section	Page
Packaging Extensions with Extension Manager CS5	4
Choose the extension package format	5
Create the extension installation file	6
About careful XML coding	7
Encoding characters	7
MXI tag summary	7
MXI tag descriptions	9
macromedia-extension	10
defaultLanguage	12
description	13
update	14
license-agreement	14
ui-access	15
products	15
product	16
author	18
files	19
file	19
file-tokens	24
token	24
configuration-changes	25
documenttype-changes	26
documenttype-insert	26
documenttype-remove	27
toolpanel-changes	27
toolpanel-item-insert	28
ftp-extension-map-changes	28
ftp-extension-insert	29
ftp-extension-remove	29
insertbar-changes	30
insertbar-insert	30
insertbar-remove	31
insertbar-item-insert	32
insertbar-item-remove	32
server-behavior-changes	33
server-format-changes	33
server-format-definition-changes	34
data-source-changes	34
menu-insert	35
menu-remove	37
menubar	37
menu	38
menuitem	39
format	40
separator	41
comment	41
shortcut-insert	42
shortcut-remove	42
shortcutlist	43
shortcut	43
taglibrary-changes	44
taglibrary-insert	44
taglibrary-remove	45
toolbar-changes	45
toolbar-insert	46
toolbar-remove	46
toolbar-item-insert	47
toolbar-item-remove	48
extensions-changes	48
extension-insert	49
extension-remove	49
Tags and their compatible products	51
Example MXI file	53
Creating multilingual extension packages (version 2.1 and later)	54
Enabling multilingual support in an MXI file	54
Setting up the folder hierarchy for localized XML files	55
Formatting XML for language-specific strings	55
Installing localized files	55
Configuration changes	56
Creating a ZXP extension package (version 5.0 only)	56
Sign ZXP format extension	56
Validate ZXP format extension	57
Creating Hybrid Extension packages (version 5.0 only)	57
Use file-type attribute	57
Use default-file-type attribute	57
Creating plug-in extension packages for InDesign CS5 and InCopy CS5 (version 5.0 only)	58
Creating Enable_for_all_disable_for_one extension packages	58
Creating Enable_for_one_disable_for_one extension packages	58
Creating updatable extension packages (version 5.0 only)	59
Creating update information file	59
Checking update upon launch of Extension Manager	60
Use Extension Manager from the command line	60
Parameter definitions	60
Attribute definitions	60
Parameter formats	61
Command execution result	61
Headless mode	61
\	62
Return code(Extension Manager CS5 only)	62
Execute command through BridgeTalk	62
Examples:	62
Install extension through CLI	62
\	62
\	63
\	63
\	63
\	63
\	63
\	63
\	64
Invalid parameters	64
Valid irregular parameters (which support dragging or double-clicking to install and package)	64
Use Extension Manager from the graphical user interface (GUI)	65

Adobe 29180248 User Guide - Page 55

Setting up the folder hierarchy for localized XML files, Formatting XML for language-specific strings

Page 55 highlights