User Guide

50 Chapter 2: Extending Dreamweaver

To change the Dreamweaver default File > 0pen file type:

1 Make a backup copy of the Extensions.txt file in the Configuration folder.

2 Open Extensions.txt in Dreamweaver or a text editor.

3 Cut the line that corresponds to the new default, and paste it at the beginning of the file, to

make it the first line of the file.

4 Save the Extensions.txt file.

5 Restart Dreamweaver.

To see the changes, select File > Open and click the pop-up menu of file types.

Localized strings

Within a document type definition file, the

<title> and <description> subtags specify the

display title and description for the document type. You can use the

MMString:loadstring

directive in the subtags as a placeholder for providing localized strings for the two subtags. This

process is similar to server-side scripting where you specify a particular string to use in your page

by using a string identifier as a placeholder. For the placeholder, you can use a special tag or you

can specify a tag attribute whose value is replaced.

To provide localized strings, perform the following steps:

1 Place the following statement at the beginning of the document type definition file:

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

2 Declare the MMString name space in the <documenttypes> tag:

<documenttypes

xmlns:MMString="http://www.macromedia.com/schemes/data/string/">

3 At the location in the document type definition file where you want to provide a localized string,

use the MMString:loadstring directive to define a placeholder for the localized string. You can

specify this placeholder in one of the following ways:

<loadstring>myJSPDocType/Description</loadstring>

</description>

</description>

In these examples, myJSPDocType/Description is a unique string identifier that acts as a

placeholder for the localized string. The localized string is defined in the next step.

4 In the Configuration/Strings folder, create a new XML file (or edit an existing file) that defines

the localized string. For example, the following code, when placed in the Configuration/Strings/

strings.xml file, defines the

myJSPDocType/Description string:

...

<string id="myJSPDocType/Description"

value=

"<![CDATA[JavaServer Page with <em>special</em> features]]>"

...

</strings>