Adding infopop plugins and adding the pops to the wst.doc feature
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..8527423
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.dtd.ui.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ </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..d294bbc
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts.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
+ *******************************************************************************/ -->
+
+<contexts>
+<context id="edtd0000">
+<description>The DTD source page editor lets you edit a document type definition. The editor provides text editing features such as syntax highlighting and unlimited undo and redo.
+</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="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>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</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 label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</context>
+
+<context id="webx0022">
+<description>This page lets you create new and edit existing templates that will be used when you edit a DTD file.
+</description>
+</context>
+
+</contexts>
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..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties
new file mode 100644
index 0000000..d6dee26
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties
@@ -0,0 +1 @@
+pluginName = DTD Editor infopops
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..6c01c5b
--- /dev/null
+++ b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.xml
@@ -0,0 +1,28 @@
+<?xml version="1.0"?>
+<?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
+ id="org.eclipse.wst.dtd.ui.infopop"
+ name="DTD infopops"
+ version="0.7.0"
+ provider-name="Eclipse.org">
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorDtdContexts.xml" plugin ="org.eclipse.wst.dtd.ui"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
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..066d82e
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+
+<toc label="DTD Editor" topic="topics/tcretdtd.html">
+ <topic label="Working with DTDs">
+ <topic label="Creating DTDs" href="topics/tcretdtd.html">
+ <topic label="Document type definitions (DTDs) - overview" href="topics/cdtdover.html"/>
+ </topic>
+ <topic label="Importing DTDs" href="topics/timptdtd.html"/>
+ <topic label="Editing DTDs" href="topics/tedtdtd.html">
+ <topic label="DTD editor" href="topics/cdtdedit.html"/>
+ <topic label="Creating elements" href="topics/tcretelm.html">
+ <topic label="Creating attributes and attribute lists" href="topics/tcretattr.html"/>
+ <topic label="Editing an element's content model" href="topics/tchgelm.html">
+ <topic label="Editing a group node" href="topics/tedtgnde.html"/>
+ </topic>
+ </topic>
+ <topic label="Creating entities" href="topics/tcretent.html">
+ <topic label="Reusing internal parameter entities in an attribute name or type" href="topics/trusintp.html"/>
+ <topic label="Reusing the value of one entity in another entity" href="topics/trusents.html"/>
+ <topic label="Reusing external parameter entities in an element's content model" href="topics/trusextp.html"/>
+ </topic>
+ <topic label="Creating notations" href="topics/tcretnot.html"/>
+ <topic label="Creating a comment" href="topics/tcretcomm.html"/>
+ <topic label="Deleting elements, attributes, entities, notations, and comments" href="topics/tremvelm.html">
+ <topic label="Referential integrity in the DTD editor" href="topics/rrefint.html"/>
+ </topic>
+ </topic>
+ <topic label="Validating DTDs" href="topics/tvaldtd.html"/>
+ <topic label="Generating XML schemas from DTD files" href="topics/tgenxmls.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/about.html b/docs/org.eclipse.wst.dtdeditor.doc.user/about.html
new file mode 100644
index 0000000..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties b/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties
new file mode 100644
index 0000000..5751813
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties
@@ -0,0 +1,5 @@
+bin.includes = doc.zip,\
+ DTDEditormap_toc.xml,\
+ dtdeditor_reference_toc.xml,\
+ plugin.properties,\
+ plugin.xml
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/dtdeditor_reference_toc.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/dtdeditor_reference_toc.xml
new file mode 100644
index 0000000..0052747
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/dtdeditor_reference_toc.xml
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<toc label="DTD editor reference files" topic="topics/rrefint.html">
+ <topic label="Referential integrity in the DTD editor" href="topics/rrefint.html"/>
+ <topic label="Icons used in the DTD editor" href="topics/rdtdicons.html"/>
+</toc>
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..e9909ab
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.properties
@@ -0,0 +1,3 @@
+# NLS_MESSAGEFORMAT_VAR
+
+Plugin.name = DTD Editor
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..d657ee5
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.xml
@@ -0,0 +1,28 @@
+<?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
+ name = "DTD Editor documentation"
+ id = "org.eclipse.wst.dtdeditor.doc.user"
+ version = "0.7.0"
+ provider-name = "Eclipse.org">
+
+ <extension point="org.eclipse.help.toc">
+
+ <toc file="DTDEditormap_toc.xml"/>
+
+ <toc file="dtdeditor_reference_toc.xml"/>
+
+
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdedit.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdedit.html
new file mode 100644
index 0000000..51b7a06
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdedit.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>DTD editor</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="cdtdedit"><a name="cdtdedit"><!-- --></a>
+
+<h1 class="topictitle1">DTD editor</h1>
+<div><p>After you have created or imported a DTD, you can open it in the
+DTD editor (by double-clicking it in the Navigator view), a tool for viewing
+and editing DTDs. You can use the DTD editor to perform a variety of tasks
+such as creating, editing, and deleting DTD elements, attributes, entities,
+notations, and comments</p><p>Before you can perform any of these tasks, you must create a DTD and open
+it in the DTD editor. After you open the DTD, you can use the <span class="uicontrol">Outline</span> view
+to create nodes and the <span class="uicontrol">Properties</span> view to provide
+details about the nodes.</p>
+<p></p>
+<p> <b>Note</b>: In the <span class="uicontrol">Outline</span> view, you can either
+work in default mode (all nodes appear in the order you added them to the
+DTD in) or group the DTD nodes into the following logical groups: notations,
+entities, elements, and other, by clicking the <span class="uicontrol">Group items logically</span> button <img src="../images/organize_dtd_logically.gif" />. </p>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tedtdtd.html" title="You can edit DTD files in both the Outline view and the Source view. Modifying the content of a DTD determines what can be used in any XML file that is associated with it.">Editing DTDs</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<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>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html
new file mode 100644
index 0000000..5e07d3b
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.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">
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Document type definition (DTD) - overview</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html
new file mode 100644
index 0000000..466b246
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html
@@ -0,0 +1,78 @@
+<?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">
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Icons used in the DTD editor</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="ricons"><a name="ricons"><!-- --></a>
+
+<h1 class="topictitle1">Icons used in the DTD editor</h1>
+<div><p>The following 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>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rrefint.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rrefint.html
new file mode 100644
index 0000000..a7eeb03
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rrefint.html
@@ -0,0 +1,73 @@
+<?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">
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Referential integrity in the DTD editor</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="rrefint"><a name="rrefint"><!-- --></a>
+
+<h1 class="topictitle1">Referential integrity in the DTD editor</h1>
+<div><p>The DTD editor has a built-in mechanism to handle referential integrity
+issues. When you delete or rename certain nodes, clean up for any nodes affected
+will automatically occur.</p><div class="skipspace">The following table describes the clean up that occurs when you delete
+or rename certain nodes.</div>
+
+<div class="skipspace"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e21"> Action taken</th>
+<th valign="top" id="d0e23"> Clean up </th>
+</tr>
+</thead>
+<tbody><tr><td valign="top" headers="d0e21 ">An element is renamed.</td>
+<td valign="top" headers="d0e23 ">All references to that element will be renamed.</td>
+</tr>
+<tr><td valign="top" headers="d0e21 ">An external parameter entity is renamed.</td>
+<td valign="top" headers="d0e23 ">Any external parameter entity references to it will be renamed.</td>
+</tr>
+<tr><td valign="top" headers="d0e21 ">A notation is renamed.</td>
+<td valign="top" headers="d0e23 ">All references to the notation will be renamed.</td>
+</tr>
+<tr><td valign="top" headers="d0e21 ">An element is deleted.</td>
+<td valign="top" headers="d0e23 ">All references to that element will be cleaned up or reset. The original
+element will be removed from the DTD file, and any references to it will be
+reset to the next available element. If there are no elements available, references
+to it will be reset to (#PCDATA).</td>
+</tr>
+<tr><td valign="top" headers="d0e21 ">An external parameter entity is deleted.</td>
+<td valign="top" headers="d0e23 ">Any external parameter entity references to it will automatically be
+deleted.</td>
+</tr>
+<tr><td valign="top" headers="d0e21 ">A notation is deleted.</td>
+<td valign="top" headers="d0e23 ">All references to the notation will be removed.</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tremvelm.html" title="If you have created elements, attributes, entities, notations, and comments you no longer need, you can delete any of them.">Deleting elements, attributes, entities, notations, and comments</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tchgelm.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tchgelm.html
new file mode 100644
index 0000000..40b16e8
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tchgelm.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">
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing an element's content model</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="tchgelm"><a name="tchgelm"><!-- --></a>
+
+<h1 class="topictitle1">Editing an element's content model</h1>
+<div><p>An element's content model represents any data that can be contained
+inside or within the content of an element (that is, between the start and
+end tags of an element in an XML file). Editing an element's content model
+enables you to determine exactly what the element can (and cannot) contain.</p><div class="skipspace"><p>There are four kinds of content models: <i>element content</i>,
+ <i>mixed content</i>, <i>EMPTY content</i> and <i>ANY content</i></p>
+<p>In
+the <i>element content</i> content model an element can only contain other
+child elements. In the <i>mixed content</i> content model, an element can
+contain both character data (text that is not parsed by the XML parser) and
+other child elements. In the <i>EMPTY content</i> content model, an element
+cannot contain any other elements or text. In the <i>ANY content</i> content
+model, the element can literally contain anything - other elements, in any
+number, and text.</p>
+<p>In the DTD editor, you can create elements with any
+of these content models. When you create an element in the DTD editor, a child
+element with an EMPTY content model is automatically created.</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 element's content
+model, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>In the Outline view, expand the parent element you want to work
+with.</span></li>
+<li class="skipspace"><span>Select the first child of the expanded parent element.</span> This
+is the element's content model.</li>
+<li class="skipspace"><span>In the Design view, you change its <span class="uicontrol">Content type</span> to</span><ul><li><span class="uicontrol">ANY</span></li>
+<li>(#PCDATA)</li>
+<li>Another element</li>
+<li><span class="uicontrol">Children Content</span> or <span class="uicontrol">Mixed Content</span>.</li>
+</ul>
+ Once you select either <span class="uicontrol">Children Content</span> or <span class="uicontrol">Mixed
+Content</span> you will have a group (represented by a group node - <img src="../images/XSDSequence.gif" /> if you select <span class="uicontrol">Children Content</span> and <img src="../images/XSDChoice.gif" /> if you select <span class="uicontrol">Mixed Content</span>),
+which you can use to create a group of child elements under the parent element.
+A child element will automatically be created under the group node. For information
+on editing a group, refer to the related information.<p><b>Note</b>: If you
+intend to have mixed content, the value of the first element in your group
+must be (#PCDATA) (consequently, if you select <span class="uicontrol">Mixed Content</span>,
+two child elements will automatically be created, the first one having a value
+of (#PCDATA).</p>
+ </li>
+<li class="skipspace"><span>If you do not want the parent element to contain anything, leave
+its <span class="uicontrol">Content type</span> as <span class="uicontrol">EMPTY</span>.</span></li>
+<li class="skipspace"><span>Select the appropriate <b>Occurrence</b> option to indicate how
+often the element can occur in an XML file.</span> This option is not
+available if you select ANY, (#PCDATA), EMPTY, or another element.</li>
+<li class="skipspace"><span>To add another existing element to a group as a child, right-click
+the group node, click <span class="uicontrol">Add Element to Content Model</span> and
+specify its name.</span></li>
+<li class="skipspace"><span>To add a group to the content model, right-click the group node
+and click <span class="uicontrol">Add Group to Content Model</span>.</span> For
+information on editing a group, refer to the link below.</li>
+</ol>
+<div class="skipspace"></div>
+</div>
+
+<div>
+<blockquote>
+<div class="ulchildlink"><b><a href="../topics/tedtgnde.html">Editing a group node</a></b><br />
+If your element has either element content or mixed content, its content model is represented by a group node. You can add children elements or another group to a group node, and specify how often, and in what manner a group of elements will be available in an XML file associated with your DTD.</div>
+</blockquote>
+
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tcretelm.html" title="You can use element declarations in DTDs to define the elements that may occur in an XML document. Element declarations can specify that an element can contain other elements, that it can contain anything at all, or that it must be empty.">Creating elements</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretattr.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretattr.html
new file mode 100644
index 0000000..fe076fb
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretattr.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating attributes and attribute lists</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="creatingattributes"><a name="creatingattributes"><!-- --></a>
+
+<h1 class="topictitle1">Creating attributes and attribute lists</h1>
+<div><p>You can use an attribute to describe an element or provide information
+about it. Attribute lists enable you to group together all related attributes
+for an element. </p><div class="skipspace"><p>All elements must have their attributes listed in an attribute
+list <img src="../images/attribute_list.gif" />. If you add an attribute <img src="../images/attribute.gif" /> to an element that does not
+already have an attribute list, an attribute list will be created for the
+element with a new attribute inserted in it.</p>
+<p>To create an attribute,
+follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>In the Outline view, right-click the element you want to work with
+and click <span class="uicontrol">Add Attribute</span>.</span> An attribute list
+will be created for your element if one does not already exist. </li>
+<li class="skipspace"><span>Select the attribute you just created. </span></li>
+<li class="skipspace"><span>In the Properties view, type the name of the attribute in the <span class="uicontrol">Name</span> field.</span></li>
+<li class="skipspace"><span>From the <span class="uicontrol">Type</span> list, select the attribute's
+type. </span></li>
+<li class="skipspace"><span>From <span class="uicontrol">Usage</span> list, select the default usage
+of the attribute.</span> It determines how the attribute can be used.</li>
+<li class="skipspace"><span>If you selected <span class="uicontrol">#FIXED</span> or <span class="uicontrol">Default</span> as
+the default usage of the attribute, you must enter a value in the <span class="uicontrol">Default
+value</span> field.</span></li>
+</ol>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tremvelm.html" title="If you have created elements, attributes, entities, notations, and comments you no longer need, you can delete any of them.">Deleting elements, attributes, entities, notations, and comments</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretcomm.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretcomm.html
new file mode 100644
index 0000000..07029d5
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretcomm.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating a comment</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="creatingacomment"><a name="creatingacomment"><!-- --></a>
+
+<h1 class="topictitle1">Creating a comment</h1>
+<div><p>Comments can be used to provide information about a document, such
+as the author's name, or the date it was last modified. Comments are visible
+to anyone reading the DTD, but are ignored by the XML parser.</p><div class="skipspace">To create a comment, follow these steps:</div>
+<ol><li><span>Open your DTD in the DTD editor.</span></li>
+<li><span>In the Outline view, right-click the DTD <img src="../images/nDTDFile.gif" alt="Image of the DTD icon" /> and select <span class="uicontrol">Add Comment</span>.</span></li>
+<li><span>In the Properties view, type your comment.</span></li>
+</ol>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tedtdtd.html" title="You can edit DTD files in both the Outline view and the Source view. Modifying the content of a DTD determines what can be used in any XML file that is associated with it.">Editing DTDs</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tremvelm.html" title="If you have created elements, attributes, entities, notations, and comments you no longer need, you can delete any of them.">Deleting elements, attributes, entities, notations, and comments</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html
new file mode 100644
index 0000000..489e7b7
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating a new document type definition (DTD)</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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, 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 <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</span></span> and click <span class="uicontrol">Next</span>. </span> If you cannot see the <span class="uicontrol">XML</span> option, select the <span class="uicontrol">Show
+All Wizards</span> check box. </li>
+<li class="skipspace"><span>If you are prompted to enable XML Development capabilities, click <span class="uicontrol">OK</span>.</span></li>
+<li class="skipspace"><span>Select the project or folder that will contain the DTD.</span></li>
+<li class="skipspace"><span>In the <span class="uicontrol">File name</span> 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"><span>Click <span class="uicontrol">Finish</span>.</span></li>
+</ol>
+<div class="skipspace"><p>The DTD appears in the Navigator view and automatically, by default,
+opens in the DTD editor. In the DTD editor, you can 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="relconceptshd">Related concepts</b><br />
+<a href="../topics/cdtdedit.html" title="After you have created or imported a DTD, you can open it in the DTD editor (by double-clicking it in the Navigator view), a tool for viewing and editing DTDs. You can use the DTD editor to perform a variety of tasks such as creating, editing, and deleting DTD elements, attributes, entities, notations, and comments">DTD editor</a><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><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtdtd.html" title="You can edit DTD files in both the Outline view and the Source view. Modifying the content of a DTD determines what can be used in any XML file that is associated with it.">Editing DTDs</a><br />
+<a href="../topics/tgenxmls.html" title="Generating an XML schema from a DTD file enables you to create an XML schema that is automatically populated with elements and attributes from your DTD file. This can save you time if you want to use an XML schema rather than a DTD file to validate your XML file, but you want to use the rules already set up in your DTD file.">Generating XML schemas from DTD files</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretelm.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretelm.html
new file mode 100644
index 0000000..1670b55
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretelm.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating elements</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="tcretelm"><a name="tcretelm"><!-- --></a>
+
+<h1 class="topictitle1">Creating elements</h1>
+<div><p>You can use element declarations in DTDs to define the elements
+that may occur in an XML document. Element declarations can specify that an
+element can contain other elements, that it can contain anything at all, or
+that it must be empty.</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><b>Creating
+elements</b></p>
+<p>To create an element, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>In the Outline view, right-click the DTD <img src="../images/nDTDFile.gif" alt="Image of the DTD icon" /> and click <span class="uicontrol">Add Element</span>.</span></li>
+<li class="skipspace"><span>In the Properties view, type the new name of the element in the <span class="uicontrol">Name</span> field.</span></li>
+<li class="skipspace"><span>When you create an element in the DTD editor, a child element that
+is EMPTY is automatically created.</span><ol type="a"><li class="skipspace"><span>Select the EMPTY child element and, in the Properties view,
+change its <span class="uicontrol">Content type</span> to ANY, (#PCDATA), or another
+element.</span> If you do not want the parent element to contain anything,
+leave its content model type as EMPTY. </li>
+<li class="skipspace"><span>If you want your parent element to contain more than one child
+element (or mixed content), select <span class="uicontrol">Children Content</span> or <span class="uicontrol">Mixed
+Content</span> from the <span class="uicontrol">Content type</span> list.</span> Once you select either of these, you will have a group (represented
+by a group node - <img src="../images/XSDSequence.gif" /> if you select
+Children Content and <img src="../images/XSDChoice.gif" /> if you select
+Mixed Content), which you can use to create a group of child elements under
+the parent element. A child element will automatically be created under
+the group node. For information on editing a group, refer to the related information.
+ </li>
+</ol>
+</li>
+<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> 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 of the element.</li>
+</ol>
+<div class="skipspace"><p><b>Note</b>: If you intend to have mixed content, the value of
+the first element in your group must be (#PCDATA) (consequently, if you select <span class="uicontrol">Mixed
+Content</span>, two child elements will automatically be created, the
+first one having a value of (#PCDATA)). As well, a group should not contain
+an EMPTY or ANY element. EMPTY or ANY elements are not legally allowed as
+nested entities.</p>
+</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcretattr.html" title="You can use an attribute to describe an element or provide information about it. Attribute lists enable you to group together all related attributes for an element.">Creating attributes and attribute lists</a><br />
+<a href="../topics/tchgelm.html" title="An element's content model represents any data that can be contained inside or within the content of an element (that is, between the start and end tags of an element in an XML file). Editing an element's content model enables you to determine exactly what the element can (and cannot) contain.">Editing an element's content model</a><br />
+<a href="../topics/tedtgnde.html" title="If your element has either element content or mixed content, its content model is represented by a group node. You can add children elements or another group to a group node, and specify how often, and in what manner a group of elements will be available in an XML file associated with your DTD.">Editing a group node</a><br />
+<a href="../topics/tremvelm.html" title="If you have created elements, attributes, entities, notations, and comments you no longer need, you can delete any of them.">Deleting elements, attributes, entities, notations, and comments</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretent.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretent.html
new file mode 100644
index 0000000..3a7704a
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretent.html
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating entities</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="tcretent"><a name="tcretent"><!-- --></a>
+
+<h1 class="topictitle1">Creating entities</h1>
+<div><p>An entity is a shortcut used to represent complex strings or symbols
+that would otherwise be impossible, difficult or repetitive to include by
+hand. </p><div class="skipspace"><p>For example, you need to place a copyright notification (for example, <var class="varname">Copyright
+2004. MyCompany publishing</var>.) at the end of every page of a book.
+Instead of writing it every time, you could create an entity that represents
+this text: <samp class="codeph"><!ENTITY copyright "Copyright 2004. MyCompany publishing."></samp> where <samp class="codeph">copyright</samp> is
+the name of the entity and <samp class="codeph">"Copyright 2004. MyCompany publishing"</samp> is
+the text that the <samp class="codeph">copyright</samp> entity represents.</p>
+<p>To create
+an entity, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>In the Outline view, right-click the DTD <img src="../images/nDTDFile.gif" alt="Image of the DTD icon" /> and click <span class="uicontrol">Add Entity </span>.</span></li>
+<li class="skipspace"><span>In the Properties view, type the new name of the entity in the <span class="uicontrol">Name</span> field.</span></li>
+<li class="skipspace"><span>From the <span class="uicontrol">Entity Type</span> list, select <span class="uicontrol">General</span> or <span class="uicontrol">Parameter</span>. </span> General entities are used in XML files, whereas parameter entities are
+used only in the DTD and do not have any use in an XML file.</li>
+<li class="skipspace"><span>Select the <span class="uicontrol">External</span> check box if you
+want to declare your entity as an external entity. An external entity references
+an external document or data.</span></li>
+<li class="skipspace"><span>If you did make the entity external, the following fields appear:</span><ul><li><span class="uicontrol">Public ID</span> (Optional). Type the path of the
+DTD you want to reference. You can then use the resources in the file you
+are referencing.</li>
+<li><span class="uicontrol">System ID</span>. Type the path of the external data
+or document you want to reference, or browse for it. You can then use the
+resources in the file you are referencing.</li>
+</ul>
+ <p>You only need to specify the <span class="uicontrol">Public ID</span> or
+the <span class="uicontrol">System ID</span>, not both. If, in your DTD, you want
+to use any of the resources (such as elements or attributes) contained in
+the document you have referenced, you must make this entity a <span class="uicontrol">Parameter</span> entity,
+and "expand" the entity by creating an external parameter entity reference
+(right-click the DTD <img src="../images/nDTDFile.gif" alt="Image of the DTD icon" />,
+click <span class="uicontrol">Add Parameter Entity Reference</span>, and select the
+entity you just created). </p>
+</li>
+<li class="skipspace"><span>If you did not make the entity external, you can specify the entity
+value in the <span class="uicontrol">Entity value</span> field. </span></li>
+<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+to provide any information about this entity.</span> The <span class="uicontrol">Documentation</span> page
+is used for human readable material, such as a description of the entity.</li>
+</ol>
+<div class="skipspace">The follow links explain different ways you can reuse entities:</div>
+</div>
+
+<div>
+<blockquote>
+<div class="ulchildlink"><b><a href="../topics/trusintp.html">Reusing internal parameter entities in an attribute name or type</a></b><br />
+Reusing parameter entities in attributes can save you a lot of time. If you have several elements using the exact same attribute, you only have to input the information once (into an entity). </div>
+<div class="ulchildlink"><b><a href="../topics/trusents.html">Reusing the value of one entity in another entity</a></b><br />
+Reusing the value of an entity in another entity can save you time in several ways. For example, if your value is long and complicated, it is much faster to simply reuse an entity than manually type in your value each time. As well, if the value changes, you only have to change it in one location.</div>
+<div class="ulchildlink"><b><a href="../topics/trusextp.html">Reusing external parameter entities in an element's content model</a></b><br />
+Using an entity in a content model can save you time if you want to have the same information in several content models. You can create a DTD that references another DTD and then declares an element whose content model refers to a parameter entity created in another DTD.</div>
+</blockquote>
+
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tedtdtd.html" title="You can edit DTD files in both the Outline view and the Source view. Modifying the content of a DTD determines what can be used in any XML file that is associated with it.">Editing DTDs</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tremvelm.html" title="If you have created elements, attributes, entities, notations, and comments you no longer need, you can delete any of them.">Deleting elements, attributes, entities, notations, and comments</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretnot.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretnot.html
new file mode 100644
index 0000000..e33764a
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretnot.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating notations </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="creatingnotations"><a name="creatingnotations"><!-- --></a>
+
+<h1 class="topictitle1">Creating notations </h1>
+<div><p>Notations are 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="skipspace"><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
+similar to this one: <samp class="codeph"><!NOTATION myshirt SYSTEM "GIF"></samp> which
+defines a notation for a GIF image.</p>
+<p>To create a notation, follow these
+steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>In the Outline view, right-click the DTD <img src="../images/nDTDFile.gif" alt="Image of the DTD icon" /> and select <span class="uicontrol">Add Notation </span>. </span></li>
+<li class="skipspace"><span>In the Properties view, type the name of the notation in the <span class="uicontrol">Name</span> field.</span></li>
+<li class="skipspace"><span>(Optional) In the <span class="uicontrol">Public ID</span> field, type
+any information you want to supply to the user or application. For example,
+a description of what the notation refers to.</span></li>
+<li class="skipspace"><span>In the <span class="uicontrol">System ID</span> field, type any information
+to be passed along to the application dealing with the binary data. For example,
+a URL.</span></li>
+<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> 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 of the notation
+contents.</li>
+</ol>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tedtdtd.html" title="You can edit DTD files in both the Outline view and the Source view. Modifying the content of a DTD determines what can be used in any XML file that is associated with it.">Editing DTDs</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tremvelm.html" title="If you have created elements, attributes, entities, notations, and comments you no longer need, you can delete any of them.">Deleting elements, attributes, entities, notations, and comments</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtdtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtdtd.html
new file mode 100644
index 0000000..7028312
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtdtd.html
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing DTDs</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="tedtdtd"><a name="tedtdtd"><!-- --></a>
+
+<h1 class="topictitle1">Editing DTDs</h1>
+<div><p>You can edit DTD files in both the Outline view and the Source
+view. Modifying the content of a DTD determines what can be used in any XML
+file that is associated with it.</p><div class="skipspace"><p>You can edit DTDs in the following ways:</p>
+<ul><li>Create or remove elements, attributes, entities, notations, and comments</li>
+<li>Edit an element's content model</li>
+<li>Edit a group</li>
+<li>Reuse entities</li>
+</ul>
+<p><b>Editing in the Outline view</b></p>
+<p>The Outline view will show
+you all the items in your DTD as you add them. In this view, you can both
+create and delete DTD nodes. </p>
+<p>The following instructions were written
+for the Resource perspective, but they will also work in many other perspectives.
+To edit a DTD in the Outline view, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Create a new DTD or double-click an existing DTD in the Navigator
+view.</span> It will automatically open in the DTD editor.</li>
+<li class="skipspace"><span>In the Outline view, right-click the DTD <img src="../images/nDTDFile.gif" alt="Image of the DTD file" /> and select the node you want to add to it.</span></li>
+<li class="skipspace"><span>In the Properties view, edit the fields for the node as appropriate.</span></li>
+</ol>
+<div class="skipspace"><p>The DTD editor has a built-in mechanism to handle referential integrity
+issues. When you delete or edit certain components, clean up will automatically
+occur. Refer to the related reference section for more information.</p>
+<p><b>Editing
+in the Source view</b></p>
+<p> You can edit the source code for your DTD in
+the Source view manually.</p>
+<p>The following instructions were written for
+the Resource perspective, but they will also work in many other perspectives.
+To edit a DTD in the Source view, follow these steps:</p>
+<ol><li>Create a new DTD or double-click an existing DTD in the Navigator view.
+It will automatically open in the DTD editor.</li>
+<li>Select the source code you want to edit - you can edit existing nodes
+or create new ones.</li>
+<li>Your changes to the DTD will automatically be reflected in the Outline
+and Properties views. If you have created any errors in your code while editing
+in the Source view, they will appear in the Problems view when you save or
+validate the file.</li>
+<li>The DTD editor has a built-in mechanism to handle referential integrity
+issues, however, this mechanism only works if you delete items using the Outline
+view or edit them in the Properties view. If you delete or edit items using
+the Source view, clean up will not automatically occur; instead you will receive
+error messages in the Problems view if you validate or save the file.</li>
+</ol>
+<p><b>Sorting nodes in the Outline view</b></p>
+<p>By default, DTD nodes
+appear in the Outline view in the order you added them to the DTD. </p>
+<p>If
+you want to sort the DTD nodes alphabetically, click the <span class="uicontrol">Sort
+items alphabetically</span> button <img src="../images/sort.gif" />. </p>
+<p>You
+can also group the DTD nodes into logical groups - notations, entities, elements,
+and other. Click the <span class="uicontrol">Group items logically</span> button <img src="../images/organize_dtd_logically.gif" /> to sort the DTD nodes into logical
+groups.</p>
+<p>The following links contain information on how you can edit
+DTD files:</p>
+</div>
+</div>
+
+<div>
+<blockquote>
+<div class="ulchildlink"><b><a href="../topics/tcretelm.html">Creating elements</a></b><br />
+You can use element declarations in DTDs to define the elements that may occur in an XML document. Element declarations can specify that an element can contain other elements, that it can contain anything at all, or that it must be empty.</div>
+<div class="ulchildlink"><b><a href="../topics/tcretent.html">Creating entities</a></b><br />
+An entity is a shortcut used to represent complex strings or symbols that would otherwise be impossible, difficult or repetitive to include by hand.</div>
+<div class="ulchildlink"><b><a href="../topics/tcretnot.html">Creating notations</a></b><br />
+Notations are 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.</div>
+<div class="ulchildlink"><b><a href="../topics/tcretcomm.html">Creating a comment</a></b><br />
+Comments can be used to provide information about a document, such as the author's name, or the date it was last modified. Comments are visible to anyone reading the DTD, but are ignored by the XML parser.</div>
+<div class="ulchildlink"><b><a href="../topics/tremvelm.html">Deleting elements, attributes, entities, notations, and comments</a></b><br />
+If you have created elements, attributes, entities, notations, and comments you no longer need, you can delete any of them.</div>
+</blockquote>
+<p><b class="relconceptshd">Related concepts</b><br />
+<a href="../topics/cdtdedit.html" title="After you have created or imported a DTD, you can open it in the DTD editor (by double-clicking it in the Navigator view), a tool for viewing and editing DTDs. You can use the DTD editor to perform a variety of tasks such as creating, editing, and deleting DTD elements, attributes, entities, notations, and comments">DTD editor</a><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><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<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 />
+<a href="../topics/timptdtd.html" title="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. The DTD editor provides you with a structured view of the DTD.">Importing DTDs</a><br />
+</p>
+<p><b class="relrefhd">Related reference</b><br />
+<a href="../topics/rrefint.html" title="The DTD editor has a built-in mechanism to handle referential integrity issues. When you delete or rename certain nodes, clean up for any nodes affected will automatically occur.">Referential integrity in the DTD editor</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtgnde.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtgnde.html
new file mode 100644
index 0000000..28b0fe3
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtgnde.html
@@ -0,0 +1,126 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing a group node</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="tedtgnde"><a name="tedtgnde"><!-- --></a>
+
+<h1 class="topictitle1">Editing a group node</h1>
+<div><p>If your element has either element content or mixed content, its
+content model is represented by a group node. You can add children elements
+or another group to a group node, and specify how often, and
+in what manner a group of elements will be available in an XML file associated
+with your DTD.</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>To
+edit a group node, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>In the Outline view, expand the tree of the element you want to
+work with.</span></li>
+<li class="skipspace"><span>Click the group node you want to work with.</span></li>
+<li class="skipspace"><span>In the Design view, select <span class="uicontrol">Sequence</span> or <span class="uicontrol">Choice</span> from
+the <span class="uicontrol">Model Group</span> list.</span> This specifies whether
+the group of elements are sorted in sequence or are available as a choice
+in an XML file </li>
+<li class="skipspace"><span>Select the appropriate option from the <span class="uicontrol">Occurrence</span> list
+to indicate how often the group of elements can occur in an XML file associated
+with this DTD. </span></li>
+<li class="skipspace"><span>To add another existing element to a group as a child, right-click
+the group node, click <span class="uicontrol">Add Element to Content Model</span>,
+and specify its name.</span></li>
+<li class="skipspace"><span>You can also add a group to an existing group node, by right-clicking
+the group note and clicking <span class="uicontrol">Add Group to Content Model</span></span></li>
+</ol>
+<div class="skipspace"><p> <b>Note:</b>The <span class="uicontrol">Occurrence</span> option for the
+group node only specifies how often the entire group of elements can occur
+in an XML file. For each child element contained in the group, you can also
+specify how often it can occur (that is, how often a child element can occur
+is completely separate from how the often the group that contains it can occur).</p>
+<p> <b>Tip:</b>:
+To change the order of elements listed below a group node, simply click the
+element you want to move and drag it to the location you want it in.</p>
+</div>
+<div class="skipspace"><p><b>Creating a group node that contains a list of small pets</b></p>
+<p>The
+following steps show you how to create a group node that contains a list of
+small pets and explains how the choices you select affect how your group node
+(and the elements it contains) can be used in any XML files based on your
+DTD file:</p>
+<ol><li>Create a new DTD called <kbd class="userinput">Pets.dtd</kbd> and open it in
+the DTD editor.</li>
+<li>In the Outline view, right-click your DTD file, and create a new element <kbd class="userinput">SmallPets</kbd>.
+Also create three more elements - <kbd class="userinput">Cats</kbd>,<kbd class="userinput">Dogs</kbd>,
+and.<kbd class="userinput">Fish</kbd></li>
+<li>Expand <span class="uicontrol">SmallPets</span> and select the <span class="uicontrol">EMPTY</span> content
+model. Select <span class="uicontrol">Mixed Content</span> from the <span class="uicontrol">Content
+type</span> list. This means your <span class="uicontrol">SmallPets</span> element
+can contain both other elements and character data.</li>
+<li>Your content model is now represented by a group node <img src="../images/XSDChoice.gif" />.
+A #PCDATA element (for character data) and new child element are automatically
+created below it. Select the <span class="uicontrol">newChild</span> and select
+ <span class="uicontrol">Dogs</span> in the <span class="uicontrol">Name</span> list.</li>
+<li>Right-click the group node and click <span class="uicontrol">Add Element to Content
+Model</span>. Select the new child node and select <span class="uicontrol">Cats</span> in
+the <span class="uicontrol">Name</span> list.</li>
+<li>Repeat the previous step and select <span class="uicontrol">Fish</span> in the <span class="uicontrol">Name</span> list.</li>
+<li>Now that you have created your list of small pets, you have to decide
+if you want users to be able to select all of them or just one of them in
+an XML file based on this Pets.dtd file. For example, you create a new XML
+file called <kbd class="userinput">Pets.xml</kbd> based on this DTD, and you create
+a <kbd class="userinput">SmallPets</kbd> element in it. If you selected <span class="uicontrol">Sequence</span> as
+the model group in the DTD file, then you can have all of the small pets ( <span class="uicontrol">Cats</span>,
+ <span class="uicontrol">Dogs</span> and <span class="uicontrol">Fish</span>) in your <span class="uicontrol">SmallPets</span> element
+in the <span class="uicontrol">Pets.xml</span> file. If, however, you selected <span class="uicontrol">Choice</span> as
+the connector type, you can only have one animal listed in your <span class="uicontrol">SmallPets</span> element
+in the <span class="uicontrol">Pets.xml</span> file. You can have <span class="uicontrol">Cats</span> or
+ <span class="uicontrol">Dogs</span> or <span class="uicontrol">Fish</span>, but you can
+only have one at a time.</li>
+<li>Now you have to decide how often this group of elements (the list of small
+pets) can occur in an XML file associated with this DTD. You can specify
+that it must appear only once ( <span class="uicontrol">Just once</span>), that it
+must appear one or more times ( <span class="uicontrol">One or more</span>), that
+it does not have to appear at all ( <span class="uicontrol">Optional</span>) or that
+it might not be used at all or might be used any number of times ( <span class="uicontrol">Zero
+or more</span>). <span class="uicontrol">Note</span>: You can also specify how
+often each child element can occur. How often a child element can occur is
+completely separate from how the often the group that contains it can occur.
+So, for example, you can specify that the <span class="uicontrol">SmallPets</span> group
+can occur <span class="uicontrol">Just once</span>, but the Cats element can appear
+several times (to do this, select the <span class="uicontrol">Cats</span> element
+and click <span class="uicontrol">One or more</span>).</li>
+<li>The order in which you specify child elements in a group affects how they
+can be used in any instances of the parent element in an XML file. For example,
+if, in your DTD file, you had specified this: <samp class="codeph"><!ELEMENT SmallPets
+(Dogs+ , Cats+ , Fish)+></samp>, any instances of<span class="uicontrol">SmallPets</span> in
+your <span class="uicontrol">Pets.xml</span> file must contain one or more instances
+of <span class="uicontrol">Dogs</span> followed by one or more instances of <span class="uicontrol">Cats</span>,
+followed by just one occurrence of <span class="uicontrol">Fish</span>. You could
+never have an occurrence of <span class="uicontrol">Fish</span> after <span class="uicontrol">Dogs</span> or <span class="uicontrol">Cats</span> before <span class="uicontrol">Dogs</span>. </li>
+<li>You can also add a group to an existing group node. Select the node, right-click
+it and click <span class="uicontrol">Add Group to Content Model</span>. You
+might want to add a group node, if you decided you wanted to sort the animals
+by breed into separate groups. </li>
+</ol>
+</div>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tchgelm.html" title="An element's content model represents any data that can be contained inside or within the content of an element (that is, between the start and end tags of an element in an XML file). Editing an element's content model enables you to determine exactly what the element can (and cannot) contain.">Editing an element's content model</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tgenxmls.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tgenxmls.html
new file mode 100644
index 0000000..bfdb7fc
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tgenxmls.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Generating XML schemas from DTD files</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tgenxmls"><a name="tgenxmls"><!-- --></a>
+
+<h1 class="topictitle1">Generating XML schemas from DTD files</h1>
+<div><p>Generating an XML schema from a DTD file enables you to create
+an XML schema that is automatically populated with elements and attributes
+from your DTD file. This can save you time if you want to use an XML schema
+rather than a DTD file to validate your XML file, but you want to use the
+rules already set up in your DTD file.</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 generate
+an XML schema file from a DTD file, follow these steps:</p>
+</div>
+<ol><li><span>In the Navigator view, right-click your DTD and click <span class="menucascade"><span class="uicontrol">Generate</span> > <span class="uicontrol"> XML Schema</span></span>.</span></li>
+<li><span>Select the project or folder that will contain the schema. </span></li>
+<li><span>Accept the default name or type a new one and click <span class="uicontrol">Next</span>.</span></li>
+<li><span>If you want to create an XML schema that will contain your DTD
+file and any DTD files it references, click the <span class="uicontrol">Create one XML
+schema that includes all the DTD files</span> radio button.</span></li>
+<li><span>Otherwise, if you want to create an individual schema for your
+DTD file and each DTD file it references, click the <span class="uicontrol">Create an XML
+schema for each DTD file</span> radio button.</span></li>
+<li><span>Click <span class="uicontrol">Finish</span>.</span></li>
+</ol>
+<div class="skipspace"><p>Your schemas appears in the Navigator view. They will have the
+same name as the DTD file they were generated from (if you accepted the default
+value in the <span class="uicontrol">File name</span> field when you generated the
+XML schema). </p>
+<p>Any entities that were in your DTD file will not be in
+the XML schema (as entities are not supported in XML schemas). However,
+any elements or attributes that referred to an entity will carry over that
+value to an XML schema.</p>
+</div>
+<div class="skipspace"><p>For example, you have a DTD called "Legal" that contains an entity
+called "Copyright". The value of the entity is "Copyright 2004. MyCompany
+Publishing" . In your DTD, you have an element called "MyCopyright", which
+refers to the entity Copyright. After you create the XML schema, the Copyright
+entity will not appear in the XML schema, however, its value is carried over
+(that is, MyCopyright will have the value: Copyright 2004. MyCompany Publishing
+).</p>
+<p>All elements and attributes that existed in your DTD file will exist
+in the XML schema file.</p>
+<p>Elements in your DTD with a content model of
+(#PCDATA) (and no attributes) appear empty in the XML schema editor. They
+are marked as having <span class="uicontrol">Built-in simple types</span> of <samp class="codeph">string</samp>.
+That is, a DTD element with a value of (#PCDATA) will map to an XML schema
+element with an XML schema primitive type <samp class="codeph">string</samp>.</p>
+<div class="note"><span class="notetitle">Note: </span>When
+you generate an XML schema from a DTD file that contains Hebrew or Arabic
+elements, certain element names might be encoded with their equivalent hexadecimal
+Hebrew and Arabic encoding values. To avoid this problem, change the encoding
+attribute of the original DTD or XML schema file to UTF-8 before performing
+the generation: That is, the XML declaration should be: <samp class="codeph"><?xml
+version="1.0" encoding="UTF-8"?></samp> The list of affected encoding values
+is: ISO-8859-8-I, ISO-8859-8, Windows-1256, and ISO-8859-6.</div>
+</div>
+</div>
+
+<p><b class="reltaskshd">Related tasks</b><br />
+<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>Related information</b><br /><a href="../../org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html">Editing XML schemas</a><br /></p>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html
new file mode 100644
index 0000000..40d9139
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Importing DTDs</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="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. The DTD editor provides you with a structured view of
+the DTD.</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">File</span> > <span class="uicontrol">Import</span></span>.</span></li>
+<li><span>Select the import source and click <span class="uicontrol">Next</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">Finish</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.</p>
+</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tedtdtd.html" title="You can edit DTD files in both the Outline view and the Source view. Modifying the content of a DTD determines what can be used in any XML file that is associated with it.">Editing DTDs</a><br />
+</p>
+</div>
+ <p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tremvelm.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tremvelm.html
new file mode 100644
index 0000000..652170e
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tremvelm.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Deleting elements, attributes, entities, notations, and comments</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="tremvelm"><a name="tremvelm"><!-- --></a>
+
+<h1 class="topictitle1">Deleting elements, attributes, entities, notations, and comments</h1>
+<div><p>If you have created elements, attributes, entities, notations,
+and comments you no longer need, you can delete any of them. </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 delete
+an element, attribute, entity, notation or comment:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>In the Outline view, click the element, attribute, entity, notation,
+or comment you want to delete.</span> If you want to delete more
+than one item, hold down the<span class="uicontrol">Ctrl</span> key while you select
+items.</li>
+<li class="skipspace"><span>Right-click the item (or one of the items if you have selected
+more than one), and, from its pop-up menu, click <span class="uicontrol">Delete</span>.</span></li>
+</ol>
+<div class="skipspace"><p>You can "undo" the deletion of an item. To do so, right-click any
+element, attribute, entity, notation, or comment and click <span class="uicontrol">Undo
+Delete</span>. You must do this before you close the editor, otherwise,
+your items will no longer exist on the system and you will have to recreate
+them if you want them again.</p>
+<p>The DTD editor has a built-in mechanism
+to handle referential integrity issues. When you delete or rename certain
+nodes, clean up will automatically occur. </p>
+</div>
+</div>
+
+<div>
+<blockquote>
+<div class="ulchildlink"><b><a href="../topics/rrefint.html">Referential integrity in the DTD editor</a></b><br />
+The DTD editor has a built-in mechanism to handle referential integrity issues. When you delete or rename certain nodes, clean up for any nodes affected will automatically occur.</div>
+</blockquote>
+
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tedtdtd.html" title="You can edit DTD files in both the Outline view and the Source view. Modifying the content of a DTD determines what can be used in any XML file that is associated with it.">Editing DTDs</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcretattr.html" title="You can use an attribute to describe an element or provide information about it. Attribute lists enable you to group together all related attributes for an element.">Creating attributes and attribute lists</a><br />
+<a href="../topics/tcretcomm.html" title="Comments can be used to provide information about a document, such as the author's name, or the date it was last modified. Comments are visible to anyone reading the DTD, but are ignored by the XML parser.">Creating a comment</a><br />
+<a href="../topics/tcretent.html" title="An entity is a shortcut used to represent complex strings or symbols that would otherwise be impossible, difficult or repetitive to include by hand.">Creating entities</a><br />
+<a href="../topics/tcretnot.html" title="Notations are 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.">Creating notations</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+ </p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusents.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusents.html
new file mode 100644
index 0000000..9f05011
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusents.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Reusing the value of one entity in another entity</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="trusents"><a name="trusents"><!-- --></a>
+
+<h1 class="topictitle1">Reusing the value of one entity in another entity</h1>
+<div><p>Reusing the value of an entity in another entity can save you time
+in several ways. For example, if your value is long and complicated, it is
+much faster to simply reuse an entity than manually type in your value each
+time. As well, if the value changes, you only have to change it in one location.</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>You
+can create an entity that reuses another entity. To do so, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Open your DTD in the DTD editor.</span></li>
+<li class="skipspace"><span>Create an entity.</span> <ol type="a"><li><span>Type a name for the entity and select <span class="uicontrol">Parameter</span> from
+the <span class="uicontrol">Entity type</span> list.</span></li>
+<li><span>Type the value of the entity in the <span class="uicontrol">Entity Value</span> field.</span></li>
+</ol>
+</li>
+<li class="skipspace"><span>Create another entity.</span><ol type="a"><li><span>Type a name and select <span class="uicontrol">General</span> from the <span class="uicontrol">Entity
+type</span> list.</span></li>
+<li><span>In the <span class="uicontrol">Entity Value</span> field, type a reference
+to the first parameter entities' value (that is, type %<var class="varname">parmentityname</var>;)</span></li>
+</ol>
+</li>
+</ol>
+<div class="skipspace"><p>You now have two entities with the exact same value. </p>
+</div>
+<div class="skipspace">The following sample shows how you might create an entity that reuses
+the value of another entity.<p>You need to place a copyright at the end of
+every page of a book. On even pages, you need to put "Copyright 2003" and
+on odd pages, you need to put "Copyright 2003. MyCompany Publishing." First
+you will declare an entity with the simpler value and then create an entity
+with the more complicated value.</p>
+<ol><li>Open your DTD in the DTD editor.</li>
+<li>Create an entity. In the <span class="uicontrol">Name</span> field, type <kbd class="userinput">CopyrightDate</kbd>.
+Select <span class="uicontrol">Parameter</span> from the <span class="uicontrol">Entity type</span> list.
+In the <span class="uicontrol">Entity Value</span>, type <kbd class="userinput">Copyright 2003</kbd>.</li>
+<li>Create another entity. In the <span class="uicontrol">Name</span> field, type <kbd class="userinput">CompanyCopyright</kbd>.
+Select <span class="uicontrol">General</span> from the <span class="uicontrol">Entity type</span> list.
+In the<span class="uicontrol">Entity Value</span> field, type <kbd class="userinput">%CopyrightDate;
+MyCompany Publishing</kbd>.</li>
+</ol>
+<p>Now, if you need to change the copyright date, you only need to do
+so in one place, not two.</p>
+<p> <b>Note</b>: Since you had to make the CopyrightDate
+entity a <span class="uicontrol">Parameter</span> entity in order to be able to reference
+it in the CompanyCopyright entity, you cannot use it in an XML file.
+You would have to create a third entity called <kbd class="userinput">XMLCopyrightDate</kbd> with
+a value of <kbd class="userinput">%CopyrightDate;</kbd> and use it instead in the
+XML file.</p>
+<p>To use the entity in an XML document, you must use the ampersand <kbd class="userinput">&</kbd> followed
+by the name of the entity, and then end with the semi-colon <kbd class="userinput">;</kbd>.
+So, in an XML document, if you were working with an even page, you would need
+to put this:</p>
+<p><kbd class="userinput">&XMLCopyrightDate; </kbd></p>
+<p> to
+call the XMLCopyrightDate entity. Remember, you cannot call the CopyrightDate
+entity because you had to make it a <span class="uicontrol">Parameter</span> entity
+in order to be able to reference it in the CompanyCopyright entity.</p>
+<p>If
+you were working with an odd page, you would need to put this:</p>
+<p><kbd class="userinput">&CompanyCopyright; </kbd></p>
+<p> to
+call the CompanyCopyright entity.</p>
+</div>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tcretent.html" title="An entity is a shortcut used to represent complex strings or symbols that would otherwise be impossible, difficult or repetitive to include by hand.">Creating entities</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/trusintp.html" title="Reusing parameter entities in attributes can save you a lot of time. If you have several elements using the exact same attribute, you only have to input the information once (into an entity). ">Reusing internal parameter entities in an attribute name or type</a><br />
+<a href="../topics/trusextp.html" title="Using an entity in a content model can save you time if you want to have the same information in several content models. You can create a DTD that references another DTD and then declares an element whose content model refers to a parameter entity created in another DTD.">Reusing external parameter entities in an element's content model</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusextp.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusextp.html
new file mode 100644
index 0000000..b338efc
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusextp.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Reusing external parameter entities in an element's content model</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="trusextp"><a name="trusextp"><!-- --></a>
+
+<h1 class="topictitle1">Reusing external parameter entities in an element's content model</h1>
+<div><p>Using an entity in a content model can save you time if you want
+to have the same information in several content models. You can create a DTD
+that references another DTD and then declares an element whose content model
+refers to a parameter entity created in another DTD. </p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
+but they will also work in many other perspectives. </p>
+<p>To create
+a DTD that reuses an external parameter entity in an element's content model,
+follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>Create a new DTD.</span> If you want to work with an existing
+DTD, open your DTD in the DTD editor.</li>
+<li class="skipspace"><span>Create an entity (for example, <kbd class="userinput">MyEntity</kbd>).</span></li>
+<li class="skipspace"><span>Select <span class="uicontrol">Parameter</span> from the <span class="uicontrol">Entity
+type</span> list, and type a value for the entity in the <span class="uicontrol">Entity
+value</span> field. </span></li>
+<li class="skipspace"><span>Save your DTD file.</span></li>
+<li class="skipspace"><span>Create another DTD.</span></li>
+<li class="skipspace"><span>Create another entity (for example, <kbd class="userinput">MySecondEntity</kbd>). </span></li>
+<li class="skipspace"><span>Select <span class="uicontrol">Parameter</span> from the <span class="uicontrol">Entity
+type</span> list and select the <span class="uicontrol">External</span> check
+box to declare this as an external entity.</span></li>
+<li class="skipspace"><span>In the <span class="uicontrol">System ID</span> field, type the path of
+the DTD (or click the <span class="uicontrol">More</span> button to browse for a file)
+you created in step 1 . The path is relative to the workspace root.</span></li>
+<li class="skipspace"><span>(Optional) Type a value in the <span class="uicontrol">Public ID</span> field.</span></li>
+<li class="skipspace"><span>In the Outline view, right-click the DTD and click <span class="uicontrol">Add
+Parameter Entity Reference</span> to add a reference to the entity you
+created in step 6 (for example, <kbd class="userinput">MySecondEntity</kbd>).</span></li>
+<li class="skipspace"><span>Add an element.</span></li>
+<li class="skipspace"><span>Change the content type for this element from EMPTY to the
+value you specified in step 2 (for example,<kbd class="userinput">MyEntity</kbd>).</span> Note how you can select the value you specified in step 2 in the list
+for the content element. This is because you included the first DTD that you
+created in an earlier step.</li>
+</ol>
+<div class="skipspace"><p>You now have a DTD that references another DTD and declares an
+element whose content model refers to a parameter entity created in the other
+DTD. </p>
+</div>
+<div class="skipspace"><p>The following sample shows how you might reuse external parameter
+entities in an element's content model.</p>
+<p>You are making a list of everything
+you have in both your work office and your home office. You have a computer
+in each office and you do not want to write out a list of each part of your
+computer more than once.</p>
+<ol><li>Create a new DTD called <kbd class="userinput">WorkOffice.dtd.</kbd>.</li>
+<li>Create the following four elements: <kbd class="userinput">Monitor</kbd>,<kbd class="userinput">Keyboard</kbd>, <kbd class="userinput">Mouse</kbd>,
+and <kbd class="userinput">Hard_Drive</kbd>. Make the value of each element <span class="uicontrol">(#PCDATA)</span>.</li>
+<li>Add an entity called <kbd class="userinput">WorkComp</kbd>. Select <span class="uicontrol">Parameter</span> as
+the <span class="uicontrol">Entity type</span>. In the <span class="uicontrol">Value</span> field,
+type: <kbd class="userinput">(Monitor, Keyboard, Mouse, Hard_Drive)</kbd>. Click
+ <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol"> Save</span></span></li>
+<li>Create another DTD called <kbd class="userinput">HomeOffice.dtd</kbd></li>
+<li>Add an entity called <kbd class="userinput">HomeComp</kbd> to your HomeOffice.dtd
+. Select <span class="uicontrol">Parameter</span> as the <span class="uicontrol">Entity type</span> and
+click the <span class="uicontrol">External</span> check box to declare this as an
+external entity. In the <span class="uicontrol">System ID</span> field, type the path
+(or click the <span class="uicontrol">More</span> button to browse for the file) of <span class="uicontrol">WorkOffice.dtd</span>.
+The path is relative to the workspace root.</li>
+<li>(Optional) Type a value in the <span class="uicontrol">Public ID</span> field.</li>
+<li>In the Outline view, right-click the DTD and select <span class="uicontrol">Add Parameter
+Entity Reference</span> to add the entity you created earlier (that is,
+%HomeComp;).</li>
+<li>Add an element called <kbd class="userinput">MyHomeComp</kbd>. Change the content
+model for MyHomeComp from <span class="uicontrol">EMPTY</span> to <b>Work Office:
+%WorkComp;</b>. The value of MyHomeComp is now: <b>Monitor Keyboard Mouse
+Hard_Drive</b>. Note how you can select the value you specified in step
+4 in the <span class="uicontrol">Content type</span> list for the content element.
+This is because you included the first DTD you created in an earlier step.</li>
+</ol>
+</div>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tcretent.html" title="An entity is a shortcut used to represent complex strings or symbols that would otherwise be impossible, difficult or repetitive to include by hand.">Creating entities</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/trusents.html" title="Reusing the value of an entity in another entity can save you time in several ways. For example, if your value is long and complicated, it is much faster to simply reuse an entity than manually type in your value each time. As well, if the value changes, you only have to change it in one location.">Reusing the value of one entity in another entity</a><br />
+<a href="../topics/trusintp.html" title="Reusing parameter entities in attributes can save you a lot of time. If you have several elements using the exact same attribute, you only have to input the information once (into an entity). ">Reusing internal parameter entities in an attribute name or type</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusintp.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusintp.html
new file mode 100644
index 0000000..586435c
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/trusintp.html
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Reusing internal parameter entities in an attribute name or type</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="trusintp"><a name="trusintp"><!-- --></a>
+
+<h1 class="topictitle1">Reusing internal parameter entities in an attribute name or type</h1>
+<div><p>Reusing parameter entities in attributes can save you a lot of
+time. If you have several elements using the exact same attribute, you only
+have to input the information once (into an entity). </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>You
+can create a DTD that reuses internal parameter entities in attributes. To
+reuse internal parameter entities in attributes, follow these steps:</p>
+</div>
+<ol><li class="skipspace"><span>In the workbench, create a new DTD.</span></li>
+<li class="skipspace"><span>Add a new entity to the DTD you just created.</span></li>
+<li class="skipspace"><span>Select <span class="uicontrol">Parameter</span> from the <span class="uicontrol">Entity
+type</span> list, and type a value in the <span class="uicontrol">Entity Value</span> field.</span></li>
+<li class="skipspace"><span>Create an element and add an attribute to it. </span></li>
+<li class="skipspace"><span>If you want to reuse the entity in an attribute name, in the <span class="uicontrol">Name</span> field
+for the attribute, type the name of the entity (that is, %NewEntity;) then
+in the <span class="uicontrol">Type</span> field, select the type for the attribute.</span> <b>Tip</b>: If you want to use an entity to replace an entire attribute
+definition, select <span class="uicontrol">(none)</span> from the <span class="uicontrol">Type</span> list.</li>
+<li class="skipspace"><span>If you want to reuse the entity as the type of an attribute, type
+the name of the attribute, and, in the <span class="uicontrol">Type</span> field,
+click the name of the entity you created in step 2.</span></li>
+<li class="skipspace"><span>Repeat steps 4 and 5 or 4 and 6 as applicable.</span></li>
+</ol>
+<div class="skipspace">You now have two attributes with the same name or type.</div>
+<div class="skipspace"><p> The following sample shows how you might reuse internal parameter
+entities in an attribute type.</p>
+<p>You are making a list of office supplies,
+and all your supplies have Part and Stock attributes.</p>
+<ol><li>Create a new DTD called <kbd class="userinput">OfficeSupplies.dtd</kbd> .</li>
+<li>Add an entity called <kbd class="userinput">PartStock</kbd>. Select <span class="uicontrol">Parameter</span> from
+the <span class="uicontrol">Entity type</span> list. In the <span class="uicontrol">Entity Value</span> field,
+type <kbd class="userinput">Part ID #REQUIRED Stock CDATA #IMPLIED</kbd>.</li>
+<li>Add three new elements to OfficeSupplies.dtd: <kbd class="userinput">pen</kbd>, <kbd class="userinput">paper</kbd>,
+and <kbd class="userinput">pencils</kbd>. Make the value of each element <span class="uicontrol">(#PCDATA)</span>.</li>
+<li>Right-click <span class="uicontrol">pen</span> and click <span class="uicontrol">Add Attribute</span>.
+In the <span class="uicontrol">Name</span> field for the attribute, type <kbd class="userinput">ID_Numbers</kbd>.
+In the <span class="uicontrol">Type</span> field, click <span class="uicontrol"> %PartStock;</span>.</li>
+<li>Repeat step 4 for <span class="uicontrol">paper</span> and <span class="uicontrol">pencils.</span></li>
+</ol>
+<p>You now have three elements with the same attribute. </p>
+</div>
+</div>
+
+<div>
+<p>
+<b class="parentlink">Parent topic:</b> <a href="../topics/tcretent.html" title="An entity is a shortcut used to represent complex strings or symbols that would otherwise be impossible, difficult or repetitive to include by hand.">Creating entities</a><br />
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/trusents.html" title="Reusing the value of an entity in another entity can save you time in several ways. For example, if your value is long and complicated, it is much faster to simply reuse an entity than manually type in your value each time. As well, if the value changes, you only have to change it in one location.">Reusing the value of one entity in another entity</a><br />
+<a href="../topics/trusextp.html" title="Using an entity in a content model can save you time if you want to have the same information in several content models. You can create a DTD that references another DTD and then declares an element whose content model refers to a parameter entity created in another DTD.">Reusing external parameter entities in an element's content model</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html
new file mode 100644
index 0000000..e5c797a
--- /dev/null
+++ b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Validating DTDs</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="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">Validate DTD File</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">Properties</span> > <span class="uicontrol">Validation</span></span> from the project's pop-up menu and specifying the maximum number
+of error messages allowed. You might have to select the <span class="uicontrol">Override
+validation preferences</span> check box in order to enable the <span class="uicontrol">Maximum
+number of validation messages</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 <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>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.html.ui.infopop/.project b/docs/org.eclipse.wst.html.ui.infopop/.project
new file mode 100644
index 0000000..59fe31e
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.html.ui.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ </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..869d87f
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts.xml
@@ -0,0 +1,103 @@
+<?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="ehtm0000">
+<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>
+
+<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/about.html b/docs/org.eclipse.wst.html.ui.infopop/about.html
new file mode 100644
index 0000000..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.html.ui.infopop/plugin.xml b/docs/org.eclipse.wst.html.ui.infopop/plugin.xml
new file mode 100644
index 0000000..eda742f
--- /dev/null
+++ b/docs/org.eclipse.wst.html.ui.infopop/plugin.xml
@@ -0,0 +1,28 @@
+<?xml version="1.0"?>
+<?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
+ id="org.eclipse.wst.html.ui.infopop"
+ name="HTML editor infopops"
+ version="0.7.0"
+ provider-name="Eclipse.org">
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorHtmlContexts.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/.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/about.html b/docs/org.eclipse.wst.sse.doc.user/about.html
new file mode 100644
index 0000000..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.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..15a1d5a
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/plugin.xml
@@ -0,0 +1,33 @@
+<?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
+ id="org.eclipse.wst.sse.doc.user"
+ name="Structured text editor and snippets documentation"
+ version="0.7.0"
+ vendor-name = "Eclipse.org">
+
+ <runtime>
+ </runtime>
+
+ <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..4f3c52f
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- /*******************************************************************************
+ * 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="Checking spelling" href="topics/tsrcedt010.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..a54efa7
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Snippets view</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="csrcedt001"><a name="csrcedt001"><!-- --></a>
+
+<h1 class="topictitle1">Snippets view</h1>
+<div><p>This documentation gives an overview of the Snippets view.</p><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>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html
new file mode 100644
index 0000000..5d99500
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Structured text editors for markup languages</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html
new file mode 100644
index 0000000..7cfd367
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>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="csrcedt006"><a name="csrcedt006"><!-- --></a>
+
+<h1 class="topictitle1">Content assist</h1>
+<div><p>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.</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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html
new file mode 100644
index 0000000..67f8ed6
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing text coded in markup languages - overview</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html
new file mode 100644
index 0000000..b2491aa
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Setting annotation preferences for markup languages</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html
new file mode 100644
index 0000000..407f1a4
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Getting content assistance in structured text editors</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html
new file mode 100644
index 0000000..77e0fa5
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Searching or finding text within a file</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html
new file mode 100644
index 0000000..7d357f6
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Checking spelling</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html
new file mode 100644
index 0000000..28fef9f
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding snippets drawers</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html
new file mode 100644
index 0000000..c04fd09
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding items to snippets drawers</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html
new file mode 100644
index 0000000..ee5b4af
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Deleting or hiding snippet items or drawers</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html
new file mode 100644
index 0000000..c78d6ee
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing snippet items</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html
new file mode 100644
index 0000000..816f2b1
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Making content assist work for JSP files</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html
new file mode 100644
index 0000000..b888500
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding and removing HTML templates</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html
new file mode 100644
index 0000000..20e6d00
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Setting preferences for structured text editors</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="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html
new file mode 100644
index 0000000..86862e6
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing with snippets - overview</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html
new file mode 100644
index 0000000..eb1447f
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding and removing markup language templates - overview</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html
new file mode 100644
index 0000000..cfc9adb
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding and removing JSP templates</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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, you may work on a group of JSP 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 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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html
new file mode 100644
index 0000000..ff61af3
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding and removing XML templates</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.project b/docs/org.eclipse.wst.sse.ui.infopop/.project
new file mode 100644
index 0000000..e8d46c2
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.ui.infopop/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.sse.ui.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.sse.ui.infopop/EditorContexts.xml b/docs/org.eclipse.wst.sse.ui.infopop/EditorContexts.xml
new file mode 100644
index 0000000..faccfb3
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.ui.infopop/EditorContexts.xml
@@ -0,0 +1,75 @@
+<?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
+ *******************************************************************************/ -->
+<contexts>
+
+<context id="sted0001">
+<description>This page lets you customize the appearance of the structured text editors.
+When the <b>Highlight matching brackets</b> option is selected, whenever the cursor is next to a bracket or curly braces, its opening or closing counter part is highlighted.
+Select the <b>Report problems as you type</b> check box to update validity annotations (temporary annotations, such as missing required attributes based on a DTD, that go away when the editor is closed, or the problem is fixed) as the user types.
+In the <b>Appearance color options</b> table, you can adjust various editor appearance features.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="sted0003">
+<description>This page lets you customize hover text in the structured text editors.
+</description>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclispe.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="xmlm1010">
+<description>Content assist helps you to finish tags or lines of code and insert templates. Depending on the source markup language, the choices that are available in the content assist list are based on tags defined by DTD and schema files, tag library descriptors, or content model standard that is specified for the file being edited. HTML content assist choices are based on the W3C HTML 4.01 content model.
+
+If your cursor is in a position where content assist is available, a pop-up list of available choices is displayed. The content assist list displays all available completions for the current cursor position, including templates. Content assist is also available by pressing Ctrl+Space.
+</description>
+<topic label="Content assist" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt006.html"/>
+<topic label="Getting content assistance in structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="xmlm1030">
+<description>Select this option to format an entire document. Formatting restores element and attribute indentation and positioning, which may have been offset during editing, to see nesting hierarchies and relationships more clearly in the file. Edit the appropriate Preferences pages to make changes in specific formatting behavior.
+</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="xmlm1040">
+<description>Select this option to format selected elements. Formatting restores element and attribute indentation and positioning, which may have been offset during editing, to see nesting hierarchies and relationships more clearly in the file.
+</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="xmlm1070">
+<description>Select this option to open the <b>Properties</b> view, which displays properties relevant to the current element if any exist.
+</description>
+<topic label="Properties view" href="../org.eclipse.platform.doc.user/concepts/cpropview.htm"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="xmlm2000">
+<description>This structured text editor lets you edit a text file that is coded in a markup language. The editor provides many text editing features, such as content assist, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting. For a more specific list of editing features, see the first link below.
+</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="webx0000">
+<description>This page lets you customize task tag discovery in the structured text editors.
+</description>
+</context>
+
+</contexts>
diff --git a/docs/org.eclipse.wst.sse.ui.infopop/about.html b/docs/org.eclipse.wst.sse.ui.infopop/about.html
new file mode 100644
index 0000000..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.ui.infopop/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.ui.infopop/plugin.xml b/docs/org.eclipse.wst.sse.ui.infopop/plugin.xml
new file mode 100644
index 0000000..3ceafc6
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.ui.infopop/plugin.xml
@@ -0,0 +1,25 @@
+<?xml version="1.0"?>
+<?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
+ *******************************************************************************/ -->
+
+<plugin
+ id="org.eclipse.wst.sse.ui.infopop"
+ name="SSE infopops"
+ version="0.7.0"
+ provider-name="Eclipse.org">
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorContexts.xml" plugin ="org.eclipse.wst.sse.ui"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
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..6620c98
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.xml.ui.infopop</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ </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..d7a9e42
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts.xml
@@ -0,0 +1,135 @@
+<?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="exml0000">
+<description>The XML source page editor 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 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 XML templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html"/>
+</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 label="Setting preferences for structured text editors" href="../org.eclispe.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</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 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.
+
+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, 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.
+
+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 label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/>
+</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> 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="webx0063">
+<description>
+This page lets you create new and edit existing templates that will be used when editing an XML 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 word_selection variable indicates the word that is selected at the beginning of template insertion, and the cursor variable determines where the cursor will be after the template is inserted in the document.
+
+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 Templates preferences page.
+</description>
+<topic label="Adding and removing XML templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html"/>
+<topic label="Setting preferences for structured text editors" href="../org.eclipse.sse.doc.user/topics/tsrcedt025.html"/>
+</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 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.eclipe.wst.sse.doc.user/topics/csrcedt004.html"/>
+<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.sse.doc.user/topics/tsrcedt000.html"/>
+</context>
+
+<context id="xcui0500">
+<!--Edit attribute dialog -->
+<description>Enter the name of the attribute in the <b>Name</b> field. 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>
+</context>
+
+<context id="xcui0010">
+<!--Edit DOCTYPE dialog -->
+<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>
+</context>
+<context id="xcui0030">
+<description>Public ID Text Edit</description>
+</context>
+<context id="xcui0040">
+<description>Public ID Browse Button</description>
+</context>
+<context id="xcui0020">
+<description>Root Element Name Text Edit</description>
+</context>
+<context id="xcui0050">
+<description>System ID Text Edit</description>
+</context>
+<context id="xcui0060">
+<description>System ID Browse Button</description>
+</context>
+
+<context id="xcui0600">
+<!--Edit element dialog -->
+<description>Enter the name of the element in the <b>Element name </b>field. Click <b>OK</b>. The element will be added to the file.</description>
+</context>
+
+<context id="xcui0300">
+<!--Edit processing instructions dialog -->
+<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>
+</context>
+
+</contexts>
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..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xml.ui.infopop/build.properties b/docs/org.eclipse.wst.xml.ui.infopop/build.properties
new file mode 100644
index 0000000..5f22cdd
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/build.properties
@@ -0,0 +1 @@
+bin.includes = META-INF/
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..1150e9f
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/plugin.properties
@@ -0,0 +1 @@
+pluginName = XML infopops
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..c382efe
--- /dev/null
+++ b/docs/org.eclipse.wst.xml.ui.infopop/plugin.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0"?>
+<?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
+ id="org.eclipse.wst.xml.ui.infopop"
+ name="XML infopops"
+ version="0.7.0"
+ provider-name="Eclipse.org">
+
+<extension point="org.eclipse.help.contexts">
+ <contexts file="EditorXmlContexts.xml" plugin ="org.eclipse.wst.xml.ui"/>
+</extension>
+
+
+</plugin>
\ No newline at end of file
