populating wst user doc folder
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.project b/docs/org.eclipse.wst.xmleditor.doc.user/.project
new file mode 100644
index 0000000..2e33af6
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.xmleditor.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml b/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml
new file mode 100644
index 0000000..2f1231f
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<toc label="Developing XML files" topic="topics/tcretxml.html">
+ <topic label="Working with XML files">
+ <topic label="Creating XML files">
+ <topic label="Creating an XML file from scratch" href="topics/tcretxml.html"/>
+ <topic label="Generating an XML file from a DTD " href="topics/tcrexdtd.html"/>
+ <topic label="Generating an XML file from an XML schema" href="topics/tcrexxsd.html"/>
+ </topic>
+ <topic label="Editing XML files" href="topics/txedttag.html">
+ <topic label="XML editor" href="topics/cwxmledt.html">
+ <topic label="XML editor integration with the workbench" href="topics/cwwedtvw.html"/>
+ <topic label="Defining XML editor preferences" href="topics/txprefs.html">
+ <topic label="Setting source highlighting styles" href="topics/ttaghilt.html"/>
+ <topic label="Working with XML templates" href="topics/twmacro.html"/>
+ <topic label="Specifying line delimiters" href="topics/tedtenc.html">
+ <topic label="Specifying XML and HTML encodings" href="topics/cxmlenc.html"/>
+ </topic>
+ </topic>
+ </topic>
+ <topic label="Editing in the Design view" href="topics/txedtdes.html">
+ <topic label="Editing your DOCTYPE declaration" href="topics/tedtdoc.html"/>
+ <topic label="Editing your namespace information" href="topics/tedtsch.html"/>
+ <topic label="Editing your XML processing instructions" href="topics/tedtproc.html"/>
+ </topic>
+ <topic label="Editing in the Source view" href="topics/txedtsrc.html">
+ <topic label="Using XML content assist" href="topics/twcdast.html"/>
+ </topic>
+ <topic label="Editing with DTD or XML schema constraints" href="topics/tedtcnst.html"/>
+ <topic label="Using xsi:type" href="topics/txsityp.html"/>
+ <topic label="Extending the content model of an XML document" href="topics/rextctn.html"/>
+ </topic>
+ <topic label="Validating XML files" href="topics/twxvalid.html"/>
+ <topic label="XML file associations with DTDs and XML schemas" href="topics/cxmlcat.html">
+ <topic label="Adding an entry to the XML Catalog" href="topics/txmlcat.html"/>
+ <topic label="Updating XML files with changes made to DTDs and schemas" href="topics/tedtgram.html"/>
+ </topic>
+ <!-- <topic label="Icons used in the XML editor" href="topics/rxmlbicons.html"/>-->
+ </topic>
+</toc>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/about.html b/docs/org.eclipse.wst.xmleditor.doc.user/about.html
new file mode 100644
index 0000000..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/build.properties b/docs/org.eclipse.wst.xmleditor.doc.user/build.properties
new file mode 100644
index 0000000..ccad714
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/build.properties
@@ -0,0 +1,5 @@
+bin.includes = doc.zip,\
+ plugin.properties,\
+ plugin.xml,\
+ XMLBuildermap_toc.xml,\
+ xmlbuilder_reference_toc.xml
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/cdatasection.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/cdatasection.gif
new file mode 100644
index 0000000..6b0872c
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/cdatasection.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/collapse_all.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/collapse_all.gif
new file mode 100644
index 0000000..7dc0de5
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/collapse_all.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/comment_obj.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/comment_obj.gif
new file mode 100644
index 0000000..28c2ccb
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/comment_obj.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/doctype.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/doctype.gif
new file mode 100644
index 0000000..3300f82
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/doctype.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/expand_all.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/expand_all.gif
new file mode 100644
index 0000000..492c14f
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/expand_all.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/nattrib.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/nattrib.gif
new file mode 100644
index 0000000..bea9974
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/nattrib.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/nelem.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/nelem.gif
new file mode 100644
index 0000000..afabdda
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/nelem.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/nrstrval.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/nrstrval.gif
new file mode 100644
index 0000000..4742b8c
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/nrstrval.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/proinst_obj.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/proinst_obj.gif
new file mode 100644
index 0000000..74436d8
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/proinst_obj.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/rldgrmr.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/rldgrmr.gif
new file mode 100644
index 0000000..049cac6
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/images/rldgrmr.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/plugin.properties b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.properties
new file mode 100644
index 0000000..5142a07
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.properties
@@ -0,0 +1 @@
+Plugin.name = XML editor
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/plugin.xml b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.xml
new file mode 100644
index 0000000..6fb4d69
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.xml
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<plugin
+ name = "%Plugin.name"
+ id = "org.eclipse.wst.xmleditor.doc.user"
+ version = "0.7.0"
+ provider-name = "Eclipse.org">
+
+ <extension point="org.eclipse.help.toc">
+
+ <toc file="XMLBuildermap_toc.xml"/>
+
+
+
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwwedtvw.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwwedtvw.html
new file mode 100644
index 0000000..7e28121
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwwedtvw.html
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>XML editor integration with the workbench</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="cwwedtvw"><a name="cwwedtvw"><!-- --></a>
+
+<h1 class="topictitle1">XML editor integration with the workbench</h1>
+<div><p>To edit a file using the XML editor, right-click the file in the
+Navigator view, and click <span class="uicontrol">Open With > XML Editor</span>. Because
+the editor that is last used to open a file becomes the default editor for
+that particular file, the XML editor will remain the default
+XML editor for that file unless you explicitly change it.</p><p>The Resource perspective is designed to facilitate XML development, so
+it contains certain views (such as the Outline and Properties view) that are
+advantageous to XML editor users. If, however, you prefer to work in a different
+perspective, that does not provide these views by default, you can add them
+by clicking <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Show View</span></span> and selecting the appropriate view.</p>
+<dl><dt class="bold">Outline view</dt>
+<dd>The Outline view provides a node-level outline, or roadmap of an XML file.
+This view is especially useful for navigating complex documents, because when
+you select an element in the Outline view, the corresponding nodes in the
+Source and Properties views are also identified as the "active" node. In addition,
+the Outline view is synchronized with the workbench Properties view, so that
+the selected element's attributes and their values are displayed in the Properties
+view (but not the Outline view). You can also use the Outline view to insert
+and delete elements.</dd>
+<dt class="bold">Properties view</dt>
+<dd>The <span class="uicontrol">Property</span> column in the Properties view contains
+a list of attributes, and the <span class="uicontrol">Value</span> column contains
+the editable values of those attributes. Attributes that are already included
+in the selected or "active" tag are displayed with their values. In addition,
+if the document contains a reference to a DTD or schema, then the attributes
+that are allowed for that tag are also displayed. When you select the value
+column of a property, you are provided with an editing option. <p>The pop-up
+menu in the Properties view contains the following options: undo, cut, copy,
+paste, delete, and select all. The options that are available at a given time
+depend on where the cursor is located when the pop-up menu is displayed. To
+see the pop-up menu options, the property value field must be active. (select
+the property, then select its value.)</p>
+ <p>Use the <span class="uicontrol">Restore Default
+Value</span> toolbar button <img src="../images/nrstrval.gif" alt="Image of the Restore default values button" /> to
+change any value back to its default setting.</p>
+ <p>Once you are in the Properties
+view, you can modify other property values for specific attributes. To edit
+another tag using the Properties view, you can select the desired node in
+the workbench Outline view, or select an attribute in the Design or Source
+view of the XML editor.</p>
+</dd>
+</dl>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html
new file mode 100644
index 0000000..31adcf5
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>XML editor</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="cwxmledt"><a name="cwxmledt"><!-- --></a>
+
+<h1 class="topictitle1">XML editor</h1>
+<div><p>The XML editor is a tool for creating and viewing XML files</p><p>You can use it to perform a variety of tasks such as the following:</p>
+<ul><li>Create new XML files, either from scratch, existing DTDs, or existing
+XML schemas</li>
+<li>Edit and validate XML files</li>
+<li>Import existing XML files for structured viewing</li>
+<li>Associate XML files with DTDs or XML schemas</li>
+</ul>
+<p>To make the XML editor the default editor for XML files, select <span class="uicontrol">Window
+> Preferences > Workbench > File Associations</span>, then select <span class="uicontrol">*.xml</span> and <span class="uicontrol">XML
+Editor</span> from the Associated Editors list. Click <span class="uicontrol">OK</span>. </p>
+<p>The XML editor has two main views - the Source view and the
+Design view.</p>
+<div class="skipspace"><h4 class="sectiontitle">Source view</h4><p>The Source view enables you to view
+and work directly with a file's source code directly.</p>
+<p>The Source view has many text editing
+features, such as syntax highlighting, unlimited undo/redo, and user-defined
+macros. Another helpful feature is content assist, which uses the information
+in a DTD or schema content model to provide a list of acceptable continuations
+depending on where the cursor is located in an XML file, or what has just
+been typed. The XML editor Source view also includes a "smart" double-clicking
+behavior. If your cursor is placed in an attribute value, one double-click
+selects that value, another double click selects the attribute-value pair,
+and a third double-click selects the entire tag. This makes it easier to copy
+and paste commonly used pieces of XML.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Design view</h4><p>The XML editor also has a Design view,
+which represents the XML file simultaneously as a table and a tree. This helps
+make navigation and editing easier. Content and attribute values can be edited
+directly in the table cells, while pop-up menus on the tree nodes give alternatives
+that are valid for that location. For example, the <span class="uicontrol">Add child</span> menu
+item will list only those elements from a DTD or XML schema which would be
+valid children at that point (as long as grammar constraints are on).</p>
+<p>The
+Design view is especially helpful if you are new to XML, or need to do form-oriented
+editing. For example, you could use the Create XML File wizard to create a
+template XML file for a job description form from a job description
+DTD. After those steps are completed, you would only have to fill in the form
+data using the Design view.</p>
+<p> <b>Note</b>: You can also use the <b>Outline</b> view
+to insert and delete elements.</p>
+</div>
+</div>
+
+<div>
+<blockquote>
+<div class="ulchildlink"><b><a href="../topics/cwwedtvw.html">XML editor integration with the workbench</a></b><br />
+To edit a file using the XML editor, right-click the file in the
+Navigator view, and click <span class="uicontrol">Open With > XML Editor</span>. Because
+the editor that is last used to open a file becomes the default editor for
+that particular file, the XML editor will remain the default
+XML editor for that file unless you explicitly change it.</div>
+<div class="ulchildlink"><b><a href="../topics/txprefs.html">Defining XML editor preferences</a></b><br />
+You can set various preferences for the Source view of the XML editor such as the formatter indentation style, line wrapping rules, and content assist rules.</div>
+</blockquote>
+
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/txedttag.html" title="">Editing XML files</a><br />
+</p>
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcretxml.html" title="You can create a new empty XML file, which you can then edit in the XML editor.">Creating an XML file from scratch</a><br />
+<a href="../topics/txedttag.html" title="Editing XML files"></a><br />
+<a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a><br />
+<a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a><br />
+<a href="../topics/twxvalid.html" title="Validating XML files"></a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html
new file mode 100644
index 0000000..2ca13af
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html
@@ -0,0 +1,173 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>XML file associations with DTDs and XML schemas</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="cxmlcat"><a name="cxmlcat"><!-- --></a>
+
+<h1 class="topictitle1">XML file associations with DTDs and XML schemas</h1>
+<div><p>There are two different ways to associate XML files with DTDs or
+XML schemas.</p><ol><li>Direct association - The XML file contains either the name of a DTD in
+its doctype declaration (for example, <!DOCTYPE root-element SYSTEM " <var class="varname">dtdfile.dtd</var>"
+>, where <var class="varname">dtdfile.dtd</var> is the name of the DTD file) or it
+contains the path of an XML schema in the schemaLocation attribute of the
+XML file root element (for example, <xsi:schemaLocation="http://www.ibm.com
+ <var class="varname">schema.xsd</var>">, where <var class="varname">schema.xsd</var> is
+the name of the XML schema.</li>
+<li>XML Catalog entry - You can register DTD and XML schema files in
+the XML Catalog and associate them with a <var class="varname">Key</var> that represents
+them. You can then refer to a DTD or XML schema file <var class="varname">Key</var> from
+an XML file instead of referring directly to the DTD or XML schema file. An
+XML Catalog entry contains two parts - the Key (which represents the DTD or
+XML schema) and a URI (which contains information about the DTD or XML schema
+location).</li>
+</ol>
+<div class="skipspace"><h4 class="sectiontitle">How an association works </h4><b>Associating an XML
+file with a DTD </b><div class="p">If an XML file is associated with a DTD, a DOCTYPE
+tag such as the following is included in the XML file:<pre><!DOCTYPE root-name PUBLIC "<var class="varname">InvoiceId</var>" "<var class="varname">C:\mydtds\Invoice.dtd</var>"></pre>
+</div>
+<p><var class="varname">InvoiceId</var> is the public identifier of
+the DTD file. It is used to associate the XML file with a DTD file (in this
+case, the DTD file is <var class="varname">Invoice.dtd</var>). If the public identifier
+InvoiceId corresponds to the <var class="varname">Key</var> of the XML Catalog entry
+for Invoice.dtd, then the <var class="varname">URI</var> of the XML Catalog entry
+(which contains information about the location of Invoice.dtd) is used to
+locate the DTD. Otherwise, the DOCTYPE's system identifier ( <var class="varname">"C:\mydtds\Invoice.dtd"</var>),
+which refers directly to the file system location of the DTD, is used to locate
+the DTD. </p>
+<p> <b>Note</b>: You can also use a system identifier as
+a Key in an XML Catalog entry. If you use a system identifier as a Key, a
+DOCTYPE tag such as the following is included in an XML file:</p>
+<pre><!DOCTYPE Root-name SYSTEM "<var class="varname">MyDTD.dtd</var>"> </pre>
+<p>where <var class="varname">MyDTD.dtd</var> is the system identifier that corresponds
+to the Key of an XML Catalog entry.</p>
+</div>
+<div class="skipspace"><b>Associating an XML file with an XML schema</b><p>If an XML file
+is associated with an XML schema, one or more schema location attributes are
+included in the XML file. The information in the schemaLocation is provided
+as a "hint" to the XML processor. Examples of schemaLocation attributes are
+shown below: </p>
+<div class="p"> <b>Example 1 </b><pre><purchaseOrder xmlns="http://www.ibm.com"
+xsi:schemaLocation="http://www.ibm.com C:\myschemas\PurchaseOrder.xsd">
+<shipTo country="US">
+...</pre>
+ </div>
+<div class="p"><b>Example 2 </b><pre><purchaseOrder xmlns="http://www.ibm.com"
+xsi:schemaLocation="http://www.ibm.com PO.xsd">
+<shipTo country="US">
+....</pre>
+ </div>
+<p>In Example 1, the schemaLocation 'hint' ('C:\myschemas\PurchaseOrder.xsd')
+refers directly to the file system location or URI of the XML schema. In this
+case, the schema file will be located by the XML processor directly.</p>
+<p>In
+Example 2, the schemaLocation 'hint' ('PO.xsd') refers to an XML Catalog entry.
+PO.xsd corresponds to the <var class="varname">Key</var> of the XML Catalog entry
+for PurchaseOrder.xsd, and the URI of the XML Catalog entry (which contains
+information about the location of PurchaseOrder.xsd) will be used to located
+the XML schema.</p>
+<p>In both examples, <samp class="codeph">http://www.ibm.com</samp> in
+the <samp class="codeph">xsi:schemaLocation</samp> tag is a URI that identifies the namespace
+for the XML schema. </p>
+<div class="p">You can also use a namespace as a Key for
+an XML Catalog entry. If you use a namespace as a Key, a schemaLocation tag
+such as the following is included in an XML file:<pre><purchaseOrder xmlns:="www.ibm.com"
+ xsi:schemaLocation="http://www.ibm.com po/xsd/PurchaseOrder.xsd "></pre>
+</div>
+<p>The
+schemaLocation attribute points to both the Key and the actual location of
+the schema.</p>
+<p><b>DTD or XML schema resides on a remote server</b></p>
+<p>Several
+functions in the XML editor, such as validation and content assist, require
+the availability of a DTD or an XML schema. The product documentation provides
+usage information for cases when the DTD or XML schema resides on your local
+machine. However, in many cases, the DTD or XML schema may reside on a remote
+server, for example:</p>
+<p><samp class="codeph"><!DOCTYPE Catalog PUBLIC "abc/Catalog"
+"http://xyz.abc.org/dtds/catalog.dtd"></samp></p>
+<p>Normally, this case
+poses no problem, because the DTD or XML schema can be retrieved from the
+remote server. However, if you are behind a firewall, and do not have a SOCKSified
+system, the workbench currently does not provide a way for you to specify
+a socks server for retrieving a DTD or XML schema. If you are unable to SOCKSify
+your system, the workaround for this problem is to retrieve a copy of the
+DTD or XML schema (using a Web browser, for example) and save that copy on
+your local machine. Then, you can either place a local copy in the same project
+as your XML file, or use the XML Catalog to associate a public identifier
+with the DTD's (local) location.</p>
+<p><b>Note</b>: If you have an XML file
+associated with an XML schema or DTD that is elsewhere in the network, and
+you are working on a machine disconnected from the network, you can follow
+the steps described above if you want to use content assist or validate your
+XML file. </p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Advantages of XML Catalog entry associations</h4><p>If
+you create a direct association between an XML file and an XML schema or DTD
+file, any time you change the location of the schema or DTD you have to track
+down and update all of the referencing XML files with the new location of
+the DTD or schema. If, however, you associate an XML file with an XML schema
+or DTD Key, then, when you change the location of the schema or DTD, you only
+have to update the XML Catalog entry, instead of each individual XML file. </p>
+<p>For
+example, you have a DTD called "Building.dtd", which is associated with five
+XML files - Office.xml, House.xml, Apartment.xml, Bank.xml, and PostOffice.xml.
+You move the DTD file Building.dtd to a new location. If you have a direction
+association between Building.dtd and all the XML files, you will have to update
+the <DOCTTYPE> declaration in each XML file to reflect the new location
+of Building.dtd. If, however, you have an XML Catalog association, and
+all the XML files just refer to the Key of Building.dtd, then you only have
+to update the URI and all the XML files will point to the new location of
+Building.dtd.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Updating an entry in the XML Catalog</h4><p>After you have
+updated an entry in the XML Catalog, you may need to refresh the XML editor
+view so that it uses the new information. To do this, click the <span class="uicontrol">Reload
+Dependencies</span> toolbar button <img src="../images/rldgrmr.gif" /> and
+the view will be updated using the current XML Catalog settings. You only
+need to refresh the XML editor view when you have an XML file open that references
+the XML Catalog entry that was updated.</p>
+<p>For more information, refer
+to the related concepts and tasks below.</p>
+<p>(c) Copyright 2001, World Wide
+Web Consortium (Massachusetts Institute of Technology, Institut National de
+Recherche en Informatique et en Automatique, Keio University).</p>
+</div>
+</div>
+
+<div>
+<blockquote>
+<div class="ulchildlink"><b><a href="../topics/txmlcat.html">Adding an entry to the XML Catalog</a></b><br />
+</div>
+<div class="ulchildlink"><b><a href="../topics/tedtgram.html">Updating XML files with changes made to DTDs and schemas</a></b><br />
+If you make changes to a DTD file or XML schema associated with
+an XML file (that is currently open), click <span class="uicontrol">XML > Reload Dependencies</span> to
+update the XML file with these changes.</div>
+</blockquote>
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a><br />
+<a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing your DOCTYPE declaration</a><br />
+<a href="../topics/txmlcat.html" title="Adding an entry to the XML Catalog"></a><br />
+<a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes.">Updating XML files with changes made to DTDs and schemas</a><br />
+<a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema it is associated with. ">Editing your namespace information</a><br />
+<a href="../topics/tedtproc.html" title="A processing instruction is a syntax in XML for passing instructions along to the application using an XML document.">Editing your XML processing instructions</a><br />
+<a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a><br />
+<a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html
new file mode 100644
index 0000000..e7cad03
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html
@@ -0,0 +1,167 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>XML and HTML encodings</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="cxmlenc"><a name="cxmlenc"><!-- --></a>
+
+<h1 class="topictitle1">XML and HTML encodings</h1>
+<div><p>The HTML and XML editors support the following encodings. The IANA
+name is used in the encoding statement of an XML file, or charset directive
+in an HTML file.</p>
+<div class="skipspace"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" class="firstcol" id="d0e20"> <p><b>XML Encoding (IANA Name)</b></p>
+ </th>
+<th valign="top" id="d0e26"> <p><b>Description</b></p>
+ </th>
+</tr>
+</thead>
+<tbody><tr><td valign="top" class="firstcol" id="d0e34" headers="d0e20 "> <p>BIG5</p>
+ </td>
+<td valign="top" headers="d0e34 d0e26 "> <p>Big5, Traditional Chinese</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e45" headers="d0e20 "> <p>EUC-JP</p>
+ </td>
+<td valign="top" headers="d0e45 d0e26 "> <p>EUC encoding, Japanese</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e56" headers="d0e20 "> <p>EUC-KR</p>
+ </td>
+<td valign="top" headers="d0e56 d0e26 "> <p>EUC encoding, Korean</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e67" headers="d0e20 "> <p>GB2312</p>
+ </td>
+<td valign="top" headers="d0e67 d0e26 "> <p>GBK, Simplified Chinese</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e78" headers="d0e20 ">GB18030</td>
+<td valign="top" headers="d0e78 d0e26 ">National Standard, Chinese</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e83" headers="d0e20 ">IBM864</td>
+<td valign="top" headers="d0e83 d0e26 ">PC Arabic
+</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e88" headers="d0e20 "> <p>ISO-2022-JP</p>
+ </td>
+<td valign="top" headers="d0e88 d0e26 "> <p>ISO 2022, Japanese</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e99" headers="d0e20 "> <p>ISO-2022-KR</p>
+ </td>
+<td valign="top" headers="d0e99 d0e26 "> <p>ISO 2022, Korean</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e110" headers="d0e20 "> <p>ISO-8859-1</p>
+ </td>
+<td valign="top" headers="d0e110 d0e26 "> <p>ISO Latin-1</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e121" headers="d0e20 ">ISO-8859-2</td>
+<td valign="top" headers="d0e121 d0e26 ">Central/East European (Slavic)</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e126" headers="d0e20 ">ISO-8859-3</td>
+<td valign="top" headers="d0e126 d0e26 ">Southern European</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e131" headers="d0e20 ">ISO-8859-4</td>
+<td valign="top" headers="d0e131 d0e26 ">ISO 8859-4, Cyrillic</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e136" headers="d0e20 ">ISO-8859-5</td>
+<td valign="top" headers="d0e136 d0e26 ">ISO 8859-5, Cyrillic</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e141" headers="d0e20 "> <p>ISO-8859-6</p>
+ </td>
+<td valign="top" headers="d0e141 d0e26 ">Arabic (Logical)</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e152" headers="d0e20 ">ISO-8859-7</td>
+<td valign="top" headers="d0e152 d0e26 ">Greek</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e157" headers="d0e20 "> <p>ISO-8859-8-I</p>
+ </td>
+<td valign="top" headers="d0e157 d0e26 "> <p>Hebrew (Logical)</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e168" headers="d0e20 "> <p>ISO-8859-8</p>
+ </td>
+<td valign="top" headers="d0e168 d0e26 "> <p>Hebrew (Visual)</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e179" headers="d0e20 ">ISO-8859-9</td>
+<td valign="top" headers="d0e179 d0e26 ">Turkish</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e184" headers="d0e20 "> <p>SHIFT_JIS</p>
+ </td>
+<td valign="top" headers="d0e184 d0e26 "> <p>Shift-JIS, Japanese</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e195" headers="d0e20 ">TIS-620</td>
+<td valign="top" headers="d0e195 d0e26 ">TISI, Thai</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e200" headers="d0e20 "> <p>US-ASCII</p>
+ </td>
+<td valign="top" headers="d0e200 d0e26 "> <p>US ASCII</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e211" headers="d0e20 "> <p>UTF-8</p>
+ </td>
+<td valign="top" headers="d0e211 d0e26 "> <p>ISO 10646/Unicode, one-byte encoding</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e222" headers="d0e20 "> <p>UTF-16</p>
+ </td>
+<td valign="top" headers="d0e222 d0e26 "> <p>ISO 10646/Unicode, two-byte encoding</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e233" headers="d0e20 "> <p>UTF-16BE</p>
+ </td>
+<td valign="top" headers="d0e233 d0e26 "> <p>Unicode BigEndian</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e244" headers="d0e20 "> <p>UTF-16LE</p>
+ </td>
+<td valign="top" headers="d0e244 d0e26 "> <p>Unicode LittleEndian</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e255" headers="d0e20 ">WINDOWS-874</td>
+<td valign="top" headers="d0e255 d0e26 ">Thai, Microsoft<sup>®</sup></td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e262" headers="d0e20 "> <p>WINDOWS-1252</p>
+ </td>
+<td valign="top" headers="d0e262 d0e26 "> <p>ISO Latin-1</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e273" headers="d0e20 "> <p>WINDOWS-1255</p>
+ </td>
+<td valign="top" headers="d0e273 d0e26 "> <p>Hebrew</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e284" headers="d0e20 "> <p>WINDOWS-1256</p>
+ </td>
+<td valign="top" headers="d0e284 d0e26 "> <p>Arabic</p>
+ </td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e295" headers="d0e20 ">X-EUC-JP</td>
+<td valign="top" headers="d0e295 d0e26 ">EUC encoding, Japanese (alias for EUC-JP)</td>
+</tr>
+<tr><td valign="top" class="firstcol" id="d0e300" headers="d0e20 ">X-SJIS</td>
+<td valign="top" headers="d0e300 d0e26 ">Shift-JIS, Japanese (alias for SHIFT_JIS)</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html
new file mode 100644
index 0000000..15a14f9
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>XML tools - overview</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="cxmltool"><a name="cxmltool"><!-- --></a>
+
+<h1 class="topictitle1">XML tools - overview</h1>
+<div><p>This product provides a comprehensive visual XML development environment.
+The tool set includes components for building DTDs, XML schemas, XML, and
+XSL files.</p><p>The following XML editor tools are available:</p>
+<p>The <b>XML editor</b> is a tool for creating and viewing XML files. You
+can use it to create new XML files, either from scratch, existing DTDs, or
+existing XML schemas. You can also use it to edit XML files, associate them
+with DTDs or schemas, and validate them.</p>
+<p>The <b>DTD editor</b> is a tool for creating and viewing DTDs. Using the
+DTD editor, you can create DTDs, and generate XML schema files.</p>
+<p>The <b>XML schema editor</b> is a tool for creating, viewing, and validating
+XML schemas. You can use the XML schema editor to perform tasks such as creating
+XML schema components, importing and viewing XML schemas, generating relational
+table definitions from XML schemas, and generating Java beans for creating
+XML instances of an XML schema.</p>
+<div class="skipspace">Exercise caution when opening large files with any of the XML editors.
+If the memory limits of the workbench are exceeded, it will abruptly close
+without saving any data (and without warning or error messages). The number
+of elements in an XML file, not its size, is the best indicator of how much
+memory will be required. Memory requirements also depend on what else is open
+in the workbench - in some cases you can open a 15 megabytes file, but in
+other cases a one-megabyte file may cause problems. Therefore, we recommend
+you save all data in the workbench before opening large XML files. This is
+a permanent restriction.</div>
+<div class="skipspace"><p>The
+behavior of the XML parser when encountering an unresolvable URI (for example,
+in a DOCTYPE declaration) is to report a fatal IO error and stop any further
+processing. An unresolved URI is seen neither as a syntactic nor a semantic
+error and as such, the parser does not attempt to handle it. Essentially,
+the document remains unchecked. This is a known problem.</p>
+</div>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+<p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html
new file mode 100644
index 0000000..1646044
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Extending the content model of an XML document</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="rextctn"><a name="rextctn"><!-- --></a>
+
+<h1 class="topictitle1">Extending the content model of an XML document</h1>
+<div><p>You can use the XML schema <samp class="codeph">any</samp> element to extend
+the content model of an XML document.</p><div class="skipspace"><p>For example, you have an XML schema file called Book.xsd which
+contains a complex type called BookType. BookType contains 4 elements (title,
+author, year, and ISBN) and one <samp class="codeph">any</samp>element. The namespace
+for the <samp class="codeph">any</samp> element is <samp class="codeph">##any</samp>. This means
+that in an instance document, you can insert any XML element to extend the
+definition of the BookType. </p>
+<p>You can also provide a more specific
+namespace. For example, you have another schema called My_Book.xsd, which
+contains a complex type called My_BookType. My_BookType contains 4 elements
+(title, author, year, and ISBN) and one <samp class="codeph">any</samp> element, but
+in this case the namespace for the BookType element is www.wesley.com. This
+means that in an instance document, you can insert any XML element to extend
+the definition of the BookType, provided that they belong to the namespace
+http://www.wesley.com. </p>
+</div>
+</div>
+
+<div>
+
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html
new file mode 100644
index 0000000..a48e561
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Limitations of XML Editor</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="rlimitations_slushXML"><a name="rlimitations_slushXML"><!-- --></a>
+
+<h1 class="topictitle1">Limitations of XML Editor</h1>
+<div><p>This section describes known product aspect limitations and workarounds.</p><div class="skipspace" id="rlimitations_slushXML__unresolv_URI"><a name="rlimitations_slushXML__unresolv_URI"><!-- --></a><p>The
+behavior of the XML parser when encountering an unresolvable URI (for example,
+in a DOCTYPE declaration) is to report a fatal IO error and stop any further
+processing. An unresolved URI is seen neither as a syntactic nor a semantic
+error and as such, the parser does not attempt to handle it. Essentially,
+the document remains unchecked. This is a known problem.</p>
+</div>
+</div>
+<div class="runningfooter">
+ <br />
+ (C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
+ <br />
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html
new file mode 100644
index 0000000..e585f19
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating an XML file from scratch</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tcretxml"><a name="tcretxml"><!-- --></a>
+
+<h1 class="topictitle1">Creating an XML file from scratch</h1>
+<div><p>You can create a new empty XML file, which you can then edit in
+the XML editor.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
+but they will also work in many other perspectives.</p>
+<p>To create an XML
+file from scratch, follow these instructions:</p>
+</div>
+<ol><li class="skipspace"><span>If necessary, create a project to contain the XML file. </span></li>
+<li class="skipspace"><span>In the workbench, click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span> > <span class="uicontrol">XML</span> > <span class="uicontrol">XML</span></span>. </span> If you cannot see the <span class="uicontrol">XML</span> option,
+select the <span class="uicontrol">Show All Wizards</span> check box.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Next</span>. </span></li>
+<li class="skipspace"><span>Click the <span class="uicontrol">Create XML file from scratch</span> radio
+button.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">Next.</span></span></li>
+<li class="skipspace"><span>Select the project or folder that will contain the XML file.</span></li>
+<li class="skipspace"><span>In the <span class="uicontrol">File name</span> field, type the name of
+the XML file, for example <kbd class="userinput">MyXMLFile.xml</kbd>. The name of
+your XML file <var class="varname">must</var> end in <kbd class="userinput">.xml</kbd>.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span></li>
+</ol>
+<div class="skipspace"><p>The XML file appears in the Navigator view and, by default, automatically
+opens in the XML source page editor. The XML source page editor offers limited
+functionality compared to the XML editor, so before editing the file, you
+should close it, then right-click the file in the Navigator view and click <span class="uicontrol">Open
+With > XML Editor</span> to open the file in the XML editor. </p>
+<p>To
+make the XML editor the default editor for XML files, select <span class="uicontrol">Window
+> Preferences > Workbench > File Associations</span>, then select <span class="uicontrol">*.xml</span> and <span class="uicontrol">XML
+Editor</span> from the Associated Editors list. Click <span class="uicontrol">OK</span>. </p>
+</div>
+</div>
+
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcrexdtd.html" title="">Generating an XML file from a DTD </a><br />
+<a href="../topics/tcrexxsd.html" title="">Generating an XML file from an XML schema</a><br />
+<a href="../topics/txedttag.html" title="">Editing XML files</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html
new file mode 100644
index 0000000..e3fbfbc
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Generate an XML file from a DTD</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tcrexdtd"><a name="tcrexdtd"><!-- --></a>
+
+<h1 class="topictitle1">Generating an XML file from a DTD </h1>
+<div><div class="skipspace"><p>You can create an XML file from a DTD file. You can then further
+customize that file in the XML editor. Generating an XML file from a
+DTD can be useful if you want to quickly create an XML file that is based
+on your DTD file.</p>
+<p>The following instructions were written for the Resource
+perspective, but they will also work in many other perspectives.</p>
+<p>To
+create an XML file from a DTD file follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Navigator view, right-click the DTD file that you want to
+work with.</span></li>
+<li class="skipspace"><span>From its pop-up menu click <span class="menucascade"><span class="uicontrol">Generate</span> > <span class="uicontrol">XML File</span></span>.</span></li>
+<li class="skipspace"><span>Select a project or folder to contain the XML file and type a name
+for it.</span> The name of the file must end in <kbd class="userinput">.xml</kbd>.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Next</span>.</span></li>
+<li class="skipspace"><span>Select the <span class="uicontrol">Root element</span> of the XML file.</span> The root element of an XML file is the element that contains all other
+elements in that file. All the elements that you have defined in the DTD will
+be shown in the<span class="uicontrol">Root element</span> list.</li>
+<li class="skipspace"><span>Select from the following content options: </span><ul><li><span class="uicontrol">Create optional attributes</span> - Both mandatory
+and optional attributes will be generated. </li>
+<li><span class="uicontrol">Create optional elements</span> - Both mandatory and
+optional elements will be generated. </li>
+<li><span class="uicontrol">Create first choice of required choice</span> -
+The first option of a required choice will be generated in your XML file.</li>
+<li><span class="uicontrol">Fill elements and attributes with data</span> - any
+elements and attributes generated will be filled with sample data.</li>
+</ul>
+ <p>If you do not select any of these options, then only the minimum
+amount of content required for the XML file will be created.</p>
+</li>
+<li class="skipspace"><span>Specify the <span class="uicontrol">Public ID</span> or <span class="uicontrol">System
+ID</span>.</span> You do not need to specify both. If you do, the
+Public ID will be used before the System ID. .</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span></li>
+</ol>
+<div class="skipspace"><p>The XML file appears in the Navigator view and, by default, automatically
+opens in the XML source page editor. The XML source page editor offers limited
+functionality compared to the XML editor, so before editing the file, you
+should close it, then right-click the file in the Navigator view and click <span class="uicontrol">Open
+With > XML Editor</span> to open the file in the XML editor. </p>
+<p>To
+make the XML editor the default editor for XML files, select <span class="uicontrol">Window
+> Preferences > Workbench > File Associations</span>, then select <span class="uicontrol">*.xml</span> and <span class="uicontrol">XML
+Editor</span> from the Associated Editors list. Click <span class="uicontrol">OK</span>. </p>
+<p>The
+XML file will only contain the selected root element and any elements or attributes
+contained in the root element. You can now add elements, attributes, entities,
+and notations to the XML file, however, they must follow the rules established
+in the DTD that you used to create the XML file.</p>
+</div>
+</div>
+
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcretxml.html" title="You can create a new empty XML file, which you can then edit in the XML editor.">Creating an XML file from scratch</a><br />
+<a href="../topics/tcrexxsd.html" title="Generating an XML file from an XML schema"></a><br />
+<a href="../topics/txedttag.html" title="Editing XML files"></a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html
new file mode 100644
index 0000000..e41a7fe
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Generating an XML file from an XML schema</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tcrexxsd"><a name="tcrexxsd"><!-- --></a>
+
+<h1 class="topictitle1">Generating an XML file from an XML schema</h1>
+<div><div class="skipspace"><p>You can generate an XML file from an XML schema file. You can
+then further customize that file in the XML editor.</p>
+<p>Generating an XML
+file from an XML schema can be useful if you want to quickly create an XML
+file that is based on your XML schema.</p>
+<p>The following instructions were
+written for the Resource perspective, but they will also work in many other
+perspectives.</p>
+<p>To generate an XML file from a schema file follow these
+steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Navigator view, right-click the XML schema file that you
+want to work with.</span></li>
+<li class="skipspace"><span>From its pop-up menu click <span class="menucascade"><span class="uicontrol">Generate</span> > <span class="uicontrol">XML File</span></span>.</span></li>
+<li class="skipspace"><span>Select a project or folder to contain the XML file and type a name
+for it.</span> The name of the file must end in<tt class="sysout">.xml.</tt> .</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Next</span>.</span></li>
+<li class="skipspace"><span>Click the <span class="uicontrol">Root element</span> of the XML file.</span> The root element of an XML file is the element that contains all other
+elements in that file. All of the global elements you have defined in the
+XML schema will be included in the Root Element list. If you do not have any
+global elements in your XML schema, you cannot create an XML file from it.</li>
+<li class="skipspace"><span>Select from the following content options: </span><ul><li><span class="uicontrol">Create optional attributes</span> - Both mandatory
+and optional attributes will be generated</li>
+<li><span class="uicontrol">Create optional elements</span> - Both mandatory and
+optional elements will be generated.</li>
+<li><span class="uicontrol">Create first choice of required choice</span> -
+The first option of a required choice will be generated in your XML file.</li>
+<li><span class="uicontrol">Fill elements and attributes with data</span> - any
+elements and attributes generated will be filled with sample data.</li>
+</ul>
+ If you do not select any of these options, then only the minimum amount
+of content required for the XML file will be created.</li>
+<li class="skipspace"><span>The Namespace information section contains information about the
+target namespace of the XML schema, its prefix, and the schema location.</span> For more information about namespaces and namespace prefixes, refer
+to the Related reference below. </li>
+<li class="skipspace"><span>Select the entry you want to edit and click <span class="uicontrol">Edit</span>. </span></li>
+<li class="skipspace"><span>The value in the <span class="uicontrol">Namespace Name</span> field is
+the target namespace of the XML schema.</span> Your XML file should be
+associated with the same namespace as its XML schema is associated with.</li>
+<li class="skipspace"><span>All qualified elements and attributes in the XML file associated
+with the namespace will be prefixed with the <span class="uicontrol">Prefix</span> value. </span></li>
+<li class="skipspace"><span>The <span class="uicontrol">Location Hint</span> field contains the location
+of the XML schema.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span>, then <span class="uicontrol">Finish</span>.</span></li>
+</ol>
+<div class="skipspace"><p>The XML file appears in the Navigator view and, by default, automatically
+opens in the XML source page editor. The XML source page editor offers limited
+functionality compared to the XML editor, so before editing the file, you
+should close it, then right-click the file in the Navigator view and click <span class="uicontrol">Open
+With > XML Editor</span> to open the file in the XML editor. </p>
+<p>To
+make the XML editor the default editor for XML files, select <span class="uicontrol">Window
+> Preferences > Workbench > File Associations</span>, then select <span class="uicontrol">*.xml</span> and <span class="uicontrol">XML
+Editor</span> from the Associated Editors list. Click <span class="uicontrol">OK</span>. </p>
+<p>The
+XML file will contain the selected root element and any elements or attributes
+contained in the root element. It also contains information about the XML
+file namespace and location. You can now add elements and attributes to the
+XML file.</p>
+<p><b>Note:</b> In certain cases, when an XML file is generated
+from a complex XML schema file, the XML file may not be valid. If this occurs,
+you can open the generated file in the XML editor and correct any errors that
+occur. Usually, only a few errors need to be fixed. The following XML schema
+constructs may present problems:</p>
+<ol><li>Restrictions. Sometimes restricted elements are erroneously generated. </li>
+<li>Facets: Default generated data values may not conform to complex facets
+(for example, patterns).</li>
+<li> Abstract elements. abstract elements are sometimes erroneously generated.</li>
+</ol>
+</div>
+</div>
+
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcretxml.html" title="You can create a new empty XML file, which you can then edit in the XML editor.">Creating an XML file from scratch</a><br />
+<a href="../topics/tcrexdtd.html" title="Generating an XML file from a DTD"></a><br />
+<a href="../topics/txedttag.html" title="Editing XML files"></a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html
new file mode 100644
index 0000000..3b9e904
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing with DTD or XML schema constraints</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tedtcnst"><a name="tedtcnst"><!-- --></a>
+
+<h1 class="topictitle1">Editing with DTD or XML schema constraints</h1>
+<div><p>In the Design view, when you edit an XML file that has a set of
+constraints (that is, a set of rules) defined by a DTD or an XML schema, you
+can turn the constraints on and off to provide flexibility in the way you
+edit, but still maintain the validity of the document periodically.</p><div class="skipspace"><p> When the constraints are turned on, and you are working in the
+Design view, the XML editor prevents you from inserting elements, attributes,
+or attribute values not permitted by the rules of the XML schema or DTD, and
+from removing necessary or predefined sets of tags and values. In this mode,
+an element's content must be valid to use the XML editor's guided editing
+options.</p>
+<p>You may want to turn the constraints off for an XML file if
+you need more flexibility. For example, you want to try working with elements
+or attributes not permitted by the associated DTD or XML schema, without actually
+removing the association with the DTD or XML schema.</p>
+<p>To turn the constraints
+for an XML file off, click <span class="uicontrol">XML > Turn Grammar Constraints Off</span>.
+After you have turned the constraints off for a file, you can insert or delete
+any element or attribute regardless of the DTD or XML schema rules. You can
+create new elements or attributes that are not in the DTD or schema - these
+Design view prompts will only appear when you have turned constraints off.
+The file may not be valid, however, if you do this. </p>
+<p>The following instructions
+were written for the Resource perspective, but they will also work in many
+other perspectives.</p>
+<p>The following is an example of what you can do if
+you turn the constraints of a DTD off:</p>
+</div>
+<ol><li class="skipspace"><span>Open the XML file in the XML editor (right-click the file in the
+Navigator view and click <span class="uicontrol">Open With > XML Editor</span>). </span></li>
+<li class="skipspace"><span>For example, you have a DTD that specifies that an element requires
+at least one of a specific child element: </span> <pre><!ELEMENT parentElement (childElement+)></pre>
+</li>
+<li class="skipspace"><span>If, in an XML file associated with your DTD, you attempt to remove
+the final child element of the element with the DTD constraints turned on,
+the editor will not allow you to do this, as it will make the document invalid.</span> You can confirm this by using the element's pop-up menu to verify that
+the<span class="uicontrol">Remove</span> option is grayed out.</li>
+<li class="skipspace"><span>To turn the DTD constraints off, click <span class="uicontrol">XML > Turn Grammar
+Constraints Off</span>. </span></li>
+<li class="skipspace"><span>If you attempt to remove the same child element with constraints
+off, the editor will allow you to.</span></li>
+<li class="skipspace"><span>To correct the invalid document, you will have to re-add the necessary
+element, or remove the invalid tagging or value.</span></li>
+</ol>
+<div class="skipspace">If you introduce errors into your files, you must save and validate
+the file in order to see a list of the errors you have introduced. They will
+be listed in the Problems view. After you fix the errors, you must save and
+validate your file again to see if the file is now valid.</div>
+</div>
+
+<div>
+
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing your DOCTYPE declaration</a><br />
+<a href="../topics/txmlcat.html" title="Adding an entry to the XML Catalog"></a><br />
+<a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes.">Updating XML files with changes made to DTDs and schemas</a><br />
+<a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema it is associated with. ">Editing your namespace information</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html
new file mode 100644
index 0000000..9716844
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing your DOCTYPE declaration</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tedtdoc">
+
+<h1 class="topictitle1">Editing your DOCTYPE declaration</h1>
+<div><p>The DOCTYPE declaration in an XML file is used at the beginning
+of it to associate it with a DTD file. You can edit your DOCTYPE declaration
+to change the DTD file your XML file is associated with.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
+but they will also work in many other perspectives.</p>
+<p>To edit your DOCTYPE
+declaration, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Design view of the XML editor, right-click <span class="uicontrol">DOCTYPE</span> and
+click <span class="uicontrol">Edit DOCTYPE</span>.</span></li>
+<li class="skipspace"><span>The value in the <span class="uicontrol">Root element mame</span> field
+should match the root element of your XML file exactly.</span> You should
+only edit the value in this field if your root element changes.</li>
+<li class="skipspace"><span>You can select a Public ID for any existing XML Catalog entries
+by clicking <span class="uicontrol">Browse</span>. </span> The value in the <span class="uicontrol">Public
+ID</span> field is the Public Identifier. It is used to associate the
+XML file (using an XML Catalog entry) with a DTD file. For more information
+on XML Catalog entries, refer to the related tasks below.</li>
+<li class="skipspace"><span>The value in the <span class="uicontrol">System ID</span> field is the
+DTD the XML file is associated with. Type the path of the DTD file you want
+the XML file associated with in this field. </span> <b>Note</b>: When
+the XML file is processed by the XML processor, it will first try to use the
+Public ID to locate the DTD, and if this fails, it will use the System ID
+to find it.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span>.</span></li>
+</ol>
+</div>
+
+<div>
+
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a><br />
+<a href="../topics/txmlcat.html" title="Adding an entry to the XML Catalog"></a><br />
+<a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes.">Updating XML files with changes made to DTDs and schemas</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html
new file mode 100644
index 0000000..98a2024
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Specifying line delimiters</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tedtenc"><a name="tedtenc"><!-- --></a>
+
+<h1 class="topictitle1">Specifying line delimiters</h1>
+<div><p>Various development platforms use different line delimiters to
+indicate the start of a new line. Select the operating system that applies
+to your development or deployment platform.</p><div class="skipspace"><p>The following instructions were written for the
+XML perspective, but they will also work in many other perspectives.</p>
+<p>To
+specify the line delimiter you want to use:</p>
+</div>
+<ol><li><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Web and XML files</span> > <span class="uicontrol">XML Files</span></span>.</span></li>
+<li><span>From the <span class="uicontrol">Line delimiter</span> field, select the
+operating system that applies to your development or deployment platform. </span></li>
+<li><span>Click <span class="uicontrol">Apply</span>, then <span class="uicontrol">OK</span>.</span></li>
+</ol>
+<div class="skipspace"></div>
+</div>
+
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html
new file mode 100644
index 0000000..6544545
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Updating XML files with changes made to DTDs and schemas</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tedtgram"><a name="tedtgram"><!-- --></a>
+
+<h1 class="topictitle1">Updating XML files with changes made to DTDs and schemas</h1>
+<div><p>If you make changes to a DTD file or XML schema associated with
+an XML file (that is currently open), click <span class="uicontrol">XML > Reload Dependencies</span> to
+update the XML file with these changes.</p><div class="skipspace"><p>The changes will be reflected in the guided editing mechanisms
+available in the editor, such as content assist.</p>
+<p>For example, you have
+a DTD file called "Contact.dtd" and an XML file called "Contact.xml" associated
+with it. Contact.dtd contains a root element called <span class="uicontrol">Contact</span> that
+can contain any of the following children elements: <span class="uicontrol">Name</span>,
+ <span class="uicontrol">PostalAddress</span>, <span class="uicontrol">Email</span>. If you
+remove the child element <span class="uicontrol">Email</span> from the DTD, you will
+no longer be able to add an <span class="uicontrol">Email</span> child element to
+your root element Contact in your Contact.xml file. This change, however,
+will not come into effect until you save your changes in the DTD and click <span class="uicontrol">XML
+> Reload Dependencies</span> in the XML editor. Until you click it, you
+will still be able to add <span class="uicontrol">Email</span> elements to Contact.xml.</p>
+<p>This
+feature is very handy when you are making updates to both DTDs and XML schemas
+and XML files that are associated with DTDs and XML schemas.</p>
+</div>
+</div>
+
+<div>
+
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a><br />
+<a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing your DOCTYPE declaration</a><br />
+<a href="../topics/txmlcat.html" title="Adding an entry to the XML Catalog"></a><br />
+<a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema it is associated with. ">Editing your namespace information</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html
new file mode 100644
index 0000000..0278097
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing your XML processing instructions</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tedtproc"><a name="tedtproc"><!-- --></a>
+
+<h1 class="topictitle1">Editing your XML processing instructions</h1>
+<div><p>A processing instruction is a syntax in XML for passing instructions
+along to the application using an XML document.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
+but they will also work in many other perspectives.</p>
+<p>To edit a processing
+instruction, follow these steps:</p>
+</div>
+<ol><li><span>In the Design view of the XML editor, right-click
+your processing instruction, and click <span class="uicontrol">Edit Processing Instruction</span>.</span></li>
+<li><span>The <span class="uicontrol">Target</span> field is used to identify the
+application the instructions belongs to.</span></li>
+<li><span>The <span class="uicontrol">Data</span> field contains the instructions.</span></li>
+<li><span>Click <span class="uicontrol">OK</span>.</span></li>
+</ol>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html
new file mode 100644
index 0000000..2745609
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing your namespace information</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tedtsch"><a name="tedtsch"><!-- --></a>
+
+<h1 class="topictitle1">Editing your namespace information</h1>
+<div><p>Your namespace information is used to provide various information
+about the XML file, such as the XML schema it is associated with. </p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
+but they will also work in many other perspectives.</p>
+<p>To edit your schema
+information, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Design view of the XML editor, right-click
+your root element and click <span class="uicontrol">Edit Namespaces</span>.</span></li>
+<li class="skipspace"><span>Your XML file may be associated with more than one namespace or
+schema.</span> Select the entry you want to edit and click <span class="uicontrol">Edit</span>.</li>
+<li class="skipspace"><span>The value in the <span class="uicontrol">Namespace Name</span> field is
+a namespace the XML file is associated with.</span> Your XML file should
+be associated with the same namespace(s) its XML schema is associated with.
+For more information about namespaces, refer to the related reference.</li>
+<li class="skipspace"><span>All qualified elements and attributes in the XML file associated
+with the namespace will be prefixed with the <span class="uicontrol">Prefix</span> value. </span></li>
+<li class="skipspace"><span>The <span class="uicontrol">Location Hint</span> field contains the location
+of the XML schema the XML file is associated with.</span> An XML Catalog
+Key or a namespace name can be specified in this field. Click <span class="uicontrol">Browse</span> to
+view all XML schemas in the workbench and XML Catalog. </li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span>, then click <span class="uicontrol">OK</span> again.</span></li>
+</ol>
+<div class="skipspace"><p>If you want to create a new association, click <span class="uicontrol">Add</span> instead
+of <span class="uicontrol">Edit</span>. You can then either click the <span class="uicontrol">Specify
+From Registered Namespace</span> radio button and select the namespace
+declarations you want to add or click the <span class="uicontrol">Specify New Namespace</span> radio
+button and fill in the fields as necessary. </p>
+</div>
+</div>
+
+<div>
+
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a><br />
+<a href="../topics/txmlcat.html" title="Adding an entry to the XML Catalog"></a><br />
+<a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes.">Updating XML files with changes made to DTDs and schemas</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html
new file mode 100644
index 0000000..8659090
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Setting source highlighting styles</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="ttaghilt"><a name="ttaghilt"><!-- --></a>
+
+<h1 class="topictitle1">Setting source highlighting styles</h1>
+<div><p>You can change how the XML source code is displayed in the Source
+view of the XML editor. </p><div class="skipspace"><p>To set highlighting styles for the XML code, follow these steps:</p>
+</div>
+<ol><li><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol"> XML
+Styles</span></span>.</span></li>
+<li><span>In the <span class="uicontrol">Content type</span> list, select the source
+tag type that you wish to set a highlighting style for. You can also
+click text in the sample text to specify the source tag type that you wish
+to set a highlighting style for.</span></li>
+<li><span>Click the <span class="uicontrol">Foreground</span> box.</span></li>
+<li><span>Select the color that you want the text of the tag to appear in
+and click <span class="uicontrol">OK</span>.</span></li>
+<li><span>Click the<span class="uicontrol">Background</span> box.</span></li>
+<li><span>Select the color that you want to appear behind the tag and click<span class="uicontrol">OK</span>. </span></li>
+<li><span>Select the <span class="uicontrol">Bold</span> check box if you want to
+make the type bold.</span></li>
+<li><span>Click <span class="uicontrol">Restore Defaults</span> to set
+the highlighting styles back to their default values.</span></li>
+<li><span>Click <span class="uicontrol">OK</span> to save your changes. </span></li>
+</ol>
+
+
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html
new file mode 100644
index 0000000..a3c3c37
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Using XML content assist</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="twcdast"><a name="twcdast"><!-- --></a>
+
+<h1 class="topictitle1">Using XML content assist</h1>
+<div><p>You can use content assist to help you finish a tag or line of
+code in the Source view of the XML editor. You can also use content assist
+to insert macros into your XML code. The placement of the cursor in your source
+file provides the context for the content assist to offer suggestions for
+completion.</p><div class="skipspace"><p>You can launch content assist in any of the following ways:</p>
+<ul><li>From the <span class="uicontrol">Edit</span> menu, click <span class="uicontrol">Content Assist</span>,
+or</li>
+<li>Press Ctrl+Space, or</li>
+</ul>
+<p>In addition, you can set up an option that causes content assist to
+pop up automatically when certain characters are typed. To set up this option,
+click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol"> Preferences</span></span> to open the Preferences window, then click <span class="menucascade"><span class="uicontrol">Web
+and XML</span> > <span class="uicontrol">XML Files </span> > <span class="uicontrol">XML Source</span></span> . In the <span class="uicontrol">Content assist</span> group box, select
+the <span class="uicontrol">Automatically make suggestions</span> check box, and supply
+any additional characters that should trigger content assist.</p>
+<p>If your
+cursor is in a position where content assist is available, a pop-up list of
+available choices is displayed when you launch content assist. The list is
+based on the context and whether a DTD or XML schema is associated with the
+XML file being edited. For example, if you have an Address element that can
+contain any of the following children elements: Name, Street, City, Zip Code,
+Country, and Province, if you place your cursor after any of them and launch
+content assist, all of the child elements will be listed in the content assist
+list.</p>
+<p>The content assist list displays all valid tags for the current
+cursor position, including templates. If your grammar constraints are turned
+off, all available tags, not just valid ones are displayed. </p>
+<p> </p>
+<p>As
+you type the first one or two letters of the tag that you want, the list automatically
+refreshes with alphabetized choices that match your input.</p>
+<p><b>Note</b>:
+The list only refreshes as described if you first type <kbd class="userinput"><</kbd> before
+prompting for content assist.</p>
+<p>Scroll down and select the tag that you
+want to use by double-clicking on it. </p>
+</div>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html
new file mode 100644
index 0000000..d2c00ff
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Working with XML templates</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="twmacro"><a name="twmacro"><!-- --></a>
+
+<h1 class="topictitle1">Working with XML templates</h1>
+<div><p>XML content assist provides a comment template, a chunk of predefined
+code that you can insert into a file. You can use the default template as
+provided, customize that template, or create your own templates.</p><div class="skipspace">For example, you may work on a group of XML pages that should all
+contain a table with a specific appearance. Create a template that contains
+the tags for that table, including the appropriate attributes and attribute
+values for each tag. (You can copy and paste the tags from a structured text
+editor into the template's Pattern field.) Then select the name of the template
+from a content assist proposal list whenever you want to insert your custom
+table into an XML file.<p>To create a new XML template follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML
+Templates</span></span>.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">New</span> if you want to create a completely
+new template.</span></li>
+<li class="skipspace"><span>Supply a new template name and description</span></li>
+<li class="skipspace"><span>Specify the <span class="uicontrol">Context</span> for the template.</span> This is the content in which the template is available in the proposal
+list when content assist is requested. </li>
+<li class="skipspace"><span>Specify the <span class="uicontrol">Pattern</span> for your template using
+the appropriate tags, attributes, or attribute values to be inserted by contente
+assit.</span></li>
+<li class="skipspace"><span>If you want to insert a variable, click the <span class="uicontrol">Variable</span> button
+and select the variable to be inserted. </span> For example, the word_selection
+variable indicates the word that is selected at the beginning of template
+insertion, and the cursor variable determines where the cursor will be after
+the template is inserted in the HTML document</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> and then <span class="uicontrol">OK</span> to
+save your changes.</span></li>
+</ol>
+<div class="skipspace">You can edit, remove, import, or export a template by using the same
+Preferences page. If you have modified a default template, you can restore
+it to its default value. You can also restore a removed template if you have
+not exited from the workbench since it was removed. <p>If you have a template
+that you do not want to remove but you no longer want the template to appear
+in the content assist list, go to the Templates preferences page and templates
+its check box.</p>
+</div>
+</div>
+
+<div>
+
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html
new file mode 100644
index 0000000..cacbc1e
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Validating XML files</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="twxvalid"><a name="twxvalid"><!-- --></a>
+
+<h1 class="topictitle1">Validating XML files</h1>
+<div><div class="skipspace"><p>The XML editor will process XML files that are invalid or not
+well-formed. The editor uses heuristics to open a file using the best interpretation
+of the tagging that it can. For example, an element with a missing end tag
+is simply assumed to end at the end of the document. As you make updates to
+a file, the editor incrementally reinterprets your document, changing the
+highlighting, tree view, and so on. Many formation errors are easy to spot
+in the syntax highlighting, so you can easily correct obvious errors on-the-fly.
+However, there will be other cases when it will be beneficial to perform formal
+validation on your documents.</p>
+</div>
+<div class="p"><span>You can validate your file by selecting it in the
+Navigator view, right-clicking it, and clicking <span class="uicontrol">Validate XML file</span>.</span></div>
+<div class="skipspace"><p>Any validation problems are indicated in the Problems view. For
+more details about a problem, right-click on the problem message and click <span class="uicontrol">Show
+Details</span>. </p>
+</div>
+<div class="skipspace"><p>In the Problems view, you can double-click on individual errors,
+and you will be taken to the invalid tag in the file, so that you can make
+corrections. </p>
+<p><b>Note</b>: If you receive an error message indicating
+that the Problems view is full, you can increase the number of error messages
+allowed by selecting <span class="menucascade"><span class="uicontrol">Properties</span> > <span class="uicontrol">Validation</span></span> from the project's pop-up menu and specifying the maximum number
+of error messages allowed. You must select the <span class="uicontrol">Override validation
+preferences</span> check box in order to be able to do this.</p>
+<p>As
+well, you can set up a project's properties so that different types of project
+resources are automatically validated when you save them. From a project's
+pop-up menu select <span class="uicontrol">Properties</span>, then select <span class="uicontrol">Validation</span>.
+Any validators you can run against your project will be listed in the
+Validation page. </p>
+</div>
+</div>
+
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html
new file mode 100644
index 0000000..3cf7c09
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html
@@ -0,0 +1,118 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing in the Design view</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="txedtdes"><a name="txedtdes"><!-- --></a>
+
+<h1 class="topictitle1">Editing in the Design view</h1>
+<div><p>The XML editor has a Design view, which represents the XML file
+simultaneously as a table and a tree. This helps make navigation and editing
+easier. Content and attribute values can be edited directly in the table cells,
+while pop-up menus on the tree elements give alternatives that are valid for
+that particular element.</p><div class="skipspace"><p> For example, the <span class="uicontrol">Add child</span> menu item will
+list only those elements from a DTD or XML schema which would be valid children
+at that point.</p>
+<p>When you have an XML file associated with an XML schema
+or DTD file, certain tags and rules for that file have already been established,
+which is why the Design view can provide prompts (via a pop-up menu) for those
+tags. When you create an XML file that is not associated with an XML schema
+or DTD file, it has no tags or rules associated with it, so the Design view
+cannot provide prompts for specific tags, but it can provide prompts to create
+new elements and attributes.</p>
+<p>For any XML file associated with an XML
+schema or DTD file, you can use the Design view to add any items defined in
+the XML schema or DTD (such as elements and attributes) to the XML file. You
+can also use it to add processing instructions and comments to all XML files. </p>
+<p>For
+more information on the icons used in the Design view, refer to the related
+reference.</p>
+<p>The following instructions were written for the Resource
+perspective, but they will also work in many other perspectives.</p>
+<p>To
+edit an XML file in the Design view, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open the XML file that you want to work with in the XML editor
+(right-click the file in the Navigator view and click <span class="uicontrol">Open With
+> XML Editor</span>). If necessary, click the <span class="uicontrol">Design</span> tab.</span></li>
+<li class="skipspace"><span>To expand all the items in your XML file, click the <span class="uicontrol">Expand
+All</span> toolbar button <img src="../images/expand_all.gif" />.</span></li>
+<li class="skipspace"><span>To collapse them, click the <span class="uicontrol">Collapse All</span> toolbar
+button <img src="../images/collapse_all.gif" />.</span></li>
+<li class="skipspace"><span>Right-click the item that you want to work with.</span> Some
+or all of the following options (as applicable) will be available from the
+pop-up menu that appears. For more information on these options, refer to
+the related tasks:<ul><li> <span class="uicontrol">Add DTD Information</span> - Click this if you want to
+associate the XML file with a DTD</li>
+<li> <span class="uicontrol">Edit DOCTYPE</span> - Click this if you want to edit
+the DOCTYPE declaration.</li>
+<li> <span class="uicontrol">Edit Namespaces</span> - Click this if you want to edit
+the existing namespace information or create a new association with a namespace.</li>
+<li> <span class="uicontrol">Edit Processing Instruction</span> - Click this if you
+want to edit the processing instruction.</li>
+<li> <span class="uicontrol">Remove</span> - Click this if you want to remove the
+item that you have selected from the XML file. This option will not be available
+if the item you want to remove must exist (for example, in your DTD, you have
+declared that "One or more" of the item must always exist in your XML file,
+and the item you have selected is the only one that exists in your XML file).</li>
+<li> <span class="uicontrol">Add Attribute</span> - Click this if you want to add
+an attribute to the element that you selected. Any attributes you are allowed
+to add to the element will be listed. After you have added the attribute to
+the XML file, you can click in the right-hand column to change the value of
+the attribute. If the attribute has set values, they will appear in a list. </li>
+<li> <span class="uicontrol">Add Child</span> - Click this to add another element,
+a comment, or a processing instruction as a child of the parent element.</li>
+<li> <span class="uicontrol">Add Before</span> - Click this to add a child element,
+comment, or processing instruction that can go before the item you have selected.
+For example, if you have a parent element called "CD Collections" that can
+contain an unlimited amount of children called "CD", you could click a CD
+element and click <span class="menucascade"><span class="uicontrol">Add Before</span> > <span class="uicontrol"> CD</span></span> , as a CD element can go before another CD element.</li>
+<li> <span class="uicontrol">Add After</span> - Click this to add a child element,
+comment, or processing instruction that can go after the item you have selected.
+For example, if you have a parent element called "CD Collections" that can
+contain an unlimited amount of children called "CD", you could click a CD
+element and click <span class="menucascade"><span class="uicontrol">Add After</span> > <span class="uicontrol"> CD</span></span>, as a CD element can go after another CD element.</li>
+<li> <span class="uicontrol">Replace With</span> - Click this if you want to replace
+one item with another. This option is not available if you turn grammar constraints
+off or if there are no valid alternatives for you to replace the item with.</li>
+</ul>
+</li>
+<li class="skipspace"><span>Click the appropriate option.</span></li>
+</ol>
+<div class="skipspace"><p>Any changes you make in the Design view are also reflected in the
+Source view and the Outline view.</p>
+</div>
+</div>
+
+<div>
+<blockquote>
+<div class="ulchildlink"><b><a href="../topics/tedtdoc.html">Editing your DOCTYPE declaration</a></b><br />
+The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.</div>
+<div class="ulchildlink"><b><a href="../topics/tedtsch.html">Editing your namespace information</a></b><br />
+Your namespace information is used to provide various information about the XML file, such as the XML schema it is associated with. </div>
+<div class="ulchildlink"><b><a href="../topics/tedtproc.html">Editing your XML processing instructions</a></b><br />
+A processing instruction is a syntax in XML for passing instructions along to the application using an XML document.</div>
+</blockquote>
+
+
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html
new file mode 100644
index 0000000..e1a74c0
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing in the Source view</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="txedtsrc"><a name="txedtsrc"><!-- --></a>
+
+<h1 class="topictitle1">Editing in the Source view</h1>
+<div><p>You can use the Source view to view and work with a file's source
+code directly.</p><div class="skipspace"><p> The Source view has many text editing features, such as:</p>
+<dl><dt class="bold">Syntax highlighting</dt>
+<dd>Each tag type is highlighted differently, enabling you to easily find
+a certain kind of tag for editing. In addition, syntax highlighting is valuable
+in locating syntax errors. For example, if you begin a comment in the middle
+of the document with <samp class="codeph"><!--</samp> everything until the next <samp class="codeph">--></samp> is
+considered a comment, and will be highlighted accordingly. The large highlighted
+area will indicate that you need to add <samp class="codeph">--></samp> to close the
+comment.<p>You can customize the syntax highlighting. Refer to the related
+tasks for more information.</p>
+</dd>
+</dl>
+<dl><dt class="bold">Unlimited undo and redo</dt>
+<dd>These options allow you to incrementally undo and redo every change made
+to a file for the entire editing session. For text, changes are incremented
+one character or set of selected characters at a time.</dd>
+<dt class="bold">Content assist</dt>
+<dd>Content assist helps you finish tags and insert macros. </dd>
+<dt class="bold">Template</dt>
+<dd>You can access templates (using content assist) to help you quickly add
+regularly-used tagging combinations.</dd>
+<dt class="bold">Node selection</dt>
+<dd>Based on the location of your cursor (or selection in the Outline view),
+the node selection indicator highlights the line numbers that include a node
+(for example, an element or attribute), in the vertical ruler in the left
+area of the Source view.</dd>
+<dt class="bold">Pop-up menu options</dt>
+<dd>From the editor's pop-up menu, you have many of the same editing options
+available as you do from the workbench <b>Edit</b> menu. You can select menu
+options such as: <span class="uicontrol">Cleanup Document,</span> to open the <span class="uicontrol">Cleanup</span>
+dialog, which contains settings to update a document so that it is well-formed
+and formatted and <span class="uicontrol">Format,</span> which formats either the
+entire document or selected elements.</dd>
+<dt class="bold">"Smart" double clicking</dt>
+<dd>You can use double-click to select attribute values, attribute-value pairs,
+and entire tag sets to quickly update, copy, or remove content.</dd>
+</dl>
+<p>To edit an XML file in the Source view, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open the XML file you want to work with in the XML editor (right-click
+the file in the Navigator view and click <span class="uicontrol">Open With > XML Editor</span>). </span> You may need to click the <span class="uicontrol">Source</span> tab. Typically,
+all that you will need to do to open the file is to double-click it in the
+Navigator view. If this does not work, right-click it and click <span class="uicontrol">Open
+With > XML Editor</span>.</li>
+<li class="skipspace"><span>Edit the code as necessary, using any of the available features.</span> As you move the cursor within your XML file (or select items from the
+Outline view), the node selection indicator will highlight the line numbers
+that encompass the node (for example, an element or attribute). You can use
+smart double-clicking behavior to select attribute values, attribute-value
+pairs, and entire tag sets to quickly update, copy, or remove content.</li>
+<li class="skipspace"><span>At intervals, you may wish to format individual nodes, or the entire
+XML file to restore element and attribute indentation to see nesting hierarchies
+more clearly in the file.</span></li>
+<li class="skipspace"><span>If desired, validate and save the XML file.</span></li>
+</ol>
+<div class="skipspace"><p>Any changes you make in the Source view are also reflected in the
+Design view and the Outline view.</p>
+</div>
+</div>
+
+<div>
+
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files">XML editor</a><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html
new file mode 100644
index 0000000..d282f25
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing XML files</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="txedttag"><a name="txedttag"><!-- --></a>
+
+<h1 class="topictitle1">Editing XML files</h1>
+<div><div class="skipspace"><p>To open an XML file in the XML editor, right-click it in the Navigator
+view and click <span class="menucascade"><span class="uicontrol">Open With</span> > <span class="uicontrol">XML
+Editor</span></span>. To make the XML editor the default editor
+for XML files, select <span class="uicontrol">Window > Preferences > Workbench > File Associations</span>,
+then select <span class="uicontrol">*.xml</span> and <span class="uicontrol">XML Editor</span> from
+the Associated Editors list. Click <span class="uicontrol">OK</span>. </p>
+<p>We
+recommend working in the Resource perspective when you are developing XML
+files. The views that appear by default in this perspective (such as
+the Outline view) help facilitate XML development.</p>
+<p>The XML editor enables
+you to directly edit XML files. There are several different views you
+can use to edit your files:</p>
+<ul><li><b>Source view</b> - you can manually insert, edit, and delete elements
+and attributes in the Source view of the XML editor. To facilitate this effort,
+you can use content assist while you are in the Source view.</li>
+<li><b>Design view</b> - you can insert, delete, and edit elements, attributes,
+comments, and processing instructions in this view.</li>
+<li><b>Properties view</b> - you can edit attribute values in this view.</li>
+<li><b>Outline view </b>- you can insert, delete, and edit elements,
+comments, and processing instructions in this view.</li>
+</ul>
+<p>Often, you may find that you have more than one way to perform a specific
+task. For example, you have an XML file "MySchoolSubjects.xml" associated
+with an XML schema file "SchoolSubjects.xsd" which list all the subjects taught
+in a school. You want to insert a new element "Math" into your file. You can
+do so the following ways:</p>
+<ul><li>In the Outline or Design view, right-click the appropriate parent element
+and select <span class="uicontrol">Math</span> from the <span class="uicontrol">Add Child</span> pop-up
+menu. </li>
+<li>In the Source view, use content assist to help you find the appropriate
+location and code for the <span class="uicontrol">Math</span> element.</li>
+<li>In the Source view, type the code for the <span class="uicontrol">Math</span> element
+in the file.</li>
+</ul>
+</div>
+</div>
+
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html
new file mode 100644
index 0000000..28450de
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding an entry to the XML Catalog</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="txmlcat"><a name="txmlcat"><!-- --></a>
+
+<h1 class="topictitle1">Adding an entry to the XML Catalog</h1>
+<div><div class="skipspace"><p>An XML Catalog entry contains two parts - a Key (which represents
+a DTD or XML schema) and a URI (which contains information about a DTD or
+XML schema's location). You can place the Key in an XML file. When the
+XML processor encounters it, it will use the XML Catalog entry to find the
+location of the DTD or XML schema associated with the Key. </p>
+<p>XML
+Catalog entries can be used in various situations. For example, you are working
+on an XML file on your main desktop computer and point its <samp class="codeph">schemaLocation</samp> towards
+a schema called <samp class="codeph">c:\MySchema.xsd</samp>. You then save it to your
+laptop computer so you can work on it later. When you open the file on your
+laptop, however, you encounter a problem - the XML editor cannot find the <samp class="codeph">MySchema.xsd</samp> schema because
+it is actually installed on your D drive. You will have to edit the <samp class="codeph">schemaLocation</samp>to
+point to <samp class="codeph">d:\MySchema.xsd</samp>. When you have finished editing
+the XML file and are ready to publish it on the Web, you will need to edit
+the URI again so that it points to a resource that is accessible on the Web.
+By now, the problem is obvious. A URI used within an XML file is not as portable
+as you would like it to be. To avoid making frequent changes to your XML document,
+you can use the XML Catalog.</p>
+<p>An XML Catalog entry is used by an XML
+processor when resolving entity references. You can provide rules to the catalog
+to specify how entities should be resolved. If you consider the example above,
+you could specify a rule that redirects an Internet resource reference (for
+example, <samp class="codeph">"http://www.ibm.com/published-schemas/MySchema.xsd"</samp>)
+so that it points to a resource on the developer's local machine (for example,
+ <samp class="codeph">"file:///C:/MySchema.xsd"</samp>). Now, instead of frequently editing
+XML documents to update the URIs (especially when there may be many documents
+in your project), you only need to update a single rule in your XML Catalog.</p>
+<p>More
+information on XML Catalog entries is included in the sample <a href="aexpledt.html">Exploring
+the XML editor</a>.</p>
+<p>The following instructions were written for the
+XML perspective, but they will also work in many other perspectives.</p>
+<p>To
+add an entry to the XML Catalog, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open the XML file that you want to associate with a DTD or XML
+schema.</span></li>
+<li class="skipspace"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Catalog</span></span>.</span></li>
+<li class="skipspace"><span>The <span class="uicontrol">XML Catalog Entries</span> field contains
+a list of any user-defined and plug-in defined catalog entries.</span><ol type="a"><li><span>Select any entry to see details about it in the <span class="uicontrol">Details</span> field. </span></li>
+<li><span>Click <span class="uicontrol">New</span> to create a new catalog entry.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>In the <span class="uicontrol">URI</span> field, type the location of the
+DTD or XML schema. You can only browse for the DTD or XML schema if it
+is located in the workbench.</span></li>
+<li class="skipspace"><span>If you specified a DTD in the <span class="uicontrol">URI</span> field,
+you can select either <span class="uicontrol">Public ID</span> or <span class="uicontrol">System
+ID</span> from the <span class="uicontrol">Key Type</span> field.</span> If
+you select<span class="uicontrol">Public ID,</span> the value you enter in the <span class="uicontrol">Key</span> field
+should be the same as the Public ID in the XML file's DOCTYPE declaration.
+If you select <span class="uicontrol">System ID</span>, the value you enter should
+correspond to the System ID in an XML file's DOCTYPE declaration.</li>
+<li class="skipspace"><span>If you specified an XML schema in the <span class="uicontrol">URI</span> field,
+you can select either <span class="uicontrol">Namespace Name</span> or <span class="uicontrol">Schema
+Location</span> from the <span class="uicontrol">Key Type</span> field.</span> If the schema defines a target namespace, it will automatically appear
+in the<span class="uicontrol">Key</span> field. Otherwise, you can enter the schema
+location in the <span class="uicontrol">Key</span> field.</li>
+<li class="skipspace"><span>Select the <span class="uicontrol">Specify alternative Web address</span> check
+box if you want to be able to specify an alternate Web address for the resource.</span> This Web address is used when an XML instance is generated from this
+catalog entry. <b>Note</b>: This option is only available if you select <span class="uicontrol">Public
+ID</span> (for a DTD) or <span class="uicontrol">Namespace Name</span> (for
+a schema) in the <span class="uicontrol">Key type</span> field.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span>.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">Advanced</span> if you want to import or
+export any XML Catalog settings.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">Export</span> if you want to persist the
+XML Catalog information. Only your user specified entries will be exported.</span><ol type="a"><li class="skipspace"><span>You will be prompted to select a project and provide a file
+name to store your catalog entries in an .xmlcatalog file, which can be opened
+from the Navigator view.</span> Snce your catalog entries are stored in
+an .xmlcatalog file, you can check them in and out and share them like any
+other project resource.</li>
+<li class="skipspace"><span> Click<span class="uicontrol">OK</span>.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Import</span> if you want to import an .xmlcatalog
+file. You will be prompted to select the file you want to import.</span><ol type="a"><li><span>When you import a .xmlcatalog file, any entries in it will be
+loaded into the XML Catalog (and any existing entries will be overwritten). </span></li>
+<li><span>Click <span class="uicontrol">OK</span>.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span> to close the Advanced XML Catalog
+Preferences dialog.</span></li>
+<li class="skipspace"><span>Make sure the XML file is in focus and click the<span class="uicontrol">Reload
+dependencies</span> toolbar button. </span></li>
+</ol>
+<div class="skipspace">The XML file is now associated with the latest version of the XML
+schema or DTD.</div>
+</div>
+
+<div>
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlcat.html" title="There are two different ways to associate XML files with DTDs or XML schemas.">XML file associations with DTDs and XML schemas</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a><br />
+<a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing your DOCTYPE declaration</a><br />
+<a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes.">Updating XML files with changes made to DTDs and schemas</a><br />
+<a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema it is associated with. ">Editing your namespace information</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html
new file mode 100644
index 0000000..7053ccb
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Defining XML editor preferences</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="txprefs"><a name="txprefs"><!-- --></a>
+
+<h1 class="topictitle1">Defining XML editor preferences</h1>
+<div><p>You can set various preferences for the Source view of the XML
+editor such as the formatter indentation style, line wrapping rules, and content
+assist rules.</p><div class="skipspace"><p>The following instructions were written for the XML perspective,
+but they will also work in many other perspectives.</p>
+<p>To define XML preferences,
+perform the following steps:</p>
+</div>
+<ol><li class="skipspace"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML
+Source</span></span>.</span></li>
+<li class="skipspace"><span>Enter a maximum width for formatted lines in the <span class="uicontrol">Line
+width</span> field</span> The default value is 72. </li>
+<li class="skipspace"><span>Select <span class="uicontrol">Split multiple attributes each on a new line</span> to
+start every attribute on a new line.</span></li>
+<li class="skipspace"><span>The <span class="uicontrol">Indent using tabs</span> check box is selected
+by default.</span> If you clear it, spaces are used instead of tab characters.</li>
+<li class="skipspace"><span>If you want blank lines to be removed when the document is formatted,
+select the <span class="uicontrol">Clear all blank lines</span> check box. </span> By default, blank lines are preserved in a formatted document.</li>
+<li class="skipspace"><span>You can specify certain characters ('<' is default) that will
+cause the content assist list to pop up automatically. Ensure the <span class="uicontrol">Automatically
+make suggestions</span> check box is selected and specify the characters
+in the <span class="uicontrol">Prompt when these characters are inserted</span> field. </span></li>
+<li class="skipspace"><span>The <span class="uicontrol">Use inferred grammar in absence of DTD/Schema </span>check
+box is selected by default. </span> If this box is selected, when you
+have an XML file that is not associated with a DTD or XML schema, you will
+still be able to get content assist - the tool will infer what should come
+next in your file based on the existing content.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> and then <span class="uicontrol">OK</span> to
+save your changes.</span></li>
+</ol>
+</div>
+
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html
new file mode 100644
index 0000000..49c1573
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Using xsi:type</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="txsityp"><a name="txsityp"><!-- --></a>
+
+<h1 class="topictitle1">Using xsi:type</h1>
+<div><p>If you have elements in your XML file whose type is a complex type,
+xsi:type support in the XML editor lets you choose between the complex type
+and any other complex types derived from it.</p><div class="skipspace"><p>The XML Schema specification allows you to derive types by extension.
+For example, you have an XML schema and you create a complex type for it called
+ <kbd class="userinput">Address</kbd>. You then add some basic elements to <kbd class="userinput">Address</kbd>,
+such as <kbd class="userinput">streetName</kbd> and <kbd class="userinput">city</kbd>. </p>
+<p>After
+this, you derive (by extension) two new complex types from <kbd class="userinput">Address</kbd> - <kbd class="userinput">USAddress</kbd> and <kbd class="userinput">UKAddress</kbd> You add a new element to <kbd class="userinput">USAddress</kbd> called
+ <kbd class="userinput">state</kbd>, and also a new element to <kbd class="userinput">UKAddress</kbd> called <kbd class="userinput">postcode</kbd>.</p>
+<p>After
+you have done this, you create two more elements - <kbd class="userinput">billTo</kbd> and <kbd class="userinput">shipTo</kbd> -
+as <tt class="sysout">Address</tt> types <tt class="sysout">.</tt></p>
+<p>When
+you create an XML instance document for an element such as <tt class="sysout">billTo</tt> or
+ <kbd class="userinput">Address</kbd>, an xsi:type attribute will automatically
+be added to it. For example:</p>
+<pre><billTo xsi:type="ipo:Address"></pre>
+<p>The
+xsi:type attribute is used to identify derived complex types (as well as complex
+types that have been derived from).</p>
+<p>In the Design view of the XML editor,
+a list will be available, letting you select the appropriate type definition
+(<span class="uicontrol">Address</span>, <span class="uicontrol">USAddress</span>, or <span class="uicontrol">UKAddress</span>).
+The guided editing for the content model will reflect the type definition
+that you choose. For example, if you select <span class="uicontrol">USAddress</span> ,
+your <samp class="codeph">billTo</samp> element can contain a <samp class="codeph">state</samp> element,
+but it cannot contain a <samp class="codeph">postcode</samp> element.</p>
+<p>The XML example
+"Editing and validating XML files" demonstrates <b>xsi:type</b> support.</p>
+<p>For
+more information about xsi:type, refer to the <b>Using Derived Types in Instance
+Documents</b> section in <a href="http://www.w3.org/TR/xmlschema-0/#UseDerivInInstDocs" target="_blank">XML Schema Part 0: Primer.</a></p>
+<p>For
+more information about validation semantics when xsi:type is used, refer to
+the <b>Schema-Related Markup in Documents Being Validated</b> section
+in <a href="http://www.w3.org/TR/xmlschema-1/#xsi_type" target="_blank">XML Schema Part 1: Structures</a> </p>
+</div>
+</div>
+
+<div>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
