This commit was manufactured by cvs2svn to create tag 'R1_0_1'.
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.cvsignore b/docs/org.eclipse.jst.jsp.ui.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.project b/docs/org.eclipse.jst.jsp.ui.infopop/.project
new file mode 100644
index 0000000..01be1bc
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jst.jsp.ui.infopop</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.jst.jsp.ui.infopop/EditorJspContexts.xml b/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts.xml
new file mode 100644
index 0000000..3abddee
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts.xml
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<contexts>
+<context id="jspf1000">
+<description>Select values for the following properties from the drop-down lists:
+- <b>Character code:</b> Specifies the page directive's pageEncoding value and contentType charset. In HTML documents, this value is also used for the <META> tag's charset property.
+- <b>Language:</b> Specifies the page directive's programming language.
+- <b>Content Type:</b> Specifies the contentType's TYPE value for the page directive. In HTML documents, this value is also used for the <META> tag's content property.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="jspr0010">
+<description>Select this option to open the <b>Refactor Rename</b> dialog, if applicable, which lets you rename the currently selected Java element and references to that element.
+</description>
+<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+<context id="jspr0020">
+<description>Select this option to open the <b>Refactor Move</b> dialog, if applicable, which lets you move the currently selected Java element. For example, you can move a method from one class to another.
+</description>
+<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="webx0050">
+<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save a JavaServer Pages (JSP) file.
+
+Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform.
+<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>.
+
+The encoding attribute is used to specify the default character encoding set that is used when creating JSP files. Changing the encoding causes any new JSP files that are created from scratch to use the selected encoding.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0051">
+<description>This page lets you customize the syntax highlighting that the JavaServer Pages (JSP) editor does when you are editing a file."
+
+The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting.
+
+The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that let you specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold.
+
+Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0052">
+<description>This page lets you create new and edit existing templates that will be used when you edit a JSP file.
+</description>
+<topic label="Adding and removing JSP templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html"/>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="xmlm1050">
+<description>Select this option to open the <b>Cleanup</b> dialog, which contains settings to update a document so that it is well-formed and formatted. Cleanup includes such activities as inserting missing tags, adding quotation marks around attribute values, node capitalization, and formatting a document.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+</contexts>
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts2.xml b/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts2.xml
new file mode 100644
index 0000000..780835a
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts2.xml
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<contexts>
+<context id="jspsource_source_HelpId">
+<description>The JSP source page editor lets you edit a JavaServer Pages file. The editor provides many text editing features, such as content assist, user-defined templates, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+<topic label="Adding and removing JSP templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html"/>
+<topic label="Making content assist work for JSP files" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html"/>
+</context>
+
+<context id="jspf1000">
+<description>Select values for the following properties from the drop-down lists:
+- <b>Character code:</b> Specifies the page directive's pageEncoding value and contentType charset. In HTML documents, this value is also used for the <META> tag's charset property.
+- <b>Language:</b> Specifies the page directive's programming language.
+- <b>Content Type:</b> Specifies the contentType's TYPE value for the page directive. In HTML documents, this value is also used for the <META> tag's content property.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="jspr0010">
+<description>Select this option to open the <b>Refactor Rename</b> dialog, if applicable, which lets you rename the currently selected Java element and references to that element.
+</description>
+<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+<context id="jspr0020">
+<description>Select this option to open the <b>Refactor Move</b> dialog, if applicable, which lets you move the currently selected Java element. For example, you can move a method from one class to another.
+</description>
+<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="webx0050">
+<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save a JavaServer Pages (JSP) file.
+
+Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform.
+<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>.
+
+The encoding attribute is used to specify the default character encoding set that is used when creating JSP files. Changing the encoding causes any new JSP files that are created from scratch to use the selected encoding.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0051">
+<description>This page lets you customize the syntax highlighting that the JavaServer Pages (JSP) editor does when you are editing a file."
+
+The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting.
+
+The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that let you specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold.
+
+Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0052">
+<description>This page lets you create new and edit existing templates that will be used when you edit a JSP file.
+</description>
+<topic label="Adding and removing JSP templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html"/>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="xmlm1050">
+<description>Select this option to open the <b>Cleanup</b> dialog, which contains settings to update a document so that it is well-formed and formatted. Cleanup includes such activities as inserting missing tags, adding quotation marks around attribute values, node capitalization, and formatting a document.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+</contexts>
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/JspWizContexts.xml b/docs/org.eclipse.jst.jsp.ui.infopop/JspWizContexts.xml
new file mode 100644
index 0000000..1d085e2
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/JspWizContexts.xml
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<contexts>
+ <context id="jspw0010">
+ <description>
+ Select the JSP template checkbox to create your JSP file based on a default template. You can choose to have your JSP created with HTML, XHTML, or XHTML with XML markup. If you do not select a template, your newly created JSP file will be completely blank.
+ </description>
+ </context>
+</contexts>
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.jsp.ui.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..1cc45ad
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %Plugin.name
+Bundle-SymbolicName: org.eclipse.jst.jsp.ui.infopop; singleton:=true
+Bundle-Version: 1.0.0.qualifier
+Bundle-Vendor: Eclipse.org
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/about.html b/docs/org.eclipse.jst.jsp.ui.infopop/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/build.properties b/docs/org.eclipse.jst.jsp.ui.infopop/build.properties
new file mode 100644
index 0000000..ce4c693
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/build.properties
@@ -0,0 +1,14 @@
+bin.includes = EditorJspContexts.xml,\
+ EditorJspContexts2.xml,\
+ about.html,\
+ plugin.xml,\
+ META-INF,\
+ /,\
+ META-INF/,\
+ EditorJspContexts2.xml,\
+ EditorJspContexts.xml,\
+ about.html,\
+ plugin.properties,\
+ plugin.xml
+ plugin.properties/
+src.includes = build.properties
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/plugin.properties b/docs/org.eclipse.jst.jsp.ui.infopop/plugin.properties
new file mode 100644
index 0000000..fc2e115
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/plugin.properties
@@ -0,0 +1,5 @@
+# NLS_MESSAGEFORMAT_VAR
+# ==============================================================================
+# Translation Instruction: section to be translated
+# ==============================================================================
+Plugin.name = JSP tools infopops
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/plugin.xml b/docs/org.eclipse.jst.jsp.ui.infopop/plugin.xml
new file mode 100644
index 0000000..3d1b116
--- /dev/null
+++ b/docs/org.eclipse.jst.jsp.ui.infopop/plugin.xml
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.1"?>
+
+<!-- ================================================= -->
+<!-- This is the plugin for declaring the help -->
+<!-- contributions for using the tool. -->
+<!-- ================================================= -->
+<!-- /*******************************************************************************
+ * 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>
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorJspContexts.xml" plugin="org.eclipse.jst.jsp.ui"/>
+ <contexts file="EditorJspContexts2.xml" plugin="org.eclipse.jst.jsp.core"/>
+ <contexts file="JspWizContexts.xml" plugin="org.eclipse.jst.jsp.ui"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.doc.user/.cvsignore b/docs/org.eclipse.wst.doc.user/.cvsignore
new file mode 100644
index 0000000..183c840
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/.cvsignore
@@ -0,0 +1,2 @@
+build.xml
+org.eclipse.wst.doc.user_1.0.0.jar
diff --git a/docs/org.eclipse.wst.doc.user/.project b/docs/org.eclipse.wst.doc.user/.project
new file mode 100644
index 0000000..cd8121a
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/.project
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.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.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..33c30e1
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.doc.user; singleton:=true
+Bundle-Version: 1.0.1.qualifier
+Bundle-Vendor: %providerName
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.doc.user/about.html b/docs/org.eclipse.wst.doc.user/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.doc.user/book.css b/docs/org.eclipse.wst.doc.user/book.css
new file mode 100644
index 0000000..3a1519e
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/book.css
@@ -0,0 +1,201 @@
+P.Code {
+ display: block;
+ text-align: left;
+ text-indent: 0.00pt;
+ margin-top: 0.000000pt;
+ margin-bottom: 0.000000pt;
+ margin-right: 0.000000pt;
+ margin-left: 15pt;
+ font-size: 10.000000pt;
+ font-weight: medium;
+ font-style: Regular;
+ color: #4444CC;
+ text-decoration: none;
+ vertical-align: baseline;
+ text-transform: none;
+ font-family: "Courier New";
+}
+
+H6.CaptionFigColumn {
+ display: block;
+ text-align: left;
+ text-indent: 0.000000pt;
+ margin-top: 3.000000pt;
+ margin-bottom: 11.000000pt;
+ margin-right: 0.000000pt;
+ margin-left: 0.000000pt;
+ font-size: 9.000000pt;
+ font-weight: medium;
+ font-style: Italic;
+ color: #000000;
+ text-decoration: none;
+ vertical-align: baseline;
+ text-transform: none;
+ font-family: "Arial";
+}
+
+P.Note {
+ display: block;
+ text-align: left;
+ text-indent: 0pt;
+ margin-top: 19.500000pt;
+ margin-bottom: 19.500000pt;
+ margin-right: 0.000000pt;
+ margin-left: 30pt;
+ font-size: 11.000000pt;
+ font-weight: medium;
+ font-style: Italic;
+ color: #000000;
+ text-decoration: none;
+ vertical-align: baseline;
+ text-transform: none;
+ font-family: "Arial";
+}
+
+EM.UILabel {
+ font-weight: Bold;
+ font-style: Regular;
+ text-decoration: none;
+ vertical-align: baseline;
+ text-transform: none;
+}
+
+EM.CodeName {
+ font-weight: Bold;
+ font-style: Regular;
+ text-decoration: none;
+ vertical-align: baseline;
+ text-transform: none;
+ font-family: "Courier New";
+}
+
+/* following font face declarations need to be removed for DBCS */
+body,h1,h2,h3,h4,h5,h6,p,table,td,caption,th,ul,ol,dl,li,dd,dt {
+ font-family: Arial, Helvetica, sans-serif;
+ color: #000000
+}
+
+pre {
+ font-family: Courier, monospace
+}
+
+/* end font face declarations */
+ /* following font size declarations should be OK for DBCS */
+body,h1,h2,h3,h4,h5,h6,p,table,td,caption,th,ul,ol,dl,li,dd,dt {
+ font-size: 10pt;
+}
+
+pre {
+ font-size: 10pt
+}
+
+/* end font size declarations */
+body {
+ background: #FFFFFF
+}
+
+h1 {
+ font-size: 18pt;
+ margin-top: 5;
+ margin-bottom: 1
+}
+
+h2 {
+ font-size: 14pt;
+ margin-top: 25;
+ margin-bottom: 3
+}
+
+h3 {
+ font-size: 11pt;
+ margin-top: 20;
+ margin-bottom: 3
+}
+
+h4 {
+ font-size: 10pt;
+ margin-top: 20;
+ margin-bottom: 3;
+ font-style: italic
+}
+
+p {
+ margin-top: 10px;
+ margin-bottom: 10px
+}
+
+pre {
+ margin-left: 6;
+ font-size: 9pt
+}
+
+a:link {
+ color: #0000FF
+}
+
+a:hover {
+ color: #000080
+}
+
+a:visited {
+ text-decoration: underline
+}
+
+ul {
+ margin-top: 0;
+ margin-bottom: 10
+}
+
+li {
+ margin-top: 0;
+ margin-bottom: 0
+}
+
+li p {
+ margin-top: 0;
+ margin-bottom: 0
+}
+
+ol {
+ margin-top: 0;
+ margin-bottom: 10
+}
+
+dl {
+ margin-top: 0;
+ margin-bottom: 10
+}
+
+dt {
+ margin-top: 0;
+ margin-bottom: 0;
+ font-weight: bold
+}
+
+dd {
+ margin-top: 0;
+ margin-bottom: 0
+}
+
+strong {
+ font-weight: bold
+}
+
+em {
+ font-style: italic
+}
+
+var {
+ font-style: italic
+}
+
+div.revision {
+ border-left-style: solid;
+ border-left-width: thin;
+ border-left-color: #7B68EE;
+ padding-left: 5
+}
+
+th {
+ font-weight: bold
+}
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.doc.user/build.properties b/docs/org.eclipse.wst.doc.user/build.properties
new file mode 100644
index 0000000..51a6d97
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/build.properties
@@ -0,0 +1,10 @@
+bin.includes = about.html,\
+ common.css,\
+ images/,\
+ META-INF/,\
+ notices.html,\
+ plugin.properties,\
+ plugin.xml,\
+ toc.xml,\
+ topics/
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.doc.user/common.css b/docs/org.eclipse.wst.doc.user/common.css
new file mode 100644
index 0000000..741d750
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/common.css
@@ -0,0 +1,1193 @@
+body {
+ font-family: Arial, sans-serif;
+ font-size: 0.8em;
+ background-color: #ffffff;
+ color: Black;
+ margin-right: 5em;
+ margin-bottom: 1em;
+}
+
+.ibmfilepath {
+ font-family: monospace;
+ font-size: 100%;
+}
+
+.ibmcommand {
+ font-weight: bold;
+}
+
+.ibmemphasis {
+ font-style: italic;
+}
+
+.mv,.pk,.pkdef,.pv {
+ font-family: monospace;
+ font-size: 100%;
+ padding-top: 0em;
+ padding-right: .3em;
+ padding-bottom: 0em;
+ padding-left: .3em;
+}
+
+tt,samp {
+ font-family: monospace;
+ font-size: 100%;
+}
+
+BODY.nav {
+ background-color: #FFFFFF;
+ border-right: 0.2em ridge black;
+ font-size: 0.95em;
+}
+
+.base {
+ font-weight: normal;
+ font-style: normal;
+ font-variant: normal;
+ text-decoration: none;
+ background-color: #ffffff;
+}
+
+TABLE {
+ color: black;
+ width: 90%;
+ border-collapse: collapse;
+ border-color: Black;
+ background: white;
+ margin-top: 0.5em;
+ margin-bottom: 0.5em;
+ margin-left: 0em;
+ margin-right: 0em;
+}
+
+.tbldesc {
+ font-style: italic;
+}
+
+TH {
+ font-weight: bold;
+ font-size: 0.7em;
+ color: black;
+ background-color: #dadada;
+ padding-top: 0.1em;
+ padding-bottom: 0.3em;
+ padding-left: 1em;
+ padding-right: 1em;
+}
+
+TH.base {
+ font-weight: bold;
+ color: black;
+ border: 1 solid #606060;
+ background-color: #dcdada;
+ padding-top: 0.65em;
+ padding-bottom: 0.65em;
+ padding-left: 1em;
+ padding-right: 1em;
+}
+
+TD {
+ font-size: 0.7em;
+ color: black;
+ background-color: white;
+ padding-top: 0.1em;
+ padding-bottom: 0.3em;
+ padding-left: 1em;
+ padding-right: 1em;
+}
+
+CITE {
+ font-style: italic;
+}
+
+EM {
+ font-style: italic;
+}
+
+STRONG {
+ font-weight: bold;
+}
+
+caption {
+ text-align: left;
+ font-style: italic;
+}
+
+DT {
+ margin-top: 0.5em;
+ margin-bottom: 0.5em;
+}
+
+DD {
+ margin-left: 1.0em;
+}
+
+PRE,pre.cgraphic {
+ font-family: monospace;
+ font-size: 12px;
+ background-color: #dadada;
+ padding: 5px;
+}
+
+.italic {
+ font-style: italic;
+}
+
+.bold {
+ font-weight: bold;
+}
+
+.underlined {
+ text-decoration: underline;
+}
+
+.bold-italic,.boldItalic {
+ font-weight: bold;
+ font-style: italic;
+}
+
+.smallCaps,.smallcaps {
+ text-transform: uppercase;
+ font-size: smaller;
+ font-variant: small-caps;
+}
+
+.italic-underlined {
+ font-style: italic;
+ text-decoration: underline;
+}
+
+.bold-underlined {
+ font-weight: bold;
+ text-decoration: underline;
+}
+
+.bold-italic-underlined {
+ font-weight: bold;
+ font-style: italic;
+ text-decoration: underline;
+}
+
+.smallcaps-underlined {
+ font-variant: small-caps;
+ text-decoration: underline;
+}
+
+.emphasis {
+ font-style: italic;
+}
+
+.inlinedef {
+ font-style: italic;
+}
+
+.sidebar {
+ background: #cccccc;
+}
+
+A:link {
+ color: #006699;
+ text-decoration: underline;
+}
+
+A:visited {
+ color: #996699;
+ text-decoration: underline;
+}
+
+A:active {
+ color: #006699;
+ text-decoration: underline;
+}
+
+A:hover {
+ color: #996699;;
+ text-decoration: underline;
+}
+
+a.toclink:link {
+ text-decoration: none;
+}
+
+a.toclink:active {
+ text-decoration: none;
+}
+
+a.toclink:visited {
+ text-decoration: none;
+}
+
+a.toclink:hover {
+ text-decoration: underline;
+}
+
+a.ptoclink:link {
+ text-decoration: none;
+}
+
+a.ptoclink:active {
+ text-decoration: none;
+}
+
+a.ptoclink:visited {
+ text-decoration: none;
+}
+
+a.ptoclink:hover {
+ text-decoration: underline;
+}
+
+a.indexlink:link {
+ text-decoration: none;
+}
+
+a.indexlink:active {
+ text-decoration: none;
+}
+
+a.indexlink:visited {
+ text-decoration: none;
+}
+
+a.indexlink:hover {
+ text-decoration: underline;
+}
+
+a.figurelist:link {
+ text-decoration: none;
+}
+
+a.figurelist:active {
+ text-decoration: none;
+}
+
+a.figurelist:visited {
+ text-decoration: none;
+}
+
+a.figurelist:hover {
+ text-decoration: underline;
+}
+
+a.tablelist:link {
+ text-decoration: none;
+}
+
+a.tablelist:active {
+ text-decoration: none;
+}
+
+a.tablelist:visited {
+ text-decoration: none;
+}
+
+a.tablelist:hover {
+ text-decoration: underline;
+}
+
+a.boldgreylink:link {
+ text-decoration: none;
+ color: #333333;
+ font-family: Verdana, Arial, sans-serif;
+ font-weight: bold;
+ font-size: 0.9em;
+}
+
+a.boldgreylink:visited {
+ text-decoration: none;
+ color: #333333;
+ font-family: Verdana, Arial, sans-serif;
+ font-weight: bold;
+ font-size: 0.9em;
+}
+
+a.boldgreylink:hover {
+ text-decoration: underline;
+ color: #333333;
+ font-family: Verdana, Arial, sans-serif;
+ font-weight: bold;
+ font-size: 0.9em;
+}
+
+.runningheader {
+ font-family: Verdana, Arial, sans-serif;
+ font-size: 0.7em;
+}
+
+.runningfooter {
+ font-family: Verdana, Arial, sans-serif;
+ font-size: 0.7em;
+}
+
+.runningfooter a:link {
+ font-weight: bold;
+ color: #000000;
+ text-decoration: none;
+}
+
+.runningfooter a:active {
+ font-weight: bold;
+ color: #000000;
+ text-decoration: none;
+}
+
+.runningfooter a:visited {
+ font-weight: bold;
+ color: #000000;
+ text-decoration: none;
+}
+
+.runningfooter a:hover {
+ font-weight: bold;
+ color: #000000;
+ text-decoration: underline;
+}
+
+#breadcrumb,.breadcrumb,span.breadcrumbs {
+ font-size: 0.75em;
+}
+
+.fastpath {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.fastpathtitle {
+ font-weight: bold;
+}
+
+.toc {
+ font-size: small;
+}
+
+.nested0 {
+ margin-top: 0em;
+}
+
+.p {
+ margin-top: 1em;
+}
+
+span.figcap {
+ font-style: italic;
+}
+
+span.figdesc {
+ font-style: italic;
+}
+
+div.figbox {
+
+}
+
+div.figrules {
+
+}
+
+div.fignone {
+
+}
+
+.fignone {
+
+}
+
+.figborder {
+
+}
+
+.figsides {
+
+}
+
+.figtop {
+
+}
+
+.figbottom {
+
+}
+
+.figtopbot {
+
+}
+
+.parentlink {
+
+}
+
+.prevlink {
+
+}
+
+.nextlink {
+
+}
+
+.relconceptshd {
+
+}
+
+.reltaskshd {
+
+}
+
+.relrefhd {
+
+}
+
+.synnone {
+
+}
+
+.synborder {
+
+}
+
+.synsides {
+
+}
+
+.syntop {
+
+}
+
+.synbottom {
+
+}
+
+.syntopbot {
+
+}
+
+.skip {
+ margin-top: 1em;
+}
+
+.skipspace {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.ulchildlink {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.olchildlink {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+ul,ol {
+ margin-top: 0.1em;
+ padding-top: 0.1em;
+}
+
+ul.simple {
+ list-style-type: none;
+}
+
+ul.indexlist {
+ list-style-type: none;
+}
+
+OL LI {
+ margin-top: 0.0em;
+ margin-bottom: 0.0em;
+ margin-left: 0.0em;
+}
+
+UL LI {
+ margin-top: 0.0em;
+ margin-bottom: 0.0em;
+ margin-left: 0.0em;
+}
+
+OL LI DIV P {
+ list-style-type: decimal;
+ margin-top: 0.2em;
+ margin-bottom: 0.2em;
+}
+
+UL LI DIV P {
+ list-style-type: disc;
+ margin-top: 0.2em;
+ margin-bottom: 0.2em;
+}
+
+* [compact="yes"]>li {
+ margin-top: 0 em;
+}
+
+* [compact="no"]>li {
+ margin-top: 0.5em;
+}
+
+hr {
+ margin-bottom: 0em;
+ margin-top: 0em;
+ padding-top: 0em;
+ padding-bottom: 0em;
+ width: 90%;
+ color: #cccccc;
+ text-align: center;
+}
+
+H1,.title,.pagetitle,.topictitle1 {
+ font-size: 1.5em;
+ font-style: normal;
+ font-weight: bold;
+ margin-bottom: 0.5em;
+ word-spacing: 0.1em;
+}
+
+H2,.subtitle,.pagesubtitle,.topictitle2 {
+ font-size: 1.25em;
+ font-style: normal;
+ font-weight: bold;
+ margin-bottom: 0.0em;
+ padding-bottom: 0.0em;
+}
+
+H3,.boldtitle,.topictitle3 {
+ font-size: 1.0em;
+ font-style: normal;
+ font-weight: bold;
+ margin-bottom: 0.2em;
+ padding-bottom: 0.1em;
+}
+
+H4,.topictitle4 {
+ font-size: 0.9em;
+ font-style: normal;
+ font-weight: bold;
+ margin-bottom: 0.1em;
+ padding-bottom: 0.1em;
+}
+
+h5,.topictitle5 {
+ font-size: 0.8em;
+ font-style: normal;
+ font-weight: bold;
+ margin-bottom: 0em;
+ padding-bottom: 0em;
+}
+
+h6,.topictitle6 {
+ font-size: 0.7em;
+ font-style: normal;
+ font-weight: bold;
+ margin-bottom: 0em;
+ padding-bottom: 0em;
+}
+
+div.headtitle {
+ font-size: 1em;
+ font-weight: bold;
+ margin-left: 0em;
+}
+
+div.head0 {
+ font-size: 0.9em;
+ font-weight: bold;
+ margin-left: 0em;
+ margin-top: 0.5em;
+}
+
+div.head1 {
+ font-size: 0.8em;
+ font-weight: bold;
+ margin-left: 1em;
+ padding-top: 0.5em;
+}
+
+div.head2 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 2em;
+}
+
+div.head3 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 3em;
+}
+
+div.head4 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 4em;
+}
+
+div.head5 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 5em;
+}
+
+div.head6 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 6em;
+}
+
+div.head7 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 7em;
+}
+
+div.head8 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 8em;
+}
+
+div.head9 {
+ font-size: 0.7em;
+ font-weight: normal;
+ margin-left: 9em;
+}
+
+.tip {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.tiptitle {
+ font-weight: bold;
+}
+
+.firstcol {
+ font-weight: bold;
+}
+
+.ptocH1 {
+ font-size: x-small;
+}
+
+.ptocH2 {
+ font-size: x-small;
+}
+
+.stitle {
+ font-style: italic;
+ text-decoration: underline;
+}
+
+.nte {
+
+}
+
+.xxlines {
+ white-space: pre;
+ font-size: 0.95em;
+}
+
+.sectiontitle {
+ margin-top: 1em;
+ margin-bottom: 0em;
+ color: black;
+ font-size: 1.2em;
+ font-weight: bold;
+}
+
+div.imageleft {
+ text-align: left;
+}
+
+div.imagecenter {
+ text-align: center;
+}
+
+div.imageright {
+ text-align: right;
+}
+
+div.imagejustify {
+ text-align: justify;
+}
+
+div.mmobj {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ text-align: center;
+}
+
+div.mmobjleft {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ text-align: left;
+}
+
+div.mmobjcenter {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ text-align: center;
+}
+
+div.mmobjright {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ text-align: right;
+}
+
+pre.screen {
+ padding: 1em 1em 1em 1em;
+ margin-top: 0.4em;
+ margin-bottom: 0.4em;
+ border: thin solid Black;
+ font-size: 100%;
+}
+
+.prereq {
+ margin-left: 1.5em;
+}
+
+.defListHead {
+ font-weight: bold;
+ text-decoration: underline;
+}
+
+span.mv {
+ font-style: italic;
+}
+
+span.md {
+ text-decoration: line-through;
+}
+
+.pk,span.pk {
+ font-weight: bold;
+}
+
+span.pkdef {
+ font-weight: bold;
+ text-decoration: underline;
+}
+
+span.pv {
+ font-style: italic;
+}
+
+span.pvdef {
+ font-style: italic;
+ text-decoration: underline;
+}
+
+span.kwd {
+ font-weight: bold;
+}
+
+span.kdwdef {
+ font-weight: bold;
+ text-decoration: underline;
+}
+
+.parmListKwd {
+ font-weight: bold;
+}
+
+.parmListVar {
+ font-style: italic;
+}
+
+span.oper {
+ font-style: normal;
+}
+
+span.operdef {
+ text-decoration: underline;
+}
+
+VAR,span.var {
+ font-style: italic;
+}
+
+span.vardef {
+ font-style: italic;
+ text-decoration: underline;
+}
+
+div.msg {
+ padding: 0.2em 1em 1em 1em;
+ margin-top: 0.4em;
+ margin-bottom: 0.4em;
+}
+
+div.msgnum {
+ float: left;
+ font-weight: bold;
+ margin-bottom: 1em;
+ margin-right: 1em;
+}
+
+div.msgtext {
+ font-weight: bold;
+ margin-bottom: 1em;
+}
+
+div.msgitemtitle {
+ font-weight: bold;
+}
+
+p.msgitem {
+ margin-top: 0em;
+}
+
+.attention,div.attention {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.attentiontitle,span.attentiontitle {
+ font-weight: bold;
+}
+
+.cautiontitle,div.cautiontitle {
+ margin-top: 1em;
+ font-weight: bold;
+}
+
+.caution,div.caution {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.danger,div.danger {
+ padding: 0.5em 0.5em 0.5em 0.5em;
+ border: solid;
+ border-width: thin;
+ font-weight: bold;
+ margin-top: 0.2em;
+ margin-bottom: 1em;
+}
+
+.dangertitle,div.dangertitle {
+ margin-top: 1em;
+ font-weight: bold;
+}
+
+.important {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.importanttitle {
+ font-weight: bold;
+}
+
+.remember {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.remembertitle {
+ font-weight: bold;
+}
+
+.restriction {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.restrictiontitle {
+ font-weight: bold;
+}
+
+div.warningtitle {
+ font-weight: bold;
+}
+
+div.warningbody {
+ margin-left: 2em
+}
+
+.note {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.notetitle,div.notetitle {
+ font-weight: bold;
+}
+
+div.notebody {
+ margin-left: 2em;
+}
+
+div.notelisttitle {
+ font-weight: bold;
+}
+
+div.fnnum {
+ float: left;
+}
+
+div.fntext {
+ margin-left: 2em;
+}
+
+div.stepl {
+ margin-left: 2em;
+}
+
+div.steplnum {
+ font-weight: bold;
+ float: left;
+ margin-left: 0.5em;
+}
+
+div.stepltext {
+ margin-left: 5em;
+}
+
+div.steplnum {
+ font-style: italic;
+ font-weight: bold;
+ float: left;
+ margin-left: 0.5em;
+}
+
+div.stepltext {
+ margin-bottom: 0.5em;
+ margin-left: 3em;
+}
+
+div.ledi {
+ margin-left: 3em;
+}
+
+div.ledesc {
+ margin-left: 3em;
+}
+
+span.pblktitle {
+ font-weight: bold;
+}
+
+div.pblklblbox {
+ padding: 0.5em 0.5em 0.5em 0.5em;
+ border: solid;
+ border-width: thin;
+ margin-top: 0.2em;
+}
+
+span.ednoticestitle {
+ font-weight: bold;
+}
+
+span.term {
+ font-weight: bold;
+}
+
+span.idxshow {
+ color: green;
+}
+
+div.code {
+ font-weight: bold;
+ margin-bottom: 1em;
+}
+
+span.refkey {
+ font-weight: bold;
+ color: white;
+ background-color: black;
+}
+
+tt.apl {
+ font-style: italic;
+}
+
+div.qualifstart {
+ padding: 0.1em 0.5em 0.5em 0.5em;
+ border-top: solid;
+ border-left: solid;
+ border-right: solid;
+ border-width: thin;
+ font-weight: bold;
+ margin-top: 0.2em;
+ margin-bottom: 0.2em;
+ text-align: center;
+}
+
+div.qualifend {
+ padding: 0.5em 0.5em 0.1em 0.5em;
+ border-bottom: solid;
+ border-left: solid;
+ border-right: solid;
+ border-width: thin;
+ font-weight: bold;
+ margin-bottom: 0.2em;
+ text-align: center;
+}
+
+.noshade {
+ background-color: transparent;
+}
+
+.xlight {
+ background-color: #DADADA;
+}
+
+.light {
+ background-color: #B0B0B0;
+}
+
+.medium {
+ background-color: #8C8C8C;
+}
+
+.dark {
+ background-color: #6E6E6E;
+}
+
+.xdark {
+ background-color: #585858;
+}
+
+.light-yellow {
+ background-color: #FFFFCC;
+}
+
+.khaki {
+ background-color: #CCCC99;
+}
+
+.medium-blue {
+ background-color: #6699CC;
+}
+
+.light-blue {
+ background-color: #CCCCFF;
+}
+
+.mid-grey {
+ background-color: #CCCCCC;
+}
+
+.light-grey {
+ background-color: #DADADA;
+}
+
+.lightest-grey {
+ background-color: #E6E6E6;
+}
+
+#changed {
+ position: absolute;
+ left: 0.2em;
+ color: #7B68EE;
+ background-color: #FFFFFF;
+ font-style: normal;
+ font-weight: bold;
+}
+
+INPUT.buttons {
+ font-size: 0.75em;
+ border-top: 0.2em outset #B1B1B1;
+ border-right: 0.2em outset #000000;
+ border-bottom: 0.2em outset #000000;
+ border-left: 0.2em outset #B1B1B1;
+ background-color: #E2E2E2;
+ margin-bottom: 0.2em;
+}
+
+.cgraphic {
+ font-size: 90%;
+ color: black;
+}
+
+.aix,.hpux,.sun,.unix,.win2,.winnt,.win,.zos,.linux,.os390,.os400,.c,.cplusplus,.cobol,.fortran,.java,.macosx,.os2,.pl1,.rpg
+ {
+ background-repeat: no-repeat;
+ background-position: top left;
+ margin-top: 0.5em;
+ text-indent: 55px;
+}
+
+.aix {
+ background-image: url(ngaix.gif);
+}
+
+.hpux {
+ background-image: url(nghpux.gif);
+}
+
+.sun {
+ background-image: url(ngsolaris.gif);
+}
+
+.unix {
+ background-image: url(ngunix.gif);
+}
+
+.win2 {
+ background-image: url(ng2000.gif);
+}
+
+.winxp {
+ background-image: url(ngxp.gif);
+}
+
+.winnt {
+ background-image: url(ngnt.gif);
+}
+
+.win {
+ background-image: url(ngwin.gif);
+}
+
+.zos {
+ background-image: url(ngzos.gif);
+}
+
+.linux {
+ background-image: url(nglinux.gif);
+}
+
+.os390 {
+ background-image: url(ng390.gif);
+}
+
+.os400 {
+ background-image: url(ng400.gif);
+}
+
+.c {
+ background-image: url(ngc.gif);
+}
+
+.cplusplus {
+ background-image: url(ngcpp.gif);
+}
+
+.cobol {
+ background-image: url(ngcobol.gif);
+}
+
+.fortran {
+ background-image: url(ngfortran.gif);
+}
+
+.java {
+ background-image: url(ngjava.gif);
+}
+
+.macosx {
+ background-image: url(ngmacosx.gif);
+}
+
+.os2 {
+ background-image: url(ngos2.gif);
+}
+
+.pl1 {
+ background-image: url(ngpl1.gif);
+}
+
+.rpg {
+ background-image: url(ngrpg.gif);
+}
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.doc.user/images/SelectExistingServer.jpg b/docs/org.eclipse.wst.doc.user/images/SelectExistingServer.jpg
new file mode 100644
index 0000000..398dbe4
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/SelectExistingServer.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/SelectNewServer.jpg b/docs/org.eclipse.wst.doc.user/images/SelectNewServer.jpg
new file mode 100644
index 0000000..95f6b44
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/SelectNewServer.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure1.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure1.jpg
new file mode 100644
index 0000000..9064bb8
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure1.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure2.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure2.jpg
new file mode 100644
index 0000000..eca4347
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure2.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure3.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure3.jpg
new file mode 100644
index 0000000..5d87d0c
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure3.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure4.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure4.jpg
new file mode 100644
index 0000000..c334bbf
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure4.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure5.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure5.jpg
new file mode 100644
index 0000000..a94614e
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure5.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/image99L.jpg b/docs/org.eclipse.wst.doc.user/images/image99L.jpg
new file mode 100644
index 0000000..506abdb
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/image99L.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/imageEJ9.jpg b/docs/org.eclipse.wst.doc.user/images/imageEJ9.jpg
new file mode 100644
index 0000000..be7350e
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/imageEJ9.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/imageIAI.jpg b/docs/org.eclipse.wst.doc.user/images/imageIAI.jpg
new file mode 100644
index 0000000..d2f625c
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/imageIAI.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/imageLKF.jpg b/docs/org.eclipse.wst.doc.user/images/imageLKF.jpg
new file mode 100644
index 0000000..ff98f42
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/imageLKF.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/imageO78.jpg b/docs/org.eclipse.wst.doc.user/images/imageO78.jpg
new file mode 100644
index 0000000..67077f8
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/imageO78.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/imageU71.jpg b/docs/org.eclipse.wst.doc.user/images/imageU71.jpg
new file mode 100644
index 0000000..9ee0430
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/imageU71.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/note.gif b/docs/org.eclipse.wst.doc.user/images/note.gif
new file mode 100644
index 0000000..f6260db
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/note.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/selectRootElementDTD.png b/docs/org.eclipse.wst.doc.user/images/selectRootElementDTD.png
new file mode 100644
index 0000000..25f260f
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/selectRootElementDTD.png
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/selectRootElementXSD.png b/docs/org.eclipse.wst.doc.user/images/selectRootElementXSD.png
new file mode 100644
index 0000000..9955ed3
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/selectRootElementXSD.png
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdl.gif b/docs/org.eclipse.wst.doc.user/images/wsdl.gif
new file mode 100644
index 0000000..8fb844f
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdl.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdl_main.gif b/docs/org.eclipse.wst.doc.user/images/wsdl_main.gif
new file mode 100644
index 0000000..9f074e8
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdl_main.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-backbutton.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-backbutton.jpg
new file mode 100644
index 0000000..ebcd1c7
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-backbutton.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-binding.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-binding.jpg
new file mode 100644
index 0000000..be74d57
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-binding.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-complex-type.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-complex-type.jpg
new file mode 100644
index 0000000..15d6071
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-complex-type.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-finished-wsdl.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-finished-wsdl.jpg
new file mode 100644
index 0000000..9c56342
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-finished-wsdl.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-operation.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-operation.jpg
new file mode 100644
index 0000000..8dc34a3
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-operation.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-skeleton.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-skeleton.jpg
new file mode 100644
index 0000000..57ddb29
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-skeleton.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-wizard.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-wizard.jpg
new file mode 100644
index 0000000..50553f6
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-wizard.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-setelement-dialog.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-setelement-dialog.jpg
new file mode 100644
index 0000000..f48165e
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-setelement-dialog.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-settype-dialog.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-settype-dialog.jpg
new file mode 100644
index 0000000..8a36a66
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-settype-dialog.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-smart-rename1.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-smart-rename1.jpg
new file mode 100644
index 0000000..cc68a44
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/wsdleditor-smart-rename1.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-backbutton.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-backbutton.jpg
new file mode 100644
index 0000000..2092605
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-backbutton.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure1.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure1.jpg
new file mode 100644
index 0000000..f3b4f6f
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure1.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure2.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure2.jpg
new file mode 100644
index 0000000..518c606
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure2.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure3.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure3.jpg
new file mode 100644
index 0000000..a66b6e7
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure3.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure4.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure4.jpg
new file mode 100644
index 0000000..2a187da
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure4.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure5.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure5.jpg
new file mode 100644
index 0000000..b9622ef
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure5.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure6.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure6.jpg
new file mode 100644
index 0000000..6e253b8
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure6.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure7.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure7.jpg
new file mode 100644
index 0000000..dfb7523
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure7.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure8.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure8.jpg
new file mode 100644
index 0000000..ef61772
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure8.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure9.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure9.jpg
new file mode 100644
index 0000000..664eecc
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure9.jpg
Binary files differ
diff --git a/docs/org.eclipse.wst.doc.user/notices.html b/docs/org.eclipse.wst.doc.user/notices.html
new file mode 100644
index 0000000..e0cf4d1
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/notices.html
@@ -0,0 +1,17 @@
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1"
+ TYPE="text/css">
+<title>Legal Notices</title>
+</head>
+<body>
+
+<h3><a NAME="Notices"></a>Notices</h3>
+<p>The material in this guide is Copyright (c) IBM Corporation and
+others 2000, 2005.</p>
+<p><a href="about.html">Terms and conditions regarding the use of this
+guide.</a></p>
+</body>
+</html>
diff --git a/docs/org.eclipse.wst.doc.user/plugin.properties b/docs/org.eclipse.wst.doc.user/plugin.properties
new file mode 100644
index 0000000..6163b89
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/plugin.properties
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 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
+###############################################################################
+
+pluginName = Master User Doc TOC
+providerName = Eclipse.org
diff --git a/docs/org.eclipse.wst.doc.user/plugin.xml b/docs/org.eclipse.wst.doc.user/plugin.xml
new file mode 100644
index 0000000..0aa617f
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/plugin.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<plugin>
+ <extension point="org.eclipse.help.toc">
+ <toc file="toc.xml" primary="true" />
+ </extension>
+</plugin>
diff --git a/docs/org.eclipse.wst.doc.user/toc.xml b/docs/org.eclipse.wst.doc.user/toc.xml
new file mode 100644
index 0000000..84f6f6c
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/toc.xml
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<!-- ============================================================================= -->
+<!-- Define the top level topics -->
+<!-- ============================================================================= -->
+<toc label="Web Application Development Guide"
+ topic="topics/overview.html">
+
+ <topic label="Creating Web applications">
+ <link
+ toc="../org.eclipse.wst.webtools.doc.user/webtools_toc.xml" />
+ </topic>
+ <topic label="Creating J2EE and enterprise applications">
+ <link toc="../org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml" />
+ <link toc="../org.eclipse.jst.ejb.doc.user/ejb_toc.xml" />
+ </topic>
+ <topic label="Editing markup language files"
+ href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html">
+ <link toc="../org.eclipse.wst.sse.doc.user/sse_toc.xml" />
+ <link
+ toc="../org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml" />
+ <link
+ toc="../org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml" />
+ <link
+ toc="../org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml" />
+ </topic>
+ <!-- <link toc="../org.eclipse.wst.xml.doc.user/xml_toc.xml"/>-->
+ <topic label="Creating Web service applications">
+ <link toc="../org.eclipse.jst.ws.doc.user/webservice_toc.xml" />
+ </topic>
+ <topic label="Using data tools">
+ <link toc="../org.eclipse.wst.datatools.server.ui.doc.user/database_explorer_toc.xml" />
+ <link toc="../org.eclipse.wst.datatools.server.ui.doc.user/dataoutput_view_toc.xml" />
+ <link toc="../org.eclipse.wst.datatools.connection.ui.doc.user/connection_ui_toc.xml" />
+ <link toc="../org.eclipse.wst.datatools.fe.ui.doc.user/fe_ui_toc.xml" />
+ <link toc="../org.eclipse.wst.datatools.data.ui.doc.user/data_ui_toc.xml" />
+ <link toc="../org.eclipse.wst.sqleditor.doc.user/sqleditor_toc.xml" />
+ </topic>
+ <topic label="Using the server tools">
+ <link toc="../org.eclipse.wst.server.ui.doc.user/wtp_main_toc.xml" />
+ </topic>
+ <topic label="Legal" href="notices.html" />
+</toc>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.doc.user/topics/overview.html b/docs/org.eclipse.wst.doc.user/topics/overview.html
new file mode 100644
index 0000000..fb18681
--- /dev/null
+++ b/docs/org.eclipse.wst.doc.user/topics/overview.html
@@ -0,0 +1,26 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css"
+ href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Web Tools Project Overview</title>
+</head>
+<body>
+<h1>Web Tools Project Overview</h1>
+<p>The Web Tools Project aims to provide common infrastructure available
+to any Eclipse-based development environment targeting Web-enabled
+applications.</p>
+</body>
+</html>
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.cvsignore b/docs/org.eclipse.wst.dtd.ui.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.project b/docs/org.eclipse.wst.dtd.ui.infopop/.project
new file mode 100644
index 0000000..df2f69d
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.dtd.ui.infopop</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.dtd.ui.infopop/EditorDtdContexts.xml b/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts.xml
new file mode 100644
index 0000000..0cf4da1
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts.xml
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+
+<contexts>
+<context id="csh_outer_container">
+<description/>
+</context>
+<context id="webx0020">
+<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save a document type definition (DTD) file.
+
+The line delimiters are Ctrl-J (UNIX), Ctrl-M (Mac), or Ctrl-M Ctrl-J (Windows).</description>
+</context>
+<context id="webx0021">
+<description>This page lets you customize the syntax highlighting that the document type definition (DTD) editor does when you are editing a file.
+
+The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting.
+
+The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that allow you to specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold.
+
+Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values.</description>
+<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html" label="Setting source highlighting styles"/>
+</context>
+<context id="webx0022">
+<description>Templates are a chunk of predefined code that you can insert into a DTD file when it is created.
+
+Click <b>New</b> if you want to create a completely new template.
+
+Supply a new template <b>Name</b> and <b>Description</b>. The <b>Context</b> for the template is the context in which the template is available in the proposal list when content assist is requested. Specify the <b>Pattern</b> for your template using the appropriate tags, attributes, or attribute values to be inserted by content assist.
+
+If you want to insert a variable, click the <b>Insert Variable</b> button and select the variable to be inserted. For example, the <b>date</b> variable indicates the current date will be inserted.
+
+You can edit, remove, import, or export a template by using the same Preferences page.
+
+If you have a template that you do not want to remove but you no longer want it to appear in the content assist list, clear its check box in the <b>Templates</b> preferences page.</description>
+<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html" label="Working with DTD templates"/>
+<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html" label="Creating DTD files"/>
+</context>
+<context id="dtdw0010">
+<description>Click the <b>Use DTD Template</b> check box if you want to use a DTD template as the initial content in your new DTD page. A list of available DTD templates is listed - select the one you want to use. A preview of your DTD file is shown once you select a DTD template.</description>
+<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html" label="Working with DTD templates"/>
+<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html" label="Creating DTD files"/>
+</context>
+</contexts>
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts2.xml b/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts2.xml
new file mode 100644
index 0000000..3a44d26
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts2.xml
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+
+<contexts>
+<context id="csh_outer_container">
+<description/>
+</context>
+<context id="dtdsource_source_HelpId">
+<description>The DTD editor lets you edit a document type definition.
+
+The editor provides text editing features such as syntax highlighting and unlimited undo and redo.
+</description>
+</context>
+</contexts>
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.dtd.ui.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..b7ecc4e
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.dtd.ui.infopop; singleton:=true
+Bundle-Version: 1.0.1.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/about.html b/docs/org.eclipse.wst.dtd.ui.infopop/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/build.properties b/docs/org.eclipse.wst.dtd.ui.infopop/build.properties
new file mode 100644
index 0000000..784ca85
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/build.properties
@@ -0,0 +1,7 @@
+bin.includes = plugin.xml,\
+ plugin.properties,\
+ about.html,\
+ EditorDtdContexts.xml,\
+ META-INF/,\
+ EditorDtdContexts2.xml
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties
new file mode 100644
index 0000000..76c52ba
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2001, 2004 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
+###############################################################################
+
+pluginName = DTD Editor infopops
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/plugin.xml b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.xml
new file mode 100644
index 0000000..aa57fbc
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.xml
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<!-- ================================================= -->
+<!-- This is the plugin for declaring the help -->
+<!-- contributions for using the tool. -->
+<!-- ================================================= -->
+<!-- /*******************************************************************************
+ * 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>
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorDtdContexts.xml" plugin ="org.eclipse.wst.dtd.ui"/>
+ <contexts file="EditorDtdContexts2.xml" plugin ="org.eclipse.wst.dtd.core"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.cvsignore b/docs/org.eclipse.wst.dtdeditor.doc.user/.cvsignore
new file mode 100644
index 0000000..912343e
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/.cvsignore
@@ -0,0 +1,2 @@
+build.xml
+org.eclipse.wst.dtdeditor.doc.user_1.0.0.jar
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.project b/docs/org.eclipse.wst.dtdeditor.doc.user/.project
new file mode 100644
index 0000000..4486d7a
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.dtdeditor.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.dtdeditor.doc.user/DTDEditormap_toc.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml
new file mode 100644
index 0000000..ad1932c
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="utf-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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="DTD Editor">
+ <topic label="Working with DTDs" href="topics/cworkdtds.html">
+ <topic label="Creating DTDs" href="topics/tcretdtd.html">
+ <topic label="Document type definitions (DTDs) - overview" href="topics/cdtdover.html"/>
+ <topic label="Setting source highlighting styles" href="topics/tedtsrcst.html"/>
+ <topic label="Working with DTD templates" href="topics/tdtemplt.html"/>
+ </topic>
+ <topic label="Importing DTDs" href="topics/timptdtd.html"/>
+ <topic label="Validating DTDs" href="topics/tvaldtd.html"/>
+ <topic label="Icons used in the DTD editor" href="topics/rdtdicons.html"/>
+ </topic>
+</toc>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.dtdeditor.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..7a935a5
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.dtdeditor.doc.user; singleton:=true
+Bundle-Version: 1.0.1.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/about.html b/docs/org.eclipse.wst.dtdeditor.doc.user/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties b/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties
new file mode 100644
index 0000000..169d040
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties
@@ -0,0 +1,9 @@
+bin.includes = DTDEditormap_toc.xml,\
+ about.html,\
+ dtdeditor_reference_toc.xml,\
+ images/,\
+ plugin.properties,\
+ plugin.xml,\
+ topics/,\
+ META-INF/
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Comment.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Comment.gif
new file mode 100644
index 0000000..39611d6
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Comment.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Element.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Element.gif
new file mode 100644
index 0000000..01f4889
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Element.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity.gif
new file mode 100644
index 0000000..cb41506
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity_Reference.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity_Reference.gif
new file mode 100644
index 0000000..5efa9b9
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity_Reference.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Notation.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Notation.gif
new file mode 100644
index 0000000..57ad089
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Notation.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDChoice.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDChoice.gif
new file mode 100644
index 0000000..89ba825
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDChoice.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDSequence.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDSequence.gif
new file mode 100644
index 0000000..8bf3f97
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDSequence.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute.gif
new file mode 100644
index 0000000..c6cde94
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute_list.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute_list.gif
new file mode 100644
index 0000000..6df0291
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute_list.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nDTDFile.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nDTDFile.gif
new file mode 100644
index 0000000..e799143
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nDTDFile.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nany.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nany.gif
new file mode 100644
index 0000000..7017d91
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nany.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nempty.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nempty.gif
new file mode 100644
index 0000000..119e3d4
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nempty.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/organize_dtd_logically.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/organize_dtd_logically.gif
new file mode 100644
index 0000000..093c6ba
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/organize_dtd_logically.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/sort.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/sort.gif
new file mode 100644
index 0000000..23c5d0b
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/images/sort.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.properties b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.properties
new file mode 100644
index 0000000..d10ce86
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.properties
@@ -0,0 +1,4 @@
+# NLS_MESSAGEFORMAT_VAR
+
+pluginName = DTD Editor documentation
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.xml
new file mode 100644
index 0000000..cd121e2
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.xml
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.1"?>
+<!-- /*******************************************************************************
+ * 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>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="DTDEditormap_toc.xml"/>
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html
new file mode 100644
index 0000000..65abeee
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html
@@ -0,0 +1,50 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Document type definition (DTD) - overview</title>
+</head>
+<body id="cdtdover"><a name="cdtdover"><!-- --></a>
+
+<h1 class="topictitle1">Document type definitions (DTDs) - overview</h1>
+<div><p>A document type definition (DTD) provides you with the means to
+validate XML files against a set of rules. When you create a DTD file, you
+can specify rules that control the structure of any XML files that reference
+the DTD file.</p><p>A DTD can contain declarations that define elements, attributes, notations,
+and entities for any XML files that reference the DTD file. It also establishes
+constraints for how each element, attribute, notation, and entity can be used
+within any of the XML files that reference the DTD file.</p>
+<p>To be considered a valid XML file, the document must be accompanied by
+a DTD (or an XML schema), and conform to all of the declarations in the DTD
+(or XML schema).</p>
+<p>Certain XML parsers have the ability to read DTDs and check to see if the
+XML file it is reading follows all of those rules. While the parser is reading
+the XML file, it will check each line to be sure that it conforms
+to the rules that are laid out in the DTD file. If there is a problem, the
+parser generates an error and points to where the error occurs in the XML
+file. This kind of parser is called a validating parser because it validates
+the content of the XML file against the DTD.</p>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tcretdtd.html" title="A document type definition (DTD) contains a set of rules that can be used to validate an XML file. After you have created a DTD, you can edit it, adding declarations that define elements, attributes, entities, and notations, and how they can be used for any XML files that reference the DTD file.">Creating DTDs</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tvaldtd.html" title="Validating a DTD file lets you verify that it is well formed and does not contain any errors.">Validating DTDs</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.html
new file mode 100644
index 0000000..2b7bba0
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.html
@@ -0,0 +1,45 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+
+<title>Working with DTDs</title>
+</head>
+<body id="workingwithdtds"><a name="workingwithdtds"><!-- --></a>
+<h1 class="topictitle1">Working with DTDs</h1>
+<div><p>This sections contains information on the following:</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="../topics/tcretdtd.html">Creating DTDs</a></strong><br />
+A document type definition (DTD) contains a set of rules that can
+be used to validate an XML file. After you have created a DTD, you can manually
+edit it, adding declarations that define elements, attributes, entities, and
+notations, and how they can be used for any XML files that reference the DTD
+file.</li>
+<li class="ulchildlink"><strong><a href="../topics/timptdtd.html">Importing DTDs</a></strong><br />
+If you want to work with DTD files that you created outside of
+the product, you can import them into the workbench and open them in the DTD
+editor. </li>
+<li class="ulchildlink"><strong><a href="../topics/tvaldtd.html">Validating DTDs</a></strong><br />
+Validating a DTD file lets you verify that it is well formed and
+does not contain any errors.</li>
+<li class="ulchildlink"><strong><a href="../topics/rdtdicons.html">Icons used in the DTD editor</a></strong><br />
+These DTD editor icons appear in the Outline view.</li>
+</ul>
+</div></body>
+</html>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html
new file mode 100644
index 0000000..9faf52d
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html
@@ -0,0 +1,76 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../org.eclipse.wst.doc.user/common.css" />
+<title>Icons used in the DTD editor</title>
+</head>
+<body id="ricons"><a name="ricons"><!-- --></a>
+
+<h1 class="topictitle1">Icons used in the DTD editor</h1>
+<div><p>These DTD editor icons appear in the Outline view.</p>
+<div class="skipspace"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e20">
+ Icon</th>
+<th valign="top" id="d0e22">Description</th>
+</tr>
+</thead>
+<tbody><tr><td valign="top" headers="d0e20 "> </td>
+<td valign="top" headers="d0e22 "> </td>
+</tr>
+<tr><td valign="top" headers="d0e20 "> <img src="../images/nany.gif" /> </td>
+<td valign="top" headers="d0e22 ">ANY content (content model)</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "><img src="../images/attribute.gif" /> </td>
+<td valign="top" headers="d0e22 ">attribute</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "><img src="../images/attribute_list.gif" /> </td>
+<td valign="top" headers="d0e22 ">attribute list</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "><img src="../images/ADD_Comment.gif" /></td>
+<td valign="top" headers="d0e22 ">comment</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "> <img src="../images/XSDChoice.gif" /></td>
+<td valign="top" headers="d0e22 ">content model - choice</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "> <img src="../images/XSDSequence.gif" /></td>
+<td valign="top" headers="d0e22 ">content model - sequence</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "><img src="../images/ADD_Element.gif" /> </td>
+<td valign="top" headers="d0e22 ">element</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "> <img src="../images/nempty.gif" /> </td>
+<td valign="top" headers="d0e22 ">EMPTY content (content model)</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "><img src="../images/ADD_Entity.gif" /> </td>
+<td valign="top" headers="d0e22 ">entity</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "><img src="../images/ADD_Notation.gif" /> </td>
+<td valign="top" headers="d0e22 ">notation</td>
+</tr>
+<tr><td valign="top" headers="d0e20 "> <img src="../images/ADD_Entity_Reference.gif" /></td>
+<td valign="top" headers="d0e22 ">parameter entity reference</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="skipspace"></div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/cworkdtds.html" title="Working with DTDs">Working with DTDs</a><br />
+</p>
+
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html
new file mode 100644
index 0000000..14aaf36
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html
@@ -0,0 +1,68 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Creating a new document type definition (DTD)</title>
+</head>
+<body id="tcretdtd"><a name="tcretdtd"><!-- --></a>
+
+<h1 class="topictitle1">Creating DTDs</h1>
+<div><p>A document type definition (DTD) contains a set of rules that can
+be used to validate an XML file. After you have created a DTD, you can edit
+it manually, adding declarations that define elements, attributes, entities, and notations,
+and how they can be used for any XML files that reference the DTD file.</p><div class="skipspace"><p></p>
+<p>The following instructions were written for the Resource perspective, but
+they will also work in many other perspectives.</p>
+<p>Follow
+these steps to create a new DTD:</p>
+</div>
+<ol><li class="skipspace"><span>If necessary, create a project to contain the DTD.</span></li>
+<li class="skipspace"><span>In the workbench, select <b><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"> DTD File</b></span></span> and click <b><span class="uicontrol">Next</span></b>. </span>
+<li class="skipspace"><span>Select the project or folder that will contain the DTD.</span></li>
+<li class="skipspace"><span>In the <b> <span class="uicontrol">File name</span></b> field, type the name of
+the DTD, for example <kbd class="userinput">MyDTD.dtd</kbd>.</span> The
+name of your DTD file must end with the extension <kbd class="userinput">.dtd.</kbd></li>
+ <li class="skipspace">Click <b>Next</b>. </li>
+ <li class="skipspace">You can use a DTD template as the basis for your new
+ DTD file. To do so, click the <b>Use DTD Template </b>check box, and select
+ the template you want to use.</li>
+ <li class="skipspace"><span>Click <span class="uicontrol"><b>Finish</b></span>.</span></li>
+</ol>
+<div class="skipspace"><p>The DTD appears in the Navigator view and automatically
+opens in the DTD editor. In the DTD editor, you can manually add elements, attributes,
+notations, entities, and comments to the DTD. If you close the file, and want
+to later re-open it in the DTD editor, double-click it in the
+Navigator view.</p>
+</div>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/cworkdtds.html" title="Working with DTDs">Working with DTDs</a><br />
+</p>
+
+</div>
+
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cdtdover.html" title="A document type definition (DTD) provides you with the means to validate XML files against a set of rules. When you create a DTD file, you can specify rules that control the structure of any XML files that reference the DTD file.">Document type definitions (DTDs) - overview</a></p>
+ <p><strong>Related tasks</strong><br>
+ <a href="tdtemplt.html">Working with DTD templates</a><br>
+ <br />
+</p>
+
+
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html
new file mode 100644
index 0000000..875373c
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Working with XML templates</title>
+</head>
+<body id="twmacro"><a name="twmacro"><!-- --></a>
+
+<h1 class="topictitle1">Working with DTD templates</h1>
+<div><p>Templates are a chunk of predefined code that you can insert into a DTD
+ file when it is created. You may find a template useful when
+ you have a certain piece of code you want to reuse several times, and you do
+ not want to write it out every time.</p>
+ <div class="skipspace"><p>To create a new DTD template follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Click <b> <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Web and XML</span> > </span>
+ <span class="uicontrol">DTD</span><span class="menucascade"><span class="uicontrol"> Files</span> > </span>
+ <span class="uicontrol">DTD</span><span class="menucascade"><span class="uicontrol">
+Templates</span></span></b>.</span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">New</span></b> if you want to create a completely
+new template.</span></li>
+<li class="skipspace"><span>Supply a new template <b>Name</b> and <b>Description</b>.</span></li>
+<li class="skipspace"><span>Specify the <b> <span class="uicontrol">Context</span></b> for the template.</span> This is the context in which the template is available in the proposal
+list when content assist is requested. </li>
+<li class="skipspace"><span>Specify the <b> <span class="uicontrol">Pattern</span></b> for your template using
+the appropriate tags, attributes, or attribute values to be inserted by content
+assist.</span></li>
+<li class="skipspace"><span>If you want to insert a variable in your <b>Pattern</b>, click the
+<b> <span class="uicontrol">Insert Variable</span></b> button
+and select the variable to be inserted. </span> For example, the<b> date </b>variable indicates
+the current date will be inserted. </li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Apply</span></b> and then
+<b> <span class="uicontrol">OK</span></b> 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. <p>If you have a template
+that you do not want to remove, but you no longer want the template to appear
+in the DTD templates list when you create a file, go to the <b>DTD Templates </b>preferences page and
+ clear
+its check box.</p>
+</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br>
+ <a href="tcretdtd.html">Creating a DTD file</a><br />
+</div>
+</div></body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html
new file mode 100644
index 0000000..13cbcd2
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html
@@ -0,0 +1,51 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Setting source highlighting styles</title>
+</head>
+<body id="ttaghilt"><a name="ttaghilt"><!-- --></a>
+
+<h1 class="topictitle1">Setting source highlighting styles</h1>
+<div><p>If desired, you can change various aspects of how the DTD source
+code is displayed in the Source view of the DTD editor, such as the colors
+the tags will be displayed in.</p>
+ </p><div class="skipspace"><p>To set highlighting styles for the DTD code, follow these steps:</p>
+</div>
+<ol><li><span>Click <b> <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Web and XML</span> > </span>
+ <span class="uicontrol">DTD</span><span class="menucascade"><span class="uicontrol"> Files</span> > </span>
+ <span class="uicontrol">DTD</span><span class="menucascade"><span class="uicontrol">
+Styles</span></span></b>.</span></li>
+<li><span>In the <b> <span class="uicontrol">Content type</span></b> 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 <b> <span class="uicontrol">Foreground</span></b> box.</span></li>
+<li><span>Select the color that you want the text of the tag to appear in
+and click <b> <span class="uicontrol">OK</span></b>.</span></li>
+<li><span>Click the<span class="uicontrol"> <b>Background</b></span> box.</span></li>
+<li><span>Select the color that you want to appear behind the tag and click<span class="uicontrol">
+<b>OK</b></span>.</span></li>
+<li><span>Select the <b> <span class="uicontrol">Bold</span></b> check box if you want to
+make the type bold.</span></li>
+<li><span>Click <b> <span class="uicontrol">Restore Defaults</span></b> to set
+the highlighting styles back to their default values. If you only want to
+reset the value for a particular content type, select it in the <b>Content type</b>
+field, the click the <b>Restore Default </b>button next to it. </span></li>
+<li><span>Click <b> <span class="uicontrol">OK</span></b> to save your changes.</span></li>
+</ol>
+</div>
+<div><div class="reltasks"> </div>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html
new file mode 100644
index 0000000..a6b92e6
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html
@@ -0,0 +1,46 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Importing DTDs</title>
+</head>
+<body id="timptdtd"><a name="timptdtd"><!-- --></a>
+
+<h1 class="topictitle1">Importing DTDs</h1>
+<div><p>If you want to work with DTD files that you created outside of
+the product, you can import them into the workbench and open them in the DTD
+editor.</p><div class="skipspace"><p>To import a DTD into the workbench, follow these steps:</p>
+</div>
+<ol><li><span>Click <span class="menucascade"><span class="uicontrol"><b>File</span> > <span class="uicontrol">Import</b></span></span>.</span></li>
+<li><span>Select the import source and click <span class="uicontrol"><b>Next</b></span>.</span></li>
+<li><span>Fill in the fields in the <span class="uicontrol">Import</span> wizard
+as necessary.</span></li>
+<li><span>When you are finished, click <span class="uicontrol"><b>Finish</b></span>.</span></li>
+<li><span>Select the DTD file in the Navigator view and double-click it to
+open it in the DTD editor.</span></li>
+</ol>
+<div class="skipspace"><p>After you have imported a DTD file into the workbench and opened
+it in the DTD editor, you can edit it manually.</p>
+</div>
+</div>
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/cworkdtds.html" title="Working with DTDs">Working with DTDs</a><br />
+</p>
+
+</div>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html
new file mode 100644
index 0000000..973982a
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html
@@ -0,0 +1,52 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Validating DTDs</title>
+</head>
+<body id="tvaldtd"><a name="tvaldtd"><!-- --></a>
+
+<h1 class="topictitle1">Validating DTDs</h1>
+<div><p>Validating a DTD file lets you verify that it is well formed and
+does not contain any errors.</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 validate
+a DTD, follow these steps:</p>
+</div>
+<div class="p"><span>In the Navigator view, right-click the DTD and click <span class="menucascade"><span class="uicontrol"><b>Validate DTD File</b></span></span>.</span></div>
+<div class="skipspace">A dialog opens, indicating if the DTD file was successfully validated
+or not. If the file is invalid, any errors will appear in the Problems view.
+ <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"><b>Properties</span> > <span class="uicontrol">Validation</b></span></span> from the project's pop-up menu and specifying the maximum number
+of error messages allowed. You might have to select the <span class="uicontrol"><b>Override
+validation preferences</span></b> check box in order to enable the <span class="uicontrol"><b>Maximum
+number of validation messages</b></span> field.</p>
+<p>You can set up 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 <b><span class="uicontrol">Properties</span></b>,
+then select <span class="uicontrol"><b>Validation</b></span>. Any validators you can run
+against your project will be listed in the Validation page. </p>
+</div>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/cworkdtds.html" title="Working with DTDs">Working with DTDs</a><br />
+</p>
+
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.html.ui.infopop/.cvsignore b/docs/org.eclipse.wst.html.ui.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.wst.html.ui.infopop/.project b/docs/org.eclipse.wst.html.ui.infopop/.project
new file mode 100644
index 0000000..05aa1b4
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.html.ui.infopop</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.html.ui.infopop/EditorHtmlContexts.xml b/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts.xml
new file mode 100644
index 0000000..8b8dc10
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts.xml
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+
+<contexts>
+<context id="misc0170">
+<description>Use this dialog to edit the Web content settings for a Web project. You can specify the default document type, CSS profile, and target device. The public ID and system ID are populated automatically. To restore the defaults, click <b>Restore Defaults</b>.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="webx0030">
+<description>This page lets you specify the line delimiter and the text encoding that will be used when you create, save, or load an HTML file.
+
+Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform.
+<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>.
+
+The encoding attribute is used to specify the default character encoding set that is used when either creating HTML files or loading your HTML files into the editor. Changing the creating files encoding causes any new HTML files that are created from scratch to use the selected encoding.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0031">
+<description>This page lets you specify the formatting, content assist, and capitalization style that will be used when you edit an HTML file.
+
+Enter a maximum width in the <b>Line width</b> field to specify the line width to break a line to fit onto more than one line when the document is formatted.
+
+Select <b>Split multiple attributes each on a new line</b> to start every attribute on a new line when the document is formatted. Attributes will return to the same margin as the previous line.
+
+Select <b>Indent using tabs</b> if you want to use tab characters (\t) as the standard formatting indentation.
+
+If you prefer to use spaces, select <b>Indent using spaces</b>.
+
+You can also specify the <b>Indentation size</b> which is the number of tabs or space characters used for formatting indentation.
+
+Select <b>Clear all blank lines</b> to remove blank lines when the document is formatted.
+
+To apply these formatting styles, select the <b>Format Document</b> menu item.
+
+If the <b>Automatically make suggestions</b> check box is selected, you can specify that certain characters will cause the content assist list to pop up automatically. Specify these characters in the <b>Prompt when these characters are inserted</b> field.
+
+Select the Uppercase or Lowercase radio button to determine the case for tag and attribute names that are inserted into the document when using content assist or code generation.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0032">
+<description>This page lets you customize the syntax highlighting that the HTML editor does when you are editing a file.
+
+The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting.
+
+The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that allow you to specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold.
+
+Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0033">
+<description>This page lets you create new and edit existing templates that will be used when you edit an HTML file.
+</description>
+<topic label="Adding and removing HTML templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html"/>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="xmlm1100">
+<description>Cleanup options enable you to update a document so that it is well-formed and formatted.
+
+The following cleanup options let you select radio buttons to choose the type of cleanup to be performed:
+- <b>Tag name case for HTML</b>: Unless set to <b>As-is</b>, changes the case of all tags in a file for easier visual parsing and consistency.
+- <b>Attribute name case for HTML</b>: Unless set to <b>As-is</b>, changes the case of all attributes in a file for easier visual parsing and consistency.
+
+The following cleanup options can be set to on or off, so that you can limit the type of cleanup performed:
+- <b>Insert required attributes</b>: Inserts an missing attributes that are required by the tag to make the element or document well-formed.
+- <b>Insert missing tags</b>: Completes any missing tags (such as adding an end tag) necessary to make the element or document well-formed.
+- <b>Quote attribute values</b>: Appropriately adds double- or single-quotes before and after attribute values if they are missing.
+- <b>Format source</b>: Formats the document just as the <b>Format Document</b> context menu option does, immediately after performing any other specified <b>Cleanup</b> options.
+- <b>Convert line delimiters to</b>: Converts all line delimiters in the file to the selected operating system's type.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+</contexts>
diff --git a/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts2.xml b/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts2.xml
new file mode 100644
index 0000000..b614187
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts2.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+
+<contexts>
+<context id="htmlsource_source_HelpId">
+<description>The HTML source page editor lets you edit a file that is coded in the Hypertext Markup Language or in XHTML. The editor provides many text editing features, such as content assist, user-defined templates, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting.
+</description>
+<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+<topic label="Adding and removing HTML templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html"/>
+</context>
+</contexts>
diff --git a/docs/org.eclipse.wst.html.ui.infopop/HTMLWizContexts.xml b/docs/org.eclipse.wst.html.ui.infopop/HTMLWizContexts.xml
new file mode 100644
index 0000000..ed68cf2
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/HTMLWizContexts.xml
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<contexts>
+<context id="htmlw0010">
+<description>Select the HTML template checkbox to create your HTML file based on a default template. Choose one of the frameset templates if you are developing a Web site with frames. If you do not select a template, your newly created JSP file will be completely blank.
+</description>
+</context>
+
+
+
+</contexts>
diff --git a/docs/org.eclipse.wst.html.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.html.ui.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..0b50faf
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: HTML editor infopops
+Bundle-SymbolicName: org.eclipse.wst.html.ui.infopop; singleton:=true
+Bundle-Version: 1.0.0.qualifier
+Bundle-Vendor: Eclipse.org
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.html.ui.infopop/about.html b/docs/org.eclipse.wst.html.ui.infopop/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.html.ui.infopop/build.properties b/docs/org.eclipse.wst.html.ui.infopop/build.properties
new file mode 100644
index 0000000..6dcb86b
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/build.properties
@@ -0,0 +1,6 @@
+bin.includes = plugin.xml,\
+ about.html,\
+ EditorHtmlContexts.xml,\
+ META-INF/,\
+ EditorHtmlContexts2.xml
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.html.ui.infopop/plugin.xml b/docs/org.eclipse.wst.html.ui.infopop/plugin.xml
new file mode 100644
index 0000000..9b085e7
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/plugin.xml
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<!-- ================================================= -->
+<!-- This is the plugin for declaring the help -->
+<!-- contributions for using the tool. -->
+<!-- ================================================= -->
+<!-- /*******************************************************************************
+ * 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>
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorHtmlContexts.xml" plugin ="org.eclipse.wst.html.ui"/>
+ <contexts file="EditorHtmlContexts2.xml" plugin ="org.eclipse.wst.html.core"/>
+ <contexts file="HTMLWizContexts.xml" plugin="org.eclipse.wst.html.ui"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/.cvsignore b/docs/org.eclipse.wst.sse.doc.user/.cvsignore
new file mode 100644
index 0000000..7ae166d
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/.cvsignore
@@ -0,0 +1,2 @@
+build.xml
+org.eclipse.wst.sse.doc.user_1.0.0.jar
diff --git a/docs/org.eclipse.wst.sse.doc.user/.project b/docs/org.eclipse.wst.sse.doc.user/.project
new file mode 100644
index 0000000..e2d6406
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.sse.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.sse.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..4829ed3
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: Structured text editor and snippets documentation
+Bundle-SymbolicName: org.eclipse.wst.sse.doc.user; singleton:=true
+Bundle-Version: 1.0.0.qualifier
+Bundle-Vendor: Eclipse.org
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.sse.doc.user/about.html b/docs/org.eclipse.wst.sse.doc.user/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/build.properties b/docs/org.eclipse.wst.sse.doc.user/build.properties
new file mode 100644
index 0000000..52caaf4
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/build.properties
@@ -0,0 +1,7 @@
+bin.includes = about.html,\
+ images/,\
+ plugin.xml,\
+ sse_toc.xml,\
+ topics/,\
+ META-INF/
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.sse.doc.user/images/ncontass.gif b/docs/org.eclipse.wst.sse.doc.user/images/ncontass.gif
new file mode 100644
index 0000000..d82014f
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/images/ncontass.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.sse.doc.user/images/njscdast.gif b/docs/org.eclipse.wst.sse.doc.user/images/njscdast.gif
new file mode 100644
index 0000000..41a141c
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/images/njscdast.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.sse.doc.user/images/nlinux.gif b/docs/org.eclipse.wst.sse.doc.user/images/nlinux.gif
new file mode 100644
index 0000000..7c135cf
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/images/nlinux.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.sse.doc.user/images/nmacscrp.gif b/docs/org.eclipse.wst.sse.doc.user/images/nmacscrp.gif
new file mode 100644
index 0000000..54a6371
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/images/nmacscrp.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.sse.doc.user/images/nquest.gif b/docs/org.eclipse.wst.sse.doc.user/images/nquest.gif
new file mode 100644
index 0000000..3faa1e2
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/images/nquest.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.sse.doc.user/plugin.xml b/docs/org.eclipse.wst.sse.doc.user/plugin.xml
new file mode 100644
index 0000000..6c83bbd
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/plugin.xml
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2001, 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
+ *******************************************************************************/ -->
+
+<!-- ===================================================== -->
+<!-- This is the plug-in for declaring the help pages -->
+<!-- for the structured text editors (source editors). -->
+<!-- ===================================================== -->
+
+<plugin>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="sse_toc.xml">
+ </toc>
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml b/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml
new file mode 100644
index 0000000..c92d56e
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="utf-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2001, 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="Structured text editors" topics="topics/csrcedt004.html">
+ <topic label="Editing text coded in markup languages " href="topics/tsrcedt000.html">
+ <topic label="Setting preferences for structured text editors" href="topics/tsrcedt025.html">
+ <topic label="Setting annotation preferences for markup languages" href="topics/tsrcedt001.html"/>
+ </topic>
+ <topic label="Getting content assistance in structured text editors" href="topics/tsrcedt005.html">
+ <topic label="Content assist" href="topics/csrcedt006.html"/>
+ <topic label="Making content assist work for JSP files" href="topics/tsrcedt023.html"/>
+ </topic>
+ <topic label="Searching or finding text within a file" href="topics/tsrcedt007.html"/>
+ <topic label="Adding and removing markup language templates - overview" href="topics/tsrcedt027.html">
+ <topic label="Adding and removing HTML templates" href="topics/tsrcedt024.html"/>
+ <topic label="Adding and removing JSP templates" href="topics/tsrcedt028.html"/>
+ <topic label="Adding and removing XML templates" href="topics/tsrcedt029.html"/>
+ </topic>
+ <topic label="Editing with snippets - overview" href="topics/tsrcedt026.html">
+ <topic label="Snippets view" href="topics/csrcedt001.html"/>
+ <topic label="Adding snippets drawers" href="topics/tsrcedt014.html"/>
+ <topic label="Adding items to snippets drawers" href="topics/tsrcedt015.html"/>
+ <topic label="Editing snippet items" href="topics/tsrcedt022.html"/>
+ <topic label="Deleting or hiding snippet items or drawers" href="topics/tsrcedt016.html"/>
+ </topic>
+ </topic>
+</toc>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.html
new file mode 100644
index 0000000..42b7e22
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Snippets view</title>
+</head>
+<body id="csrcedt001"><a name="csrcedt001"><!-- --></a>
+
+<h1 class="topictitle1">Snippets view</h1>
+<div><p>The Snippets view lets you catalog and organize reusable programming objects,
+such as HTML tagging, JavaScript™, and JSP code, along with files
+and custom JSP tags. The view can be extended based on additional objects
+that you define and include.</p>
+<p>To view or collapse the objects in a specific drawer, click the drawer
+name.</p>
+<div class="p">The Snippets view has the following features: <ul><li>Drag-and-drop to various source editing pages: You can drag items from
+the view into the active editor and the text will be dropped into the document
+at the cursor location </li>
+<li>Double-click support: You can double-click on an item and have it inserted
+at the current cursor position in the active editor </li>
+<li>User-defined drawers and items: You can define, edit, and remove items
+from view drawers as desired.</li>
+<li>Plug-in-defined drawers and items: Plug-in developers can contribute a
+default list of items to their own drawers.</li>
+<li>Variables in insertions: By default, items will be edited using a dialog
+and, when inserted, you will be prompted for values for each of the variables.</li>
+<li>Customization: You can select which drawers and items are shown in the
+Snippets view.</li>
+<li>Custom insertion: Plug-in developers can customize the behavior of items
+so that when they are dropped during a drag-and-drop action, both the text
+that is inserted and the insertion location are strictly defined.</li>
+</ul>
+</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a><br />
+<a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a><br />
+<a href="tsrcedt015.html" title="This documentation describes how to add a new item to a drawer in the Snippets view.">Adding items to snippets drawers</a><br />
+<a href="tsrcedt022.html" title="This documentation describes how to modify the template code that is in an item in a drawer in the Snippets view.">Editing snippet items</a><br />
+<a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or
+drawers</a><br />
+<!-- <a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages - overview</a>--><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html
new file mode 100644
index 0000000..3df15e8
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html
@@ -0,0 +1,110 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Structured text editors for markup languages</title>
+</head>
+<body id="csrcedt004"><a name="csrcedt004"><!-- --></a>
+
+<h1 class="topictitle1">Structured text editors for markup languages</h1>
+<div><p><span class="q">"Structured text editor"</span> is any of several text editors that
+you can use to edit various markup languages such as HTML, JavaScript, or
+XML.</p><p>The structured text editor is represented by various editors that you can
+use to edit files coded with markup tags:</p>
+
+<div class="skipspace"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e29">File type</th>
+<th valign="top" id="d0e31">Editor</th>
+<th valign="top" id="d0e33">Content assist?</th>
+</tr>
+</thead>
+<tbody><tr><td valign="top" headers="d0e29 ">Cascading style sheet</td>
+<td valign="top" headers="d0e31 ">CSS source page editor</td>
+<td valign="top" headers="d0e33 ">Yes</td>
+</tr>
+<tr><td valign="top" headers="d0e29 ">Deployment descriptor (web.xml)</td>
+<td valign="top" headers="d0e31 ">Source tab of deployment descriptor editor</td>
+<td valign="top" headers="d0e33 ">Yes</td>
+</tr>
+<tr><td valign="top" headers="d0e29 ">Document type definitions</td>
+<td valign="top" headers="d0e31 ">DTD source page editor</td>
+<td valign="top" headers="d0e33 ">No</td>
+</tr>
+<tr><td valign="top" headers="d0e29 ">HTML</td>
+<td valign="top" headers="d0e31 ">HTML source page editor</td>
+<td valign="top" headers="d0e33 ">Yes</td>
+</tr>
+<tr><td valign="top" headers="d0e29 ">JavaScript™</td>
+<td valign="top" headers="d0e31 ">JavaScript source page editor or source
+tab of JavaScript editor</td>
+<td valign="top" headers="d0e33 ">Yes</td>
+</tr>
+<tr><td valign="top" headers="d0e29 ">JSP</td>
+<td valign="top" headers="d0e31 ">JSP source page editor</td>
+<td valign="top" headers="d0e33 ">Yes</td>
+</tr>
+<tr><td valign="top" headers="d0e29 ">XML</td>
+<td valign="top" headers="d0e31 ">XML source page editor or Source tab of XML editor</td>
+<td valign="top" headers="d0e33 ">Yes</td>
+</tr>
+<tr><td valign="top" headers="d0e29 ">XSD (schema)</td>
+<td valign="top" headers="d0e31 ">Source tab of XML schema editor</td>
+<td valign="top" headers="d0e33 ">Yes</td>
+</tr>
+</tbody>
+</table>
+</div>
+<p>You can access the structured text editor by right-clicking on a relevant
+file name in Navigator or Package Explorer view and then clicking <span class="uicontrol">Open
+With</span> and selecting the editor mentioned above.</p>
+<p>The structured text editor provides a consistent interface regardless of
+the markup language with which it is associated. It provides capabilities
+such as find and replace, undo, redo, a spelling checker, and coding assistance
+(unless otherwise noted). It also highlights syntax in different colors. Following
+is a brief description of some of the structured text editor's capabilities:</p>
+<dl><dt class="bold">syntax highlighting</dt>
+<dd>Each keyword type and syntax type is highlighted differently, enabling
+you to easily find a certain kind of keyword for editing. For example, in
+HTML, element names, attribute names, attribute values, and comments have
+different colors; in JavaScript, function and variable names,
+quoted text strings, and comments have different colors.</dd>
+<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 to insert JavaScript functions, HTML tags, or other
+keywords. Choices available in the content assist list are based on functions
+defined by the syntax of the language in which the file is coded.</dd>
+<dt class="bold">user-defined templates and snippets</dt>
+<dd>By using the Snippets view, you can access user-defined code snippets
+and (for all code types except JavaScript) templates to help you quickly
+add regularly used text strings.</dd>
+<dt class="bold">function selection</dt>
+<dd>Based on the location of your cursor, the function or tag selection indicator
+highlights the line numbers that include a function or tag in the vertical
+ruler on the left area of the Source page.</dd>
+<dt class="bold">pop-up menu options</dt>
+<dd>These are the same editing options available in the workbench <span class="uicontrol">Edit</span> menu.</dd>
+</dl>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages - overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html
new file mode 100644
index 0000000..8b08d77
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html
@@ -0,0 +1,150 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Content assist</title>
+</head>
+<body id="csrcedt006"><a name="csrcedt006"><!-- --></a>
+
+<h1 class="topictitle1">Content assist</h1>
+<div><p>Content assist (Ctrl+Spacebar) helps you insert or finish a tag or function or
+finish a line of code in a structured text editor. The placement of the cursor
+in the source file provides the context for the content assist to offer suggestions
+for completion.</p><p>Most of the structured text editors have content assist. For a list of
+editors that have content assist, see <a href="csrcedt004.html">Structured
+text editors for markup languages</a>. For information on how to get content
+assistance, see <a href="tsrcedt005.html">Getting content assistance
+in structured text editors</a></p>
+<p>The sections below describe specifics of HTML content assist, JavaScript™ content
+assist, and JSP content assist.</p>
+<div class="skipspace"><h4 class="sectiontitle">HTML content assist</h4><p>HTML is flexible in that some
+HTML elements allow end tags to be optionally omitted, such as <samp class="codeph">P</samp>, <samp class="codeph">DT</samp>, <samp class="codeph">DD</samp>, <samp class="codeph">LI</samp>, <samp class="codeph">THEAD</samp>, <samp class="codeph">TR</samp>, <samp class="codeph">TD</samp>, <samp class="codeph">TH</samp>,
+and so on. Other HTML elements that are defined to have no content may require
+the end tag always be omitted, such as <samp class="codeph">BR</samp>, <samp class="codeph">HR</samp>, <samp class="codeph">LINK</samp>, <samp class="codeph">META</samp>,
+and <samp class="codeph">IMG</samp>. This flexibility makes the content assist function
+within the HTML source page editor less precise than it might be with a more
+rigidly constrained markup language.</p>
+<p>HTML content assist is most beneficial
+when you need to complete a tag name, add an attribute name-value pair within
+a start tag, or select from an enumerated list of attribute values.</p>
+<p>Although
+content assist only shows attribute names that have not already been specified
+in a start tag, it does not take into account grammar constraints for tags.
+For example, the <samp class="codeph">HEAD</samp> element in HTML only permits zero or
+one occurrences of a <samp class="codeph">TITLE</samp> tag in its content. If you prompt
+for content assist within a <samp class="codeph">HEAD</samp> content that already contains
+a <samp class="codeph">TITLE</samp> tag, content assist will still show <samp class="codeph">TITLE</samp> in
+its proposal list.</p>
+<p>However, if an attribute is required according to
+the DTD/Schema, that attribute will show up at the top of the list, with a
+yellow circle indicator on its icon.</p>
+<p>If your cursor is in a position
+where content assist is available, a pop-up list of available choices is displayed.
+The list is based on the context. For example, if you use content assist directly
+after an opening paragraph tag (<samp class="codeph"><p></samp>) , the first item
+in the content assist list will be the corresponding closing paragraph (<samp class="codeph"></p></samp>)
+tag.</p>
+<p>The content assist list displays all available tags for the current
+cursor position, including templates. The picture below shows the default
+content assist list for a paragraph tag example:<br /><img src="../images/ncontass.gif" alt="HTML Content assist" /><br /></p>
+<p>Tag proposals are listed
+alphabetically. If you type a <samp class="codeph"><</samp> (to begin a new tag) before
+prompting for content assist, and begin typing the first one or two letters
+of the tag that you want to add, the proposal list automatically refreshes
+to reflect proposals that match the pattern you have typed. If you do not
+type a <samp class="codeph"><</samp> before prompting for content assist, you can
+click within the proposal list and then type the letter that the tag begins
+with, to reduce (somewhat) the amount of scrolling to locate the desired tag.</p>
+<p>As
+you type the first one or two letters of the attribute names or enumerated
+attribute values that you want to add to a tag, the list automatically refreshes
+to reflect proposals that match the pattern you have typed.</p>
+<div class="restriction"><span class="restrictiontitle">Restriction: </span><img src="../images/nlinux.gif" alt="For Linux." /> When using Linux (Motif or
+GTK) and a DBCS locale, double-clicking on the content assist list can sometimes
+cause the Java™ VM to terminate. Instead of double-clicking on
+the list, use the arrows and Enter keys to make the selection from the list.</div>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">JavaScript content assist</h4><p>Items
+in the JavaScript content assist list are preceded by an Internet
+Explorer icon, a Netscape icon, or both, to indicate whether specific JavaScript objects,
+methods, or functions are supported by one or both browsers. If the Internet
+Explorer icon is present, it indicates that the object, method, or function
+is supported by Internet Explorer Version 5.0 or higher. If the Netscape
+icon is present, it indicates that the object, method, or function is supported
+by Netscape Navigator Version 4.7 or higher. A question mark icon (<img src="../images/nquest.gif" alt="Question mark icon" />)
+in place of one of the browser icons indicates that it is unknown whether
+the browser supports the object, method, or function.</p>
+<p>The picture below
+shows the default content assist list within a JavaScript file:<br /><img src="../images/njscdast.gif" alt="JavaScript content assist" /><br /></p>
+<p>Code
+proposals are listed alphabetically. If you type a <samp class="codeph">. </samp> (include
+the space) before prompting for content assist, and begin typing the first
+one or two letters of the code that you want to add, the proposal list automatically
+refreshes to reflect proposals that match the pattern you have typed, to reduce
+(somewhat) the amount of scrolling to locate the desired code.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">JSP content assist</h4><p>You have many options for embedding Java and
+HTML code in your JSP pages by using content assist.</p>
+<p>All of the JSP
+tags are included both in the template list and in XML format (for example, <samp class="codeph"><jsp:expression></samp>).
+To add JSP scriptlet tags, for example, move the cursor to the appropriate
+position in the file and press Ctrl+Space to use content assist. Select <img src="../images/nmacscrp.gif" alt="JSP scriptlet content assist" /> from
+the proposal list to insert <samp class="codeph"><% %></samp> in the document.</p>
+<div class="p">Scriptlets
+are inserted in a tag <samp class="codeph"><% %></samp>. For example: <pre><% System.currentTimeMillis() %></pre>
+</div>
+<p>This
+example will evaluate the Java statement to get the current time
+in milliseconds.</p>
+<div class="p">To have the result of the statement inserted in the
+file, put an equals sign (=) in the front of the statement. For example: <pre><b>This is the time : <%= System.currentTimeMillis()%></b></pre>
+</div>
+<div class="p">When you are within a scriptlet you are writing pure Java code.
+Therefore, content assist works exactly the same as it does for the Java editor.
+For example, if you request content assist after <samp class="codeph">System</samp>,
+content assist displays a list of methods. <div class="note"><span class="notetitle">Note: </span>Java content assist works only in a Web
+project, because it requires a buildpath to find the appropriate Java classes.</div>
+</div>
+<div class="p">There
+are also special tags such as useBean. For example: <pre><jsp:useBean id="useBean" class="java.lang.String"/></pre>
+</div>
+<p>The
+useBean tag enables you to create a bean called <samp class="codeph">aString</samp> of
+type <samp class="codeph">String</samp>. Then when you use content assist, this is recognized
+as a declared variable. For example, if you use content assist after <samp class="codeph">aString</samp>,
+as follows:</p>
+<div class="p"> <pre><% aString. %> </pre>
+the content assist
+list shows available methods. This is because <samp class="codeph">aString</samp> has
+been declared as a bean of type String.</div>
+<div class="p">If you use content assist after
+the <samp class="codeph">a</samp>, as follows: <pre><% a %> </pre>
+content
+assist knows that <samp class="codeph">aString</samp> exists, and it is shown in the
+content assist list.</div>
+</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt005.html" title="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor.">Getting content assistance in structured
+text editors</a><br />
+<a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html
new file mode 100644
index 0000000..29029fe
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing text coded in markup languages - overview</title>
+</head>
+<body id="tsrcedt000"><a name="tsrcedt000"><!-- --></a>
+
+<h1 class="topictitle1">Editing text coded in markup languages - overview</h1>
+<div><p>You can edit text coded in markup languages with a <dfn class="term">structured
+text editor</dfn>. This is a generic term for several editors that you can
+use to edit any of several markup languages such as HTML or XML.</p><div class="skipspace">In addition to basic editing tasks such as adding, modifying, and
+deleting text, you can perform the following tasks:</div>
+<ul><li><span><a href="tsrcedt025.html">Set preferences for structured
+text editors</a></span></li>
+<li><span><a href="tsrcedt005.html">Get content assistance
+in structured text editors</a></span></li>
+<li><span><a href="tsrcedt007.html">Search or find text within
+a file</a></span></li>
+<li><span><a href="tsrcedt010.html">Check spelling</a></span></li>
+<li><span><a href="tsrcedt027.html">Add or remove markup language
+templates</a></span></li>
+<li><span><a href="tsrcedt026.html">Edit with snippets</a></span></li>
+</ul>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+<a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a><br />
+<a href="csrcedt001.html" title="This documentation gives an overview of the Snippets view.">Snippets view</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt025.html" title="">Setting preferences for structured text editors</a><br />
+<a href="tsrcedt005.html" title="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor.">Getting content assistance in structured text editors</a><br />
+<a href="tsrcedt007.html" title="">Searching or finding text within a file</a><br />
+<a href="tsrcedt010.html" title="This documentation describes how to check spelling in a structured text editor.">Checking spelling</a><br />
+<a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language templates - overview</a><br />
+<a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html
new file mode 100644
index 0000000..fb63bd2
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Setting annotation preferences for markup languages</title>
+</head>
+<body id="tsrcedt001"><a name="tsrcedt001"><!-- --></a>
+
+<h1 class="topictitle1">Setting annotation preferences for markup languages</h1>
+<div><p>This documentation describes how to set <dfn class="term">annotation preferences</dfn> for
+Web and XML files. The annotation preferences include whether to analyze the
+syntactic validity of your file while you are typing and what colors to use
+to highlight errors, warnings, tasks, search results, bookmarks, and other
+text.</p><div class="skipspace"> <p>By default, when you edit in a structured text editor, your source
+code is validated as you type it in. Like other Eclipse-based editors, the
+structured text editors for markup languages flag warnings and errors in the
+source code in the editor area. The warnings and errors also show up in the
+Tasks view when you save the file.</p>
+<div class="note"><span class="notetitle">Note: </span>Highlighting is fully dynamic
+with the exception of search results. Search results are highlighted based
+upon what has been saved to disk.</div>
+<div class="tip"><span class="tiptitle">Tip: </span>You can improve a
+structured text editor's performance by turning off the real-time validation.</div>
+<p>To
+set annotation preferences, complete 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>.</span> A Preferences window appears.</li>
+<li class="skipspace"><span>In the Preferences window, click <span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Editors</span></span>.</span></li>
+<li class="skipspace"><span>Select one of the following options:</span><ul><li>To turn off real-time syntax validation, click <span class="uicontrol">Structured
+Text Editor</span> and uncheck the <span class="uicontrol">Analyze annotations while
+typing</span> box.</li>
+<li>To control other annotation settings, click <span class="uicontrol">Annotations</span> and
+select your annotation preferences.</li>
+</ul>
+</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span> to save your preferences and close
+the page.</span></li>
+</ol>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt025.html" title="">Setting preferences for structured
+text editors</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html
new file mode 100644
index 0000000..9c3751b
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html
@@ -0,0 +1,66 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Getting content assistance in structured text editors</title>
+</head>
+<body id="tsrcedt005">
+
+<h1 class="topictitle1">Getting content assistance in structured text editors</h1>
+<div><p>To get help in adding markup to a file, you can use content assist
+in a structured text editor. Content assist helps you insert or finish a tag
+or function or finish a line of code in a structured text editor.</p><div class="skipspace">Content assist also enables you to select and insert templates in
+structured text editors. The placement of the cursor in the source file provides
+the context for the content assist to offer suggestions for completion.</div>
+<div class="p"><span></span> You can request content assist in either of the following
+two ways:<ul><li>From the <span class="uicontrol">Edit</span> menu, select <span class="uicontrol">Content
+Assist</span></li>
+<li>Press Ctrl+Space</li>
+</ul>
+ <div class="p">In addition, you can set a preference that causes content assist
+to pop up automatically when certain characters are typed, such as <samp class="codeph">.</samp> in
+the case of JavaScript™ or <samp class="codeph"><</samp> in the case of
+HTML and XML. To set this preference, select <span class="uicontrol">Preferences</span> from
+the <span class="uicontrol">Window</span> menu, and then select <span class="uicontrol">Web and
+XML Files</span>, followed by one of the following sequences:<ul><li><span class="menucascade"><span class="uicontrol">HTML Files</span> > <span class="uicontrol">HTML Source</span></span></li>
+<li><span class="menucascade"><span class="uicontrol">JavaScript Files</span> > <span class="uicontrol">JavaScript
+Source</span></span></li>
+<li><span class="menucascade"><span class="uicontrol">XML Files</span> > <span class="uicontrol">XML Source</span></span></li>
+</ul>
+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.</div>
+<p>If your cursor is in a position
+where content assist is available, a pop-up list of all available choices
+is displayed. For each of these choices, a brief description of the code is
+provided.</p>
+</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt023.html" title="Having the proper files defined in the Java build class path is essential for content assist to work properly in JSP files. It is also essential for the links builder to be able to correctly resolve links to servlets or Java beans in JSP and HTML files.">Making content assist work for JSP
+files</a><br />
+<a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language
+templates - overview</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html
new file mode 100644
index 0000000..d3ace4a
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html
@@ -0,0 +1,50 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Searching or finding text within a file</title>
+</head>
+<body id="tsrcedt007">
+
+<h1 class="topictitle1">Searching or finding text within a file</h1>
+<div><div class="p"><div class="tip"><span class="tiptitle">Tip: </span>Before you do a Search operation in a structured
+text editor, save the file you are searching. The search function works from
+the most recently saved version of the file rather than from the contents
+that you see in the editor area. You do not need to save your file before
+you do a Find/Replace operation. </div>
+</div>
+<div class="skipspace">Each structured text editor provides two ways to locate a text string
+in the file you are editing and optionally replace it with another string: <dl><dt class="bold">Find/Replace</dt>
+<dd>Lets you locate text in the file currently being edited.</dd>
+<dt class="bold">Search</dt>
+<dd>Lets you locate text in files that have been saved to your workspace.</dd>
+</dl>
+<p>To locate and optionally replace text, select one of the
+following menu paths:</p>
+</div>
+<div class="p"><span><span class="menucascade"><span class="uicontrol">Edit</span> > <span class="uicontrol">Find/Replace</span></span> (or <span class="uicontrol">Ctrl+F</span>)</span> This option is
+self-explanatory.</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in
+markup languages - overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html
new file mode 100644
index 0000000..cddfca2
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html
@@ -0,0 +1,56 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Checking spelling</title>
+</head>
+<body id="tsrcedt010"><a name="tsrcedt010"><!-- --></a>
+
+<h1 class="topictitle1">Checking spelling</h1>
+<div><p>This documentation describes how to check spelling in a structured
+text editor.</p><div class="skipspace"> <p>The structured text editors for markup languages (accessed from
+the Project Explorer's pop-up menu or by clicking the Source tab in certain
+editors) provide a spell checking feature.</p>
+<p>To check spelling in an HTML,
+XML, or other file that uses a structured markup language:</p>
+ </div>
+<ol><li><span>(Optional) To select the dictionary that will be used, click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Spell
+Check</span></span>.</span></li>
+<li><span>Open in a structured text editor the file whose spelling you want
+to check.</span></li>
+<li><span>Start the spelling checker by clicking <span class="menucascade"><span class="uicontrol">Edit</span> > <span class="uicontrol">Spell Check</span></span>.</span></li>
+<li><span>Type a new spelling into the <span class="uicontrol">Change to</span> field,
+or select one of the available options. Click the <span class="uicontrol">Change</span> button
+to change the current instance of the word in the current document. Click
+the <span class="uicontrol">Change All</span> button to change all instances of the
+word in the current document. You can also click the <span class="uicontrol">Add</span> button
+to add the currently selected spelling to your dictionary.</span></li>
+<li><span>Use the controls in the Spell Check dialog box to ignore, change,
+or add terms to the current dictionary. (To remove a word after it has been
+added to the dictionary, click the <span class="uicontrol">Dictionary</span> push
+button.)</span></li>
+</ol>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html
new file mode 100644
index 0000000..ce5a037
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding snippets drawers</title>
+</head>
+<body id="tsrcedt014"><a name="tsrcedt014"><!-- --></a>
+
+<h1 class="topictitle1">Adding snippets drawers</h1>
+<div><p>This documentation explains how to customize the Snippets view
+by adding a new drawer.</p><div class="skipspace">To add a new drawer to the Snippets view:</div>
+<ol><li><span>Right-click anywhere in the Snippets view and select <span class="uicontrol">Customize</span> from
+the pop-up menu.</span></li>
+<li><span>Click <span class="menucascade"><span class="uicontrol">New</span> > <span class="uicontrol">New Drawer</span></span> and type the name of the new drawer in the <span class="uicontrol">Name</span> field.</span></li>
+<li><span>Optionally, type a description in the <span class="uicontrol">Description</span> field.</span></li>
+<li><span>Select the drawer's behavior by checking check boxes as appropriate.
+The check boxes are as follows:</span>
+<table border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="skipspace">
+<thead><tr><td><b>Option</b></td><td><b>Description</b></td></tr></thead>
+<tbody>
+<tr><td align="left" valign="top" id="d0e43"><b>Hide</b></td>
+<td align="left" valign="top" headers="d0e43">Do not display the drawer.</td>
+</tr>
+<tr><td align="left" valign="top" id="d0e48"><b>Open drawer at start-up</b></td>
+<td align="left" valign="top" headers="d0e48">At start-up, display
+the drawer's items.</td>
+</tr>
+<tr><td align="left" valign="top" id="d0e53"><b>Pin drawer open at start-up</b></td>
+<td align="left" valign="top" headers="d0e53">Keep the drawer
+open.</td>
+</tr>
+</tbody></table>
+</li>
+<li><span>Click <span class="uicontrol">OK</span>. The new drawer will be added to
+the list of drawers in the Snippets view.</span></li>
+</ol>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt001.html" title="This documentation gives an overview of the Snippets view.">Snippets view</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a><br />
+<a href="tsrcedt015.html" title="This documentation describes how to add a new item to a drawer in the Snippets view.">Adding items to snippets drawers</a><br />
+<a href="tsrcedt022.html" title="This documentation describes how to modify the template code that is in an item in a drawer in the Snippets view.">Editing snippet items</a><br />
+<a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or
+drawers</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html
new file mode 100644
index 0000000..9f04898
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html
@@ -0,0 +1,80 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding items to snippets drawers</title>
+</head>
+<body id="tsrcedt015"><a name="tsrcedt015"><!-- --></a>
+
+<h1 class="topictitle1">Adding items to snippets drawers</h1>
+<div><p>This documentation describes how to add a new item to a drawer
+in the Snippets view.</p><div class="skipspace"> To add new items to an existing snippets drawer:</div>
+<ol><li class="skipspace"><span>Do one of the following choices:</span>
+<div class="skipspace"><table cellpadding="4" cellspacing="0" summary="" frame="hsides" border="1" rules="rows"><thead align="left"><tr><th valign="top" id="d0e24">To start with this:</th>
+<th valign="top" id="d0e26">Do this:</th>
+</tr>
+</thead>
+<tbody><tr><td valign="top" headers="d0e24 ">An empty item that you can edit</td>
+<td valign="top" headers="d0e26 ">Right-click anywhere in an existing drawer, select <span class="uicontrol">Customize</span>,
+and click <span class="menucascade"><span class="uicontrol">New</span> > <span class="uicontrol">New Item</span></span>.</td>
+</tr>
+<tr><td valign="top" headers="d0e24 ">Existing text pasted into a new item in an existing
+drawer</td>
+<td valign="top" headers="d0e26 ">Copy or cut text to the clipboard. In the Snippets view,
+right-click anywhere in an existing drawer and click <span class="uicontrol">Paste</span>.</td>
+</tr>
+<tr><td valign="top" headers="d0e24 ">Existing text pasted into a new item in a new or existing
+drawer</td>
+<td valign="top" headers="d0e26 ">Select the text, right-click, click <span class="uicontrol">Add to
+Snippets</span>, specify the name of the drawer in the Snippets view
+to which you want to add the item, and click <span class="uicontrol">OK</span>.</td>
+</tr>
+</tbody>
+</table>
+</div>
+ A <span class="wintitle">Customize Palette</span> window
+appears.</li>
+<li class="skipspace"><span>Type a name for the new item, and, optionally, provide a description.</span> The value that you type in the <span class="uicontrol">Name</span> field
+will appear next to the item's icon in the Snippets view.</li>
+<li class="skipspace"><span>To include in the <span class="uicontrol">Template Pattern</span> field
+a variable that you have already defined, click <span class="uicontrol">Insert Variable
+Placeholder</span>. </span> A variable placeholder is a marker that,
+when tagging is inserted into the active file, will be replaced by the value
+that is entered into the <span class="uicontrol">Insert Template:</span><var class="varname">Item_name</var> dialog
+at insertion time. Clicking the <span class="uicontrol">Insert Variable Placeholder</span> button
+or typing Ctrl+Space activates a pop-up in the text area that prompts you
+with the correct sequences to create a marker for the variable. For
+example, if you create two variables named <var class="varname">uri</var> and <var class="varname">prefix</var>,
+and create variable placeholders for both, the template pattern might look
+like this:<pre><%@ taglib uri="${uri}" prefix="${prefix}" %></pre>
+</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span>.</span></li>
+</ol>
+<div class="skipspace">The new item will be added to the list of items in the appropriate
+drawer.</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt001.html" title="This documentation gives an overview of the Snippets view.">Snippets view</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a><br />
+<a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a><br />
+<a href="tsrcedt022.html" title="This documentation describes how to modify the template code that is in an item in a drawer in the Snippets view.">Editing snippet items</a><br />
+<a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or
+drawers</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html
new file mode 100644
index 0000000..29935d7
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html
@@ -0,0 +1,45 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Deleting or hiding snippet items or drawers</title>
+</head>
+<body id="tsrcedt016"><a name="tsrcedt016"><!-- --></a>
+
+<h1 class="topictitle1">Deleting or hiding snippet items or drawers</h1>
+<div><p>This documentation describes how to delete or hide drawers and
+items in the Snippets view.</p><div class="skipspace">You can hide any drawer or item that shows up in the Snippets view.
+If the drawer or item is user-defined, you can delete it permanently. To delete
+or hide a drawer or item, complete the following steps:</div>
+<ol><li><span>Select the item or drawer that you want to remove.</span></li>
+<li><span>Right-click and select <span class="uicontrol">Customize</span> from the
+pop-up menu.</span></li>
+<li><span>Select the item or drawer and click <span class="uicontrol">Delete</span> or <span class="uicontrol">Hide</span>.</span></li>
+<li><span>Click <span class="uicontrol">OK</span>. The item or drawer will be deleted
+or hidden from the Snippets view.</span></li>
+</ol>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt001.html" title="This documentation gives an overview of the Snippets view.">Snippets view</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a><br />
+<a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a><br />
+<a href="tsrcedt015.html" title="This documentation describes how to add a new item to a drawer in the Snippets view.">Adding items to snippets drawers</a><br />
+<a href="tsrcedt022.html" title="This documentation describes how to modify the template code that is in an item in a drawer in the Snippets view.">Editing snippet items</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html
new file mode 100644
index 0000000..ac5ceee
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing snippet items</title>
+</head>
+<body id="tsrcedt022"><a name="tsrcedt022"><!-- --></a>
+
+<h1 class="topictitle1">Editing snippet items</h1>
+<div><p>This documentation describes how to modify the template code that
+is in an item in a drawer in the Snippets view.</p><div class="skipspace"> To modify an existing item in a Snippets drawer, complete the steps
+listed below. If you have just completed the task <a href="tsrcedt015.html">Adding an item to a snippets drawer</a> and the <span class="wintitle">Customize
+Palette</span> window is still open, you can skip steps 1 and 2.</div>
+<ol><li class="skipspace"><span>In the Snippets view, right-click the name of the item that you
+want to modify, and select <span class="uicontrol">Customize</span>.</span></li>
+<li class="skipspace"><span>Optionally, type a new name and a new description for the item.</span></li>
+<li class="skipspace"><span>To declare a variable, click <span class="uicontrol">New</span> and type
+the variable's name, description, and default value.</span></li>
+<li class="skipspace"><span>To edit an existing variable, type over the existing values.</span></li>
+<li class="skipspace"><span>To edit the <span class="uicontrol">Template Pattern</span> field, type
+into the field, cut and paste into the field, or, if you have defined one
+or more variables, click the <span class="uicontrol">Insert Variable Placeholder</span> button,
+and double-click the name of the variable that you want to insert.</span> For
+example, if you have declare variables named <var class="varname">uri</var> and <var class="varname">prefix</var>,
+clicking the button brings up a menu that contains those names. Double-clicking <var class="varname">uri</var> inserts <samp class="codeph">${uri}</samp>,
+as in the following example:<pre><%@ taglib uri="${uri}" prefix="${prefix}" %></pre>
+ Later, when you insert the snippet into a file, <samp class="codeph">${uri}</samp> and <samp class="codeph">${prefix}</samp> are
+each converted to the default value declared in the Variables table. Users
+can replace the default values in the <span class="uicontrol">Insert Template:</span><var class="varname">Item_name</var> dialog
+at insertion time.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span>.</span></li>
+</ol>
+<div class="skipspace">The modified item will be added to the list of items in the appropriate
+drawer.</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt001.html" title="This documentation gives an overview of the Snippets view.">Snippets view</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a><br />
+<a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a><br />
+<a href="tsrcedt015.html" title="This documentation describes how to add a new item to a drawer in the Snippets view.">Adding items to snippets drawers</a><br />
+<a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or
+drawers</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html
new file mode 100644
index 0000000..3f93df8
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Making content assist work for JSP files</title>
+</head>
+<body id="tsrcedt023"><a name="tsrcedt023"><!-- --></a>
+
+<h1 class="topictitle1">Making content assist work for JSP files</h1>
+<div><p>Having the proper files defined in the Java™ build class path is essential for
+content assist to work properly in JSP files. It is also essential for the
+links builder to be able to correctly resolve links to servlets or Java beans
+in JSP and HTML files.</p><div class="skipspace">To make content assist work for JSP files:</div>
+<ol><li class="skipspace"><span>To determine whether the build path is correct, select <span class="uicontrol">Properties</span> from
+the project's pop-up menu. </span></li>
+<li class="skipspace"><span>Select <span class="uicontrol">Java Build Path</span>, and then the <span class="uicontrol">Libraries</span> page. </span> You should see the following files:<ul><li>j2ee.jar</li>
+<li>rt.jar </li>
+<li>servlet.jar</li>
+<li>webcontainer.jar</li>
+</ul>
+</li>
+<li class="skipspace"><span>If they are not present, add them as External JAR files. You may
+have your own versions of these files, depending on the level of JDK or Servlet
+API for which you are developing.</span></li>
+<li class="skipspace"><span>If your Web applications reference other JARs, you can place them
+in the build path as follows:</span><ol type="a"><li><span>Use the <span class="uicontrol">Add JARs</span> button on the Library
+page. You must ensure that the JAR file is available to the server by properly
+configuring the server.</span></li>
+<li><span>Add the JARs to the <span class="filepath">WEB-INF/lib</span> directory.
+They will be automatically added to the build path and deployed to the server
+in as part of the project WAR.</span></li>
+</ol>
+</li>
+</ol>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt005.html" title="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor.">Getting content assistance in structured
+text editors</a><br />
+<a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html
new file mode 100644
index 0000000..b140ed1
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html
@@ -0,0 +1,77 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding and removing HTML templates</title>
+</head>
+<body id="tsrcedt024">
+
+<h1 class="topictitle1">Adding and removing HTML templates</h1>
+<div><p>HTML content assist provides several templates, or chunks of predefined
+code, that you can insert into a file. You can use the default templates as
+provided, customize the default templates, or create your own templates.</p><div class="skipspace"> <p>For example, you may work on a group of HTML 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 <span class="uicontrol">Pattern</span> field.) Then select
+the name of the template from a content assist proposal list whenever you
+want to insert your custom table into an HTML or XHTML file.</p>
+<p>To add
+a new HTML template, complete the following steps:</p>
+ </div>
+<ol><li class="skipspace"><span>From the <span class="uicontrol">Window</span> menu, select <span class="uicontrol">Preferences</span>.</span></li>
+<li class="skipspace"><span>In the Preferences page, select <span class="menucascade"><span class="uicontrol">Web and
+XML</span> > <span class="uicontrol">HTML Files</span> > <span class="uicontrol">HTML Templates</span></span>.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">New</span>. </span></li>
+<li class="skipspace"><span>Enter the new template name (a text string) and a brief description
+of the template.</span></li>
+<li class="skipspace"><span>Using the <span class="uicontrol">Context</span> drop-down list, specify
+the context in which the template is available in the proposal list when content
+assist is requested.</span></li>
+<li class="skipspace"><span>In the <span class="uicontrol">Pattern</span> field, enter the appropriate
+tags, attributes, or attribute values (the content of the template) to be
+inserted by content assist.</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 <var class="varname">word_selection</var> variable
+indicates the word that is selected at the beginning of template insertion,
+and the <var class="varname">cursor</var> 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">OK</span> to save the new template.</span></li>
+</ol>
+<div class="skipspace"><p>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>
+<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 uncheck
+its check box.</p>
+</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language
+templates - overview</a><br />
+<a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a><br />
+<a href="tsrcedt029.html" title="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.">Adding and removing XML templates</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html
new file mode 100644
index 0000000..9bc1844
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html
@@ -0,0 +1,97 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Setting preferences for structured text editors</title>
+</head>
+<body id="tsrcedt025">
+
+<h1 class="topictitle1">Setting preferences for structured text editors</h1>
+<div><div class="skipspace">You can customize your working environment by specifying preferences
+for the structured text editor.</div>
+<ol><li class="skipspace"><span>In the main menu, click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span></span>.</span></li>
+<li class="skipspace"><span>Select one of the choices that are shown in the following table:</span>
+<table border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="skipspace">
+<tbody>
+<tr><th align="left" valign="bottom" id="d0e29" width="25%">Item</th>
+<th align="left" valign="bottom" id="d0e31" width="75%">Menu path</th>
+</tr>
+<tr><td align="left" valign="top" id="d0e34" headers="d0e29"><b>Annotation settings</b></td>
+<td align="left" valign="top" headers="d0e31 d0e34"><span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Editors</span> > <span class="uicontrol">Annotations</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e45" headers="d0e29"><b>Character encoding</b></td>
+<td align="left" valign="top" headers="d0e31 d0e45"><span class="uicontrol">Web and XML</span>,
+then one of the following choices: <span class="uicontrol">CSS Files</span>, <span class="uicontrol">HTML
+Files</span>, <span class="uicontrol">JSP Files</span>, <span class="uicontrol">XML Files</span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e63" headers="d0e29"><b>Content assist: HTML</b></td>
+<td align="left" valign="top" headers="d0e31 d0e63"><span class="menucascade"><span class="uicontrol">Web
+and XML</span> > <span class="uicontrol">HTML Files</span> > <span class="uicontrol">HTML Source</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e74" headers="d0e29"><b>Content assist: JavaScript</b></td>
+<td align="left" valign="top" headers="d0e31 d0e74"><span class="menucascade"><span class="uicontrol">Web and XML</span> > <span class="uicontrol">JavaScript Files</span> > <span class="uicontrol">JavaScript Source</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e85" headers="d0e29"><b>Content assist: XML</b></td>
+<td align="left" valign="top" headers="d0e31 d0e85"><span class="menucascade"><span class="uicontrol">Web
+and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML Source</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e96" headers="d0e29"><b>Editor appearance</b></td>
+<td align="left" valign="top" headers="d0e31 d0e96"><span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> > <span class="uicontrol">Appearance</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e109" headers="d0e29"><b>Editor font</b></td>
+<td align="left" valign="top" headers="d0e31 d0e109"><span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Colors and Fonts</span> > <span class="uicontrol">Structured Text Editor</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e120" headers="d0e29"><b>Editor navigation</b></td>
+<td align="left" valign="top" headers="d0e31 d0e120"><span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> > <span class="uicontrol">Navigation</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e133" headers="d0e29"><b>File-type-specific settings</b></td>
+<td align="left" valign="top" headers="d0e31 d0e133"><span class="uicontrol">Web
+and XML</span>, then navigate to the file type and particular setting</td>
+</tr>
+<tr><td align="left" valign="top" id="d0e140" headers="d0e29"><b>Hover help</b></td>
+<td align="left" valign="top" headers="d0e31 d0e140"><span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> > <span class="uicontrol">Hovers</span></span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e153" headers="d0e29"><b>Key bindings</b></td>
+<td align="left" valign="top" headers="d0e31 d0e153"><span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Keys</span> > <span class="uicontrol">Keyboard Shortcuts</span></span> then
+in the <span class="uicontrol">Category</span> field specify <span class="uicontrol">Source</span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e170" headers="d0e29"><b>Spell checking</b></td>
+<td align="left" valign="top" headers="d0e31 d0e170"><span class="uicontrol">Spell Check</span></td>
+</tr>
+<tr><td align="left" valign="top" id="d0e176" headers="d0e29"><b>Syntax checking</b></td>
+<td align="left" valign="top" headers="d0e31 d0e176"><span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> > <span class="uicontrol">Appearance</span></span> then check or uncheck the <span class="uicontrol">Analyze
+annotations while typing</span> box.</td>
+</tr>
+</tbody></table>
+ <div class="note"><span class="notetitle">Note: </span>You cannot set <span class="uicontrol">Web and XML</span> preferences
+unless the Core XML Support capability (<span class="menucascade"><span class="uicontrol">Workbench</span> > <span class="uicontrol">Capabilities</span></span>) is enabled, and you cannot
+set preferences for DTD files unless the XML Development capability is enabled.</div>
+</li>
+</ol>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt001.html" title="This documentation describes how to set annotation preferences for Web and XML files. The annotation preferences include whether to analyze the syntactic validity of your file while you are typing and what colors to use to highlight errors, warnings, tasks, search results, bookmarks, and other text.">Setting annotation preferences for
+markup languages</a><br />
+<a href="tsrcedt010.html" title="This documentation describes how to check spelling in a structured text editor.">Checking spelling</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html
new file mode 100644
index 0000000..c61f1d7
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html
@@ -0,0 +1,47 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing with snippets - overview</title>
+</head>
+<body id="tsrcedt026"><a name="tsrcedt026"><!-- --></a>
+
+<h1 class="topictitle1">Editing with snippets - overview</h1>
+<div><p>The Snippets view lets you catalog and organize reusable programming
+objects, such as HTML tagging, JavaScript™, and JSP code, along with files
+and custom JSP tags. The view can be extended based on additional objects
+that you define and include.</p><div class="skipspace">In the Snippets view you can perform the following tasks:</div>
+<ul><li><span>Add snippets drawers</span></li>
+<li><span>Add items to snippets drawers</span></li>
+<li><span>Edit snippet items</span></li>
+<li><span>Delete or hide snippet items or drawers</span></li>
+</ul>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt001.html" title="This documentation gives an overview of the Snippets view.">Snippets view</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a><br />
+<a href="tsrcedt015.html" title="This documentation describes how to add a new item to a drawer in the Snippets view.">Adding items to snippets drawers</a><br />
+<a href="tsrcedt022.html" title="This documentation describes how to modify the template code that is in an item in a drawer in the Snippets view.">Editing snippet items</a><br />
+<a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or
+drawers</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages - overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html
new file mode 100644
index 0000000..c35845c
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html
@@ -0,0 +1,43 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding and removing markup language templates - overview</title>
+</head>
+<body id="tsrcedt027"><a name="tsrcedt027"><!-- --></a>
+
+<h1 class="topictitle1">Adding and removing markup language templates - overview</h1>
+<div><p>Content assist provides templates, or chunks of predefined code,
+that you can insert into a file. You can use the default templates as provided,
+customize the default templates, or create your own templates.</p><div class="skipspace">Templates are available for the following markup languages:<ul><li>HTML or XHTML</li>
+<li>JSP</li>
+<li>XML</li>
+</ul>
+</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a><br />
+<a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a><br />
+<a href="tsrcedt029.html" title="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.">Adding and removing XML templates</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html
new file mode 100644
index 0000000..67f4f45
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html
@@ -0,0 +1,77 @@
+<?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>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding and removing JSP templates</title>
+</head>
+<body id="tsrcedt028"><a name="tsrcedt028"><!-- --></a>
+
+<h1 class="topictitle1">Adding and removing JSP templates</h1>
+<div><p>JSP content assist provides several templates, or chunks of predefined
+code, that you can insert into a file. You can use the default templates as
+provided, customize the default templates, or create your own templates.</p><div class="skipspace"> <p>For example, suppose you want to work on a group of JSP pages that
+all contain a table with a specific appearance. You can 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 <span class="uicontrol">Pattern</span> field.) Then you can select
+the name of the template from a content assist proposal list whenever you
+want to insert your custom table into a JSP file.</p>
+<p>To add a new JSP template,
+complete the following steps:</p>
+ </div>
+<ol><li class="skipspace"><span>From the <span class="uicontrol">Window</span> menu, select <span class="uicontrol">Preferences</span>.</span></li>
+<li class="skipspace"><span>In the Preferences page, select <span class="menucascade"><span class="uicontrol">Web and
+XML</span> > <span class="uicontrol">JSP Files</span> > <span class="uicontrol">JSP Templates</span></span>.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol">New</span>. </span></li>
+<li class="skipspace"><span>Enter the new template name (a text string) and a brief description
+of the template.</span></li>
+<li class="skipspace"><span>Using the <span class="uicontrol">Context</span> drop-down list, specify
+the context in which the template is available in the proposal list when content
+assist is requested.</span></li>
+<li class="skipspace"><span>In the <span class="uicontrol">Pattern</span> field, enter the appropriate
+tags, attributes, or attribute values (the content of the template) to be
+inserted by content assist.</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 <var class="varname">word_selection</var> variable
+indicates the word that is selected at the beginning of template insertion,
+and the <var class="varname">cursor</var> 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">OK</span> to save the new template.</span></li>
+</ol>
+<div class="skipspace"><p>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>
+<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 uncheck
+its check box.</p>
+</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language
+templates - overview</a><br />
+<a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a><br />
+<a href="tsrcedt029.html" title="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.">Adding and removing XML templates</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html
new file mode 100644
index 0000000..4f7e8b3
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html
@@ -0,0 +1,77 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding and removing XML templates</title>
+</head>
+<body id="tsrcedt027"><a name="tsrcedt027"><!-- --></a>
+
+<h1 class="topictitle1">Adding and removing 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"> <p>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 <span class="uicontrol">Pattern</span> 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>
+<p>To add a new XML
+template, complete the following steps: </p>
+ </div>
+<ol><li class="skipspace"><span>From the <span class="uicontrol">Window</span> menu, select <span class="uicontrol">Preferences</span>.</span></li>
+<li class="skipspace"><span>In the Preferences page, select <span class="menucascade"><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>. </span></li>
+<li class="skipspace"><span>Enter the new template name (a text string) and a brief description
+of the template.</span></li>
+<li class="skipspace"><span>Using the <span class="uicontrol">Context</span> drop-down list, specify
+the context in which the template is available in the proposal list when content
+assist is requested.</span></li>
+<li class="skipspace"><span>In the <span class="uicontrol">Pattern</span> field, enter the appropriate
+tags, attributes, or attribute values (the content of the template) to be
+inserted by content assist.</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 <var class="varname">word_selection</var> variable
+indicates the word that is selected at the beginning of template insertion,
+and the <var class="varname">cursor</var> variable determines where the cursor will
+be after the template is inserted in the XML document.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span> to save the new template.</span></li>
+</ol>
+<div class="skipspace"><p>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>
+<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 uncheck
+its check box.</p>
+</div>
+</div>
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language
+templates - overview</a><br />
+<a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a><br />
+<a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a><br />
+<a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages such as HTML or XML.">Editing text coded in markup languages
+- overview</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.web.ui.infopop/.project b/docs/org.eclipse.wst.web.ui.infopop/.project
new file mode 100644
index 0000000..10c4a6e
--- /dev/null
+++ b/docs/org.eclipse.wst.web.ui.infopop/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.web.ui.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.web.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.web.ui.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..ad5f8d2
--- /dev/null
+++ b/docs/org.eclipse.wst.web.ui.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: Static Web infopop
+Bundle-SymbolicName: org.eclipse.wst.web.ui.infopop; singleton:=true
+Bundle-Version: 1.0.1.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.web.ui.infopop/StaticWebWizContexts.xml b/docs/org.eclipse.wst.web.ui.infopop/StaticWebWizContexts.xml
new file mode 100644
index 0000000..f933736
--- /dev/null
+++ b/docs/org.eclipse.wst.web.ui.infopop/StaticWebWizContexts.xml
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<contexts>
+<context id="org.eclipse.wst.web.ui.webw2000">
+<description> Use this page to name your Web project and specify the file system location (the place where the resources you create are stored.) When the Use default check box is selected, the project will be created in the file system location where your workspace resides. To change the default file system location, clear the checkbox and locate the path using the <b>Browse</b> button. To configure additional options, select the <b>Next</b> button.
+In the Target Runtime field, select the server where you want to publish the Web project. if a server is not already defined, click <b>New</b> to select a server runtime environment. </description>
+<topic label="Creating a static Web project" href="../org.eclipse.wst.webtools.doc.user/topics/twcresta.html"/>
+</context>
+
+<context id="org.eclipse.wst.web.ui.webw2100">
+<description>Presets are used to define a default set of facet versions that will configure a project for a particular type of development. The Static Web Module facet enables the project to be deployed as a static
+Web module. Click Show Runtimes to view the available runtimes and runtime compositions.</description>
+<topic label="Creating a static Web project" href="../org.eclipse.wst.webtools.doc.user/topics/twcresta.html"/>
+</context>
+
+<context id="org.eclipse.wst.web.ui.webw2200">
+<description>The Web content folder is where the elements of your Web site such as Web pages, graphics and style sheets are stored. This directory structure is necessary to ensure that the content of your Web site will be included in the WAR file at deployment and that link validation will work correctly.
+</description>
+<topic label="Creating a static Web project" href="../org.eclipse.wst.webtools.doc.user/topics/twcresta.html"/>
+</context>
+
+
+</contexts>
diff --git a/docs/org.eclipse.wst.web.ui.infopop/about.html b/docs/org.eclipse.wst.web.ui.infopop/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.web.ui.infopop/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.web.ui.infopop/build.properties b/docs/org.eclipse.wst.web.ui.infopop/build.properties
new file mode 100644
index 0000000..d9a93d8
--- /dev/null
+++ b/docs/org.eclipse.wst.web.ui.infopop/build.properties
@@ -0,0 +1,6 @@
+bin.includes = StaticWebWizContexts.xml,\
+ about.html,\
+ plugin.xml,\
+ plugin.properties,\
+ META-INF/
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.web.ui.infopop/plugin.properties b/docs/org.eclipse.wst.web.ui.infopop/plugin.properties
new file mode 100644
index 0000000..b61d2de
--- /dev/null
+++ b/docs/org.eclipse.wst.web.ui.infopop/plugin.properties
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2006 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
+###############################################################################
+
+pluginName = Static Web infopop
+pluginProvider = Eclipse.org
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.web.ui.infopop/plugin.xml b/docs/org.eclipse.wst.web.ui.infopop/plugin.xml
new file mode 100644
index 0000000..20ac018
--- /dev/null
+++ b/docs/org.eclipse.wst.web.ui.infopop/plugin.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+
+<!-- ================================================= -->
+<!-- This is the plugin for declaring the help -->
+<!-- contributions for using the tool. -->
+<!-- ================================================= -->
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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>
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="StaticWebWizContexts.xml" plugin ="org.eclipse.wst.web.ui"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/.cvsignore b/docs/org.eclipse.wst.webtools.doc.user/.cvsignore
new file mode 100644
index 0000000..2d79bd9
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/.cvsignore
@@ -0,0 +1,2 @@
+build.xml
+org.eclipse.wst.webtools.doc.user_1.0.0.jar
diff --git a/docs/org.eclipse.wst.webtools.doc.user/.project b/docs/org.eclipse.wst.webtools.doc.user/.project
new file mode 100644
index 0000000..bd5b157
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.webtools.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.webtools.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.webtools.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..85561b6
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.webtools.doc.user; singleton:=true
+Bundle-Version: 1.0.1.qualifier
+Bundle-Vendor: %providerName
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.webtools.doc.user/about.html b/docs/org.eclipse.wst.webtools.doc.user/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/build.properties b/docs/org.eclipse.wst.webtools.doc.user/build.properties
new file mode 100644
index 0000000..6609225
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/build.properties
@@ -0,0 +1,8 @@
+bin.includes = plugin.xml,\
+ webtools_toc.xml,\
+ about.html,\
+ images/,\
+ topics/,\
+ META-INF/,\
+ plugin.properties
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/fixit.gif b/docs/org.eclipse.wst.webtools.doc.user/images/fixit.gif
new file mode 100644
index 0000000..ffafc3d
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/fixit.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/grptype.gif b/docs/org.eclipse.wst.webtools.doc.user/images/grptype.gif
new file mode 100644
index 0000000..46d245f
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/grptype.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/menubutton.gif b/docs/org.eclipse.wst.webtools.doc.user/images/menubutton.gif
new file mode 100644
index 0000000..7ef1a62
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/menubutton.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nlinux.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nlinux.gif
new file mode 100644
index 0000000..7c135cf
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nlinux.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nshowerr.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nshowerr.gif
new file mode 100644
index 0000000..c2bfdd6
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nshowerr.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwarning.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwarning.gif
new file mode 100644
index 0000000..cf4fdf9
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwarning.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwin.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwin.gif
new file mode 100644
index 0000000..895f9ca
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwin.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkbrk.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkbrk.gif
new file mode 100644
index 0000000..6321433
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkbrk.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkcss.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkcss.gif
new file mode 100644
index 0000000..1a0caf6
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkcss.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr-l.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr-l.gif
new file mode 100644
index 0000000..9c73b6a
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr-l.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr.gif
new file mode 100644
index 0000000..f3c6261
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkind.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkind.gif
new file mode 100644
index 0000000..943f756
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkind.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkmal.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkmal.gif
new file mode 100644
index 0000000..889c47f
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkmal.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnknum.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnknum.gif
new file mode 100644
index 0000000..f324a63
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnknum.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkotr.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkotr.gif
new file mode 100644
index 0000000..f596591
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkotr.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkque.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkque.gif
new file mode 100644
index 0000000..345f939
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkque.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnktsk.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnktsk.gif
new file mode 100644
index 0000000..9cd47ee
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnktsk.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/skipit.gif b/docs/org.eclipse.wst.webtools.doc.user/images/skipit.gif
new file mode 100644
index 0000000..55f5b1b
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/skipit.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/viewlink.gif b/docs/org.eclipse.wst.webtools.doc.user/images/viewlink.gif
new file mode 100644
index 0000000..407b051
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/images/viewlink.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.webtools.doc.user/plugin.properties b/docs/org.eclipse.wst.webtools.doc.user/plugin.properties
new file mode 100644
index 0000000..acba026
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/plugin.properties
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2001, 2004 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
+###############################################################################
+
+pluginName = Web tools documentation
+providerName = Eclipse.org
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/plugin.xml b/docs/org.eclipse.wst.webtools.doc.user/plugin.xml
new file mode 100644
index 0000000..d7e149f
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/plugin.xml
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<?eclipse version="3.0"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+<!-- /*******************************************************************************
+ * 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>
+ <extension point="org.eclipse.help.toc">
+ <toc file="webtools_toc.xml" />
+ </extension>
+ </plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.html
new file mode 100644
index 0000000..59b1d41
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.html
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Static Web projects</title>
+</head>
+<body id="ccstatic"><a name="ccstatic"><!-- --></a>
+<h1 class="topictitle1">Static Web projects</h1>
+<div><p>If you want to create a content-based Web application that does not contain
+any dynamic content (such as servlets, JSP files, filters, and associated
+metadata) you might prefer to create a static Web project, as opposed to a <a href="ccwebprj.html">dynamic Web project</a>.</p>
+<div class="p">Static Web projects have the following characteristics: <ul><li>a Web content folder (called WebContent) for all publishable resources,
+You can change the name of this folder from the project's pop-up menu.</li>
+<li>a Theme folder, the suggested directory for storing cascading style sheets
+and other style-related objects.</li>
+<li>the ability to define folders outside of the Web content folder, for storing
+intermediate files, such as MIF files</li>
+<li>a conversion path from a static Web project to a dynamic Web project.
+If you decide to <a href="twpcnvrt.html">convert</a> the project, it will be a fully-valid dynamic
+Web project. </li>
+</ul>
+</div>
+<div class="p">In addition, your project will still have the following features (which
+are common to both static and dynamic Web projects ) : <ul><li>HTML syntax validation</li>
+<li>a broken link fix-up wizard</li>
+<li>a Web site navigation tool</li>
+<li>a new server type, the Static Web server, which makes it easy to publish
+static Web projects</li>
+</ul>
+ </div>
+<p>The folder that a static Web project is published to is modifiable, so
+that when you set the publishing "root" value (called a <em>context root</em>),
+such as <samp class="codeph">/web1</samp>, for a static project, everything in the Web
+content folder will be published to the <span class="filepath">web1</span> folder under
+the Web server's doc root. This enables you to group Web resources on a Web
+server in folders that correspond to Web projects in the workbench. When projects
+defined in this way are ready for production, you can publish specific projects
+directly to the doc root by changing the value to <samp class="codeph">/</samp> and all
+publishing, link fixing, and browsing will update automatically.</p>
+<div class="p">Aliases can also be used to specify a context root value. For example,
+suppose that there is an alias that is defined on the target Web server, as
+follows: <pre>Alias /scripts/ "/var/www/scripts"</pre>
+In this
+example, in which the current static Web project will contain common JavaScript™ files,
+you can set the context root value to be <span>"scripts"</span>. In order for
+the resources in the static Web project to be published to the correct location
+on the Web server, you must add this Alias mapping to the server tools instance
+of the static Web server, as follows. <ol><li>From the Server view, double-click on the static Web server configuration
+to open the server configuration editor.<div class="note"><span class="notetitle">Note:</span> This assumes that you've already
+defined the static Web server.</div>
+</li>
+<li>Click the <b>Configuration</b> editor tab.</li>
+<li>Scroll down to the <b>Alias Path Mapping</b> section,
+and add the new Alias mapping.</li>
+</ol>
+Now that <span>"scripts"</span> is defined as an Alias, the Web content in
+the static Web project will be published to the mapped path, <span class="filepath">/var/www/scripts</span>.</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwebresources.html">Web resources</a></div>
+<div><a href="cwwarovr.html">Web archive (WAR) files</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twcresta.html">Creating a static Web project</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.html
new file mode 100644
index 0000000..aaa9bbc
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.html
@@ -0,0 +1,139 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Dynamic Web projects and applications</title>
+</head>
+<body id="ccwebprj"><a name="ccwebprj"><!-- --></a>
+<h1 class="topictitle1">Dynamic Web projects and applications</h1>
+<div><p>There are two types of Web projects: dynamic and <a href="ccstatic.html">static</a>. Dynamic web projects can contain dynamic J2EE
+resources such as servlets, JSP files, filters, and associated metadata, in
+addition to static resources such as images and HTML files. Static web projects
+only contains static resources. When you create Web projects, you can include
+cascading style sheets and JSP tag libraries (for dynamic Web projects), so
+that you can begin development with a richer set of project resources.</p>
+<p>Dynamic Web projects are always imbedded in Enterprise Application projects.
+The wizard that you use to create a dynamic Web project will also create an
+Enterprise Application (EAR) project if it does not already exist. The wizard
+will also update the <span class="filepath">application.xml</span> deployment descriptor
+of the specified Enterprise Application project to define the Web project
+as a module element. If you are importing a WAR file rather than creating
+a dynamic Web project new, the WAR Import wizard requires that you specify
+a Web project, which already requires an EAR project. </p>
+<p>J2EE conventions may represent extra overhead if you only want to create
+a static, content-based Web application, which contains no dynamic files,
+such as JSP files or servlets. In this case, when you need only the most basic
+Web project, you might want to use the <em>static</em> Web project type (see <a href="ccstatic.html">Static Web projects</a>). Note that
+static Web projects can be converted to dynamic Web projects by selecting <strong>Convert
+to a Dynamic Web Project</strong>, from the Project menu.</p>
+<p>The J2EE model, and more specifically, the <cite>Sun Microsystems Java™ Servlet
+2.3 Specification</cite>, defines a Web application directory structure that
+specifies the location of Web content files, class files, class paths, deployment
+descriptors, and supporting metadata. The Web project hierarchy mirrors that
+of the Web application created from a project. In the workbench, you can use
+the <span>New Web Project</span> wizard to create a new Web project.</p>
+<div class="p">The main project folder contains all development objects related to a Web
+application. The Web content folder contains the elements of the project necessary
+to create a Web application. This folder structure maps to the Web application
+archive (WAR) structure defined by Sun Microsystems.. The following default
+elements are located in the Web project folder hierarchy: <div class="note"><span class="notetitle">Note:</span> In the Project
+Explorer view, Web projects are filtered into folder nodes to customize the
+display of Web resources for easy management during development. For information
+on the filtered structure, see <a href="ccwebvw.html">Project
+Explorer view</a>.</div>
+<dl><dt class="dlterm">Web Deployment Descriptor</dt>
+<dd>The standard Web application deployment descriptor (the <span class="filepath">web.xml</span> file).</dd>
+<dt class="dlterm">JavaSource</dt>
+<dd>Contains the project's Java source code for classes, beans, and
+servlets. When these resources are added to a Web project, they are automatically
+compiled and the generated files are added to the WEB-INF/classes directory.
+The contents of the source directory are not packaged in WAR files unless
+an option is specified when a WAR file is created. <div class="note"><span class="notetitle">Note:</span> Though the default
+name given to the folder is JavaSources, you can change the name through the
+Project Explorer view or through the Preferences page available by selecting <span class="menucascade"><b>Window</b> > <b>Preferences</b> > <b>Web
+Tools</b> > <b>New J2EE Project</b></span>.</div>
+</dd>
+<dt class="dlterm">imported_classes folder</dt>
+<dd>This folder may be created during a WAR import, and contains class files
+that do not have accompanying source. The <b>imported_classes</b> folder
+is a Java classes
+folder; Java classes folders can also be created using the Web
+project <b>Java Build Path</b> properties page.</dd>
+<dt class="dlterm">WebContent folder</dt>
+<dd>The mandatory location of all Web resources, including HTML, JSP, graphic
+files, and so on. If the files are not placed in this directory (or in a subdirectory
+structure under this directory), the files will not be available when the
+application is executed on a server. The Web content folder represents the
+contents of the WAR file that will be deployed to the server. Any files not
+under the Web content folder are considered development-time resources (for
+example, .java files, .sql files, and .mif files), and are not deployed when
+the project is unit tested or published. <div class="note"><span class="notetitle">Note:</span> Though the default name given
+to the folder is <span class="filepath">WebContent</span>, you can change the name
+ in the Project Explorer by right-clicking the folder and selecting <b>Rename</b> or
+from the Web page of the project's Properties dialog. In a dynamic Web project,
+changing the folder name will update the Java build output directory. You can change
+the preference for the default folder name to be applied when creating new
+Web projects by selecting <span class="menucascade"><b>Window</b> > <b>Preferences</b> > <b>Web Tools</b> > <b>New J2EE Project</b></span>.</div>
+</dd>
+<dt class="dlterm">META-INF</dt>
+<dd>This directory contains the <span class="filepath">MANIFEST.MF</span> file, which
+is used to map class paths for dependent JAR files that exist in other projects
+in the same Enterprise Application project. An entry in this file will update
+the run-time project class path and Java build settings to include the referenced
+JAR files.</dd>
+<dt class="dlterm">theme</dt>
+<dd>The suggested directory for cascading style sheets and other style-related
+objects.</dd>
+<dt class="dlterm">WEB-INF</dt>
+<dd>Based on the <cite>Sun Microsystems Java Servlet 2.3 Specification</cite>, this
+directory contains the supporting Web resources for a Web application, including
+the <span class="filepath">web.xml</span> file and the classes and lib directories.</dd>
+<dt class="dlterm">/classes</dt>
+<dd>This directory is for servlets, utility classes, and the Java compiler
+output directory. The classes in this directory are used by the application
+class loader to load the classes. Folders in this directory will map package
+and class names, as in: <samp class="codeph">/WEB-INF/classes/com/mycorp/servlets/MyServlet.class</samp>.<p>Do
+not place any .class files directly into this directory. The .class files
+are placed in this directory automatically when the Java compiler
+compiles Java source files that are in the <span class="filepath">Java Resources</span> directory.
+Any files placed directly in this directory will be deleted by the Java compiler
+when it runs.</p>
+</dd>
+<dt class="dlterm">/lib</dt>
+<dd>The supporting JAR files that your Web application references. Any classes
+in .jar files placed in this directory will be available for your Web application</dd>
+<dt class="dlterm">Libraries</dt>
+<dd>The supporting JAR files that your Web application references. This folder
+mirrors the content of the lib folder. In addition, Web Library Projects,
+which are "virtual" JAR files that do not physically reside in the Web project,
+but are associated with Java projects elsewhere in your workspace,
+are included in this folder. They are packaged with your project when you
+export the application's WAR file.</dd>
+</dl>
+ <div class="note"><span class="notetitle">Note:</span> A library entry on the Java build path will remain there unless
+the actual JAR file is deleted from the WEB-INF/lib folder. If you remove
+a library path entry but not the JAR file, the library entry will be re-added
+to the path automatically.</div>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwebresources.html">Web resources</a></div>
+<div><a href="cwwarovr.html">Web archive (WAR) files</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twcreprj.html">Creating a dynamic Web project</a></div>
+<div><a href="tjcrejsp.html">Creating JavaServer Pages (JSP) files</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.html
new file mode 100644
index 0000000..0810e9f
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.html
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Project Explorer view and Web development</title>
+</head>
+<body id="ccwebvw"><a name="ccwebvw"><!-- --></a>
+<h1 class="topictitle1">Project Explorer view and Web development</h1>
+<div><div class="section"><div class="p">The Project Explorer view provides the following notable features: <ul><li><img src="../images/nwin.gif" alt="For Windows"> You can drag and drop files from Windows<sup>®</sup> Explorer or the desktop into
+the Navigator view.</li>
+<li>View filtering is supported by selecting <span><b>Filters</b></span> from
+the Navigator view <span><b>Menu</b></span> button. Resources
+can be filtered by name, project type or working set. Files beginning with
+a period are filtered out by default.</li>
+<li>The status line shows the full path of the selected resource.</li>
+<li>Dragging a .java file from the Navigator view into a JSP file will insert
+a usebean tag, the same behavior that is exhibited when a .class file is dragged
+into a JSP file.</li>
+<li>Errors and warnings on resources (including Java™, HTML/JSP, and Links Builder errors
+and warnings) are indicated with a red error <img src="../images/nshowerr.gif" alt="Error icon"> or yellow warning <img src="../images/nwarning.gif" alt="Warning icon"> next to the resource with the error, as well as
+the parent containers up to the project. This applies for all project types,
+not only Web projects.</li>
+<li>Items available from the <span><b>New</b></span> cascading
+menu in the project pop-up menu are context sensitive. All menus will have <span><b>Project</b></span> and <span><b>Other</b></span> options.</li>
+<li>All projects are automatically grouped by type. <img src="../images/grptype.gif" alt="Group Project by Type Icon">. </li>
+</ul>
+</div>
+</div>
+<div class="section"><h4 class="sectiontitle">Organization of the Project Explorer view</h4><p>The Project
+Explorer view shows a custom view of a dynamic Web project. By default, dynamic
+web projects appear under a top-level category called Dynamic Web Projects.
+The following are some of the notable top-level objects that appear beneath
+the project node (based on default folder names).</p>
+<div class="p"><strong>Web content folder</strong> -
+This folder contains items to be published to the server. By default, this
+folder will be named <strong>WebContent</strong> for newly created static and dynamic
+Web projects. <div class="note"><span class="notetitle">Note:</span> You can change the name in the Web page of the project's
+Properties dialog. In a dynamic Web project, changing the folder name will
+update the Java build output directory. You can change the preference
+for the default folder name to be applied when creating new Web projects by
+selecting <span class="menucascade"><b>Window</b> > <b>Preferences</b> > <b>Web Tools</b> > <b>New J2EE Project</b></span>. </div>
+<ul><li><strong>META-INF</strong> - This directory contains the <span class="filepath">MANIFEST.MF</span> file,
+which is used to map class paths for dependent JAR files that exist in other
+projects in the same Enterprise Application project. An entry in this file
+will update the run-time project class path and Java build settings to include the referenced
+JAR files.</li>
+</ul>
+<ul><li><strong>WEB-INF</strong> - The directory where supporting Web resources for a Web
+application are kept (for example: .xmi files, .xml files, and web.xml.) Note
+that double-clicking on the web.xml file has the same effect as double-clicking
+on the Deployment Descriptor: it opens the Web Deployment Descriptor editor.</li>
+</ul>
+ </div>
+ </div>
+</div>
+<div></div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.html
new file mode 100644
index 0000000..f9a9711
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Web application overview</title>
+</head>
+<body id="ccwtover"><a name="ccwtover"><!-- --></a>
+<h1 class="topictitle1">Web application overview</h1>
+<div><p>The Web development environment provides the tools you need to develop
+Web applications as defined in the <cite>Sun Microsystems Java™ Servlet
+2.3 Specification</cite> and the <cite>Sun Microsystems JSP 1.2 Specification</cite>.
+Web applications can be simple (consisting of only static Web pages) or they
+can be more advanced and include JavaServer Pages (JSP) files and Java servlets.
+These resources, along with an XML deployment descriptor (and other <a href="cwebresources.html"> Web resources</a>, are contained
+within a Web project during development. When you are ready to publish the
+Web application to the Web, you deploy the Web project to the server in the
+form of a Web archive (WAR) file . The end user can then view the Web application
+as a Web site from a URL.</p>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwtfeatures.html" title="The integrated Web development environment makes it easy to cooperatively create, assemble, publish, deploy and maintain dynamic, interactive Web applications.">Web tools features</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twcreprj.html">Creating a dynamic Web project</a></div>
+<div><a href="tjdetags.html">Creating and editing Web pages - overview</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.html
new file mode 100644
index 0000000..e14e150
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>JavaServer Pages (JSP) technology</title>
+</head>
+<body id="cpdjsps"><a name="cpdjsps"><!-- --></a>
+<h1 class="topictitle1">JavaServer Pages (JSP) technology</h1>
+<div><p>The JavaServer Pages technology enables you to generate dynamic web content,
+such as HTML, DHTML, XHTML, and XML files, to include in a Web application.
+JSP files are one way to implement server-side dynamic page content. JSP files
+allow a Web server, such as WebSphere<sup>®</sup> Application Server or Apache Tomcat,
+to add content dynamically to your HTML pages before they are sent to a requesting
+browser.</p>
+<p>When you deploy a JSP file to a Web server that provides a servlet engine,
+it is preprocessed into a servlet that runs on the Web server. This is in
+contrast with client-side JavaScript™ (within <samp class="codeph"><SCRIPT></samp> tags),
+which is run in a browser. A JSP page is ideal for tasks that are better suited
+to execution on the server, such as accessing databases or calling Enterprise Java™ beans.</p>
+<p>You can create and edit a JSP file in the HTML editor by adding your own
+text and images using HTML, JSP tagging, or JavaScript, including Java source
+code inside of scriptlet tags. Typically, JSP files have the file extension
+.jsp. Additionally, the JSP specification suggests that JSP fragment files
+should have file extension .jspf. If this convention is not followed, the
+JSP validator will treat JSP fragments as regular standalone JSP files, and
+compilation errors might be reported.</p>
+<p>The <cite>Sun Microsystems JSP 1.2 Specification</cite> provides the ability
+to create custom JSP tags. Custom tags simplify complex actions and provide
+developers with greater control over page content. Custom tags are collected
+into a library (taglib). A tag library descriptor file (taglib.tld) is an
+XML document that provides information about the tag library, including the
+taglib short name, library description, and tag descriptions. Refer to the <cite>Sun
+Microsystems JSP 1.2 Specification</cite> for more details.</p>
+<p>To use JSP 1.2 custom taglibs, you can import the tag library .tld and
+.jar files into your project to use them, or associate them as Web Library
+projects. You can also reference a TLD file by using a URI.</p>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwservbn.html">Servlets</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="tjcrejsp.html">Creating JavaServer Pages (JSP) files</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.html
new file mode 100644
index 0000000..8ef59db
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Web page design</title>
+</head>
+<body id="cwebpagedesign"><a name="cwebpagedesign"><!-- --></a>
+<h1 class="topictitle1">Web page design</h1>
+<div><p>Web pages are an integral part of every Web application. Each Web page
+should serve to help achieve the overall goal of the entire Web site.</p>
+<p> There are many types of Web pages, ranging from simple HTML pages that
+contain no dynamic elements, to advanced Java-based pages that make use of
+servlets, scripts, forms, or data access components.</p>
+<p>A few of the many items you should consider when designing your pages are
+markup language, links, images, and style sheets.</p>
+</div>
+<div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="tjdetags.html">Creating and editing Web pages - overview</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.html
new file mode 100644
index 0000000..56cf180
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.html
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Web projects</title>
+</head>
+<body id="cwebprojects"><a name="cwebprojects"><!-- --></a>
+<h1 class="topictitle1">Web projects</h1>
+<div><p>Web projects hold all of the Web resources that are created and used when
+developing your Web application. The first step to creating or importing a
+Web application is to create either a static or a dynamic Web project. Static
+Web projects are meant to contain only simple Web site resources, such as
+HTML files. Dynamic Web projects are used to structure Web applications that
+will use more complicated, dynamic Web technologies, such as JavaServer Pages
+files, and possibly data access resources.</p>
+<p>Though the Web project is structured on your file system in compliance
+with the J2EE Web application standard for deployment purposes, the Project
+Explorer view is designed to show the most convenient display of project resources
+for use while you are actually developing the Web application. When you are
+finished developing your Web application, you use the Web project to deploy
+the correct resources to the server. These resources will be packaged in a
+file called a Web archive, or WAR file.</p>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="ccstatic.html">Static Web projects</a></div>
+<div><a href="ccwebprj.html">Dynamic Web projects and applications</a></div>
+<div><a href="cwwarovr.html">Web archive (WAR) files</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twcresta.html">Creating a static Web project</a></div>
+<div><a href="twcreprj.html">Creating a dynamic Web project</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.html
new file mode 100644
index 0000000..f7ed6b8
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Web resources</title>
+</head>
+<body id="cwebresources"><a name="cwebresources"><!-- --></a>
+<h1 class="topictitle1">Web resources</h1>
+<div><p>In most cases, all of the resources that you need to create for your Web
+application are developed during Web site or Web page design; however, there
+are additional resources that you may need to include in your Web project
+if you are using more advanced Web technologies in your application.</p>
+<p>These Web resources are not typical Web page files, and are often not the
+resources that you consider part of the final Web site. For example, tag libraries
+and Java™ resources,
+such as JAR files, are resources you might need to include in your Web project. </p>
+<p>In fact, even the WAR file itself could be considered a Web resource, if
+you consider importing or exporting the resource.</p>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwwarovr.html">Web archive (WAR) files</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.html
new file mode 100644
index 0000000..1e4c23b
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Servlets</title>
+</head>
+<body id="cwservbn"><a name="cwservbn"><!-- --></a>
+<h1 class="topictitle1">Servlets</h1>
+<div><p>Servlets are server-side Java™ programs that use the <cite>Sun Microsystems Java Servlet
+API</cite> and its associated classes and methods, as defined in the <cite>Sun
+Microsystems Java Servlet 2.3 Specification</cite>. These Java programs
+extend the functionality of a Web server by generating dynamic content and
+responding to Web client requests. When a browser sends a request to the server,
+the server can send the request information to a servlet, so that the servlet
+can construct the response that is sent back to the browser.</p>
+<p>Just as applets run on a Web browser and extend the browser's capabilities,
+servlets run on a Java-enabled Web server, such as the WebSphere<sup>®</sup> Application Server and extend
+the server's capabilities. Because of their flexibility and scalability, servlets
+are commonly used to enable businesses to connect databases to the Web.</p>
+<div class="p">Although a servlet can be a completely self-contained program, you can
+split application development into two portions: <ul><li>The business logic (content generation), which governs the relationship
+between input, processing, and output</li>
+<li>The presentation logic (content presentation, or graphic design rules),
+which determines how information is presented to the user</li>
+</ul>
+Using this paradigm, you may choose to have business logic handled by Java beans,
+the presentation logic handled by JavaServer Pages (JSP) or HTML files, and
+the HTTP protocol handled by a servlet. <div class="note"><span class="notetitle">Note:</span> JSP files can be used to manage
+both the presentation and business logic for a Web application. JSP files
+use structured markup for presentation, and supply servlet model behavior
+at run time.</div>
+</div>
+<p>You can develop, debug, and deploy servlets, set breakpoints within servlet
+objects, and step through code to make changes that are dynamically folded
+into the running servlet on a running server, without having to restart each
+time.</p>
+<p>For more information about servlets, refer to the <cite>Sun Microsystems Java Servlet
+2.3 Specification</cite> at <samp class="codeph">java.sun.com/products/servlet/download.html</samp>.</p>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="ccwtover.html">Web application overview</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twsrvwiz.html">Creating servlets</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.html
new file mode 100644
index 0000000..4aa0ae1
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.html
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Web tools features</title>
+</head>
+<body id="cwtfeatures"><a name="cwtfeatures"><!-- --></a>
+<h1 class="topictitle1">Web tools features</h1>
+<div><p> The integrated Web development environment makes it easy to cooperatively
+create, assemble, publish, deploy and maintain dynamic, interactive Web applications.</p>
+<div class="p">The Web development environment provides the following high-level capabilities:
+ <ul><li>Dynamic Web project creation, using the J2EE-defined hierarchy, or a static
+version that reduces project overhead when dynamic elements are not required.
+ Static Web projects can later be converted to dynamic Web projects.<p></p>
+</li>
+<li>Creation and editing of a Web application deployment descriptor (<span class="filepath">web.xml</span>)
+ file<p></p>
+</li>
+<li>JSP and HTML file creation, validation, editing, and debugging<p></p>
+</li>
+<li>An extensible view, called the Snippets view, which allows users to catalog
+ and organize reusable programming objects, such as HTML, JavaScript™,
+ and JSP markup, along with files and custom tags, that can be embedded in
+ existing files<p></p>
+</li>
+<li>Dynamic tag help (content assist) , which displays tag usage and attribute
+information for HTML, JSP, and JavaScript tags based on cursor location
+ in the Source page. (You invoke Content Assist by pressing (Ctrl+Spacebar)
+)<p></p>
+</li>
+<li>Cascading style sheet (CSS) editing support<p></p>
+</li>
+<li>HTTP/FTP import<p></p>
+</li>
+<li>FTP export (simple resource copy) to a server<p></p>
+</li>
+<li>WAR file import, export, and validation<p></p>
+</li>
+<li>Servlet creation, which employs the Servlet Wizard to create new servlets.<p></p>
+</li>
+</ul>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="ccwebprj.html">Dynamic Web projects and applications</a></div>
+<div><a href="cwebpagedesign.html">Web page design</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twcreprj.html">Creating a dynamic Web project</a></div>
+<div><a href="tjcrejsp.html">Creating JavaServer Pages (JSP) files</a></div>
+<div><a href="twsrvwiz.html">Creating servlets</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.html
new file mode 100644
index 0000000..abfebbe
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Web archive (WAR) files</title>
+</head>
+<body id="cwwarovr"><a name="cwwarovr"><!-- --></a>
+<h1 class="topictitle1">Web archive (WAR) files</h1>
+<div><p> A Web application is a group of HTML pages, JSP pages, servlets, resources
+and source file, which can be managed as a single unit. A Web archive (WAR)
+file is a packaged Web application. WAR files can be used to import a Web
+application into a Web server.</p>
+<p>In addition to project resources, the WAR file includes a Web deployment
+descriptor file. The Web deployment descriptor is an XML file that contains
+deployment information, MIME types, session configuration details, and other
+settings for a Web application. The Web deployment descriptor file (<span class="filepath">web.xml</span>)
+provides information about the WAR file is shared with the developers, assemblers,
+and deployers in a J2EE environment.</p>
+<div class="p">The Web development environment provides facilities for importing and exporting
+WAR files, using the following wizards: <ul><li><span>Import Resources from a WAR File</span>, which requires that you to
+specify a Web project. You can use existing projects or create them as you
+use the wizard.</li>
+<li><span>Export Resources to a WAR File</span>, which requires only an export
+location and some optional settings</li>
+</ul>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwebresources.html">Web resources</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twimpwar.html">Importing Web archive (WAR) files</a></div>
+<div><a href="twcrewar.html">Exporting Web Archive (WAR) files</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.html
new file mode 100644
index 0000000..2d89446
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.html
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Workbench integration with Web editors</title>
+</head>
+<body id="cwwedtvw"><a name="cwwedtvw"><!-- --></a>
+<h1 class="topictitle1">Workbench integration with Web editors</h1>
+<div><p>There are several editors for use in various contexts for various file
+types. To edit a file using its default editor, double-click on the file name
+in the Project Explorer view, or right-click on the file and select <b>Open</b>.
+The editor that is last used to open a file becomes the default for that particular
+file. To edit the file with a different editor, right-click on the file and
+select <b>Open With</b> to choose from a list of available
+editors.</p>
+<p>In the workbench, you can associate file-name extensions for different
+types of resources with various editors. A resource extension can have more
+than one editor associated with it; the last editor used for a particular
+extension type is indicated by a black dot before it in the <b>Open
+With</b> pop-up menu. You can associate extensions that are known
+to the workbench with additional editors, by using the <strong>File Associations</strong> preferences
+page, accessed by selecting <span class="menucascade"><b>Window</b> > <b>Preferences</b> > <b>Workbench</b> > <b>File Associations</b></span>.</p>
+<div class="p">The Properties view provides general capabilities that are advantageous
+to Web editor users. <dl><dt class="dlterm">Properties view</dt>
+<dd>The Properties view (<span class="menucascade"><b>Window</b> > <b>Show
+View</b> > <b>Properties</b></span>) contains
+a list of attributes and editable attribute values. For example, when you
+select an image tag <b>img</b> , the width and height values
+appear for editing. In addition, any other attributes allowed by the standard
+specified in the DOCTYPE for the file (such as the HTML 4.0.1 DTD) are listed.
+When you click the value column of a property, you can select from among the
+list of available attribute values. <p>The pop-up menu in the Properties view
+enables you to undo, cut, copy, paste, delete, and select all. The options
+that are available at a given time depends on where the cursor is located
+when you right-click to display the pop-up menu. To see the pop-up menu that
+contains undo, cut, and so on, the property value field must be active. (This
+is accomplished by selecting the property and then selecting its value.) Otherwise,
+the pop-up menu will contain different options.</p>
+ <p>Use the <b>Restore
+Default Value</b> button to change any value back to the default setting.</p>
+ <p>After
+you are in the Properties view, you can modify other property values for specific
+tags. To edit another tag using the Properties view, move the cursor within
+the editing area of the Source page or Design page to the tag you want to
+edit. The appropriate properties and values are displayed in the Properties
+view.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.html
new file mode 100644
index 0000000..00a974d
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Specifying an implicit document type for an HTML, XHTML, or JSP fragment</title>
+</head>
+<body id="tjchgxdt"><a name="tjchgxdt"><!-- --></a>
+<h1 class="topictitle1">Specifying an implicit document type for an HTML, XHTML, or JSP fragment</h1>
+<div><div class="section"> <p>An <em>implicit</em> document type is used for content assist (CTRL+Spacebar),
+the Properties view, and other editing contexts when no DOCTYPE declaration
+is specified in an HTML, XHTML, or JSP file. Typically, this feature is used
+for a fragment (partial document) that can be included in other pages using
+JSP include or server-side include.</p>
+<p>To assign an implicit document type
+to an HTML, XHTML, or JSP fragment, do the following: </p>
+ </div>
+<ol><li class="stepexpand"><span>From the Project Explorer view, select the HTML, XHTML, or JSP
+fragment.</span></li>
+<li class="stepexpand"><span>Select <span><b>Properties</b></span> from the file's
+pop-up menu.</span></li>
+<li class="stepexpand"><span>In the <b>Web Content Settings</b> page, select
+the desired DOCTYPE from the <span><b>Document type</b></span> drop-down
+list.</span> <p>The <span><b>Properties</b></span> dialog
+for Web projects also includes an <span><b>Web Content Settings</b></span> page,
+where you can specify project-default HTML document type. This setting will
+be used if no DOCTYPE declaration is specified in the file, and no default
+document type is specified in the <span><b>Web Content Settings</b></span> page
+on the <span><b>Properties</b></span> dialog for the file.</p>
+</li>
+</ol>
+</div>
+<div></div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.html
new file mode 100644
index 0000000..b57d3bd
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Creating HTML and XHTML files and framesets</title>
+</head>
+<body id="tjcrehtm"><a name="tjcrehtm"><!-- --></a>
+<h1 class="topictitle1">Creating HTML and XHTML files and framesets</h1>
+<div><p>You can use the New HTML File wizard to create HTML and XHTML files
+and framesets. </p>
+<div class="section"> </div>
+<ol><li class="stepexpand"><span>Create a static or a dynamic Web project if you have not already
+done so.</span></li>
+<li class="stepexpand"><span>In the Project Explorer, expand your project and right click on
+your WebContent folder or on a subfolder under WebContent. </span> Note
+that if you choose any other folder in which to create the HTML file, then
+it will not be included in the WAR file that is deployed to the server. In
+addition, link validation will not encompass files that are not under the
+WebContent folder.</li>
+<li class="stepexpand"><span>From the context menu, select <span class="menucascade"><b>New</b> > <b>Other</b> > <b>Web</b> > <b>HTML</b></span>.</span> The New HTML Page window appears with your
+folder selected</li>
+<li class="stepexpand"><span>Type a file name into the File name field, making sure you include
+an html extension (html, htm, xhtml, htpl, wml, shtml, or shtm) in the file
+name.</span></li>
+<li class="stepexpand"><span> You have several options for proceeding:</span><ul><li>To accept the defaults associated with a new HTML file, select <b>Finish.</b></li>
+<li> To use a template file for the initial content of your HTML page,
+select <b>Next</b>. The Select HTML Template window appears.
+Select the <b>Use HTML Template</b> check box, and then select
+one of the sample templates. You can also select the <b>HTML Templates</b> link
+to add or remove HTML templates to your list of templates.</li>
+</ul>
+</li>
+</ol>
+</div>
+<div></div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.html
new file mode 100644
index 0000000..1dff5d3
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Creating JavaServer Pages (JSP) files</title>
+</head>
+<body id="tjcrejsp"><a name="tjcrejsp"><!-- --></a>
+<h1 class="topictitle1">Creating JavaServer Pages (JSP) files</h1>
+<div><div class="section"><p>Most types of JSP files can be created using the New JSP File
+wizard. To create a basic JSP file using the wizard, complete the following
+steps: </p>
+</div>
+<ol><li class="stepexpand"><span>Create a dynamic Web project if you have not already done so.</span></li>
+<li class="stepexpand"><span>In the Project Explorer, expand your project and right click on
+your WebContent folder or on a subfolder under WebContent. Note that if you
+choose any other folder in which to create the JSP, then it will not be included
+in the WAR file that is deployed to the server. In addition, link validation
+will not encompass files that are not under the WebContent folder.</span></li>
+<li class="stepexpand"><span>From the context menu, select <span class="menucascade"><b>New</b> > <b>JSP</b></span>.</span> The New Java Server
+Page window appears with your folder selected</li>
+<li class="stepexpand"><span>Type a file name into the File name field, making sure you include
+the jsp extension (jsp, jsv, jtpl, or jspx) in the file name.</span></li>
+<li class="stepexpand"><span> You have several options for proceeding:</span><ul><li>To accept the defaults associated with a new JSP file, select <b>Finish.</b></li>
+<li>To link to a file in the file system and specify path variables, select <b>Advanced</b> and
+then make your selections using the <b>Browse</b> and <b>Variables</b> buttons. </li>
+<li> To use a template file for the initial content of your JSP page,
+select <b>Next</b>. The Select JSP Template window appears.
+Select the <b>Use JSP Template</b> check box, and then select
+one of the sample templates. You can also select the <b>JSP Templates</b> link
+to add or remove JSP templates to your list of templates.</li>
+</ul>
+</li>
+</ol>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cpdjsps.html">JavaServer Pages (JSP) technology</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twcreprj.html" title="You create and maintain the resources for your Web applications in Web projects.">Creating a dynamic Web project</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.html
new file mode 100644
index 0000000..d712412
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Creating and editing Web pages - overview</title>
+</head>
+<body id="tjdetags"><a name="tjdetags"><!-- --></a>
+<h1 class="topictitle1">Creating and editing Web pages - overview</h1>
+<div><div class="section"> <p>To aid in Web site development and editing, there is local tag
+hover help for all supported tag sets, as well as <a href="../../org.eclipse.sse.doc.user/topics/tsrcedt005.html">content assist</a> (Ctrl+Spacebar), a tool that helps you
+insert or finish a tag or function or finish a line of code in a structured
+text editor.</p>
+<p><img src="../images/nwin.gif" alt="For Windows"> You can toggle among three modes to visually design pages, work with
+HTML, JavaScript™ or
+JSP content, and preview your pages. To help you create the visual impact
+you want on your Web sites, the editor includes its own library of reusable
+graphics and two graphic programs for creating, editing, and animating image
+files. </p>
+<p><img src="../images/nlinux.gif" alt="For Linux"> You can toggle between two modes to visually design pages or work
+with HTML, JavaScript or JSP content. To help you create
+the visual impact you want on your Web sites, the editor includes its own
+library of reusable graphics and a graphic program for creating, editing,
+and animating image files.</p>
+<div class="note"><span class="notetitle">Note:</span> Use either uppercase or lowercase alphanumeric
+characters consistently when naming HTML files and embedded files (such as
+image files) used in your Web pages, because some server operating systems
+are case sensitive. Do not use spaces or special characters such as exclamation
+points or question marks in file names.</div>
+ </div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="ccwtover.html">Web application overview</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.html
new file mode 100644
index 0000000..e3ff8fd
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head><!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Defining HTML file preferences</title>
+</head>
+<body id="tjprefs"><a name="tjprefs"><!-- --></a>
+<h1 class="topictitle1">Defining HTML file preferences</h1>
+<div><div class="section"> <p>To define general HTML file preferences, complete the following
+steps::</p>
+</div>
+<ol><li class="stepexpand"><span>From the <b>Window</b> menu, select <b>Preferences</b>.</span></li>
+<li class="stepexpand"><span>In the Preferences window, select <span class="menucascade"><b>Web and
+XML</b> > <b>HTML Files</b></span>.</span></li>
+<li class="stepexpand"><span>Specify the following settings related to saving an HTML source
+page. The defaults are recommended and should only be modified when there
+is a specific reason to do so. </span> <dl><dt class="dlterm">Line delimiter</dt>
+<dd>Specify the appropriate EOL character for your environment. The default
+is <b>No translation</b>.</dd>
+<dt class="dlterm">Add this suffix</dt>
+<dd>Specify a default suffix for files that you save. The default is <kbd class="userinput">html</kbd>.</dd>
+<dt class="dlterm">Encoding, IANA, (Use workbench default)</dt>
+<dd>Specify the default encoding (code page) for files that you create. The
+default is the Workbench's encoding preference. </dd>
+<dt class="dlterm">Insert DOCTYPE declaration</dt>
+<dd>Optionally, you can automatically add a DOCTYPE declaration to HTML files.
+The default DOCTYPE is determined when you create an HTML file or a JSP file
+using a wizard. If you add the DOCTYPE declaration, you should include at
+least a Public ID specification, and, optionally, a System ID.</dd>
+<dt class="dlterm">Insert GENERATOR with META tag</dt>
+<dd>Optionally, select the check box to specify GENERATOR in a META tag in
+the HTML file header.</dd>
+<dt class="dlterm">Loading files</dt>
+<dd>Specify the default encoding (code page) for files that you open. The
+default is the Workbench's encoding preference. Deselect the <b>Use
+workbench default</b> check box to select another encoding. <div class="note"><span class="notetitle">Note:</span> Encoding
+detection (when loading files) is performed in the following order: <ul><li>Locate the encoding name embedded in the document.</li>
+<li>When no encoding is embedded in the document, an automatic encoding detector
+attempts to determine encoding used in the document.</li>
+<li>If the encoding still cannot be determined, the encoding defined in the <b>Encoding</b> field
+is used.</li>
+</ul>
+ </div>
+ </dd>
+</dl>
+ </li>
+<li class="stepexpand"><span>Click <b>Apply</b> then <b>OK</b> to
+save your changes.</span></li>
+</ol>
+</div>
+<div></div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.html
new file mode 100644
index 0000000..9a82c90
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Server targeting for Web applications</title>
+</head>
+<body id="tservertarget"><a name="tservertarget"><!-- --></a>
+<h1 class="topictitle1">Server targeting for Web applications</h1>
+<div><p>To support different J2EE application servers, the J2EE tooling allows
+you to target a specific server during your Enterprise Application (EAR) project
+development. In most cases, a Web project must target the same server as the
+EAR project in order to deploy the Web application to the server properly. </p>
+<p>After you have a Web project created, you can modify the target server
+using the project's properties dialog. To do this, right-click on the project
+in the Project Explorer view, and select <span class="menucascade"><b>Properties</b> > <b>Server</b></span>.</p>
+</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="twcreprj.html" title="You create and maintain the resources for your Web applications in Web projects.">Creating a dynamic Web project</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.html
new file mode 100644
index 0000000..cf86543
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Creating cascading style sheets</title>
+</head>
+<body id="tstylesheet"><a name="tstylesheet"><!-- --></a>
+<h1 class="topictitle1">Creating cascading style sheets</h1>
+<div><p>Cascading style sheets enable you to define a consistent look and
+feel throughout your Web site by maintaining the contents (Web pages) and
+the design (the style sheet) separately.</p>
+<div class="section">To create a new cascading style sheet:</div>
+<ol><li class="stepexpand"><span>Create a static or a dynamic Web project if you have not already
+done so.</span></li>
+<li class="stepexpand"><span>In the Project Explorer, expand your project and right click on
+your WebContent folder or on a subfolder under WebContent. </span> Note
+that if you choose any other folder in which to create the CSS file, then
+it will not be included in the WAR file that is deployed to the server. </li>
+<li class="stepexpand"><span>From the context menu, select <span class="menucascade"><b>New</b> > <b>Other</b> > <b>Web</b> > <b>CSS</b></span>.</span> The New Cascading Style Sheet window appears
+with your folder selected</li>
+<li class="stepexpand"><span>Type a file name into the File name field, making sure you include
+a css extension in the file name.</span></li>
+<li class="stepexpand"><span> You have several options for proceeding:</span><ul><li>To accept the defaults associated with a new CSS file, select <b>Finish.</b></li>
+<li> To use a template file for the initial content of your CSS file,
+select <b>Next</b>. The Select CSS Template window appears.
+Select the <b>Use CSS Template</b> check box, and then select
+one of the sample templates. You can also select the <b>CSS Templates</b> link
+to add or remove HTML templates to your list of templates.</li>
+</ul>
+</li>
+</ol>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.html
new file mode 100644
index 0000000..4eab70a
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Creating a dynamic Web project</title>
+</head>
+<body id="twcreprj"><a name="twcreprj"><!-- --></a>
+<h1 class="topictitle1">Creating a dynamic Web project</h1>
+<div><p>You create and maintain the resources for your Web applications
+in Web projects.</p>
+<div class="section"> <p> Unlike with <a href="twcresta.html">static</a> Web
+projects, dynamic Web projects enable you to create resources such as JavaServer
+Pages and servlets.</p>
+<p>To create a new dynamic Web project, complete the
+following steps:</p>
+</div>
+<ol><li><span>Open the J2EE perspective.</span></li>
+<li><span>In the Project Explorer, right click on Dynamic Web Projects, and
+select <span class="menucascade"><b>New</b> > <b>Dynamic Web Project</b></span> from the context menu. The New Dynamic Web Project wizard starts.</span></li>
+<li><span>Follow the project wizard prompts.</span></li>
+</ol>
+<div class="section"><p><strong>General Information</strong></p>
+<dl><dt class="dlterm">Project Facets </dt>
+<dd>A facet represents a unit of functionality in a Web project. For example,
+the Dynamic Web Module facet enables the project to be deployed as a dynamic
+Web module. A brief description of a project facet appears in the wizard
+when you select it. Note that in many instances, you can view the constraints
+for a project facet by right clicking on the facet and selecting project constraints
+from the pop up menu. </dd>
+<dt class="dlterm">Target Runtime</dt>
+<dd>Use this field to define a new installed runtime environment. Runtimes
+are used at build time to compile projects.</dd>
+<dt class="dlterm">Enterprise Application project (EAR Project)</dt>
+<dd>A new or existing Enterprise Application project (EAR Project) must be
+associated with your new Web project to facilitate deployment. If you want
+to override the default settings for the Enterprise Application project, you
+can do so using the wizard. When your Web project is created at the end of
+the wizard, the new Enterprise Application project is also created with the
+name specified in the EAR project field. Note that the default is the name
+of the web project appended with EAR (unless the ear project was selected
+when you opened the wizard.)</dd>
+<dt class="dlterm">Context Root</dt>
+<dd>The context root is the Web application root, which is the top-level directory
+of your application when it is deployed to the Web server. You can change
+the context root after you create a project using the project Properties dialog,
+which you access from the project's pop-up menu. The context root can also
+be used by the links builder to ensure that your links remain ready to publish
+as you move and rename files inside your project.</dd>
+</dl>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="ccstatic.html">Static Web projects</a></div>
+<div><a href="ccwebprj.html">Dynamic Web projects and applications</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br>
+<div><a href="tjcrejsp.html">Creating JavaServer Pages (JSP) files</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.html
new file mode 100644
index 0000000..4300bf6
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Creating a static Web project</title>
+</head>
+<body id="twcresta"><a name="twcresta"><!-- --></a>
+<h1 class="topictitle1">Creating a static Web project</h1>
+<div><p></p>
+<div class="section"><p> In the workbench, you create and maintain resources for Web applications
+in Web projects. If you want to create a static, content-based Web application
+that contains no dynamic elements, such as JSP files or servlets, use the <span><b>New
+Static Web Project</b></span> wizard. </p>
+<p>To create a new static
+Web project, complete the following steps:</p>
+</div>
+<ol><li class="stepexpand"><span>Open the J2EE perspective </span> </li>
+<li class="stepexpand"><span>In the Project Explorer, right click on Other Projects and select <strong>New->Other->Web->Static
+Web Project</strong> from the context menu. The New Static Web Project wizard starts. </span></li>
+<li class="stepexpand"><span>Follow the project wizard prompts</span> </li>
+</ol>
+<div class="section"><p><strong>General Information</strong></p>
+<dl><dt class="dlterm">Project Facets </dt>
+<dd>A facet represents a unit of functionality in a Web project. For example,
+the Static Web Module facet enables the project to be deployed as a static
+Web module. A brief description of a project facet appears in the wizard
+when you select it. Note that in many instances, you can view the constraints
+for a project facet by right clicking on the facet and selecting project constraints
+from the pop up menu. </dd>
+<dt class="dlterm">Target Runtime</dt>
+<dd>Use this field to define a new installed runtime environment. Runtimes
+are used at build time to compile projects. </dd>
+</dl>
+<dl><dt class="dlterm">Web Content Folder</dt>
+<dd>The folder in which you want to store your publishable resources. </dd>
+</dl>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="ccstatic.html">Static Web projects</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.html
new file mode 100644
index 0000000..2a9ac28
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.html
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Exporting Web Archive (WAR) files</title>
+</head>
+<body id="twcrewar"><a name="twcrewar"><!-- --></a>
+<h1 class="topictitle1">Exporting Web Archive (WAR) files</h1>
+<div><div class="section"> <p> A Web archive (WAR) file is a packaged Web application that
+can be exported to test, publish, and deploy the resources developed within
+a Web project.</p>
+<p>To export a WAR file from a Web project, do the following: </p>
+</div>
+<ol><li class="stepexpand"><span>Right click on a Web project folder and select <strong>Export</strong> from
+the pop-up menu. Then select<strong> WAR file</strong> in the Export window and then
+select <strong>Next</strong>.</span></li>
+<li class="stepexpand"><span>Specify the Web project you want to export (this field is primed
+if you used the pop-up menu to open the wizard), and specify a location for
+the new WAR file</span></li>
+<li class="stepexpand"><strong>Optional: </strong><span>Optionally, supply WAR export <span>Options</span>,
+such as whether or not to include Java™ source files in the WAR, and whether
+to overwrite any existing resources during the export process. </span> Source
+files are not usually included in a WAR file, because they are not necessary
+for the server to run the web application.</li>
+<li class="stepexpand"><span>Click <span><b>Finish</b></span>.</span></li>
+</ol>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwwarovr.html">Web archive (WAR) files</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.html
new file mode 100644
index 0000000..8718c26
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Setting CVS repository defaults</title>
+</head>
+<body id="twcvsr"><a name="twcvsr"><!-- --></a>
+<h1 class="topictitle1">Setting CVS repository defaults</h1>
+<div><div class="section"> <p>When you use a CVS repository during team development, you might
+want to use the following setup to ensure that the CVS versioning support
+ignores the project's build output folder:</p>
+ </div>
+<ol><li class="stepexpand"><span>Create a file called .cvsignore in your project's <span class="filepath">WebContent/WEB-INF</span> folder.</span></li>
+<li class="stepexpand"><span>In this file, add a line with the name of the build output folder
+(for example, <samp class="codeph">classes</samp>).</span> <p>Currently, you have
+the option of creating this file automatically (as a feature) when using the
+New Dynamic Web Project wizard.</p>
+<p>When you synchronize with a CVS team
+stream, the output folder will be ignored.</p>
+</li>
+<li class="stepexpand"><span>In addition, you should turn off the <span><b>Prune empty
+directories</b></span> option. Select <span><span class="menucascade"><b>Windows</b> > <b>Preferences</b></span></span>, switch to the <span><span class="menucascade"><b>Team</b> > <b>CVS</b></span></span> properties
+page, and ensure that the <span><b>Prune empty directories</b></span> check
+box is not checked.</span> <p>If this option is enabled and your Web project's
+source directory is empty, it will be deleted when the project is added to
+your workspace from a CVS repository, causing a Java™ build error.</p>
+</li>
+</ol>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.html
new file mode 100644
index 0000000..a344764
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Importing Web archive (WAR) files</title>
+</head>
+<body id="twimpwar"><a name="twimpwar"><!-- --></a>
+<h1 class="topictitle1">Importing Web archive (WAR) files</h1>
+<div><div class="section"> <p>A Web Archive (WAR) file is a portable, packaged Web application
+that you can import into your workspace. </p>
+<p> Before importing a WAR file,
+you should first determine if the WAR file contains needed Java™ source
+files. When importing a WAR file into an existing Web project, the imported
+Web deployment descriptor files are either not changed or overwritten by the
+ones included in the imported WAR file, based on your response to the prompt
+that is provided. In either case, this action does <em>not</em> represent a
+merging of the two sets of deployment descriptors. </p>
+ <p>To import the
+Web project resources in a WAR file into your workspace, complete the following
+steps:</p>
+</div>
+<ol><li class="stepexpand"><span>Select <span><span class="menucascade"><b>File</b> > <b>Import</b></span></span>.</span></li>
+<li class="stepexpand"><span> In the Import dialog, select <span><b>WAR file</b></span> and
+then click <span><b>Next</b></span>. </span></li>
+<li class="stepexpand"><span>Locate the WAR file that you want to import using the <span><b>Browse</b></span> button.</span></li>
+<li class="stepexpand"><span> The wizard assumes you want to create a new Web project with the
+same name as the WAR file. If you accept this choice, the project will be
+created with the same servlet version as specified by the WAR file and in
+the same location. If you want to override these settings, you can click <strong>New</strong> and
+specify your new settings in the Dynamic Web Project wizard.</span> <p>If
+you want to import the WAR file into an existing Web project, you can select
+the project from the Web project drop-down list. Note that if you select an
+existing project, you must decide whether you want to select the setting to <strong>overwrite
+existing resources without warning</strong></p>
+</li>
+<li class="stepexpand"><span>Click <span><b>Finish</b></span> to populate the Web
+project.</span></li>
+</ol>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwwarovr.html">Web archive (WAR) files</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.html
new file mode 100644
index 0000000..04715d0
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Converting static Web projects to dynamic Web projects</title>
+</head>
+<body id="twpcnvrt"><a name="twpcnvrt"><!-- --></a>
+<h1 class="topictitle1">Converting static Web projects to dynamic Web projects</h1>
+<div><div class="section"> <p> If you want to add dynamic elements to a static web project,
+such as Java™ servlets and JSP files, you must convert the project
+from a static to a dynamic one. To convert a static Web project to a dynamic
+Web project, complete the following steps:</p>
+ </div>
+<ol><li class="stepexpand"><span>Select the project in the Project Explorer view, and then select <span><b>Convert
+to a Dynamic Web Project</b></span> from the <strong>Project</strong> menu.</span> This conversion assumes the project name and location will be the same.
+The conversion does not change the CSS file specified in the original static
+project, so it will be included in the resulting dynamic Web project. </li>
+<li class="stepexpand"><span> Specify the project properties that are available when <a href="twcreprj.html">Creating a Dynamic Web project.</a></span></li>
+</ol>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="ccstatic.html">Static Web projects</a></div>
+<div><a href="ccwebprj.html">Dynamic Web projects and applications</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.html
new file mode 100644
index 0000000..8dbdebd
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Adding Web library projects</title>
+</head>
+<body id="twplib"><a name="twplib"><!-- --></a>
+<h1 class="topictitle1">Adding Web library projects</h1>
+<div><div class="section"> <p>Web library projects allow you to associate Java™ projects
+with "virtual" JAR files in a Web project's WEB-INF/lib directory. You can
+reference JAR files that exist elsewhere in the Enterprise Application project
+that contains your Web project, if they are in the Web project's build path,
+and avoid the need to explicitly copy these JAR files into the project's lib
+folder before you publish the Web application to a server.</p>
+<p>Currently,
+Web Library projects are supported only when testing in the WebSphere test
+environment or remotely publishing to a WebSphere<sup>®</sup> Application Server. After
+these associations are made, you must restart and republish the server for
+the changes to take effect.</p>
+<p>To set up these associations:</p>
+ </div>
+<ol><li class="stepexpand"><span>Right click on a Web project and select <b>Properties</b> from
+the pop-up menu.</span> </li>
+<li class="stepexpand"><span>Expand <b>J2EE Module Dependencies</b></span></li>
+<li class="stepexpand"><span>Click <b>Web Libraries</b></span></li>
+<li class="stepexpand"><span>Set up your associations in the Web Libraries window</span></li>
+<li class="stepexpand"><span>Click <span><b>OK</b></span> when you are done.</span></li>
+</ol>
+</div>
+<div></div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.html
new file mode 100644
index 0000000..5e2bd44
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.html
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Setting Web project properties</title>
+</head>
+<body id="twprjset"><a name="twprjset"><!-- --></a>
+<h1 class="topictitle1">Setting Web project properties</h1>
+<div><div class="section"> <p>There are many Web project properties that you can set that affect
+the phases in the lifecycle of your project and its dependencies on other
+Web resources and Web development processes. You might want to verify or update
+these properties after you have updated an existing project or have imported
+Web resources into a project .</p>
+<p>To view or set Web project properties,
+do the following: </p>
+ </div>
+<ol><li class="stepexpand"><span>Right-click on a Web Project, and from the pop-up menu select <span><b>Properties</b></span>.</span></li>
+<li class="stepexpand"><span>Select a property type in the left pane of the Properties dialog
+to view or update properties in the Web project. For each property, you can
+apply changes and modify default settings. Based on whether you have a static
+or a dynamic Web project, the following property types are available:</span> <dl><dt class="dlterm">Info</dt>
+<dd>Provides general information about project type, location, and modification
+status. </dd>
+<dt class="dlterm">BeanInfo Path (Dynamic Web project only)</dt>
+<dd>If you select the Enable Beaninfo Introspection on this project, you can
+specify the contents and order of Java™ Bean search paths to provide Bean information
+relevant to the project. You can add, remove, and reorder (using the <span>Up</span> and <span>Down</span> buttons)
+the packages used to include Bean information.</dd>
+<dt class="dlterm">Builders</dt>
+<dd>Add, remove, or reorder external tools in the build order. When you select <b>New</b> to
+create a new external tool to the list, the New External Tool wizard opens,
+so that you can define the new build tool.</dd>
+<dt class="dlterm">J2EE (Dynamic Web project only)</dt>
+<dd>Identify Web level specification and modify context root and Web content
+folder name</dd>
+<dt class="dlterm">Java Build
+Path (Dynamic Web project only)</dt>
+<dd>View or change the information about the Java build path that you supplied when creating
+the project using the <span>Create a DynamicWeb Project</span> wizard. Whenever
+the Web project is rebuilt, any class files that are created or updated will
+be output to the specified output folder. <div class="note"><span class="notetitle">Note:</span> A library entry on the Java build
+path will remain there unless the actual JAR file is deleted from the WEB-INF/lib
+folder. If you remove a library path entry but not the JAR file, the library
+entry will be re-added to the path automatically.</div>
+</dd>
+<dt class="dlterm">Java Compiler
+(Dynamic Web project only)</dt>
+<dd>Define whether to use workspace settings or project setting for compiling Java code,
+including settings for Problems, Style, Compliance and Classfiles, and Build
+Path.</dd>
+<dt class="dlterm">Javadoc Location (Dynamic Web project only)</dt>
+<dd>Define a default location (URL) for any Javadoc available to the project.</dd>
+<dt class="dlterm">Java JAR
+Dependencies (Dynamic Web project only)</dt>
+<dd>Define and reorder JAR dependencies for the project. Note that these dependencies
+may differ based on a Web project's association with multiple Enterprise application
+projects.</dd>
+<dt class="dlterm">JSP Task Tags</dt>
+<dd>Add, edit, or remove JSP task tags and assign tag priorities. These &to do& items appear in your Tasks view.</dd>
+<dt class="dlterm">JSP Compilation</dt>
+<dd>Specify when in the build process a JSP should be set to compile</dd>
+<dt class="dlterm">JSP Fragment (dynamic Web project only)</dt>
+<dd>Define default encoding, page directive, and content type values for JSP
+fragment documents in the web project.</dd>
+<dt class="dlterm">Links Validation/Refactoring</dt>
+<dd>Define project-level link management and validation settings. These settings
+override corresponding settings in the Workbench Preference settings for the
+current project.</dd>
+<dt class="dlterm">Project References</dt>
+<dd>Reference other Web projects that exist on your workbench workspace.</dd>
+<dt class="dlterm">Server</dt>
+<dd>Select the server instance used to perform necessary development, test,
+and publishing functions for the project.</dd>
+<dt class="dlterm">Validation</dt>
+<dd>Specify which validators should run for the project, and whether validation
+should occur automatically when resource updates are written to the project.
+The available validators are based on the types of resources in your project.
+By default, validators are automatically run when you save resources in a
+Web project. If you do not want validators to run automatically when you save
+these resources, enable the <b>Override validation</b> preferences
+option and disable the <b>Run validation automatically when you save
+changes to resources</b> option. <div class="note"><span class="notetitle">Note:</span> You can also disable automatic
+validation (and builds) for all projects by disabling <b>Perform build
+ automatically on resource modification</b> from the <b>Workbench</b> properties.
+If you disable automatic builds, you can manually run a build (and validation)
+by selecting <span class="menucascade"><b>Project</b> > <b>Rebuild
+project</b></span>.</div>
+</dd>
+<dt class="dlterm">Web Content Settings</dt>
+<dd>Provide any applicable Web content settings for a Web project. You can
+specify the document type, CSS profile, and target device.</dd>
+<dt class="dlterm">Web Project Features</dt>
+<dd>Select the features you want to be enabled for your Web project, such
+as Page Template support.</dd>
+</dl>
+</li>
+<li class="stepexpand"><span>When you have completed updates to Web project settings, click <span><b>OK</b></span> to
+save and close the Properties dialog.</span></li>
+</ol>
+</div>
+<div></div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.html
new file mode 100644
index 0000000..f73dd3f
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html><head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/>
+<title>Creating servlets</title>
+</head>
+<body xml:lang="en-us" id="twsrvwiz"><a name="twsrvwiz"><!-- --></a>
+<h1 class="topictitle1">Creating servlets</h1>
+<div><p>The servlet wizard helps you create Java™ servlets by walking you through the
+creation process and by providing you with output files that you can use or
+that you can modify for use with your Web application. The servlets can run
+on J2EE-compliant Web servers.</p>
+<div class="section"> <p>To create a servlet, complete the following steps: </p>
+</div>
+<ol><li class="stepexpand"><span>From the J2EE perspective, expand your <a href="ccwebprj.html">dynamic project</a> in the Project Explorer view.</span></li>
+<li class="stepexpand"><span>Right click on the <strong>Servlet</strong> icon, and select <span class="menucascade"><b>New</b> > <b>Servlet</b></span> from
+the pop-up menu.</span> The <b>Create Servlet</b> wizard
+appears.</li>
+<li class="stepexpand"><span>Follow the project wizard prompts.</span></li>
+</ol>
+<div class="section"><p><strong>General Information</strong></p>
+<dl><dt class="dlterm">Modifiers</dt>
+<dd>You can select a modifier in the wizard to specify whether your servlet
+class is public, abstract, or final. Note that classes cannot be both abstract
+and final.</dd>
+<dt class="dlterm">javax.servlet.Servlet</dt>
+<dd>Although javax.servlet.Servlet is provided as the default interface, you
+can use the wizard to add additional interfaces to implement.</dd>
+<dt class="dlterm">Interface selection dialog</dt>
+<dd>This dialog appears if you elect to add an interface to your servlet.
+As you type the name of the interface that you are adding, a list of available
+interfaces listed in the Matching types list box updates dynamically to display
+only the interfaces that match the pattern. You should choose an interface
+to see the qualifier, and then click OK when finished.</dd>
+<dt class="dlterm">Method stubs</dt>
+<dd>You can select any appropriate method stubs to be created in the servlet
+file. The stubs created by using the Inherited abstract methods option must
+be implemented if you do not intend to create an abstract servlet. Note that
+this is not true for Constructors from superclass</dd>
+</dl>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br>
+<div><a href="cwservbn.html">Servlets</a></div>
+</div>
+</div>
+</body></html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.xml b/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.xml
new file mode 100644
index 0000000..2032a2b
--- /dev/null
+++ b/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.xml
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="utf-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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="Web application development" topic="topics/ccwtover.html">
+ <topic label="Web tools features" href="topics/cwtfeatures.html">
+ <topic label="Project Explorer view and Web development" href="topics/ccwebvw.html"/>
+ <topic label="Web resources" href="topics/cwebresources.html"/>
+ <topic label="Web page design" href="topics/cwebpagedesign.html"/>
+ </topic>
+ <topic label="Web projects" href="topics/cwebprojects.html">
+ <topic label="Web archive (WAR) files" href="topics/cwwarovr.html"/>
+ <topic label="Creating a dynamic Web project" href="topics/twcreprj.html">
+ <topic label="Dynamic Web projects and applications" href="topics/ccwebprj.html"/>
+ </topic>
+ <topic label="Creating a static Web project" href="topics/twcresta.html">
+ <topic label="Converting static Web projects to dynamic Web projects" href="topics/twpcnvrt.html"/>
+ <topic label="Static Web projects" href="topics/ccstatic.html"/>
+ </topic>
+ <topic label="Importing Web archive (WAR) files" href="topics/twimpwar.html"/>
+ <topic label="Exporting Web Archive (WAR) files" href="topics/twcrewar.html"/>
+ <topic label="Adding Web library projects" href="topics/twplib.html"/>
+ <topic label="Setting Web project properties" href="topics/twprjset.html"/>
+ </topic>
+ <topic label="Workbench integration with Web editors" href="topics/cwwedtvw.html"/>
+ <topic label="Creating and editing Web pages - overview" href="topics/tjdetags.html">
+ <topic label="Creating HTML and XHTML files and framesets" href="topics/tjcrehtm.html"/>
+ <topic label="Defining HTML file preferences" href="topics/tjprefs.html"/>
+ <topic label="Creating cascading style sheets" href="topics/tstylesheet.html"/>
+ <topic label="Creating servlets" href="topics/twsrvwiz.html">
+ <topic label="Servlets" href="topics/cwservbn.html"/>
+ </topic>
+ <topic label="Creating JavaServer Pages (JSP) files" href="topics/tjcrejsp.html">
+ <topic label="JavaServer Pages (JSP) technology" href="topics/cpdjsps.html"/>
+ </topic>
+ </topic>
+ <topic label="Setting CVS repository defaults" href="topics/twcvsr.html"/>
+ <topic label="Server targeting for Web applications" href="topics/tservertarget.html"/>
+</toc>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.cvsignore b/docs/org.eclipse.wst.xml.ui.infopop/.cvsignore
new file mode 100644
index 0000000..c14487c
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/.cvsignore
@@ -0,0 +1 @@
+build.xml
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.project b/docs/org.eclipse.wst.xml.ui.infopop/.project
new file mode 100644
index 0000000..110ff69
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.xml.ui.infopop</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.xml.ui.infopop/EditorXmlContexts.xml b/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts.xml
new file mode 100644
index 0000000..364fca9
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts.xml
@@ -0,0 +1,143 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<contexts>
+<context id="csh_outer_container">
+<description/>
+</context>
+<context id="webx0060">
+<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save an XML related file.
+
+Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform.
+
+<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>.
+
+The encoding attribute is used to specify the default character encoding set that is used when creating XML related files (DTDs, XML files, XML schemas). Changing the encoding causes any new, XML related files that are created from scratch to use the selected encoding.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html" label="Specifying XML default encoding and line delimiters"/>
+</context>
+<context id="webx0061">
+<description>This page lets you specify the formatting and content assist preferences that will be used when editing an XML file.
+
+Enter a maximum width in the <b>Line width</b> field to specify when a line should be broken to fit onto more than one line. This will be applied when the document is formatted.
+
+Select <b>Split multiple attributes each on a new line</b> to start every attribute on a new line when the document is formatted.
+
+Select <b>Clear all blank lines</b> to remove blank lines when the document is formatted.
+
+Select <b>Indent using tabs</b> if you want to use tab characters (\t) as the standard formatting indentation.
+
+If you prefer to use spaces, select <b>Indent using spaces</b>.
+
+You can also specify the <b>Indentation size</b> which is the number of tabs or space characters used for formatting indentation.
+
+To apply these formatting styles, right-click in your XML document, and click <b>Format > Document</b>.
+
+If the <b>Automatically make suggestions</b> check box is selected, you can specify that certain characters will cause the content assist list to pop up automatically. Specify these characters in the <b>Prompt when these characters are inserted</b> field.
+
+If you select <b>Strict</b> from the <b>Suggestion strategy</b> list, suggestions that are grammatically valid will be shown first (with bold icons) in the content assist list. Other suggestions that are applicable to the element scope, but not grammatically valid, will be shown below them with a de-emphasized icon. The default value for this field is <b>Lax</b>.
+
+If a DTD or schema (or other model) is not specified for an XML file, selecting <b>Use inferred grammar in absence of DTD/Schema</b> allows the editor to "guess" what elements or attributes are available based on existing content.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html" label="Defining XML editor preferences"/>
+</context>
+<context id="webx0062">
+<description>This page lets you customize the syntax highlighting that the XML editor does when you are editing a file.
+
+The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting.
+
+The <b>Foreground</b> and <b>Background</b> buttons open <b>Color</b> dialog boxes that allow you to specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold.
+
+Click the <b>Restore Defaults</b> button to set the highlighting styles back to their default values. If you only want to reset the value for a particular content type, select it in the <b>Content type</b> field, the click the <b>Restore Default</b> button next to it.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html" label="Setting source highlighting styles"/>
+</context>
+<context id="webx0063">
+<description>This page lets you create new templates and edit existing ones that can be used when editing an XML file. A template is a chunk of predefined code that you can insert into a file.
+
+Click <b>New</b> if you want to create a completely new template.
+
+Supply a new template <b>Name</b> and <b>Description</b>. The <b>Context</b> for the template is the context in which the template is available in the proposal list when content assist is requested. Specify the <b>Pattern</b> for your template using the appropriate tags, attributes, or attribute values to be inserted by content assist.
+
+If you want to insert a variable, click the <b>Insert Variable</b> button and select the variable to be inserted. For example, the <b>date</b> variable indicates the current date will be inserted.
+
+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.
+
+If you have a template that you do not want to remove but you no longer want it to appear in the content assist list, clear its check box in the <b>Templates</b> preferences page.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html" label="Working with XML templates"/>
+</context>
+<context id="xmlm1200">
+<description>Cleanup options enable you to update a document so that it is well-formed and consistently formatted.
+
+The following cleanup options can be set to on or off, so that you can limit the type of cleanup performed:
+
+- <b>Compress empty element tags</b>: Compress element tags with no content to one tag with an end tag delimiter (ie: change <tag></tag> to <tag/>).
+
+- <b>Insert required attributes</b>: Inserts any missing attributes that are required by the tag to make the element or document well-formed.
+
+- <b>Insert missing tags</b>: Completes any missing tags (such as adding an end tag) necessary to make the element or document well-formed.
+
+- <b>Quote attribute values</b>: Appropriately adds double- or single-quotes before and after attribute values if they are missing.
+
+- <b>Format source</b>: Formats the document just as the <b>Format Document</b> context menu option does, immediately after performing any other specified <b>Cleanup</b> options.
+
+- <b>Convert line delimiters to</b>: Converts all line delimiters in the file to the selected operating system's type.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html" label="Editing in the Source view"/>
+</context>
+<context id="xcui0500">
+<description>Enter the name of the attribute in the <b>Name</b> field, then enter the value of the attribute in the <b>Value</b> field. Click <b>OK</b>. The attribute will be added to the file.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+</context>
+<context id="xcui0010">
+<description>The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can use the <b>Public ID</b> field to create an association using an XML Catalog entry or the <b>System ID</b> field to create an association using a file in the workbench.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/>
+</context>
+<context id="xcui0020">
+<description>This should match the name of your XML file's root element.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/>
+</context>
+<context id="xcui0030">
+<description>The value in this field is the Public Identifier. It is used to associate the XML file (using an XML catalog entry) with a DTD file by providing a hint to the XML processor.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/>
+</context>
+<context id="xcui0050">
+<description>The value in this field is the DTD the XML file is associated with. You can change the DTD the file is associated with by editing this field. The XML processor will try to use the Public ID to locate the DTD, and if this fails, it will use the System ID to find it.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/>
+</context>
+<context id="xcui0600">
+<description>Enter the name of the element in the <b>Element name</b> field, then click <b>OK</b>. The element will be added to the file.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+</context>
+<context id="xcui0300">
+<description>A processing instruction is a syntax in XML for passing instructions along to the application using an XML document. The <b>Target</b> field is used to identify the application the instructions belongs to. The <b>Data</b> field contains the instructions.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html" label="Editing XML processing instructions"/>
+</context>
+<context id="xcui0100">
+<description>This is a read-only dialog. Select the entry you want to edit and click <b>Edit</b>.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing your namespace information"/>
+</context>
+<context id="xcui0200">
+<description>The value in the <b>Namespace Name</b> field is the namespace the XML file belongs to.
+
+All qualified elements and attributes in the XML file associated with the namespace will be prefixed with the <b>Prefix</b> value.
+
+The <b>Location Hint</b> field contains the location of the XML schema the XML file is associated with. An XML Catalog ID or a URI can be specified in this field. You can search for the schema you want to use by clicking <b>Browse</b>. Once you select a file, the <b>Namespace Name</b> and <b>Prefix</b> fields will automatically be filled with the appropriate values from the schema (you must leave the fields blank for this to occur). <b>Note</b>: If you are creating an XML file from an XML schema, you cannot change the <b>Namespace Name</b> or <b>Location Hint</b> values.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing your namespace information"/>
+</context>
+<context id="xcui0400">
+<description>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). Select the catalog entry you want to associate your XML file with.</description>
+</context>
+</contexts>
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts2.xml b/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts2.xml
new file mode 100644
index 0000000..60ebab5
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts2.xml
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<contexts>
+<context id="csh_outer_container">
+<description/>
+</context>
+<context id="xml_source_HelpId">
+<description>The XML source view lets you edit a file that is coded in the Extensible Markup Language. The editor provides many text editing features, such as content assist, user-defined templates, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html" label="Editing in the Source view"/>
+</context>
+</contexts>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.xml.ui.infopop/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..34068a0
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.xml.ui.infopop; singleton:=true
+Bundle-Version: 1.0.1.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/TableTree.xml b/docs/org.eclipse.wst.xml.ui.infopop/TableTree.xml
new file mode 100644
index 0000000..263c6e1
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/TableTree.xml
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+
+<contexts>
+<context id="csh_outer_container">
+<description/>
+</context>
+<context id="xmlm3000">
+<description>The Design view of the XML editor represents your file simultaneously as a table and a tree, which helps make navigation and editing easier. Depending on the kind of file you are working with, content and attribute values can be edited directly in table cells, while pop-up menus on tree elements give alternatives that are valid for that location.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/>
+</context>
+</contexts>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/XMLWizardContexts.xml b/docs/org.eclipse.wst.xml.ui.infopop/XMLWizardContexts.xml
new file mode 100644
index 0000000..4e781c5
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/XMLWizardContexts.xml
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+
+<contexts>
+<context id="csh_outer_container">
+<description/>
+</context>
+<context id="xmlc0101">
+<description>Select the <b>Create XML file from a DTD file</b> radio button to create an XML file from a DTD file. The file will contain the selected root element, populated with any required elements and attributes.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+</context>
+<context id="xmlc0102">
+<description>Select the <b>Create XML file from an XML schema file</b> radio button to create an XML file from an XML schema. The file will contain the selected root element of the XML schema and any elements or attributes it contains.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/>
+</context>
+<context id="xmlc0103">
+<description>Select the <b>Create XML file from scratch</b> radio button if you want to create an XML file not associated with any XML schema or DTD file.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html" label="Creating empty XML files"/>
+</context>
+<context id="xmlc0500">
+<description>Select the <b>Select file from workbench</b> radio button if you want to create your XML file from a DTD or XML schema that is in the workbench.
+
+Select the <b>Select XML Catalog entry</b> radio button if you want to use a file listed in the XML Catalog to create your XML file.</description>
+</context>
+<context id="xmlc0410">
+<description>The root element of an XML file is the element that contains all other elements in that file. All elements defined in the DTD or all global elements defined in the XML schema are included in this list.
+
+<b>Note</b>: If you do not have any elements in your DTD or any global elements in your XML schema, you cannot create an XML file from it.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/>
+</context>
+<context id="xmlc0441">
+<description>If you select this check box, both mandatory and optional attributes will be generated. If you do not select it, only mandatory attributes will be generated.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/>
+</context>
+<context id="xmlc0442">
+<description>If you select this check box, both the mandatory and optional elements will be generated. If you do not select it, only mandatory elements will be generated.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/>
+</context>
+<context id="xmlc0443">
+<description>If you select this check box, the first choice of a required choice will be generated in your XML file.
+
+For example, if you have the following code in your source file:
+
+<b><choice> <element name="a" type="string> <element name="b" type="integer> </choice></b>
+
+and you select this check box, an element such as the following will be created in your XML file:
+
+<b><a>hello</a></b> </description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/>
+</context>
+<context id="xmlc0444">
+<description>If you select this check box, any elements and attributes generated will be filled with sample data, such as <b><text>EmptyText</text>.</b> Otherwise, they will be empty - that is, <b><text></text>.</b> </description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/>
+</context>
+<context id="xmlc0210">
+<description>The System ID value corresponds to the URI (physical location) of the DTD file. The Public ID value can refer to a DTD entry in an XML Catalog.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+</context>
+<context id="xmlc0220">
+<description>The System ID value corresponds to the URI (physical location) of the DTD file. The Public ID value can refer to a DTD entry in an XML Catalog.</description>
+<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/>
+</context>
+</contexts>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/about.html b/docs/org.eclipse.wst.xml.ui.infopop/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/build.properties b/docs/org.eclipse.wst.xml.ui.infopop/build.properties
new file mode 100644
index 0000000..c491d33
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/build.properties
@@ -0,0 +1,9 @@
+bin.includes = META-INF/,\
+ EditorXmlContexts.xml,\
+ EditorXmlContexts2.xml,\
+ about.html,\
+ plugin.properties,\
+ plugin.xml,\
+ src.includes = build.properties,\
+ XMLWizardContexts.xml,\
+ TableTree.xml
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/plugin.properties b/docs/org.eclipse.wst.xml.ui.infopop/plugin.properties
new file mode 100644
index 0000000..8725f94
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/plugin.properties
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2006 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
+###############################################################################
+
+pluginName = XML infopops
+pluginProvider = Eclipse.org
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/plugin.xml b/docs/org.eclipse.wst.xml.ui.infopop/plugin.xml
new file mode 100644
index 0000000..2287c84
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/plugin.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.1"?>
+<!-- /*******************************************************************************
+ * 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>
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorXmlContexts.xml" plugin ="org.eclipse.wst.xml.ui"/>
+ <contexts file="EditorXmlContexts2.xml" plugin ="org.eclipse.core.runtime"/>
+ <contexts file="TableTree.xml" plugin ="org.eclipse.wst.xml.ui"/>
+ <contexts file="XMLWizardContexts.xml" plugin ="org.eclipse.wst.xml.ui"/>
+
+</extension>
+
+
+</plugin>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.cvsignore b/docs/org.eclipse.wst.xmleditor.doc.user/.cvsignore
new file mode 100644
index 0000000..11f459a
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/.cvsignore
@@ -0,0 +1,2 @@
+build.xml
+org.eclipse.wst.xmleditor.doc.user_1.0.0.jar
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/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.xmleditor.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..70b9e74
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.wst.xmleditor.doc.user; singleton:=true
+Bundle-Version: 1.0.1.qualifier
+Bundle-Vendor: %pluginProvider
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
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..ce59f82
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="utf-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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/cworkXML.html">
+ <topic label="Working with XML files" href="topics/cworkXML.html">
+ <topic label="Creating XML files" href="topics/ccreatxm.html">
+ <topic label="Creating empty XML files" href="topics/tcretxml.html"/>
+ <topic label="Generating XML files from a DTDs" href="topics/tcrexdtd.html"/>
+ <topic label="Generating XML files from XML schemas" href="topics/tcrexxsd.html"/>
+ </topic>
+ <topic label="Editing XML files" href="topics/txedttag.html">
+ <topic label="XML editor" href="topics/cwxmledt.html">
+ <topic label="Defining XML editor preferences" href="topics/txprefs.html">
+ <topic label="Setting source highlighting styles" href="topics/ttaghilt.html"/>
+ <topic label="Specifying XML default encoding line delimiters" href="topics/tedtenc.html">
+ <topic label="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 DOCTYPE declarations" href="topics/tedtdoc.html"/>
+ <topic label="Editing namespace information" href="topics/tedtsch.html"/>
+ <topic label="Editing 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 label="Working with XML templates" href="topics/twmacro.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="Editing XML documents with multiple namespaces" 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 entries 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..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</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..b2a5023
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/build.properties
@@ -0,0 +1,8 @@
+bin.includes = XMLBuildermap_toc.xml,\
+ about.html,\
+ images/,\
+ plugin.properties,\
+ plugin.xml,\
+ topics/,\
+ META-INF/
+src.includes = build.properties
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..13ed1ee
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.properties
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2006 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
+###############################################################################
+
+pluginName = XML editor
+pluginProvider = Eclipse.org
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..20b6e01
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.xml
@@ -0,0 +1,19 @@
+<?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>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="XMLBuildermap_toc.xml"/>
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html
new file mode 100644
index 0000000..6a742a4
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html
@@ -0,0 +1,31 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Creating XML files</title>
+</head>
+<body id="creatingxmlfiles"><a name="creatingxmlfiles"><!-- --></a>
+<h1 class="topictitle1">Creating XML files</h1>
+<div><p>This section contains information on creating XML files:</p>
+</div>
+<div>
+<div class="linklist">
+<div><a href="tcretxml.html" title="You can create a new, empty XML file, which you can then edit in the XML editor. When you create a new, empty XML file, it is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating empty XML files</a></div>
+<div><a href="tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from a DTDs</a></div>
+<div><a href="tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">
+ Generating XML files from XML schemas
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html
new file mode 100644
index 0000000..afb687a
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html
@@ -0,0 +1,34 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>XML editor</title>
+</head>
+<title>Working with XML files</title>
+</head>
+<body id="workingwithxmlfiles"><a name="workingwithxmlfiles"><!-- --></a>
+<h1 class="topictitle1">Working with XML files</h1>
+<div><p>This section contains information on the following:</p>
+</div>
+<div>
+<div class="linklist">
+<div><a href="ccreatxm.html" title="This section contains information on creating XML files:">Creating XML files</a></div>
+<div><a href="txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div>
+<div><a href="twxvalid.html" title="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed.">Validating XML files</a></div>
+<div><a href="cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML
+schema</a></div>
+<div><a href="rxmlbicons.html" title="The following XML editor icons appear in the Outline and Design view.">Icons used in the XML editor</a></div></div>
+</div></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..0c924a6
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html
@@ -0,0 +1,79 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>XML editor</title>
+</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:</p>
+<ul><li>Creating new, empty XML files or generating them from existing DTDs or
+existing XML schemas</li>
+<li>Editing XML files</li>
+<li>Importing existing XML files for structured viewing</li>
+<li>Associating XML files with DTDs or XML schemas</li>
+</ul>
+<p>The XML editor has two main views - the Source view and the Design view.
+You can also use the <strong>Outline</strong> view to insert and delete elements.</p>
+<div class="section"><h4 class="sectiontitle">Source view</h4><p>The Source view enables you to view
+and work directly with a file's source code.</p>
+<div class="p">The Source view has many text editing features,
+such as: <ul><li> Syntax highlighting, unlimited undo/redo, and user-defined templates.</li>
+<li> 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 type</li>
+<li>"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.</li>
+</ul>
+</div>
+</div>
+<div class="section"><h4 class="sectiontitle">Design view</h4><div class="p">The XML editor also has a Design view.
+In it: <ul><li>The XML file is represented simultaneously as a table and a tree. This
+helps make navigation and editing easier.</li>
+<li>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).</li>
+</ul>
+</div>
+<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>The
+following links provide more information about the XML editor:</p>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tcretxml.html" title="You can create a new, empty XML file, which you can then edit in the XML editor. When you create a new, empty XML file, it is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating empty XML files</a></div>
+<div><a href="../topics/tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from DTDs</a></div>
+<div><a href="../topics/tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML schemas</a></div>
+<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div>
+<div><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></div>
+<div><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></div>
+<div><a href="../topics/twxvalid.html" title="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed.">Validating XML files</a></div>
+</div>
+</div></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..c42ca28
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html
@@ -0,0 +1,175 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>XML file associations with DTDs and XML schemas</title>
+</head>
+<body id="cxmlcat"><a name="cxmlcat"><!-- --></a>
+
+<h1 class="topictitle1">XML file associations with DTDs and XML schemas</h1>
+<div><p>When an XML file is associated with a DTD or XML schema, it is
+bound by any structural rules contained in the DTD or XML schema. To be considered
+a valid XML file, a document must be accompanied by a DTD or an XML schema,
+and conform to all of the declarations in the DTD or the XML schema.</p>
+<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 previously 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><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div><br/>
+<div><strong>Related tasks</strong><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></div>
+ <div>
+ <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 DOCTYPE declarations</a></div>
+ <div>
+ <a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (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">Adding entries to the XML Catalog</a></div>
+ <div>
+ <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. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div>
+ <div>
+ <a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div>
+ <div>
+ <a href="../topics/tedtproc.html" title="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction.">Editing XML processing instructions</a></div>
+ <div>
+ <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></div>
+ <div>
+ <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></div>
+</div>
+</div></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..ee7563a
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html
@@ -0,0 +1,170 @@
+<?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>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+<meta name="security" content="public" />
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>XML and HTML encodings</title>
+</head>
+<body id="cxmlenc"><a name="cxmlenc"><!-- --></a>
+
+<h1 class="topictitle1">XML and HTML encodings</h1>
+<div><p>Encodings enable you to specify what character encoding your text
+is in.</p>
+<p>The IANA name is used in the encoding statement of an XML file, or charset
+directive in an HTML file.</p>
+<p>The HTML and XML editors support the following encodings:</p>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" class="firstcol" id="d0e31"> <p><strong>XML Encoding (IANA Name)</strong></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>
+</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..7669633
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html
@@ -0,0 +1,50 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>XML tools - overview</title>
+</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, and XML files.</p><p>The following XML 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. </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 and importing and viewing XML schemas. </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>
+</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..cb72188
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html
@@ -0,0 +1,40 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<!-- US Government Users Restricted Rights -->
+<title>Editing XML documents with multiple namespaces</title>
+</head>
+<body id="rextctn"><a name="rextctn"><!-- --></a>
+<h1 class="topictitle1">Editing XML documents with multiple namespaces</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>
+</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..2aa4b59
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html
@@ -0,0 +1,31 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Limitations of XML Editor</title>
+</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>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html
new file mode 100644
index 0000000..acb1cba
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Icons used in the XML editor</title>
+</head>
+<body id="ricons"><a name="ricons"><!-- --></a>
+<h1 class="topictitle1">Icons used in the XML editor</h1>
+<div><p>The following XML editor icons appear in the Outline and Design
+view.</p>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><tbody><tr><td valign="bottom"><strong>Icon</strong> </td>
+<td valign="bottom"><strong>Description</strong></td>
+</tr>
+<tr><td valign="top"> <img src="../images/nattrib.gif" alt="This graphic is the attribute icon" /> </td>
+<td valign="top">attribute</td>
+</tr>
+<tr><td valign="top"> <img src="../images/cdatasection.gif" alt="This graphic is the character data icon" /></td>
+<td valign="top">character data (CDATA) section</td>
+</tr>
+<tr><td valign="top"> <img src="../images/comment_obj.gif" alt="This graphic is the comment icon" /></td>
+<td valign="top">comment</td>
+</tr>
+<tr><td valign="top"> <img src="../images/doctype.gif" alt="This graphic is the DOCTYPE icon" /></td>
+<td valign="top">DOCTYPE declaration</td>
+</tr>
+<tr><td valign="top"> <img src="../images/nelem.gif" alt="This graphic is the element icon" /> </td>
+<td valign="top">element</td>
+</tr>
+<tr><td valign="top"> <img src="../images/proinst_obj.gif" alt="This graphic is the processing instructions icon" /></td>
+<td valign="top">processing instructions</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><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></div>
+</div>
+</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..814fad3
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html
@@ -0,0 +1,55 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *
+<meta name="DC.Title" content="Creating empty XML files" />
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Creating empty XML files</title>
+</head>
+<body id="tcretxml"><a name="tcretxml"><!-- --></a>
+<h1 class="topictitle1">Creating empty XML files</h1>
+<div><p>You can create a new, empty XML file, which you can then edit in
+the XML editor. When you create a new, empty XML file, it is not associated
+with a DTD or XML schema file, so there are no restrictions on the kind of
+content it can contain.</p>
+<div class="section"><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 <b> <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></b>. </span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Next</span></b>.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Create XML file from scratch</span>
+</b>radio
+button.</span></li>
+<li class="skipspace"><span>Click <span class="uicontrol"><b>Next</b>.</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 <b> <span class="uicontrol">Finish</span></b>.</span></li>
+</ol>
+</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>
+</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..0805947
--- /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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Generate an XML file from a DTD</title>
+</head>
+<body id="tcrexdtd"><a name="tcrexdtd"><!-- --></a>
+
+<h1 class="topictitle1">Generating XML files from DTDs</h1>
+<div><p>You can generate an XML file from your DTD if you want to quickly
+create an XML file based on your DTD file. Generating an XML file from your
+DTD saves you time by creating an XML file that is already associated with
+your DTD, and contains at least some of the elements and attributes in your
+DTD.</p>
+<div class="section"><p>After you have generated your XML file, you can further customize
+it in the XML editor.</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 <b> <span class="menucascade"><span class="uicontrol">Generate</span> > <span class="uicontrol">XML File</span></span></b>.</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 <b> <span class="uicontrol">Next</span></b>.</span></li>
+<li class="skipspace"><span>Select the <b> <span class="uicontrol">Root element</span>
+</b>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>
+ <b><span class="uicontrol">Create optional attributes</span> </b>- Both
+ mandatory and optional attributes will be generated.</li>
+<li><b><span class="uicontrol">Create optional elements</span> </b>- Both
+mandatory and optional elements will be generated.</li>
+<li><b><span class="uicontrol">Create first choice of required choice</span></b> -
+The first choice of a required choice will be generated in your XML file.</li>
+<li><b><span class="uicontrol">Fill elements and attributes with data</span></b> - 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 <b> <span class="uicontrol">Public ID</span></b> or
+<b> <span class="uicontrol">System
+ID</span>.</b></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 <b> <span class="uicontrol">Finish</span></b>.</span></li>
+</ol>
+<div class="skipspace">
+<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">Generating an XML file from an XML schema</a><br />
+<a href="../topics/txedttag.html" title="Editing XML files">Editing XML files</a><br />
+</p>
+</div>
+</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..705cd7c
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html
@@ -0,0 +1,109 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Generating an XML file from an XML schema</title>
+</head>
+<body id="tcrexxsd"><a name="tcrexxsd"><!-- --></a>
+
+<h1 class="topictitle1">Generating XML files from XML schemas</h1>
+<div><p>You can generate an XML file from your XML schema if you want to
+quickly create an XML file based on your XML schema file. Generating an XML
+file from your XML schema saves you time by creating an XML file that is already
+associated with your XML schema, and contains at least some of the elements
+and attributes in your XML schema.</p>
+<div class="section"><p>After you have generated your XML file, you can further customize
+it in the XML editor.</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 <b> <span class="menucascade"><span class="uicontrol">Generate</span> > <span class="uicontrol">XML File</span></span></b>.</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 <b> <span class="uicontrol">Next</span></b>.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Root element</span>
+</b>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 <b>Root Element </b>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>
+ <b><span class="uicontrol">Create optional attributes</span> </b>- Both mandatory
+and optional attributes will be generated</li>
+<li><b><span class="uicontrol">Create optional elements</span> </b>- Both mandatory and
+optional elements will be generated.</li>
+<li><b><span class="uicontrol">Create first choice of required choice</span></b> -
+The first choice of a required choice will be generated in your XML file.</li>
+<li><b><span class="uicontrol">Fill elements and attributes with data</span> </b>- 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 <b>Namespace</b> <b>information</b> 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 <b> <span class="uicontrol">Edit</span></b>.</span></li>
+<li class="skipspace"><span>The value in the <b> <span class="uicontrol">Namespace Name</span>
+</b>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 <b> <span class="uicontrol">Prefix</span></b> value.</span></li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">Location Hint</span>
+</b>field contains the location
+of the XML schema.</span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">OK</span></b>, then
+<b> <span class="uicontrol">Finish</span></b>.</span></li>
+</ol>
+<div class="skipspace">
+<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">Generating an XML file from a DTD</a><br />
+<a href="../topics/txedttag.html" title="Editing XML files">Editing XML files</a><br />
+</p>
+
+<p><b class="reltaskshd">Related references</b><br />
+<a href="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html">XML
+namespaces</a><br />
+</p>
+</div>
+</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..721e5f3
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html
@@ -0,0 +1,83 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing with DTD or XML schema constraints</title>
+</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 <b> <span class="uicontrol">Open With > XML Editor</span></b>). </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"> <b>Remove</b></span> option is grayed out.</li>
+<li class="skipspace"><span>To turn the DTD constraints off, click <b> <span class="uicontrol">XML > Turn Grammar
+Constraints Off</span></b>. </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">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>
+</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..5f3dbdc
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html
@@ -0,0 +1,68 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing DOCTYPE declarations</title>
+</head>
+<body id="tedtdoc"><a name="tedtdoc"><!-- --></a>
+<h1 class="topictitle1">Editing DOCTYPE declarations</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 <b> <span class="uicontrol">Edit DOCTYPE</span></b>.</span></li>
+<li class="skipspace"><span>The value in the <b> <span class="uicontrol">Root element
+name</span></b> 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 <b>Public ID</b> for any existing XML Catalog entries
+by clicking <b> <span class="uicontrol">Browse</span></b>. </span> The value in the
+<b> <span class="uicontrol">Public
+ID</span></b> 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 <b> <span class="uicontrol">System ID</span>
+</b>field is the
+DTD the XML file is associated with. Type the path of the DTD file (or browse
+for it) 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 <b> <span class="uicontrol">OK</span></b>.</span></li>
+</ol>
+<div class="section">If you do not have a DOCTYPE declaration in your XML file, you can
+right-click in the Design view and click <b> <span class="uicontrol">Add DTD Information</span></b> to
+add one.</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">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="txedtdes.html">Editing in the XML design view</a><br />
+</p>
+</div>
+</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..7e4abda
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html
@@ -0,0 +1,38 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Specifying line delimiters</title>
+</head>
+<body id="tedtenc"><a name="tedtenc"><!-- --></a>
+<h1 class="topictitle1">Specifying XML default encoding and line delimiters</h1>
+<div><p>This page lets you specify the line delimiter and the text encoding that
+ will be used when you create or save an XML related file.</p>
+<div class="section">
+<p>To specify the line
+delimiter you want to use:</p>
+</div>
+<ol><li><span>Click <b> <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>.</b></span></li>
+<li><span>From the <b> <span class="uicontrol">Line delimiter</span> </b>field, select the
+operating system that applies to your development or deployment platform. </span></li>
+ <li>From the <b>Encoding</b> field, specify the default character encoding
+ set that is used when creating XML related files (DTDs, XML files, XML
+ schemas). Changing the encoding causes any new, XML related files that are
+ created from scratch to use the selected encoding.</li>
+<li><span>Click <b> <span class="uicontrol">Apply</span></b>, then <b> <span class="uicontrol">OK</span></b>.</span></li>
+</ol>
+</div>
+</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..a23b95f
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html
@@ -0,0 +1,57 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Updating XML files with changes made to DTDs and schemas</title>
+</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 <b> <span class="uicontrol">XML > Reload Dependencies</span>
+ </b>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 <b> <span class="uicontrol">XML
+> Reload Dependencies</span></b> 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">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>
+</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..7abf218
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html
@@ -0,0 +1,43 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing XML processing instructions</title>
+</head>
+<body id="tedtproc"><a name="tedtproc"><!-- --></a>
+
+<h1 class="topictitle1">Editing XML processing instructions</h1>
+<div><p>If you have instructions you want to pass along to an application
+using an XML document, you can use a processing instruction. </p>
+<div class="section"><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 <b> <span class="uicontrol">Edit Processing Instruction</span></b>.</span></li>
+<li><span>The <b> <span class="uicontrol">Target</span></b> field is used to identify the
+application the instructions belongs to.</span></li>
+<li><span>The <b> <span class="uicontrol">Data</span></b> field contains the instructions.</span></li>
+<li><span>Click <b> <span class="uicontrol">OK</span></b>.</span></li>
+</ol>
+<div class="section">To create a new processing instruction, right-click in the Design
+view, and click <b> <span class="uicontrol">Add Child</span></b>, <b> <span class="uicontrol">Add Before</span></b> or
+ <b> <span class="uicontrol">Add
+After</span></b>, then click <b> <span class="uicontrol">Add Processing Instruction</span></b>.<p>
+ <p></b><strong>Related tasks</strong><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></div></div>
+</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..287a3d8
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html
@@ -0,0 +1,75 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing your namespace information</title>
+</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 and namespace it is associated with. If desired, you can change the schema and namespace your XML file
+is associated with or add a new association. Modifying any associations can
+impact what content is allowed in the XML file.</p>
+<div class="section"><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 <b> <span class="uicontrol">Edit Namespaces</span></b>.</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 <b> <span class="uicontrol">Edit</span></b>.</li>
+<li class="skipspace"><span>The value in the <b> <span class="uicontrol">Namespace Name</span></b> 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 <b> <span class="uicontrol">Prefix</span></b> value.</span></li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">Location Hint</span>
+</b>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 <b> <span class="uicontrol">Browse</span></b>
+to view all XML schemas in the workbench and XML Catalog.</li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">OK</span></b>, then click
+<b> <span class="uicontrol">OK</span></b> again.</span></li>
+</ol>
+<div class="skipspace"><p>If you want to create a new association, click <b> <span class="uicontrol">Add</span></b> instead
+of <b> <span class="uicontrol">Edit</span></b>. You can then either click the <span class="uicontrol">S<b>pecify
+From Registered Namespace</b></span> radio button and select the namespace
+declarations you want to add or click the <b> <span class="uicontrol">Specify New Namespace</span></b> radio
+button and fill in the fields as necessary. </p>
+</div>
+<div class="section">If you do not have namespace information in your XML file, you
+can right-click your root element in the Design view and click <b> <span class="uicontrol">Edit
+Namespaces</span></b> to add it. If you do not have a root element, you must
+create one before you can add the namespace information.</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">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/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>
+</p>
+<p><strong>Related information</strong><br />
+<a href="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html">XML namespaces</a></div>
+</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..c460093
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html
@@ -0,0 +1,51 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Setting source highlighting styles</title>
+</head>
+<body id="ttaghilt"><a name="ttaghilt"><!-- --></a>
+
+<h1 class="topictitle1">Setting source highlighting styles</h1>
+<div><p>If desired, you can change various aspects of how the XML source
+code is displayed in the Source view of the XML editor, such as the colors
+the tags will be displayed in.</p>
+ </p><div class="skipspace"><p>To set highlighting styles for the XML code, follow these steps:</p>
+</div>
+<ol><li><span>Click <b> <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></b>.</span></li>
+<li><span>In the <b> <span class="uicontrol">Content type</span></b> 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 <b> <span class="uicontrol">Foreground</span></b> box.</span></li>
+<li><span>Select the color that you want the text of the tag to appear in
+and click <b> <span class="uicontrol">OK</span></b>.</span></li>
+<li><span>Click the<span class="uicontrol"> <b>Background</b></span> box.</span></li>
+<li><span>Select the color that you want to appear behind the tag and click<span class="uicontrol">
+<b>OK</b></span>.</span></li>
+<li><span>Select the <b> <span class="uicontrol">Bold</span></b> check box if you want to
+make the type bold.</span></li>
+<li><span>Click <b> <span class="uicontrol">Restore Defaults</span></b> to set
+the highlighting styles back to their default values. If you only want to
+reset the value for a particular content type, select it in the <b>Content type</b>
+field, the click the <b>Restore Default </b>button next to it. </span></li>
+<li><span>Click <b> <span class="uicontrol">OK</span></b> to save your changes.</span></li>
+</ol>
+</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><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></div>
+</div>
+</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..1b7cacb
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html
@@ -0,0 +1,72 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/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 <b> <span class="uicontrol">Edit</span></b> menu, click <b> <span class="uicontrol">Content Assist</span>,</b>
+or</li>
+<li>Press <b>Ctrl+Space</b></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 <b> <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol"> Preferences</span></span></b> to open the Preferences window, then click
+<b> <span class="menucascade"><span class="uicontrol">Web
+and XML</span> > <span class="uicontrol">XML Files </span> > <span class="uicontrol">XML Source</span></span></b>. In the
+<b> <span class="uicontrol">Content assist</span> </b>group box, select
+the <b> <span class="uicontrol">Automatically make suggestions</span></b> 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, and 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>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><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></div>
+<div><a href="../topics/twmacro.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time.">Working with XML templates</a></div>
+</div>
+</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..7e4cc0e
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html
@@ -0,0 +1,67 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Working with XML templates</title>
+</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 may find a template useful when
+ you have a certain piece of code you want to reuse several times, and you do
+ not want to write it out every time.</p>
+ <div class="skipspace">You can use the default template as
+provided, customize that template, or create your own templates. 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 <b>Pattern</b> 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 <b> <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></b>.</span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">New</span></b> if you want to create a completely
+new template.</span></li>
+<li class="skipspace"><span>Supply a new template <b>Name</b> and <b>Description</b>.</span></li>
+<li class="skipspace"><span>Specify the <b> <span class="uicontrol">Context</span></b> for the template.</span> This is the context in which the template is available in the proposal
+list when content assist is requested. </li>
+<li class="skipspace"><span>Specify the <b> <span class="uicontrol">Pattern</span></b> for your template using
+the appropriate tags, attributes, or attribute values to be inserted by content
+assist.</span></li>
+<li class="skipspace"><span>If you want to insert a variable in your <b>Pattern</b>, click the
+<b> <span class="uicontrol">Insert Variable</span></b> button
+and select the variable to be inserted. For example, the <b>date</b> variable
+indicates the current date will be inserted. </span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Apply</span></b> and then
+<b> <span class="uicontrol">OK</span></b> 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 <b>XML Templates </b>preferences page and
+ clear
+its check box.</p>
+</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><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></div>
+<div><a href="../topics/twcdast.html" title="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 templates into your XML code.">Using XML content assist</a></div>
+</div>
+</div></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..b7f8d12
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html
@@ -0,0 +1,63 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Validating XML files</title>
+</head>
+<body id="twxvalid"><a name="twxvalid"><!-- --></a>
+
+<h1 class="topictitle1">Validating XML files</h1>
+<div><p>When you validate your XML file, the XML validator will check to
+see that your file is valid and well-formed.</p>
+<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 <b> <span class="uicontrol">Validate XML file</span>.</b></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 <b> <span class="uicontrol">Show
+Details</span></b>. </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 <b> <span class="menucascade"><span class="uicontrol">Properties</span> > <span class="uicontrol">Validation</span></span></b> from the project's pop-up menu and specifying the maximum number
+of error messages allowed. You must select the <b> <span class="uicontrol">Override validation
+preferences</span> </b>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 <b> <span class="uicontrol">Properties</span></b>, then select
+<b> <span class="uicontrol">Validation</span></b>.
+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>
+</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..ee36707
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html
@@ -0,0 +1,121 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing in the Design view</title>
+</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 <b> <span class="uicontrol">Add child</span></b> 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 <b> <span class="uicontrol">Open With
+> XML Editor</span></b>). 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
+<b> <span class="uicontrol">Expand
+All</span> </b>toolbar button <img src="../images/expand_all.gif" />.</span></li>
+<li class="skipspace"><span>To collapse them, click the <b> <span class="uicontrol">Collapse All</span></b> 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 links below:<ul><li> <b> <span class="uicontrol">Add DTD Information</span>
+ </b>- Click this if you want to
+associate the XML file with a DTD.</li>
+<li> <b> <span class="uicontrol">Edit DOCTYPE</span></b> - Click this if you want to edit
+the DOCTYPE declaration. Refer to the related task for more details.</li>
+<li> <b> <span class="uicontrol">Edit Namespaces</span></b> - Click this if you want to edit
+the existing namespace information or create a new association with a namespace.</li>
+Refer to the related task for more details.</li>
+<li> <b> <span class="uicontrol">Edit Processing Instruction</span></b> - Click this if you
+want to edit the processing instruction. Refer to the related task for more
+details.</li>
+<li> <b> <span class="uicontrol">Remove</span></b> - 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> <b> <span class="uicontrol">Add Attribute</span></b> - 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> <b> <span class="uicontrol">Add Child</span> </b>- Click this to add another element,
+a comment, or a processing instruction as a child of the parent element.</li>
+<li> <b> <span class="uicontrol">Add Before</span></b> - 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 <b> <span class="menucascade"><span class="uicontrol">Add Before</span> > <span class="uicontrol"> CD</span></span></b> , as a CD element can go before another CD element.</li>
+<li> <b> <span class="uicontrol">Add After</span> </b>- 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 <b> <span class="menucascade"><span class="uicontrol">Add After</span> > <span class="uicontrol"> CD</span></span>,</b> as a CD element can go after another CD element.</li>
+<li> <b> <span class="uicontrol">Replace With</span></b> - 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>
+
+
+
+<p><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div>
+<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div>
+</p>
+<p class="reltasks"><strong>Related tasks</strong><br />
+<div><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></div>
+<div><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 DOCTYPE declarations</a></div>
+<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div>
+<div><a href="../topics/tedtproc.html" title="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction.">Editing XML processing instructions</a></div>
+</p>
+<p class="relref"><strong>Related reference</strong><br />
+<div><a href="../topics/rxmlbicons.html" title="The following XML editor icons appear in the Outline and Design view.">Icons used in the XML editor</a></div>
+</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..e2c1762
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html
@@ -0,0 +1,96 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing in the Source view</title>
+</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"><b>Syntax highlighting</b></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"><b>Unlimited undo and redo</b></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"><b>Content assist</b></dt>
+<dd>Content assist helps you finish tags and insert macros. Refer to
+the related task for more details.</dd>
+<dt class="bold"><b>Template</b></dt>
+<dd>You can access templates (using content assist) to help you quickly add
+regularly-used tagging combinations. Refer to the related task for more details.</dd>
+<dt class="bold"><b>Node selection</b></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"><b>Pop-up menu options</b></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"><b>Cleanup Document</b>,</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"><b>Format</b>,</span> which formats either the
+entire document or selected elements.</dd>
+<dt class="bold"><b>"Smart" double clicking</b></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 <b> <span class="uicontrol">Open With > XML Editor</span></b>). </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 <b> <span class="uicontrol">Open
+With > XML Editor</span></b>.</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 />
+<div><a href="../topics/twcdast.html" title="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 templates into your XML code.">Using XML content assist</a></div>
+<div><a href="../topics/twmacro.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time.">Working with XML templates</a></div>
+<div><a href="../topics/ttaghilt.html" title="If desired, you can change various aspects of how the XML source code is displayed in the Source view of the XML editor, such as the colors the tags will be displayed in.">Setting source highlighting styles</a></div></p>
+</div>
+</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..31a37c1
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html
@@ -0,0 +1,66 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing XML files</title>
+</head>
+<body id="txedttag"><a name="txedttag"><!-- --></a>
+
+<h1 class="topictitle1">Editing XML files</h1>
+<div><p>This file contains information about editing XML files.</p>
+<div><div class="skipspace"><p>To open an XML file in the XML editor, right-click it in the Navigator
+view and click <b> <span class="menucascade"><span class="uicontrol">Open With</span> > <span class="uicontrol">XML
+Editor</span></span></b>. </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>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 <b> <span class="uicontrol">Add Child</span></b>
+ 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>
+<p class="section">The following links provide more information about the XML editor
+and editing XML files:</p>
+</div>
+<p><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div>
+</p>
+<p class="reltasks"><strong>Related tasks</strong><br />
+<div><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></div>
+<div><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></div>
+
+</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..16f5140
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html
@@ -0,0 +1,132 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding entries to the XML Catalog</title>
+</head>
+<body id="txmlcat"><a name="txmlcat"><!-- --></a>
+
+<h1 class="topictitle1">Adding entries 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 Uniform Resource Identifier (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>
+<div class="section"><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>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 <b> <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></b>.</span></li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">XML Catalog Entries</span></b> 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
+ <b> <span class="uicontrol">Details</span></b> field. </span></li>
+<li><span>Click <span class="uicontrol"><b>Add</b></span> to create a new catalog entry.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>In the <b> <span class="uicontrol">URI</span></b> field, type the location of the DTD or XML schema
+or browse for it. </span></li>
+<li class="skipspace"><span>If you specified a DTD in the <b> <span class="uicontrol">URI</span></b> field,
+you can select either <span class="uicontrol"><b>Public ID</b></span> or <b>
+<span class="uicontrol">System
+ID</span> </b>from the <b> <span class="uicontrol">Key Type</span></b> field.</span> If
+you select<b><span class="uicontrol"> Public ID,</span></b> the value you enter in the
+<b> <span class="uicontrol">Key</span></b> field
+should be the same as the <b>Public ID i</b>n the XML file's DOCTYPE declaration.
+If you select <b> <span class="uicontrol">System ID</span>,</b> 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 <b> <span class="uicontrol">URI</span></b> field,
+you can select either <b> <span class="uicontrol">Namespace Name</span> </b>or
+<b> <span class="uicontrol">Schema
+Location</span> </b>from the <b> <span class="uicontrol">Key Type</span></b> field.</span> If the schema defines a target namespace, it will automatically appear
+in the<span class="uicontrol"> <b>Key</b></span> field. Otherwise, you can enter the schema
+location in the <b> <span class="uicontrol">Key</span></b> field.</li>
+<li class="skipspace"><span>Select the <b> <span class="uicontrol">Specify alternative Web address</span>
+</b>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 <b> <span class="uicontrol">Public
+ID</span> </b>(for a DTD) or <b> <span class="uicontrol">Namespace Name</span>
+</b>(for
+a schema) in the <b> <span class="uicontrol">Key type</span> </b>field.</li>
+ <li class="skipspace">If you want to refer to another catalog without
+ importing it into the workbench, click <b>Next Catalog. </b>Type or browse
+ for the XML catalog you want to refer to. </li>
+<li class="skipspace"><span>When you are done creating catalog entries, click <span class="uicontrol">
+<b>OK</b></span> to close the Add XML Catalog Entry dialog. </span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Advanced</span></b> if you want to import or
+export any XML Catalog settings.</span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Export</span></b> 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> Since 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"> <b>OK</b></span>.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Import</span></b> 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 <b> <span class="uicontrol">OK</span></b>.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">OK</span></b> 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">
+<b>Reload</b>
+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>
+</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..67fb963
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html
@@ -0,0 +1,65 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Defining XML editor preferences</title>
+</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. To apply the formatting styles, right-click in in the Source view
+ for your XML document, and click<b> Format > Document</b>.</p><div class="skipspace">
+<p>To define XML preferences,
+perform the following steps:</p>
+</div>
+<ol><li class="skipspace"><span>Click <b> <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></b>.</span></li>
+<li class="skipspace"><span>Enter a maximum width for formatted lines in the <b> <span class="uicontrol">Line
+width</span> </b>field.</span> The default value is <b>72</b>.</li>
+<li class="skipspace"><span>Select <span class="uicontrol"><b>Split multiple attributes each on a new line</b></span> to
+start every attribute on a new line.</span></li>
+ <li class="skipspace"><span>If you want blank lines to be removed when the document is formatted,
+select the <b> <span class="uicontrol">Clear all blank lines</span> </b>check box. </span> By default, blank lines are preserved in a formatted document.</li>
+ <li class="skipspace">Select <b>Indent using tabs </b>if you want to use tab
+ characters (\t) as the standard formatting indentation, or, if you prefer to
+ use spaces, select <b>Indent using spaces.</b></li>
+ <li class="skipspace">You can also specify the <b>Indentation size</b> which
+ is the number of tabs or space characters used for formatting indentation.</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<b> <span class="uicontrol">Automatically
+make suggestions</span></b> check box is selected and specify the characters
+in the <b> <span class="uicontrol">Prompt when these characters are inserted</span>
+</b>field. </span></li>
+ <li class="skipspace">If you select <b>Strict</b> from the <b>Suggestion
+ strategy</b> list, suggestions that are grammatically valid will be shown
+ first (with bold icons) in the content assist list. Other suggestions that
+ are applicable to the element scope, but not grammatically valid, will be
+ shown below them with a de-emphasized icon. The default value for this field
+ is <b>Lax</b>.</li>
+<li class="skipspace"><span>The<b> <span class="uicontrol">Use inferred grammar in absence of DTD/Schema </span>
+</b>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 <b> <span class="uicontrol">Apply</span></b> and then
+<b> <span class="uicontrol">OK</span></b> to
+save your changes.</span></li>
+</ol>
+</div>
+</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..4551071
--- /dev/null
+++ b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html
@@ -0,0 +1,65 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Using xsi:type</title>
+</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>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.cvsignore b/docs/org.eclipse.wst.xsdeditor.doc.user/.cvsignore
new file mode 100644
index 0000000..f358e62
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/.cvsignore
@@ -0,0 +1,2 @@
+build.xml
+org.eclipse.wst.xsdeditor.doc.user_1.0.0.jar
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.project b/docs/org.eclipse.wst.xsdeditor.doc.user/.project
new file mode 100644
index 0000000..82170b5
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.xsdeditor.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.xsdeditor.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.xsdeditor.doc.user/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..6539516
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %Plugin.name
+Bundle-SymbolicName: org.eclipse.wst.xsdeditor.doc.user; singleton:=true
+Bundle-Version: 1.0.0.qualifier
+Bundle-Vendor: Eclipse.org
+Bundle-Localization: plugin
+Eclipse-AutoStart: true
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml
new file mode 100644
index 0000000..d692eb7
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="utf-8"?>
+<?NLS type="org.eclipse.help.contexts"?>
+<!-- /*******************************************************************************
+ * 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="XML schemas" topic="topics/tcxmlsch.html">
+ <topic label="Working with XML schemas (XSDs)" href ="topics/cworkXSD.html">
+ <topic label="Creating XML schemas" href="topics/tcxmlsch.html">
+ </topic>
+ <topic label="Importing XML schemas" href="topics/timpschm.html"/>
+ <topic label="Navigating XML schemas" href="topics/tnavsrc.html"/>
+ <topic label="Editing XML schema file preferences" href="topics/tedtpref.html"/>
+ <topic label="Editing XML schema properties" href="topics/tedtschm.html">
+ <topic label="XML schema editor" href="topics/cxmlsced.html">
+ </topic>
+ <topic label="Adding attribute groups" href="topics/taddagrp.html"/>
+ <topic label="Adding complex types" href="topics/taddcmxt.html"/>
+ <topic label="Adding content models" href="topics/taddcmod.html">
+ <topic label="Adding an any element" href="topics/taddanye.html"/>
+ <topic label="Adding elements" href="topics/taddelm.html"/>
+ <topic label="Adding element references" href="topics/taddelmr.html"/>
+ <topic label="Adding group references" href="topics/taddgrpr.html"/>
+ </topic>
+ <topic label="Adding global attributes" href="topics/taddglba.html"/>
+ <topic label="Adding global elements" href="topics/taddglem.html"/>
+ <topic label="Adding groups" href="topics/taddgrup.html"/>
+ <topic label="Adding import elements" href="topics/taddimpt.html"/>
+ <topic label="Adding include elements" href="topics/taddincl.html"/>
+ <topic label="Adding notations" href="topics/taddnot.html"/>
+ <topic label="Adding redefine elements" href="topics/taddrdfn.html"/>
+ <topic label="Adding simple types" href="topics/taddsmpt.html">
+ <topic label="Adding pattern facets to simple types" href="topics/taddreg.html"/>
+ </topic>
+ </topic>
+ <topic label="Icons used in the XML schema editor" href="topics/rxsdicons.html"/>
+ <topic label="Deleting XML schema components" href="topics/tdelscmp.html">
+ <topic label="Referential integrity in the XML schema editor" href="topics/rrefintg.html"/>
+ </topic>
+ <topic label="Validating XML schemas" href="topics/tvdtschm.html"/>
+ <topic label="XML namespaces" href="topics/rnmspc.html"/>
+ </topic>
+</toc>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/about.html b/docs/org.eclipse.wst.xsdeditor.doc.user/about.html
new file mode 100644
index 0000000..4c99086
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/about.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>February 24, 2005</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation 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
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/build.properties b/docs/org.eclipse.wst.xsdeditor.doc.user/build.properties
new file mode 100644
index 0000000..b9ce6e5
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/build.properties
@@ -0,0 +1,9 @@
+bin.includes = XSDeditormap_toc.xml,\
+ about.html,\
+ images/,\
+ plugin.properties,\
+ plugin.xml,\
+ topics/,\
+ xsdeditor_reference_toc.xml,\
+ META-INF/
+src.includes = build.properties
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/More.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/More.gif
new file mode 100644
index 0000000..63211bf
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/More.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif
new file mode 100644
index 0000000..6d74e80
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif
new file mode 100644
index 0000000..a39f93c
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif
new file mode 100644
index 0000000..5280cc2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif
new file mode 100644
index 0000000..79d49d0
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif
new file mode 100644
index 0000000..648462f
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif
new file mode 100644
index 0000000..a89fa8f
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif
new file mode 100644
index 0000000..8365af2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif
new file mode 100644
index 0000000..89ba825
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif
new file mode 100644
index 0000000..007f852
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif
new file mode 100644
index 0000000..dd45f08
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif
new file mode 100644
index 0000000..749acfc
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif
new file mode 100644
index 0000000..79d49d0
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif
new file mode 100644
index 0000000..dd45f08
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif
new file mode 100644
index 0000000..555ef53
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif
new file mode 100644
index 0000000..3621342
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif
new file mode 100644
index 0000000..9e44ce5
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif
new file mode 100644
index 0000000..b26c527
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif
new file mode 100644
index 0000000..56964c1
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif
new file mode 100644
index 0000000..8bf3f97
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif
new file mode 100644
index 0000000..11d7958
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif
new file mode 100644
index 0000000..a113cf4
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif
new file mode 100644
index 0000000..75f33c2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties
new file mode 100644
index 0000000..45279a5
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties
@@ -0,0 +1 @@
+Plugin.name = XML schema editor
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml
new file mode 100644
index 0000000..9f5a148
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml
@@ -0,0 +1,19 @@
+<?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>
+
+ <extension point="org.eclipse.help.toc">
+ <toc file="XSDeditormap_toc.xml"/>
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html
new file mode 100644
index 0000000..1a08bdd
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html
@@ -0,0 +1,35 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Working with XML schemas</title>
+</head>
+<body id="workingwithxmlschemas"><a name="workingwithxmlschemas"><!-- --></a>
+<h1 class="topictitle1">Working with XML schemas</h1>
+<div><p>This sections contains information on the following:</p>
+</div>
+<p><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div>
+<div><a href="timpschm.html" title="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema.">Importing XML schemas</a></div>
+<div><a href="tnavsrc.html" title="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to.">Navigating XML schemas</a></div>
+<div><a href="tedtpref.html" title="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used.">Editing XML schema file preferences</a></div>
+<div><a href="tdelscmp.html" title="If you have created any XML schema components you no longer need, you can delete them.">Deleting XML schema components</a></div>
+<div><a href="tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div>
+<p class="relref"><strong>Related reference</strong><br />
+<div><a href="rxsdicons.html" title="The following XML schema editor icons appear in the Outline, Graph, and Properties view.">Icons used in the XML schema editor</a></div>
+<div><a href="rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
new file mode 100644
index 0000000..5697286
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
@@ -0,0 +1,71 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>XML schema editor</title>
+</head>
+<body id="cxmlsced"><a name="cxmlsced"><!-- --></a>
+
+<h1 class="topictitle1">XML schema editor</h1>
+<div><p>XML schemas are an XML language for describing and constraining the
+the content of XML files.</p>
+<p>XML schemas are a formal specification of element names that indicates
+which elements are allowed in an XML file, and in which combinations. A schema
+is functionally equivalent to a DTD, but is written in XML; a schema also
+provides for extended functionality such as data typing, inheritance, and
+presentation rules.</p>
+<p>For more information on XML schema, refer to:</p>
+<ul><li> <a href="http://www.w3.org/TR/xmlschema-0/" target="_blank">http://www.w3.org/TR/xmlschema-0/</a> </li>
+<li> <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">http://www.w3.org/TR/xmlschema-1/</a> </li>
+<li> <a href="http://www.w3.org/TR/xmlschema-2/" target="_blank">http://www.w3.org/TR/xmlschema-2/</a> </li>
+</ul>
+<p>This product provides an XML schema editor for creating, viewing, and validating
+XML schemas. Using the XML schema editor, you can:</p>
+<ul><li>Create and delete XML schema components such as complex types, simple
+types, elements, attributes, attribute groups, and groups</li>
+<li>Edit XML schemas</li>
+<li>Import existing XML schemas for structured viewing</li>
+</ul>
+<p>The XML Schema specification from the W3C Web site is used for validation.</p>
+<div class="skipspace"><h4 class="sectiontitle">XML schema editor views - Graph, Outline, Properties, and
+Source</h4>There are four main views you can work with in the XML schema
+editor:<ul><li>Graph - the Graph view provides a graphical way to edit your schema</li>
+<li>Outline - the Outline view shows you the main components in your XML schema.
+You can use this view to add and remove certain components.</li>
+<li>Properties - the Properties view enables you to edit the properties of
+your XML schema components</li>
+<li>Source - the Source view enables you to edit your source code directly</li>
+</ul>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Status of the XML schema</h4><p></p>
+<p>Three status indicators
+for the schema are available. They are in the bottom right corner:</p>
+<ul><li> <span class="uicontrol">Writable</span> or <span class="uicontrol">Read Only</span>. </li>
+<li> (Source view only) <span class="uicontrol">Smart Insert</span> or <span class="uicontrol">Overwrite</span>.
+To toggle between these modes, press the <span class="uicontrol">Insert</span> button
+on your keyboard.</li>
+<li> <span class="uicontrol">Line</span> and <span class="uicontrol">column</span> number. </li>
+</ul>
+</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor.">Creating XML schemas</a><br />
+<a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a><br />
+<a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating an XML schema</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
new file mode 100644
index 0000000..3686085
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
@@ -0,0 +1,255 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>XML namespaces</title>
+</head>
+<body id="rnmspc"><a name="rnmspc"><!-- --></a>
+
+<h1 class="topictitle1">XML namespaces</h1>
+<div><p>An XML namespace is a collection of names, identified by a URI
+reference, which are used in XML documents as element types and attribute
+names.</p>
+<div><div class="skipspace">XML namespaces are defined by a W3C recommendation, dating 14 January
+1999, called <a href="http://www.w3.org/TR/REC-xml-names/">Namespaces
+in XML</a>. XML tag names should be globally unique, as well as short for
+performance reasons. In order to resolve this conflict, the W3C namespace
+recommendation defines an attribute xmlns which can amend any XML element.
+If it is present in an element, it identifies the namespace for this element.</div>
+<div class="skipspace"><p>The xmlns attribute has the following syntax:</p>
+<p><samp class="codeph"> xmlns: <var class="varname">prefix</var>:namespace</samp> </p>
+<p>where <samp class="codeph">namespace</samp> is a unique URI (such as www.ibm.com) and where <samp class="codeph"><var class="varname">prefix</var></samp> represents
+the namespace and provides a pointer to it.</p>
+<p>In the following customer
+element definition, an accounting namespace is defined in order to be able
+to distinguish the element tags from those appearing in customer records created
+by other business applications:</p>
+<div class="p"><pre><acct:customer xmlns:acct="http://www.my.com/acct-REV10">
+ <acct:name>Corporation</acct:name>
+ <acct:order acct:ref="5566"/>
+ <acct:status>invoice</acct:status>
+</acct:customer> </pre>
+ </div>
+<p>The <i>namespace definition</i> in
+the first line assigns the namespace <i>http://www.my.com/acct-REV10</i> to
+the prefix. This prefix is used on the element names such as name in order
+to attach them to the namespace. A second application, for example, a fulfillment
+system, can assign a different namespace to its customer elements:</p>
+<div class="p"><pre><ful:customer xmlns:ful="http://www.your.com/ful">
+ <ful:name>Corporation</ful:name>
+ <ful:order ful:ref="A98756"/>
+ <ful:status>shipped</ful:status>
+ </ful:customer></pre>
+ </div>
+<p>An application processing both data
+structures is now able to treat the accounting and the fulfillment data differently.
+There is a default namespace. It is set if no local name is assigned in the
+namespace definition:</p>
+<div class="p"><pre><acct:customer xmlns="http://www.my.com/acct-REV10" xmlns:acct="http://www.my.com/acct-REV10 ">
+<name>Corporation</name>
+<order acct:ref="5566"/>
+<status>invoice</status>
+</customer></pre>
+</div>
+<p>In this example, all tags in the customer
+record are qualified to reside in the namespace <i>http://www.my.com/acct-REV10.</i> No
+explicit prefix is needed because the default namespace is used. Note that
+the default namespace applies to any attributes definitions.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">XML schemas and namespaces</h4><p>In the XML schema below,
+the default namespace for the schema is defined as the standard XML schema
+namespace <i>http://www.w3.org/2001/XMLSchem</i>a; there is also a schema
+specific namespace <i>http://www.ibm.com</i>.</p>
+<div class="p"><pre><?xml version="1.0">
+<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:TestSchema="http://www.ibm.com">
+ <simpleType name="ZipCodeType">
+ <restriction base="integer">
+ <minInclusive value="10000"/>
+ <maxInclusive value="99999"/>
+</restriction>
+ </simpleType>
+ <!--element definitions skipped -->
+</schema> </pre>
+</div>
+<p>Assuming that the preceding XML schema is
+is saved as <span class="filepath">C:\temp\TestSchema.xsd</span>, a sample XML file
+that validates against this schema is:</p>
+<div class="p"><pre><?xml version="1.0">
+<x:addressList xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd">
+ xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd">
+<x:address>
+ <x:street>x:Vangerowstrasse</x:street>
+ <x:zipCode>69115</x:zipCode>
+ <x:city>x:Heidelberg</x:city>
+ </x:address>
+ <x:address>
+<x:street>x:Bernal Road</x:street>
+<x:zipCode>90375</x:zipCode>
+ <x:city>x:San Jose</x:city>
+ </x:address>
+</x:addressList> </pre>
+</div>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Target namespace</h4><p> The target namespace serves to
+identify the namespace within which the association between the element and
+its name exists. In the case of declarations, this association determines
+the namespace of the elements in XML files conforming to the schema. An XML
+file importing a schema must reference its target namespace in the schemaLocation
+attribute. Any mismatches between the target and the actual namespace of an
+element are reported as schema validation errors. In our example, the target
+namespace is http://www.ibm.com; it is defined in the XML schema file and
+referenced twice in the XML file. Any mismatch between these three occurrences
+of the namespace lead to validation errors.</p>
+<p> The following examples
+show how target namespaces and namespace prefixes work in XML schemas and
+their corresponding XML instance documents.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Sample 1 - A schema with both a default and target namespace
+and unqualified locals</h4><p>The XML schema: </p>
+<div class="p"><pre><?xml version="1.0">
+<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com">
+<complexType name="AddressType">
+<sequence>
+<element name="name" type="string"></element>
+</sequence>
+</complexType>
+<element name="MyAddress" type="x:AddressType"></element>
+</schema> </pre>
+ </div>
+<p>A valid XML instance document created from
+this schema looks like this. Local elements and attributes are <i>unqualified</i>.</p>
+<div class="p"><pre><?xml version="1.0">
+<x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com x.xsd ">
+<name>Peter Smith</name>
+</x:MyAddress> </pre>
+</div>
+<p>When local elements (such as the <i>"name"</i> element)
+and attributes are unqualified in an XML file, then only the root element
+is qualified. So, in this example, the <i>"x"</i> namespace prefix is assigned
+to the root element <i>"MyAddress"</i>, associating it with the namespace <i>"http://www.ibm.com",</i> but
+the<i>"x"</i> prefix is not assigned to the local element <i>"name"</i>.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Sample 2 - A schema with both a default and target namespace
+and qualified locals</h4><div class="p"><pre><?xml version="1.0">
+<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com" elementFormDefault="qualified">
+<complexType name="AddressType">
+<sequence>
+<element name="name" type="string"></element>
+</sequence>
+</complexType>
+<element name="MyAddress" type="x:AddressType"></element>
+ </schema> </pre>
+</div>
+<p>A valid XML instance document created from
+this schema looks like this. Local elements and attributes are <i>qualified</i> This
+is because the elementFormDefault attribute is set to qualified in the XML
+schema.</p>
+<div class="p"><pre><?xml version="1.0">
+ <x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.ibm.com x.xsd ">
+<x:name>Peter Smith</x:name>
+ </x:MyAddress></pre>
+ </div>
+<p>In this example, the <i>"x"</i> namespace
+prefix is assigned to both the root element <i>"MyAddress"</i> and the local
+element <i>"name"</i>, associating them with the namespace <i>"http://www.ibm.com",</i>.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Sample 3 - Schema with target Namespace, and explicitly defines
+xmlns:xsd</h4><p>This XML schema adds this attribute: </p>
+<samp class="codeph">xmlns:xsd="http://www.w3.org/2001/XMLSchema </samp><p>What
+this means is that each of the constructs that are defined by the XML schema
+language will need to be qualified with the <var class="varname">"xsd"</var> prefix.
+For example, xsd:complexType and xsd:string</p>
+<p>. Note that you can chose
+any other prefixes such as <var class="varname">"xs"</var> or <var class="varname">"foobar"</var> in
+your declaration and usage.</p>
+<p>You can specify this prefix in the XML Schema
+preferences page. For more information, refer to the related tasks below.</p>
+<p>All
+user defined types belong to the namespace http://www.ibm.com as defined
+by the targetNamespace attribute, and the prefix is <i>"x"</i> as defined
+by the xmlns:x attribute.</p>
+<div class="p"><pre><?xml version="1.0">
+<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com">
+<xsd:complexType name="AddressType">
+<xsd:sequence>
+ <xsd:element name="name" type="xsd:string"></xsd:element>
+</xsd:sequence>
+ </xsd:complexType>
+ <xsd:element name="MyAddress" type="x:AddressType"></xsd:element>
+</xsd:schema></pre>
+ </div>
+<p>A valid XML instance document created
+from this schema looks like this. Local elements and attributes are <i>unqualified</i>.
+The semantics of qualification is the same as Sample 1.</p>
+<div class="p"><pre><?xml version="1.0">
+ <x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com x.xsd ">
+<name>Peter Smith</name>
+ </x:MyAddress></pre>
+</div>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Sample 4 - Schema with undeclared target Namespace that explicitly
+defines xmlns:xsd</h4><p>This XML schema has no target namespace for itself.
+In this case, it is highly recommended that all XML schema constructs be explicitly
+qualified with a prefix such as <i>"xsd"</i>. The definitions and declarations
+from this schema such as <i>AddressType</i> are referenced without namespace
+qualification since there is no namespace prefix. </p>
+<div class="p"><pre><?xml version="1.0">
+<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
+<xsd:complexType name="AddressType">
+<xsd:sequence>
+<xsd:element name="name" type="xsd:string"></xsd:element>
+<xsd:element name="name" type="xsd:string"></xsd:element>
+<xsd:element name="name" type="xsd:string"></xsd:element>
+</xsd:sequence>
+</xsd:complexType>
+<xsd:element name="MyAddress" type="AddressType"></xsd:element>
+</xsd:schema> </pre>
+</div>
+<p>A valid XML instance document created
+from the schema looks like this. All elements are <i>unqualified</i>.</p>
+<div class="p"><pre><?xml version="1.0">
+<MyAddress xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="x.xsd">
+<name>name</name>
+</MyAddress></pre>
+ </div>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Sample 5 - A schema where the target namespace is the default
+namespace</h4><p>This is an XML schema where the target namespace is the
+default namespace. As well, the namespace has no namespace prefix.</p>
+<div class="p"><pre><?xml version="1.0">
+ <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns="http://www.ibm.com">
+<xsd:complexType name="AddressType">
+<xsd:sequence>
+<xsd:element name="name" type="xsd:string"></xsd:element>
+</xsd:sequence>
+</xsd:complexType>
+ <xsd:element name="MyAddress" type="AddressType"></xsd:element>
+ </xsd:schema> </pre>
+ </div>
+<p>A valid XML instance document created
+from the schema looks like this:</p>
+<div class="p"><pre><?xml version="1.0" encoding="UTF-8">
+<MyAddress xmlns="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com NewXMLSchema.xsd">
+<name>name</name>
+ </MyAddress> </pre>
+ </div>
+</div>
+</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tedtpref.html" title="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used.">Editing XML schema file preferences</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
new file mode 100644
index 0000000..8c33e5f
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
@@ -0,0 +1,92 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Referential integrity</title>
+</head>
+<body id="rrefintg"><a name="rrefintg"><!-- --></a>
+
+<h1 class="topictitle1">Referential integrity in the XML schema editor</h1>
+<div><p>The XML schema editor has a built-in mechanism to handle referential
+integrity issues. When you delete certain nodes, clean up for any nodes affected
+will automatically occur.</p>
+<div><p>When you define a complex type, you can add a content model to
+it and reference a global element. </p><div class="skipspace"><div class="p">For example:<pre><schema>
+ <element name="comment" type="string">
+ <complexType name="Items">
+ <sequence>
+ <element ref="comment">
+ </sequence>
+ </complexType>
+</schema></pre>
+</div>
+<p>If the global element (comment) was deleted,
+all references to it would be in error. However, when you delete the global
+element, the XML schema editor will clean up using the following algorithm:</p>
+<ul><li>If there are one or more global elements in the schema, it will change
+all existing references to the first global element.</li>
+<li>If there is no global element, then it will delete the element reference
+from the content model.</li>
+</ul>
+<p>Similar cleanup operations are performed when other types of objects
+are deleted. The following lists describes various cleanup operations. </p>
+<p>Deleting
+a global attribute will cause the following cleanup:</p>
+<ul><li>Any item that references the deleted global attribute will be reset using
+the preceding algorithm.</li>
+</ol>
+ </ul>
+ <p>Deleting a complex type will cause the following cleanup:</p>
+ <ul>
+ <li>Any element type that is set to the deleted complex type will be reset
+to the <tt class="sysout">string</tt> type.</li>
+ <li>Any complex type that derives from the deleted complex type will be reset
+to no derivation.</li>
+ </ul>
+ <p>Deleting a simple type will cause the following cleanup:</p>
+ <ul>
+ <li>Any attribute type that is set to the deleted simple type will be reset
+to the <tt class="sysout">string</tt> type.</li>
+ <li>Any element type that is set to the deleted simple type will be reset
+to the <tt class="sysout">string</tt> type.</li>
+ <li>Any simple type that derives from the deleted simple type will be reset
+to <tt class="sysout">string</tt> as its base type.</li>
+ </ul>
+ <p>Deleting a group or attribute group will cause the following cleanup:</p>
+ <ul>
+ <li>Any complex type that references the deleted group or attribute group
+will be reset using the algorithm similar to the one described earlier for
+deleted global elements.</li>
+ </ul>
+</div>
+<div class="section"><h4 class="sectiontitle">Deleting included and imported schema</h4><div class="p">If an included
+or imported schema is deleted, you must manually reset the following type
+references as appropriate: <ul><li>Global element and element's type</li>
+<li>Attribute type</li>
+<li>Complex type derivation</li>
+<li>Simple type derivation</li>
+</ul>
+They will not automatically be reset if an included or imported schema
+is deleted.</div>
+</div>
+</div>
+<p><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.">XML schema editor</a></div>
+</p>
+<p class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div>
+</div>
+</p></body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html
new file mode 100644
index 0000000..2d6e1c4
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html
@@ -0,0 +1,99 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Icons used in the XML schema editor</title>
+</head>
+<body id="ricons"><a name="ricons"><!-- --></a>
+<h1 class="topictitle1">Icons used in the XML schema editor</h1>
+<div><p>The following XML schema editor icons appear in the Outline, Graph,
+and Properties view.</p>
+<div class="section"></div>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><tbody><tr><td valign="bottom"><strong>Icon</strong></td>
+<td valign="bottom"><strong>Description</strong></td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAnyAttribute.gif" alt="This graphic is the any attribute icon" /></td>
+<td valign="top"><samp class="codeph">any</samp> attribute</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAny.gif" alt="This graphic is the any element icon" /></td>
+<td valign="top"><samp class="codeph">any</samp> element</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttribute.gif" alt="This graphic is the attribute icon" /></td>
+<td valign="top">attribute</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttributeGroup.gif" alt="This graphic is the attribute group icon" /></td>
+<td valign="top">attribute group</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttributeGroupRef.gif" alt="This graphic is the attribute group reference icon" /></td>
+<td valign="top">attribute group reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttributeRef.gif" alt="This graphic is the attribute reference icon" /></td>
+<td valign="top">attribute reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAll.gif" alt="This graphic is the content model - all icon" /></td>
+<td valign="top">content model - all</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDChoice.gif" alt="This graphic is the content model - choice icon" /></td>
+<td valign="top">content model - choice</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSequence.gif" alt="This graphic is the content model - sequence icon" /></td>
+<td valign="top">content model - sequence</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDComplexType.gif" alt="This graphic is the any element icon" /></td>
+<td valign="top">complex type</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDElement.gif" alt="This graphic is the element icon" /></td>
+<td valign="top">element</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDElementRef.gif" alt="This graphic is the element reference icon" /></td>
+<td valign="top">element reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSimpleEnum.gif" alt="This graphic is the enumeration icon" /></td>
+<td valign="top">enumeration</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDGlobalAttribute.gif" alt="This graphic is the global attribute icon" /></td>
+<td valign="top">global attribute</td>
+</tr>
+<tr><td valign="top"> <img src="../images/XSDGlobalElement.gif" alt="This graphic is the global element icon" /></td>
+<td valign="top">global element</td>
+</tr>
+<tr><td valign="top"> <img src="../images/XSDGroup.gif" alt="This graphic is the group icon" /></td>
+<td valign="top">group</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDGroupRef.gif" alt="This graphic is the group reference icon" /></td>
+<td valign="top">group reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDImport.gif" alt="This graphic is the import icon" /></td>
+<td valign="top">import</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDInclude.gif" alt="This graphic is the include icon" /></td>
+<td valign="top">include</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSimplePattern.gif" alt="This graphic is the pattern icon" /></td>
+<td valign="top">pattern</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDRedefine.gif" alt="This graphic is the redefine icon" /></td>
+<td valign="top">redefine</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSimpleType.gif" alt="This graphic is the simple type icon" /></td>
+<td valign="top">simple type</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div></div></body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
new file mode 100644
index 0000000..22106ed
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
@@ -0,0 +1,101 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding attribute groups</title>
+</head>
+<body id="taddagrp"><a name="taddagrp"><!-- --></a>
+
+<h1 class="topictitle1">Adding attribute groups</h1>
+<div><p>An attribute group definition is an association between a name
+and a set of attribute declarations. Named groups of attribute declarations
+can greatly facilitate the maintenance and reuse of common attribute declarations
+in an XML schema.</p>
+<div class="section"><p>The following instructions were written for the Resource perspective,
+but they will also work in many other perspectives.</p>
+<p>To add an
+attribute group to an XML schema, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, right-click the XML schema and click
+<b> <span class="uicontrol">Add
+Attribute Group</span></b>.</span> It appears in the <span class="uicontrol">Attribute
+Groups</span> folder.</li>
+<li class="skipspace"><span>Select your new group, and in the Properties view, type a name
+for the attribute group in the <b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>To add an attribute, right-click your attribute group in the Outline
+view, click <b> <span class="uicontrol">Add Attribute</span></b>.</span> The attribute
+appears below the attribute group in the Outline view.<ol type="a"><li class="skipspace"><span>Select the attribute, and in the Properties view, type the
+ <b> <span class="uicontrol">Name</span></b> of it.</span></li>
+<li><span>Click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button and specify the
+type for the attribute. The</span> Set Type dialog lists all built-in and
+user-defined types currently available. You can change the <b>
+<span class="uicontrol">Scope</span></b> of the list by selecting one of the
+following options:
+<ul>
+ <li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types
+ available in your workspace. </li>
+ <li><b><span class="uicontrol">Enclosing Project</span>.</b> Lists all of
+ the types available in the project that contains your file. </li>
+ <li>(Default) <b><span class="uicontrol">Current Resource</span>.</b> List
+ all of the types available in your current file.</li>
+</ul>
+ </li>
+</ol>
+</li>
+<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
+To add an attribute reference, right-click your attribute group, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b></span> A declaration that references a global
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference (which appears below the attribute group
+in the Outline view), then select the global attribute you want it to reference
+from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
+group. To add an attribute group reference, right-click your attribute group,
+and click <span class="uicontrol"><b>Add Attribute Group Ref</b></span>, and fill in the
+field values as necessary.</span> A declaration that references an attribute
+group enables the referenced attribute group to appear in the instance document
+in the context of the referencing declaration. The menu option to add an attribute
+group reference only appears if there are attribute groups defined elsewhere
+in the document.<ol type="a"><li><span>Select the reference (which appears below the attribute group
+in the Outline view), then select the attribute group you want it to reference
+from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute
+element enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click your attribute group and click <b> <span class="uicontrol">Add Any Attribute</span></b>.</span> The <samp class="codeph">any</samp> attribute
+appears below the attribute group in the Outline
+view. You can specify the following values for an <samp class="codeph">any</samp> attribute:<ul><li>For a <b>namespace</b> value, you can select <b>##any</b> (this allows
+any well-formed XML from any namespace), <b>##local </b> (this allows any
+well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
+allows any well-formed XML that is not from the target namespace of the type
+being defined) or <b>##targetNamespace </b> (which is shorthand for the target
+namespace of the type being defined). </li>
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
+XML processor will not validate the attribute content at all), <b>lax</b> (the
+XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
+XML processor will validate all the attribute content).</li>
+</ul>
+ </li>
+</ol>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
new file mode 100644
index 0000000..a10c6b2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
@@ -0,0 +1,71 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding an any element</title>
+</head>
+<body id="taddanye"><a name="taddanye"><!-- --></a>
+
+<h1 class="topictitle1">Adding an any element</h1>
+<div><p>You can use the <samp class="codeph">any</samp> element to provide something
+similar to a DTD's ANY content model, however, it must be done in conjunction
+with namespaces. This enables you to include any well-formed XML content,
+such as an HTML Web page that conforms to XHTML 1.0 syntax.</p><div class="skipspace"><p>For example:</p>
+<div class="p"><pre><element name = "MyWebPage">
+<complexType>
+<any namespace ="http://www.w3.org/1999/xhtml>
+ < minOccurs="1" maxOccurs="unbounded" processContents="skip"/>
+</complexType>
+</element></pre>
+</div>
+<p>The preceding schema fragment allows a <var class="varname"><MyWebPage></var> element
+to contain any well-formed XHTML data that appears in the specified namespace.</p>
+<p>The following instructions were written for the Resource perspective, but
+they will also work in many other perspectives.</p>
+<p>To add an <samp class="codeph">any</samp> element,
+follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Outline view, right-click the content model that you want
+to work with and click <b> <span class="uicontrol">Add Any</span></b>. </span></li>
+<li class="skipspace"><span>Select the new <samp class="codeph">any</samp> element.</span></li>
+<li class="skipspace"><span>In the Properties view of the schema editor, for a <b>namespace</b> value,
+you can select <b>##any</b> (this allows any well-formed XML from any namespace), <b>##local </b> (this
+allows any well-formed XML that is not declared to be in a namespace), <b>##other </b> (this
+allows any well-formed XML that is not from the target namespace of the type
+being defined) or <b>##targetNamespace </b> (which is shorthand for the target
+namespace of the type being defined). </span></li>
+<li class="stepexpand"><span>For a <span class="uicontrol">processContents</span> value, you can select <strong>skip</strong> (the
+XML processor will not validate the content at all), <strong>lax</strong> (the XML processor
+will validate the content as much as it can), or <strong>strict </strong> (the XML processor
+will validate all the content).</span></li>
+<li class="stepexpand"><span>The <span class="uicontrol">minOccurs</span> value is the number of times
+the <samp class="codeph">any</samp> element must appear in an instance document. You
+can select <span class="uicontrol">0</span> if you want the element to be optional;
+otherwise, select <span class="uicontrol">1</span>. </span></li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">maxOccurs </span>value</b> is the maximum number
+of times an <samp class="codeph">any</samp> element may appear. You can select <span class="uicontrol">0</span>, <span class="uicontrol">1</span>,
+or, to indicate there is no maximum number of occurrences, <span class="uicontrol">unbounded</span>.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+<div class="skipspace"><p>(c) Copyright 2001, World Wide Web (Massachusetts Institute of
+Technology, Institut National de Recherche en Informatique et en Automatique,
+Keio University).</p>
+</div>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
new file mode 100644
index 0000000..a17d228
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
@@ -0,0 +1,100 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding a content model</title>
+</head>
+<body id="taddcmod"><a name="taddcmod"><!-- --></a>
+
+<h1 class="topictitle1">Adding content models</h1>
+<div><p>A content model is the representation of any data that can be contained
+inside an element, global element, complex type, or group. It is a formal
+description of the structure and permissible content of an element, global
+element, complex type, or group, which may be used to validate a document
+instance.</p>
+<div class="section"><div class="p">There are three different kinds of content models:<ul><li><strong>Sequence</strong>, which means that all the content model's children can
+appear in an instance of the XML schema. They must, however, appear in the
+order they are listed in the content model.</li>
+<li><b>Choice</b>, which means that only one of the content model's children
+can appear in an instance of the XML schema.</li>
+<li><b>All</b>, which means that all of the content model's children can appear
+once or not at all, and they may appear in any order. If you select this option,
+all of the contents model's children must be individual elements and no element
+in the content model may appear more than once</li>
+</ul>
+</div>
+<p>The following instructions were written for the Resource perspective, but
+they will also work in many other perspectives.</p>
+<p>To add a content
+model to an element, global element, complex type, or group, follow these
+steps:</p>
+</div>
+<ol><li class="stepexpand"><span>In the Outline view, select your element, global element, complex
+type, or group:</span><ul><li>If you selected an element or global element, you can right-click
+it, and click <span class="uicontrol">Add Sequence</span>, <span class="uicontrol">Add Choice</span>,
+or <b> <span class="uicontrol">Add All</span></b> to add the type of content model you want
+to your element or global element. Your content model is automatically added
+as a child of a local complex type - expand your element or global element
+in the Outline view to see it.</li>
+<li>If you selected a complex type, you can right-click it and click <b> <span class="uicontrol">Add
+Sequence</span></b>, <b> <span class="uicontrol">Add Choice</span></b>, or <b> <span class="uicontrol">Add
+All</span></b> to add the type of content model you want to your complex
+type. Your content model is automatically added as a child of your complex
+type - expand in the Outline view to see it. <b>Note: </b>These
+options will not appear if you have set a base type for your complex type.
+You can either set a base type for your complex type, or you add a content
+model to it, but you cannot do both.</li>
+<li>Your group is automatically created with a sequence content model
+child. Expand it in the Outline view to see it and select it. In the Properties
+view, you can select to change it to a <b> <span class="uicontrol">choice</span></b> or
+<b> <span class="uicontrol">all</span></b> content
+model by selecting these options from the <b> <span class="uicontrol">Kind</span></b> drop
+down list.</li>
+</ul>
+</li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MinOccurs</span></b> field.</span> This is the number of times the content model must appear. If you want
+the content model to be optional, select <b> <span class="uicontrol">0</span></b>. Otherwise,
+select <b> <span class="uicontrol">1</span></b>. </li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MaxOccurs</span></b> field.</span> This is the maximum number of times a content model may appear. You
+can select <span class="uicontrol">unbounded</span> to indicate there is no maximum
+number of occurrences.</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this content model.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+<div class="skipspace"><p>You can add the following to a content object model. </p>
+<ul><li>Another content model.</li>
+<li>A group reference which enables the referenced group to appear in the
+instance document in the context of the referencing declaration. This
+menu option only appears if there are global groups defined elsewhere in the
+document or if groups are defined in included schemas.</li>
+<li>An element, fundamental building blocks in XML.</li>
+<li>An element reference, which provides a reference to a global element.
+This menu option only appears if there are global elements defined elsewhere
+in the document.</li>
+<li>An <samp class="codeph">any</samp> element. You can use an <samp class="codeph">any</samp> element
+to extend your content model by any elements belonging to a specified namespace.</li>
+</ul>
+</div>
+</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddanye.html" title="You can use the any element to provide something similar to a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div>
+<div><a href="../topics/taddelm.html" title="Elements are fundamental building blocks in XML. Element declarations provide value constraints, and a description that can be used for validation, as well as establishing constraining relationships between related elements and attributes, and controlling substitution of elements.">Adding elements</a></div>
+<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div>
+<div><a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.">Adding group references</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
new file mode 100644
index 0000000..a8fc3a2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
@@ -0,0 +1,143 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding a complex type</title>
+</head>
+<body id="taddcmxt"><a name="taddcmxt"><!-- --></a>
+
+<h1 class="topictitle1">Adding complex types</h1>
+<div><p>A complex type allows elements in its content and can carry attributes.
+Complex types can be used to help determine the appropriate content for any
+instance documents generated from or associated with your XML schema.</p>
+<div class="section"><p>You can add as many complex types as you want to an 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
+add a complex type to an XML schema, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, select your schema.</span></li>
+<li class="skipspace"><span>In the Graph view, right click in the <b>Types</b> section and
+click <b> <span class="uicontrol">Add Complex Type</span></b>.</span></li>
+<li class="skipspace"><span>In the Properties view, type a new name for the complex type in
+the <b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> to select a base type
+for your complex type.</span> You can either set a base type for your
+complex type, or you add a content model to it (which represents any data
+that may be contained inside an element), but you cannot do both. For more
+information about content models, refer to the related tasks.</li>
+<li class="stepexpand"><span>Select <span class="uicontrol">restriction</span> or <span class="uicontrol">extension</span> from
+the <span class="uicontrol">Derived by</span> list.</span> This specifies whether
+your type is derived from its base type by restriction or extension.</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span> The following
+optional values can be specified in this page:<ol type="a"><li class="skipspace"><span>Select the appropriate value in the
+ <b> <span class="uicontrol">abstract</span></b> list.</span> When a complex type is declared abstract, it cannot be used in an instance
+document. Click <b>true</b> if you want the complex type to be abstract; otherwise,
+click <b>false</b>.</li>
+<li class="skipspace"><span>Select the appropriate value in the <b> <span class="uicontrol">block</span></b> list.</span> If you select <b>#all</b>, the complex type may not be replaced by any
+derivations. If you select <b>extension</b>, the complex type may not be replaced
+by any type derived from it by extending it. If you select <b>restriction</b>,
+the complex type may not be replaced by any type derived from it by restricting
+it.</li>
+<li class="skipspace"><span> Select the appropriate value in the <b> <span class="uicontrol">final</span></b> list.</span> If you select <b>#all</b>, the complex type may not be derived from
+at all. If you select <b>extension</b>, the complex type may not be derived
+from by extension. If you select <b>restriction</b>, the complex type may
+not be derived from by restriction.</li>
+<li class="skipspace"><span>Select the appropriate value in the <b> <span class="uicontrol">mixed</span></b> list.</span> If you click <b>true</b>, the complex type can contain mixed content
+(both character data and other elements). If you click <b>false</b>, the complex
+type can only contain other elements.</li>
+</ol>
+</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> tab.</span> You
+can use this page to add attributes, attribute references, attributes group
+references, and <samp class="codeph">any</samp> attributes to your complex type.</li>
+<li class="skipspace"><span>An attribute associates an attribute name with a specific type
+and value. To add an attribute, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute</span></b>.</span> You can specify the following values for
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span></b>. Click the
+ <b> <span class="uicontrol">More</span></b> button <span>
+ <img border="0" src="../images/More.gif" width="22" height="18"></span>
+and select the <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
+button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
+has a fixed value, which cannot be changed. If you select <b>Default</b>,
+the attribute has a default value. When an attribute has a default value,
+the value of the attribute is whatever value appears as the attribute's value
+in an instance document.</li>
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
+of this attribute in an instance of the XML schema must be qualified by a
+namespace.</li>
+<li><span class="uicontrol"><b>name</b>. </span>Enter the name of the attribute.</li>
+<li><span class="uicontrol"><b>type</b>. </span>Click the <b> <span class="uicontrol">More</span></b> button <span>
+<img border="0" src="../images/More.gif" width="22" height="18"></span>
+and select the type of the attribute. </li>
+<li><span class="uicontrol"><b>use</b>. </span>This field indicates how an attribute may
+be used in an instance document. If you select <b>optional</b>, the attribute
+may appear once, but it does not have to. If you select <b>required</b>, the
+attribute must appear once. If you select <b>prohibited</b>, the attribute
+must not appear. <b>Note</b>: If you selected the <b> <span class="uicontrol">Default</span></b> radio
+button, you must select <b>optional</b> in this field, otherwise the default
+value will not be valid.</li>
+</ul>
+</li>
+<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b> </span>A declaration that references a global
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
+group. To add an attribute group reference, right-click in the Attributes
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref. </span></b></span> A
+declaration that references an attribute group enables the referenced attribute
+group to appear in the instance document in the context of the referencing
+declaration. The menu option to add an attribute group reference only appears
+if there are attribute groups defined elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the attribute group you want
+it to reference from the<span class="uicontrol"> <b>ref</b></span> drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute
+element enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page, and click <b> <span class="uicontrol">Add Any Attribute</span></b>.</span> You can specify the following values for an <samp class="codeph">any</samp> attribute:<ul><li>For a <b>namespace</b> value, you can select <b>##any</b> (this allows
+any well-formed XML from any namespace), <b>##local </b> (this allows any
+well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
+allows any well-formed XML that is not from the target namespace of the type
+being defined) or <b>##targetNamespace </b> (which is shorthand for the target
+namespace of the type being defined). </li>
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
+XML processor will not validate the attribute content at all), <b>lax </b>(the
+XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
+XML processor will validate all the attribute content).</li>
+</ul>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this complex type.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddcmod.html" title="You can add a content model to an element, global element, a complex type, or a group. A content model is the representation of any data that may be contained inside the element, global element, complex type, or group.">Adding a content model</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
new file mode 100644
index 0000000..55d2288
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
@@ -0,0 +1,168 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding elements</title>
+</head>
+<body id="taddelm"><a name="taddelm"><!-- --></a>
+
+<h1 class="topictitle1">Adding elements</h1>
+<div><p>Elements are fundamental building blocks in XML. Element declarations
+ provide value constraints, and a description that can be used for
+ validation, as well as establishing constraining relationships between
+ related elements and attributes, and controlling substitution of elements.</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 add an
+element, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Outline view, right-click the content
+ model you want to
+work with and click <b> <span class="uicontrol">Add Element</span></b>.</span></li>
+<li class="skipspace"><span>In the Properties view, type a new name for the element in the
+<b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Specify its type information by clicking the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and selecting the appropriate type.</span>
+The Set Type dialog lists all built-in and user-defined types currently
+available. You can change the <b><span class="uicontrol">Scope</span></b> of the
+list by selecting one of the following options:
+<div>
+ <ul>
+ <li><b><span class="uicontrol">Workspace</span></b>. Lists all of the
+ types available in your workspace. </li>
+ <li><b><span class="uicontrol">Enclosing Project</span></b>. Lists all
+ of the types available in the project that contains your file. </li>
+ <li>(Default) <b><span class="uicontrol">Current Resource</span>. </b>
+ List all of the types available in your current file. </li>
+ </ul>
+</div>
+ </li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b>
+<span class="uicontrol">MinOccurs</span></b> field.</span> This is the number of times the element may appear. If you want the
+element to be optional, select <b><span class="uicontrol">0</span></b>. Otherwise, select
+<b><span class="uicontrol">1</span></b>. </li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MaxOccurs</span></b> field.</span> This is the maximum number of times the element may appear. You can
+select <b> <span class="uicontrol">unbounded</span></b> to indicate there is no maximum number
+of occurrences.</li>
+<li class="skipspace">
+<div>
+ (Optional) Click the <b><span class="uicontrol">Other</span></b> tab. In
+ this page, you can specify the following various values for the element:
+ <ul>
+ <li><b><span class="uicontrol">block</span></b>. This field determines
+ whether the element may be replaced by an element derived from it. </li>
+ <li><b><span class="uicontrol">fixed/default</span>.</b> Click the <b>
+ <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and
+ select the <b><span class="uicontrol">Fixed</span></b> or <b>
+ <span class="uicontrol">Default</span></b> radio button and specify an
+ appropriate value. If you select <strong>Fixed</strong>, the element has
+ a fixed value, which cannot be changed. If you select <strong>Default</strong>,
+ the element has a default value. </li>
+ <li><b><span class="uicontrol">form</span></b>. Use this field to
+ indicate if the appearance of this element in an instance of the XML
+ schema (that is, an XML file associated with the XML schema) must be
+ qualified by a namespace. </li>
+ <li><b><span class="uicontrol">maxOccurs</span></b>. This is the minimum
+ number of times the element can appear in an instance document. You can
+ specify this option here or in the General page. </li>
+ <li><b><span class="uicontrol">minOccurs</span></b>. This is the maximum
+ number of times the element can appear in an instance document. You can
+ specify this option here or in the General page. </li>
+ <li><b><span class="uicontrol">nillable</span></b>. Select <strong>true</strong>
+ if you do not want the element to be able to have any child elements,
+ only attributes. </li>
+ </ul>
+</div>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> tab.</span> You
+can use this page to add attributes, attribute references, attributes group
+references, and <samp class="codeph">any</samp> attributes to your element.</li>
+<li class="skipspace"><span>An attribute associates an attribute name with a specific type
+and value. To add an attribute, right-click in the Attributes page, and click<b> <span class="uicontrol">Add
+Attribute</span>.</b></span> You can specify the following values for
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span>.</b> Click the
+ <b> <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and select the
+ <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
+button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
+has a fixed value, which cannot be changed. If you select <b>Default</b>,
+the attribute has a default value.</li>
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
+of this attribute in an instance of the XML schema must be qualified by a
+namespace.</li>
+<li><b><span class="uicontrol">name</span></b>. Enter the name of the attribute.</li>
+<li><b><span class="uicontrol">type</span></b>. Click the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and select the type of the attribute. </li>
+<li><b><span class="uicontrol">use</span></b>. This field indicates how an attribute
+may be used in an instance document. If you select <b>optional</b>, the attribute
+may appear once, but it does not have to. If you select <b>required</b>, the
+attribute must appear once. If you select <b>prohibited</b>, the attribute
+must not appear. <b>Note</b>: If you selected the <span class="uicontrol">Default</span> radio
+button, you must select <b>optional</b> in this field, otherwise the default
+value will not be valid.</li>
+</ul>
+</li>
+<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span></b>.</span> A declaration that references a global
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the<span class="uicontrol"> <b>ref</b></span> drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
+group. To add an attribute group reference, right-click in the Attributes
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref</span>.</b></span> A
+declaration that references an attribute group enables the referenced attribute
+group to appear in the instance document in the context of the referencing
+declaration. The menu option to add an attribute group reference only appears
+if there are attribute groups defined elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the attribute group you want
+it to reference from the<span class="uicontrol"> <b>ref</b></span> drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute
+element enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page and click <b> <span class="uicontrol">Add Any Attribute</span>.</b></span> You can specify the following values for an <samp class="codeph">any</samp> attribute:<ul><li>For a <strong>namespace</strong> value, you can select <strong>##any</strong> (this allows
+any well-formed XML from any namespace), <b>##local </b> (this allows any
+well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
+allows any well-formed XML that is not from the target namespace of the type
+being defined) or <b>##targetNamespace </b> (which is shorthand for the target
+namespace of the type being defined). </li>
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
+XML processor will not validate the attribute content at all), <b>lax</b> (the
+XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
+XML processor will validate all the attribute content).</li>
+</ul>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+<div class="skipspace">You can add a content model to an element, which is the representation
+of any data that may be contained inside the element. For more information
+about working with content models, refer to the related tasks.</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddcmod.html" title="You can add a content model to an element, global element, a complex type, or a group. A content model is the representation of any data that may be contained inside the element, global element, complex type, or group.">Adding a content model</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
new file mode 100644
index 0000000..0893b05
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
@@ -0,0 +1,147 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding an element reference</title>
+</head>
+<body id="taddelmr"><a name="taddelmr"><!-- --></a>
+
+<h1 class="topictitle1">Adding element references</h1>
+<div><p>An element reference provides a reference to a global element. A
+ declaration that references a global element enables the referenced global
+element to appear in the instance document in the context of the referencing
+declaration.</p>
+<div class="section"><p>You can modify the contents of your global element directly via
+an element reference. For example, you can add attributes and attribute reference
+to an element reference, but they are actually being added to your global
+element.</p>
+The menu option to add an element reference only appears if there
+are global elements defined elsewhere in the document.<p>The following instructions
+were written for the Resource perspective, but they will also work in many
+other perspectives.</p>
+<p>To add an element reference, follow these
+steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Outline view, right-click the content model you want to
+work with and click <b> <span class="uicontrol">Add Element Ref</span>.</b></span></li>
+<li class="skipspace"><span>Select the element reference.</span></li>
+<li class="skipspace"><span>In the Properties view, select the global element you want to reference
+in the <span class="uicontrol">ref</span> list.</span></li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MinOccurs</span></b> field.</span> This is the number of times the global element referenced may appear.
+If you want the element to be optional, select <span class="uicontrol">0</span>. Otherwise,
+select <span class="uicontrol">1</span>. </li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MaxOccurs</span></b> field.</span> This is the maximum number of times the global element referenced may
+appear. You can select <span class="uicontrol">unbounded</span> to indicate there
+is no maximum number of occurrences.</li>
+<li class="stepexpand"><span>(Optional) Click the <b> <span class="uicontrol">Other</span></b> tab.</span> In
+this page, you can specify the following various values for the global element
+you are referencing: <ul><li><b><span class="uicontrol">abstract</span></b>. Click <strong>true </strong>if you want the
+global element to be abstract. When a global element is declared to be abstract,
+it cannot be used in an instance document. Instead, a member of that global
+element's substitution group must appear in the instance document.</li>
+<li><b><span class="uicontrol">block</span></b>. This field determines whether the global
+element may be replaced by an element derived from it.</li>
+<li><b><span class="uicontrol">final</span></b>. This field determines whether this global
+element may be derived from.</li>
+<li><b><span class="uicontrol">fixed/default</span>.</b> Click the <b> <span class="uicontrol">More</span></b> button
+and select the <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
+button and specify an appropriate value. If you select <strong>Fixed</strong>, the global
+element has a fixed value, which cannot be changed. If you select <strong>Default</strong>,
+the element has a default value.</li>
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
+of this global element in an instance of the XML schema (that is, an XML file
+associated with the XML schema) must be qualified by a namespace.</li>
+<li><b><span class="uicontrol">nillable</span></b>. Select <strong>true</strong> if you do not
+want the global element to be able to have any child elements, only attributes. </li>
+<li><b><span class="uicontrol">substitutionGroup</span></b>. A substitution group allows
+elements to be substituted for other elements.</li>
+</ul>
+</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> tab.</span> You
+can use this page to add attributes, attribute references, attributes group
+references, and <samp class="codeph">any</samp> attributes to your element reference.</li>
+<li class="skipspace"><span>An attribute associates an attribute name with a specific type
+and value. To add an attribute, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute</span></b>.</span> You can specify the following values for
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span>.</b> Click the
+ <b> <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and select the
+ <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
+button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
+has a fixed value, which cannot be changed. If you select <b>Default</b>,
+the attribute has a default value.</li>
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
+of this attribute in an instance of the XML schema must be qualified by a
+namespace.</li>
+<li><b><span class="uicontrol">name</span></b>. Enter the name of the attribute.</li>
+<li><b><span class="uicontrol">type</span></b>. Click the <span class="uicontrol">More</span> button
+and select the type of the attribute. </li>
+<li><b><span class="uicontrol">use</span></b>. This field indicates how an attribute
+may be used in an instance document. If you select <b>optional</b>, the attribute
+may appear once, but it does not have to. If you select <b>required</b>, the
+attribute must appear once. If you select <b>prohibited</b>, the attribute
+must not appear. <b>Note</b>: If you selected the <b> <span class="uicontrol">Default</span></b> radio
+button, you must select <b>optional</b> in this field, otherwise the default
+value will not be valid.</li>
+</ul>
+</li>
+<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b></span> A declaration that references a global
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the <b> <span class="uicontrol">ref</span> </b>drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
+group. To add an attribute group reference, right-click in the Attributes
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref</span></b>.</span> A
+declaration that references an attribute group enables the referenced attribute
+group to appear in the instance document in the context of the referencing
+declaration. The menu option to add an attribute group reference only appears
+if there are attribute groups defined elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the attribute group you want
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
+</ol>
+</li>
+<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element
+enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page and click<b> <span class="uicontrol">Add Any Attribute</span>.</b></span> You can specify the following values for an <samp class="codeph">any</samp> attribute:<ul><li>For a <strong>namespace</strong> value, you can select <strong>##any</strong> (this allows
+any well-formed XML from any namespace), <b>##local </b> (this allows any
+well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
+allows any well-formed XML that is not from the target namespace of the type
+being defined) or <b>##targetNamespace </b> (which is shorthand for the target
+namespace of the type being defined). </li>
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
+XML processor will not validate the attribute content at all), <b>lax </b>(the
+XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
+XML processor will validate all the attribute content).</li>
+</ul>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this element reference.</span> The <span class="uicontrol">Documentation</span> page is used for human readable
+material, such as a description, and the <span class="uicontrol">App Info</span>
+page can be used to provide information for applications.</li>
+</ol>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddglem.html" title="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a complex type definition.">Adding a global element</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
new file mode 100644
index 0000000..fcb254c
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
@@ -0,0 +1,56 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding a global attribute</title>
+</head>
+<body id="taddglba"><a name="taddglba"><!-- --></a>
+
+<h1 class="topictitle1">Adding global attributes</h1>
+<div><p>A global attribute is an attribute that can be recognized anywhere in a
+ document. Once declared, a global attribute can be referenced in one or more
+ declarations using an attribute reference.</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 add a global
+attribute, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+schema and its contents should be displayed in the Graph view.</li>
+<li class="skipspace"><span>In the Graph view, right click in the <b>Attributes</b> section
+and click <b> <span class="uicontrol">Add Global Attribute</span>.</b></span></li>
+<li class="skipspace"><span>In the Properties view, type the attribute <b> <span class="uicontrol">Name</span></b>.</span> </li>
+<li class="skipspace"><span>Click the <b>More</b> button next to the <b> <span class="uicontrol">Type</span></b> field
+to launch the Set Types dialog.</span></li>
+<li class="skipspace"><span>Select the type you want in the type
+list, then click <b> <span class="uicontrol">OK</span></b>. </span>The Set Type dialog lists all built-in and user-defined types currently
+available. You can change the <b> <span class="uicontrol">Scope</span></b> of the list by
+selecting one of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span>.</b> Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default) <b> <span class="uicontrol">Current Resource</span>.</b> List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this global attribute.</span> The <span class="uicontrol">Documentation</span> page is used for human readable
+material, such as a description, and the <span class="uicontrol">App Info</span>
+page can be used to provide information for applications.</li>
+</ol>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
new file mode 100644
index 0000000..d87d4e2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
@@ -0,0 +1,161 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding a global element</title>
+</head>
+<body id="taddglem"><a name="taddglem"><!-- --></a>
+
+<h1 class="topictitle1">Adding global elements</h1>
+<div><p>A global element is an element with a global scope. It is one that has
+ been declared as part of the main schema rather than as part of a content
+ model.</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 add a global
+element, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+schema and its contents should be displayed in the Graph view.</li>
+<li class="skipspace"><span>In the Graph view, right click in the <b>Elements</b> section and
+click <b> <span class="uicontrol">Add Element</span></b>.</span></li>
+<li class="skipspace"><span>In the Properties view, click the <b> <span class="uicontrol">General</span></b> tab,
+and type a new name for the global element in the <b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Specify its type information by clicking the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and selecting the appropriate type.</span> The Set Type dialog lists all
+built-in and user-defined types currently available. You can change the <b> <span class="uicontrol">Scope</span></b> of
+the list by selecting one of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span>.</b> Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default) <b> <span class="uicontrol">Current Resource</span>.</b> List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="skipspace">
+<div>
+ (Optional) Click the <b><span class="uicontrol">Other</span></b> tab. In
+ this page, you can specify the following various values for the global
+ element:
+ <ul>
+ <li><b><span class="uicontrol">abstract</span></b>. Click <strong>true
+ </strong>if you want the global element to be abstract. When a global
+ element is declared to be abstract, it cannot be used in an instance
+ document. Instead, a member of that global element's substitution group
+ must appear in the instance document. </li>
+ <li><b><span class="uicontrol">block</span></b>. This field determines
+ whether the global element may be replaced by an element derived from
+ it. </li>
+ <li><b><span class="uicontrol">final</span></b>. This field determines
+ whether this global element may be derived from. </li>
+ <li><b><span class="uicontrol">fixed/default</span>.</b> Click the <b>
+ <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and
+ select the <b><span class="uicontrol">Fixed</span></b> or <b>
+ <span class="uicontrol">Default</span></b> radio button and specify an
+ appropriate value. If you select <strong>Fixed</strong>, the global
+ element has a fixed value, which cannot be changed. If you select
+ <strong>Default</strong>, the element has a default value. </li>
+ <li><b><span class="uicontrol">form</span></b>. Use this field to
+ indicate if the appearance of this global element in an instance of the
+ XML schema (that is, an XML file associated with the XML schema) must be
+ qualified by a namespace. </li>
+ <li><b><span class="uicontrol">nillable</span></b>. Select <strong>true</strong>
+ if you do not want the global element to be able to have any child
+ elements, only attributes. </li>
+ <li><b><span class="uicontrol">substitutionGroup</span></b>. A
+ substitution group allows elements to be substituted for other elements.</li>
+ </ul>
+</div>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> tab.</span> You
+can use this page to add attributes, attribute references, attributes group
+references, and <samp class="codeph">any</samp> attributes to your global element.</li>
+<li class="skipspace"><span>An attribute associates an attribute name with a specific type
+and value. To add an attribute, right-click in the Attributes page, and click <span class="uicontrol">Add
+Attribute</span>.</span> You can specify the following values for
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span></b>. Click the <span class="uicontrol">More</span> button
+and select the <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
+button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
+has a fixed value, which cannot be changed. If you select <b>Default</b>,
+the attribute has a default value.</li>
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
+of this attribute in an instance of the XML schema must be qualified by a
+namespace.</li>
+<li><b><span class="uicontrol">name</span></b>. Enter the name of the attribute.</li>
+<li><b><span class="uicontrol">type</span></b>. Click the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and select the type of the attribute. </li>
+<li><b><span class="uicontrol">use</span></b>. This field indicates how an attribute
+may be used in an instance document. If you select <b>optional</b>, the attribute
+may appear once, but it does not have to. If you select <b>required</b>, the
+attribute must appear once. If you select <b>prohibited</b>, the attribute
+must not appear. <b>Note</b>: If you selected the <span class="uicontrol">Default</span> radio
+button, you must select <b>optional</b> in this field, otherwise the default
+value will not be valid.</li>
+</ul>
+</li>
+<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b></span> A declaration that references a global
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
+group. To add an attribute group reference, right-click in the Attributes
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref</span></b>.</span> A
+declaration that references an attribute group enables the referenced attribute
+group to appear in the instance document in the context of the referencing
+declaration. The menu option to add an attribute group reference only appears
+if there are attribute groups defined elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the attribute group you want
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
+</ol>
+</li>
+<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element
+enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page and click <b> <span class="uicontrol">Add Any Attribute</span></b>.</span> You can specify the following values for an <samp class="codeph">any</samp> attribute:<ul><li>For a <strong>namespace</strong> value, you can select <strong>##any</strong> (this allows
+any well-formed XML from any namespace), <b>##local </b> (this allows any
+well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
+allows any well-formed XML that is not from the target namespace of the type
+being defined) or <b>##targetNamespace </b> (which is shorthand for the target
+namespace of the type being defined). </li>
+<li>For a <span class="uicontrol">processContents</span> value, you can select <b>skip</b> (the
+XML processor will not validate the attribute content at all), <b>lax</b>(the
+XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
+XML processor will validate all the attribute content).</li>
+</ul>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this global element.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+<div class="skipspace">You can add a content model to a global element, which is the representation
+of any data that may be contained inside the global element. For more information
+about working with content models, refer to the related tasks.</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddcmod.html" title="You can add a content model to an element, global element, a complex type, or a group. A content model is the representation of any data that may be contained inside the element, global element, complex type, or group.">Adding a content model</a><br />
+<a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.?">Adding an element reference</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
new file mode 100644
index 0000000..d68bd69
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
@@ -0,0 +1,47 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding a group reference</title>
+</head>
+<body id="taddgrpr"><a name="taddgrpr"><!-- --></a>
+
+<h1 class="topictitle1">Adding group references</h1>
+<div><p>A group reference is a declaration that references a group. It enables
+ the referenced group to appear in the instance document in the context of
+ the referencing declaration.</p><div class="skipspace">The menu option to add a group reference only appears if there are
+groups defined elsewhere in the document.<p>The following instructions were
+ written for the Resource perspective, but they will also work in many
+ other perspectives.</p>
+<p>To add a group reference, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Outline view, right-click the content model you want to
+work with and select <b> <span class="uicontrol">Add Group Ref</span></b>.</span></li>
+<li class="skipspace"><span>Select the new group reference.</span></li>
+<li class="skipspace"><span>In the Properties view, select the group you want to refer to in
+the <b> <span class="uicontrol">ref</span></b> list.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this group reference.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddgrup.html" title="A group consists of element declarations, wildcards, and other content model groups. When you create a group, it automatically contains a content model.">Adding a group</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
new file mode 100644
index 0000000..d9809bd
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
@@ -0,0 +1,57 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding a group</title>
+</head>
+<body id="taddgrup"><a name="taddgrup"><!-- --></a>
+
+<h1 class="topictitle1">Adding groups</h1>
+<div><p>When you create a group, it automatically contains a content model.
+The content model is a representation of any data that can be grouped together
+by the group, such as elements, element references, and group references.</p>
+<div class="section"><p></p>
+<p>The following instructions were written for the Resource perspective, but
+they will also work in many other perspectives.</p>
+<p>To
+add a group, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+schema and its contents should be displayed in the Graph view.</li>
+<li class="skipspace"><span>In the Graph view, right click in the <b>Groups</b> section and
+click <span class="uicontrol"><b>Add Group</b>.</span></span></li>
+<li class="skipspace"><span>In the Properties view, type a new name for the group in the
+<b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this group element.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+<li class="skipspace"><span>In the Outline view, expand the <b> <span class="uicontrol">Groups</span></b> folder
+and your new group.</span></li>
+<li class="skipspace"><span>Your group automatically contains a content model. </span> A
+group's content model is the representation of any data that may be contained
+inside the group. For more information about working with content models,
+refer to the related tasks.</li>
+</ol>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.?">Adding a group reference</a><br />
+<a href="../topics/taddcmod.html" title="You can add a content model to an element, global element, a complex type, or a group. A content model is the representation of any data that may be contained inside the element, global element, complex type, or group.">Adding a content model</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
new file mode 100644
index 0000000..a2c1e54
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
@@ -0,0 +1,93 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding import elements</title>
+</head>
+<body id="taddimpt"><a name="taddimpt"><!-- --></a>
+
+<h1 class="topictitle1">Adding import elements</h1>
+<p>As schemas become larger, it is often desirable to divide their content among
+several schema documents for purposes such as ease of maintenance, reuse, and
+readability. You can use an <samp class="codeph">import</samp> element to bring
+in definitions and declarations from an imported schema into the current schema.
+</p>
+<div class="section">
+ The imported schema can come from a different namespace than the current
+ schema does.</div>
+<div class="skipspace">
+ <p>You can add multiple import elements
+to an XML schema, however, prefixes and namespaces have to unique amongst
+the imported schemas.</p>
+ <p>The following instructions were written for the Resource perspective, but
+ they will also work in many other perspectives.</p>
+ <p>To add an import element,
+follow these steps:</p></div>
+<ol>
+ <li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+ <li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+schema and its contents should be displayed in the Graph view.</li>
+ <li class="skipspace"><span>In the Graph view, right click in the <b>Directives</b> section
+and click <b><span class="uicontrol">Add Import</span></b>.</span></li>
+ <li class="skipspace"><span>In the Properties view, click the <b>General</b> tab and click
+the <b><span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> to the right of the
+ <b><span class="uicontrol">Schema
+location</span></b> field.</span></li>
+ <li class="skipspace"><span>If you want to import an XML schema located in the workbench, select
+the <b><span class="uicontrol">Workbench projects</span></b> radio button and click
+ <b><span class="uicontrol">Next</span></b>. </span>
+ <ol type="a">
+ <li><span>Select the schema you want to import and click <b>
+ <span class="uicontrol">Finish</span></b>.</span></li>
+ </ol></li>
+ <li class="skipspace"><span>If you want to import an XML schema located on the Web, select
+the <b><span class="uicontrol">HTTP</span></b> radio button and click <b>
+ <span class="uicontrol">Next</span></b>.</span><ol type="a">
+ <li class="skipspace"><span>Type the <b>URL</b> of the XML schema and click
+ <b><span class="uicontrol">Finish</span></b>.</span>
+ <div class="note"><span class="notetitle"><b>Note</b>: </span>A local copy of the schema will not be stored in the workbench.
+Every time you validate your schema, the schema's contents will be checked
+from the URL you specify.</div></li>
+ </ol></li>
+ <li class="skipspace"><span>The XML schema editor will retrieve the namespace for the imported
+XML schema file and display it as read-only in the <b><span class="uicontrol">Namespace</span></b> field.</span></li>
+ <li class="skipspace"><span>If necessary, type a unique prefix for this namespace in the
+ <b><span class="uicontrol">Prefix</span></b> field.</span></li>
+ <li class="skipspace"><span>Click the <b><span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this import element.</span> The
+ <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the
+ <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+<div class="skipspace">
+ <p>Once you have added an import element to your XML schema, when
+you define new elements, attributes, complex types, or simple types where
+you can specify type information, any declarations from the included schema
+will be available in the <b><span class="uicontrol">Type</span></b> list for the element,
+attribute, complex or simple type.</p></div>
+<div class="skipspace"></div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an include element</a><br />
+<a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. Like the include mechanism, redefine requires the external components to be in the same target namespace as the redefining schema, although external components from schemas that have no namespace can also be redefined.">Adding a redefine element</a><br />
+</p>
+<p><b class="relrefhd">Related reference</b><br />
+<a href="../topics/rnmspc.html" title="">XML namespaces</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
new file mode 100644
index 0000000..fd392ec
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
@@ -0,0 +1,95 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding include elements</title>
+</head>
+<body id="taddincl"><a name="taddincl"><!-- --></a>
+
+<h1 class="topictitle1">Adding include elements</h1>
+<div><p>As schemas become larger, it is often desirable to divide their content
+ among several schema documents for purposes such as ease of maintenance,
+ reuse, and readability. You can use the <samp class="codeph">include</samp>
+ element to brings in definitions and declarations from the included schema
+ into the current schema. The included schema must be in the same target
+ namespace as the including schema. </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
+add an include element , follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+schema and its contents should be displayed in the Graph view.</li>
+<li class="skipspace"><span>In the Graph view, right click in the <b>Directives</b> section
+and click <b> <span class="uicontrol">Add Include</span>.</b></span></li>
+<li class="skipspace"><span>In the Properties view, click the <b>General</b> tab and click
+the <b> <span class="uicontrol">More</span></b> button
+<img src="../images/More.gif" width="22" height="18"> to the right of the
+<b> <span class="uicontrol">Schema
+location</span> </b>field.</span> The XML schema file you select must
+have the same namespace as the current schema.</li>
+<li class="skipspace"><span>If you want to select an XML schema located in the
+workbench, select the <b> <span class="uicontrol">Workbench projects</span></b> radio button
+and click <b> <span class="uicontrol">Next</span></b>. </span><ol type="a"><li><span>Select the schema you want to include and click
+ <b> <span class="uicontrol">Finish</span></b>.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>If you want to select an XML schema located on the Web, select
+the <b> <span class="uicontrol">HTTP</span></b> radio button and click <b> <span class="uicontrol">Next</span></b>.</span><ol type="a"><li><span>Type the URL of the XML schema and click
+ <b> <span class="uicontrol">Finish</span></b>. </span></li>
+</ol>
+ <div class="note"><span class="notetitle"><b>Note</b>: </span> A local copy of the schema will not be stored in the workbench.
+Every time you validate your schema, the schema's contents will be checked
+from the URL you specify.</div>
+</li>
+<li class="skipspace"><span>The XML schema editor will retrieve the location of the included
+XML schema file and display it as read-only in the <b> <span class="uicontrol">Schema location</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this include element.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+<div class="skipspace"><p>Once you have added the include element to your XML schema, when
+you define new elements, attributes, complex types, or simple types where
+you can specify type information, any declarations from the included schema
+will be available in the <span class="uicontrol">Type</span> list for the element,
+attribute, complex or simple type.</p>
+<p>For example, if Address.xsd has the
+following content:</p>
+<pre><complexType name="Address">
+ <sequence>
+ <element name="name" type="string">
+ <element name="street" type="string">
+ </sequence>
+</complexType></pre>
+and you have an XML schema called PurchaseOrder.xsd that has added
+an include for Address.xsd, then when defining a new element in PurchaseOrder,
+you can select Address as its type. <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><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an import element</a><br />
+<a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. Like the include mechanism, redefine requires the external components to be in the same target namespace as the redefining schema, although external components from schemas that have no namespace can also be redefined.">Adding a redefine element</a><br />
+</p>
+<p><b class="relrefhd">Related reference</b><br />
+<a href="../topics/rnmspc.html" title="">XML namespaces</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html
new file mode 100644
index 0000000..75078b0
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html
@@ -0,0 +1,52 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding notations</title>
+</head>
+<body id="taddnot"><a name="taddnot"><!-- --></a>
+
+<h1 class="topictitle1">Adding notations</h1>
+<div><p>A notation is a means of associating a binary description with
+an entity or attribute. The most common uses of notations are to include familiar
+types of binary references, such as GIFs and JPGs, in an XML file.</p>
+<div class="section"><p>For example, you are making a catalogue of your clothing and want
+to include an image of one of your shirts. You would have to create a notation
+like this: <kbd class="userinput"><notation name="My_Shirt" system="GIF"></notation></kbd> which
+defines a notation for a GIF image.</p>
+<p>The following instructions were written for the Resource perspective, but
+they will also work in many other perspectives.</p>
+<p>To
+create a notation, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, right-click your XML schema and click
+<b> <span class="uicontrol">Add
+Notation</span></b>.</span></li>
+<li class="skipspace"><span>In the Properties view, type the name of the notation in the
+<b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span></li>
+<li class="skipspace"><span>In the <b> <span class="uicontrol">public</span></b> field, type a public identifier.</span> This is optional if you enter a value in the
+<b> <span class="uicontrol">system</span></b> field.</li>
+<li class="skipspace"><span>In the <b> <span class="uicontrol">system</span></b> field, type a URI reference.</span> This is optional if you enter a value in the
+<b> <span class="uicontrol">public</span></b> field.</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this notation.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
new file mode 100644
index 0000000..d056100
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding redefine elements</title>
+</head>
+<body id="taddrdfn"><a name="taddrdfn"><!-- --></a>
+
+<h1 class="topictitle1">Adding redefine elements</h1>
+<div>
+ <div class="skipspace">
+ <div>
+ <div>
+ You can use the <samp class="codeph">redefine</samp> mechanism
+ to redefine simple and complex types, groups, and attribute
+ groups obtained from external schema files. When you redefine a
+ component, you are modifying its contents.<p>Like the
+ <samp class="codeph">include</samp> mechanism,
+ <samp class="codeph">redefine</samp> requires the external
+ components to be in the same target namespace as the redefining
+ schema, although external components from schemas that have no
+ namespace can also be redefined.</div>
+ </div>
+ <p>The following instructions were written for the Resource perspective,
+ but they will also work in many other perspectives.</p>
+<p>To
+add a redefine element, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+schema and its contents should be displayed in the Graph view.</li>
+<li class="skipspace"><span>In the Graph view, right-click in the <b>Directives</b> section
+and click <span class="uicontrol">Add Redefine</span>.</span></li>
+<li class="skipspace"><span>In the Properties view, click the <b>General</b> tab and click
+the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> to the right of the
+<b> <span class="uicontrol">Schema
+location</span> </b>field.</span> The XML schema file you select must
+have the same namespace as the current schema.</li>
+<li class="skipspace"><span>If you want to select an XML schema located in the workbench, select
+the <b> <span class="uicontrol">Workbench projects</span> </b>radio button and click <span class="uicontrol">
+<b>Next</b>.</span></span><ol type="a"><li><span> Select the schema you want to include and click
+ <b> <span class="uicontrol">Finish</span></b>.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>If you want to select an XML schema located on the Web, select
+the <b> <span class="uicontrol">HTTP</span></b> radio button and click <b> <span class="uicontrol">Next</span></b>.</span><ol type="a"><li><span>Type the URL of the XML schema and click
+ <b> <span class="uicontrol">Finish</span></b>.
+ </span></li>
+</ol>
+ <div class="note"><span class="notetitle"><b>Note</b>: </span>A local copy of the schema will not be stored in the workbench.
+Every time you validate your schema, the schema's contents will be checked
+from the URL you specify.</div>
+</li>
+<li class="skipspace"><span>The XML schema editor will retrieve the location of the included
+XML schema file and display it as read-only in the <b> <span class="uicontrol">Schema location</span>
+</b>field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this redefine element.</span> The <span class="uicontrol">Documentation</span> page is used for human readable
+material, such as a description, and the <span class="uicontrol">App Info</span>
+page can be used to provide information for applications.</li>
+</ol>
+<div class="skipspace"><p>Once you have added the redefine element to your XML
+ schema, you can redefine any of the simple and complex types, groups, and
+ attribute groups in the XML schema you selected in the redefine element. </p>
+</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an import element</a><br />
+<a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an include element</a><br />
+</p>
+<p><b class="relrefhd">Related reference</b><br />
+<a href="../topics/rnmspc.html" title="">XML namespaces</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
new file mode 100644
index 0000000..9db7e77
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
@@ -0,0 +1,63 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding pattern facets to simple types</title>
+</head>
+<body id="taddreg"><a name="taddreg"><!-- --></a>
+
+<h1 class="topictitle1">Adding pattern facets to simple types</h1>
+<div><div class="skipspace"><p>A pattern facet can be used to constrain the value of a type's
+lexical space (the set of string literals that represent the values of a type),
+which indirectly constrains the value space. </p>
+ <p>The value of the pattern is called
+a regular expression. You can specify it using the<b> <span class="uicontrol">Regular Expression</span></b> wizard.</p>
+<p>To
+add a pattern to a simple type, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the Graph view, select the simple type you want to work with.</span></li>
+<li class="skipspace"><span>In the Properties view, click the <b> <span class="uicontrol">Advanced</span></b> tab,
+then the <b> <span class="uicontrol">Patterns</span></b> tab.</span> The <b> <span class="uicontrol">Patterns</span></b> tab
+will only appear if the pattern facet is applicable to the base type of the
+simple type.</li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Add</span></b>.</span> The Regular Expression
+Wizard opens.</li>
+<li class="skipspace"><span>Select the token you want to add to the expression.</span></li>
+<li class="skipspace"><span>Indicate how often you want the token to appear in order for a
+match to succeed.</span> If you want the token to repeat, click <span class="uicontrol">
+<b>Repeat</b> </span>and
+specify the number of times the token must appear. If you want to specify
+a minimum and maximum number of times the token can appear, click <b> <span class="uicontrol">Range</span></b> and
+enter a minimum and maximum value.</li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Add</span></b> to
+add the token to the regular expression.</span></li>
+<li class="skipspace"><span>Repeat the previous three steps as necessary to create the entire
+expression.</span></li>
+<li class="skipspace"><span>When you are finished, click <b> <span class="uicontrol">Next</span></b>.</span></li>
+<li class="skipspace"><span>(Optional) Enter some sample text to test against the regular expression
+and see if a match occurs. </span></li>
+<li class="skipspace"><span>Click<span class="uicontrol"> <b>Finish</b></span>.</span></li>
+</ol>
+<div class="skipspace">The regular expression will appear in the Patterns page.</div>
+</div>
+<p>To edit an existing pattern, select it in the Patterns page and click <b>
+<span class="uicontrol">Edit</span></b>. To delete an existing pattern, select
+it in the Patterns page and click <b><span class="uicontrol">Delete</span></b>.
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace." href="taddsmpt.html">Adding
+simple types</a></p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
new file mode 100644
index 0000000..fe99353
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
@@ -0,0 +1,141 @@
+<?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 lang="en-us" xml:lang="en-us">
+<head>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Adding simple types</title>
+</head>
+<body id="taddsmpt"><a name="taddsmpt"><!-- --></a>
+<h1 class="topictitle1">Adding simple types</h1>
+<div><p>Simple types are used to created derived datatypes. They provide
+a set of constraints on the value space (that is, a set of values) and the
+lexical space (that is, a set of valid literals) of a datatype.</p>
+<div class="section"><p>A simple type cannot have element content and cannot carry attributes.
+Elements that contain numbers (and strings, and dates, and so on) but do not
+contain any sub-elements are said to have a simple type.</p>
+<p>The following
+instructions were written for the Resource perspective, but they will also
+work in many other perspectives.</p>
+<p>To add a simple type, follow these
+steps:</p>
+</div>
+<ol><li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li>
+<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire
+schema and its contents should be displayed in the Graph view.</li>
+<li class="stepexpand"><span>In the Graph view, right-click in the <strong>Types</strong> section and
+click <b> <span class="uicontrol">Add Simple Type</span></b>.</span></li>
+<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab,
+and type a new name for the simple type in the <b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="stepexpand"><span>You can select the following options from the <b> <span class="uicontrol">Variety</span></b> list:</span><ul><li>
+ <b><span class="uicontrol">atomic</span></b>. Atomic types are all the simple types
+built into the XML schema language.</li>
+<li><b><span class="uicontrol">list</span></b>. List types are comprised of sequences
+of atomic types. They have values that are comprised of finite-length sequences
+of atomic values. </li>
+<li><b><span class="uicontrol">union</span></b>. A union type enables an element or attribute
+value to be one or more instances of one type drawn from the union of multiple
+atomic and list types.</li>
+</ul>
+</li>
+<li class="stepexpand"><span>If you selected <span class="uicontrol">atomic</span> from the
+<b> <span class="uicontrol">Variety</span></b> drop
+down list, click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button next to the
+<b> <span class="uicontrol">Base
+type</span></b> field to specify a base type for the simple type.</span> The Set
+Type dialog lists all built-in and user-defined types currently available. You
+can change the <b> <span class="uicontrol">Scope</span></b> of the list by selecting one
+of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span></b>. Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default)<b> <span class="uicontrol">Current Resource</span>.</b> List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="stepexpand"><span>If you selected <span class="uicontrol">list</span> from the
+<b> <span class="uicontrol">Variety</span></b> drop
+down list, click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button next to the
+<b> <span class="uicontrol">Item
+type</span> </b>field to specify a item type for the simple type.</span> The
+Set Type dialog lists all built-in and user-defined types currently available.
+You can change the <b> <span class="uicontrol">Scope</span></b> of the list by selecting one
+of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span></b>. Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default) <b> <span class="uicontrol">Current Resource</span></b>. List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="stepexpand"><span>If you selected <span class="uicontrol">union</span> from the
+<b> <span class="uicontrol">Variety</span></b> drop
+down list, click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button next to the
+<b> <span class="uicontrol">Member
+types</span> </b>field to specify the member types for the simple type.</span> You can select to add both
+<b> <span class="uicontrol">Built-in simple types</span></b> and <b> <span class="uicontrol">User-defined
+simple types</span></b> to the member types value list. </li>
+<li class="stepexpand"><span>Click the <b> <span class="uicontrol">Enumerations</span></b> tab.</span> Enumerations
+help you to define a set of valid values for simple types. They are the actual
+values the simple type can take as valid values in the instance document.
+You can either add one enumeration or several enumerations at a time:<ol type="a"><li class="substepexpand"><span>To add one enumeration at a time, click the
+ <b> <span class="uicontrol">Add</span></b> button
+and specify a value for the enumeration.</span></li>
+<li class="substepexpand"><span>To add several enumerations at one time, follow these steps:</span> <ol type="i"><li>Click the
+ <b> <span class="uicontrol">Add...</span></b> button.</li>
+<li>Enter the value of each enumeration. Each value must be separated by the <b> <span class="uicontrol">Delimiter
+character</span></b>. For example: <samp class="codeph">First, Second</samp> will create
+two enumerations, one with the value "First" and one with the value "Second".</li>
+<li>Select the <b> <span class="uicontrol">Preserve leading and trailing whitespace</span></b> check
+box if you want any white space around your enumeration values to be preserved.
+If, for example, you select this check box, the values of <samp class="codeph">First, Second</samp> will
+show up as "First" and " Second" (there is a space before Second) because
+you put a space before "Second" when entered the value.</li>
+<li>Click <b> <span class="uicontrol">OK</span></b>. Your enumerations will be created and
+appear in the Properties view.</li>
+</ol>
+</li>
+</ol>
+</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this simple type.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Advanced</span></b> tab.</span> The options
+available from this page will vary depending on what option you selected in
+the <b> <span class="uicontrol">Variety</span></b> field, and the <b> <span class="uicontrol">Base type</span>,</b>
+<b> <span class="uicontrol">Item
+type</span>,</b> or <b> <span class="uicontrol">Member types</span></b> field on the <span class="uicontrol">General</span> page.</li>
+<li class="skipspace"><span>If applicable to the type, the <b> <span class="uicontrol">Facets</span></b> table
+will be populated with constraining facets. A constraining facet is an optional
+property that can be applied to a datatype to constrain its value.</span><ol type="a"><li><span>To change a facet's value, click its name in the
+ <b> <span class="uicontrol">Name</span></b> column,
+then click its value (or the empty cell that will contain its value) in the <b> <span class="uicontrol">Value</span></b> column
+and type or select a new value.</span></li>
+<li><span> To change whether a facet's value is fixed or not, click its
+name in the <b>Name</b> column, then click the appropriate cell in the <b>Fixed</b> column,
+and change the value to true or false.</span></li>
+</ol>
+</li>
+<li class="stepexpand"><span>If applicable to the type, a Pattern page will be available. Click
+the <b> <span class="uicontrol">Patterns</span></b> tab to switch to it.</span> A pattern
+can be used to constrain the value of a type's lexical space (the set of string
+literals that represent the values of a type), which indirectly constrains
+the value space. For more information on adding a pattern to a simple type,
+refer to the related tasks.</li>
+</ol>
+ <p><b class="reltaskshd">Related tasks</b><br />
+ <a href="taddreg.html">Adding pattern facets to simple types</a></p>
+ </div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
new file mode 100644
index 0000000..bcd548e
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
@@ -0,0 +1,47 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Creating XML schemas</title>
+</head>
+<body id="tcxmlsch"><a name="tcxmlsch"><!-- --></a>
+
+<h1 class="topictitle1">Creating XML schemas</h1>
+<div><p>You can create an XML schema and then edit it using the XML schema
+editor. Using the XML schema editor, you can specify element names that indicates
+which elements are allowed in an XML file, and in which combinations.</p><div class="skipspace">To create an XML schema, follow these steps:</div>
+<ol><li class="skipspace"><span>Create a project to contain the XML schema.</span> </li>
+<li class="skipspace"><span>In the workbench, select<b> <span class="menucascade"><span class="uicontrol">File > New >
+Other > XML > XML Schema</span></span></b>. Click <b> <span class="uicontrol">Next</span></b>.</span> </li>
+<li class="skipspace"><span>Select the project or folder that will contain the XML schema.
+In the </span> <b> <span class="uicontrol">File name</span></b> field, type the name of
+the XML schema, for example <kbd class="userinput">MyXMLSchema.xsd</kbd>. The name
+of your XML schema must end in <tt class="sysout">.xsd</tt></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Finish</span></b>.</span></li>
+</ol>
+<div class="skipspace">The XML schema opens in the XML schema editor. </div>
+</div>
+
+<div>
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.?">XML schema editor</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a><br />
+<a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating an XML schema</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
new file mode 100644
index 0000000..5215087
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
@@ -0,0 +1,41 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Deleting XML schema components</title>
+</head>
+<body id="tdelscmp"><a name="tdelscmp"><!-- --></a>
+
+<h1 class="topictitle1">Deleting XML schema components</h1>
+<div><p>If you have created any XML schema components you no longer need,
+you can delete them.</p>
+<div class="section"><p>The following instructions were written for the Resource perspective,
+but they will also work in many other perspectives.</p>
+<p>To delete
+an XML schema component, follow these steps:</p>
+</div>
+<ol><li><span>Open your XML schema in the XML schema editor.</span></li>
+<li><span>In the Outline view, click the item to delete.</span></li>
+<li><span>Right-click the item, and, from its pop-up menu, click <b> <span class="uicontrol">Delete</span></b>.</span></li>
+</ol>
+<div class="skipspace"><p>The XML schema editor has a built-in mechanism to
+ handle referential integrity issues. When you delete certain components,
+ cleanup will automatically occur. </p>
+ <p><b class="reltaskshd">Related reference</b><br />
+ <a href="rrefintg.html">Referential integrity in the XML schema editor</a></p>
+</div>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html
new file mode 100644
index 0000000..f137064
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html
@@ -0,0 +1,50 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing XML schema file preferences</title>
+</head>
+<body id="tedtpref"><a name="tedtpref"><!-- --></a>
+<h1 class="topictitle1">Editing XML schema file preferences</h1>
+<div><p>You can set various preferences for XML schema files such as the default
+ target namespace and XML Schema language constructs prefix used.</p><div class="skipspace"><p>To define XML schema preferences, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Select <b> <span class="menucascade"><span class="uicontrol">Window > Preferences > Web and
+XML > XML Schema Files</span></span></b>.</span></li>
+<li class="skipspace"><span>Select the <b> <span class="uicontrol">Qualify XML schema language constructs </span>
+</b>check
+box if you want a prefix applied to all XML Schema language constructs in
+your XML schema.</span></li>
+<li class="skipspace"><span>In the<b> <span class="uicontrol">XML schema language constructs prefix</span>
+</b>field,
+type the prefix you want applied to XML Schema language constructs in your
+XML schema.</span> The prefix <b> <span class="uicontrol">xsd</span></b> is
+used by convention to denote the XML Schema namespace, but any prefix can
+be used. The purpose of the association is to identify the elements and simple
+types as belonging to the vocabulary of the XML Schema language rather than
+the vocabulary of the schema author. <div class="note"><span class="notetitle">
+ <b>Note</b>: </span>This prefix will not appear in
+any schemas that currently exist - it will only appear in new schemas you
+create after you type the prefix and click <span class="uicontrol">Apply</span>. Any
+schemas that already exist will have the prefix specified in the schema applied
+to the XML schema language constructs.</div>
+</li>
+<li class="skipspace"><span>You can change the <b> <span class="uicontrol">Default Target Namespace</span></b> value.</span> The value specified in this field will be the default target namespace
+for any new XML schema files created.</li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">OK</span></b>.</span></li>
+</ol>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
new file mode 100644
index 0000000..789d62f
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
@@ -0,0 +1,87 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Editing XML schema properties</title>
+</head>
+<body id="tedtschm"><a name="tedtschm"><!-- --></a>
+
+<h1 class="topictitle1">Editing XML schema properties</h1>
+<div><p>After you create an XML schema, you can edit its various properties,
+such as its namespace and prefix.</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 an XML schema's
+properties follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Create a new XML schema or double-click an existing schema in the
+Navigator view.</span> It will automatically open in the XML schema editor.</li>
+<li class="skipspace"><span>In the Properties view, click the <b> <span class="uicontrol">General</span></b> tab.</span></li>
+<li class="skipspace"><span>You can change the <b> <span class="uicontrol">Prefix</span></b> associated with
+the current namespace.</span> Element and attribute names that are associated
+with this namespace will be prefixed with this value.</li>
+<li class="skipspace"><span>You can also edit the <b> <span class="uicontrol">Target namespace</span>
+</b>for
+this schema.</span> A namespace is a URI that provides a unique name
+to associate with all the elements and type definitions in a schema.<ol type="a"><li><span>Click
+ <b> <span class="uicontrol">Advanced</span></b> if you want to add more
+namespace declarations to your XML schema.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span> You can
+modify the following values in this page.<ol type="a"><li class="skipspace"><span>The
+ <b> <span class="uicontrol">attributeFormDefault</span></b> value. </span> Select
+ <b> <span class="uicontrol">qualified</span></b> if you want attributes in an
+XML schema instance to be qualified by the prefix that is associated with
+the schema namespace; otherwise, select <b> <span class="uicontrol">unqualified</span></b>.</li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">blockDefault</span></b> value.</span> This
+field determines whether the types or elements in the schema may be replaced
+by elements or types derived from them. The effect of specifying the
+blockDefault attribute is equivalent to specifying a block attribute on every
+type definition and element declaration in the schema. You can either select
+<strong>#all</strong> (nothing may be replaced by derivations),<strong>
+extension</strong> (nothing may be replaced by derivations-by-extension),
+<strong>restriction</strong> (nothing may be replaced by
+derivations-by-restrictions ) or <strong>substitution</strong> (nothing may be
+replaced by derivations-by-substitution). </li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">elementFormDefault</span></b> value.</span> Select <span class="uicontrol">qualified</span> if
+you want elements in an XML schema instance to be qualified by the prefix
+that is associated with the schema namespace; otherwise, select <span class="uicontrol">unqualified</span>.</li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">finalDefault</span></b> value.</span> This
+field determines whether the types or elements in the schema may be derived
+from. The effect of specifying the final default attribute is equivalent to
+specifying a final attribute on every type definition and element declaration in
+the schema. If you select <strong>#all</strong>, no types or elements in the
+schema may be derived from. If you select <strong>extension</strong>, no types
+or elements in the schema may be derived from using extension. If you select
+<strong>restriction</strong>, no types or elements in the schema may be derived
+from using restriction. </li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">version</span></b>
+value.</span> Type the version number of the schema in the <b> <span class="uicontrol">
+version</span></b> field.</li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">xml:lang</span> </b>value. </span> Type
+the appropriate ISO-IETF (for example, en-us) tag in this field. This tag
+may be inserted in documents to specify the language used in the contents
+and attribute values of any element in an XML file.</li>
+</ol>
+</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
+to provide any information about this XML schema.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description, and the <span class="uicontrol">App
+Info</span> page can be used to provide information for applications.</li>
+</ol>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
new file mode 100644
index 0000000..bac41e2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
@@ -0,0 +1,57 @@
+<?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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Importing XML schemas</title>
+</head>
+<body id="timpschm"><a name="timpschm"><!-- --></a>
+
+<h1 class="topictitle1">Importing XML schemas</h1>
+<div>
+ <div>
+ <div>
+ If you want to work with XML schema files that you created outside
+ of the product, you can import them into the workbench and open them
+ in the XML schema editor. The XML schema editor provides you with a
+ structured view of the XML schema.</div>
+ </div>
+ <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 import
+an XML schema into the workbench, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Click <b> <span class="menucascade"><span class="uicontrol">File > Import</span></span></b>.</span></li>
+<li class="skipspace"><span>Select the import source.</span> Click <b> <span class="uicontrol">Next</span></b>.</li>
+<li class="skipspace"><span>Fill in the fields in the Import wizard as necessary.</span> When
+you are finished, click <b> <span class="uicontrol">Finish</span></b>.</li>
+</ol>
+<div class="skipspace"><p>The imported schema now appears in the Navigator view. Double-click
+it to open it in the XML schema editor.</p>
+</div>
+</div>
+
+<div><p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.?">XML schema editor</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a><br />
+<a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating an XML schema</a><br />
+<a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an import element</a><br />
+<a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an include element</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
new file mode 100644
index 0000000..f3e6e10
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Navigating XML schemas</title>
+</head>
+<body id="tnavsrc"><a name="tnavsrc"><!-- --></a>
+<h1 class="topictitle1">Navigating XML schemas</h1>
+<div><p>When you are working in the Source view, you can use F3 to navigate
+through the file by placing your cursor in the appropriate item and clicking
+F3 to jump to the item it refers to. </p>
+<div class="section"><p>You can jump to any of the following items:</p>
+<ul><li>Element or attribute declaration's type</li>
+<li>Element references</li>
+<li>Group references</li>
+<li>Attribute references</li>
+<li>Attribute group references</li>
+<li>Import, include, and redefine element (the external schema will open in
+the XML schema editor. This only works with schemas in the workspace).</li>
+</ul>
+<p>You must place your cursor exactly in the location of the reference
+(for example between the double quotes for <tt class="sysout">type = " "</tt> or
+ <tt class="sysout">base = " "</tt>).</p>
+<p>For example,
+if you place your cursor anywhere in the following text and click F3:</p>
+<p> <tt class="sysout"><element
+name="shipTo" type="po:USAddress"></element></tt> </p>
+<p>the
+cursor will automatically jump to the location in the file where the type
+USAddress is defined.</p>
+<p>Or, if you place your cursor anywhere in the following
+text and click F3:</p>
+<p> <tt class="sysout"><element ref="po:ContactElement"></element></tt> </p>
+<p>the
+cursor will automatically jump to the location in the file where the global
+element ContactElement is defined.</p>
+<p>This works across files. For example,
+if the type you have selected is defined in another XML schema and you click
+F3, you will automatically be taken to that file.</p>
+</div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.">XML schema editor</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html
new file mode 100644
index 0000000..c1c62e3
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.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>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Validating an XML schema</title>
+</head>
+<body id="tvdtschm"><a name="tvdtschm"><!-- --></a>
+
+<h1 class="topictitle1">Validating XML schemas</h1>
+<div><p>Validating an XML schema determines whether the current state of
+the XML schema file is semantically valid. Any errors will be displayed in
+the Problems view.</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 validate
+an XML schema, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Right-click your file in the Navigator view and click <span class="uicontrol">
+ <b>Validate
+XML Schema</b>.</span></span></li>
+<li class="skipspace"><span>You will receive a message indicating whether the XML schema file is
+valid.</span> If validation was not successful, refer to the Problems
+view to see what problems were logged. <div class="note"><span class="notetitle">
+ <b>Note</b>: </span>If you receive an error message
+indicating that the Problems view is full, you can increase the number of
+error messages allowed by selecting <b> <span class="menucascade"><span class="uicontrol">Properties >
+Validation</span></span></b> from the project's pop-up menu and specifying
+the maximum number of error messages allowed.</div>
+</li>
+</ol>
+<div class="skipspace"><p>The XML schema support in the XML schema editor is
+based on the W3C XML Schema Recommendation Specification of 2 May 2001. The
+XML Schema specifications <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">XML Schema Part 1: Structures</a> and <a href="http://www.w3.org/TR/xmlschema-2/" target="_blank">XML Schema Part 2: Datatypes</a>
+ from the W3C Web site are used for validation.</p>
+<p>Certain error messages contain
+a reference to the schema constraints listed in Appendix C of the <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">XML Schema Part 1: Structures</a> document.
+Each constraint has a unique name that will be referenced in the error message.
+For example, if you receive an error message with this text: <tt class="sysout">ct-props-correct.2,</tt> and
+you searched in the Structure document for the text, you would find that it
+is for the section "Schema Component Constraint: Complex Type Definition Properties
+Correct". The <tt class="sysout">.2</tt> means the 2nd constraint, which
+reads: "2. If the {base type definition} is a simple type definition, the
+{derivation method} must be extension."</p>
+<p>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="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor.">Creating XML schemas</a><br />
+</p>
+</div>
+</body>
+</html>
\ No newline at end of file
