diff options
Diffstat (limited to 'docs/org.eclipse.wst.xmleditor.doc.user/topics')
58 files changed, 0 insertions, 4604 deletions
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.dita deleted file mode 100644 index 9019048638..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.dita +++ /dev/null @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<?Pub Inc?>
-<concept id="creatingxmlfiles" xml:lang="en-us">
-<title>Creating XML files</title>
-<shortdesc>This section contains information on creating XML files:</shortdesc>
-<conbody></conbody>
-<related-links>
-<linklist>
-<link href="tcretxml.dita"><linktext>Creating empty XML files</linktext></link>
-<link href="tcrexdtd.dita"><linktext>Generating XML files from a DTDs</linktext>
-</link>
-<link href="tcrexxsd.dita"><linktext>Generating XML files from XML
-schemas</linktext></link>
-</linklist>
-</related-links>
-</concept>
-<?Pub *0000000718?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html deleted file mode 100644 index 1ebbd51acf..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Creating XML files" /> -<meta name="abstract" content="This section contains information on creating XML files:" /> -<meta name="description" content="This section contains information on creating XML files:" /> -<meta scheme="URI" name="DC.Relation" content="tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrexxsd.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="creatingxmlfiles" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating XML files</title> -</head> -<body id="creatingxmlfiles"><a name="creatingxmlfiles"><!-- --></a> - - -<h1 class="topictitle1">Creating XML files</h1> - - -<div><p>This section contains information on creating XML files:</p> -</div> - -<div> -<div class="linklist"> -<div><a href="tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating empty XML files</a></div> -<div><a href="tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from a DTDs</a></div> -<div><a href="tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML -schemas</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html deleted file mode 100644 index e4aa40e820..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html +++ /dev/null @@ -1,45 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Working with XML files" /> -<meta name="abstract" content="This section contains information on the following:" /> -<meta name="description" content="This section contains information on the following:" /> -<meta scheme="URI" name="DC.Relation" content="ccreatxm.html" /> -<meta scheme="URI" name="DC.Relation" content="txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="twxvalid.html" /> -<meta scheme="URI" name="DC.Relation" content="cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="rxmlbicons.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="workingwithxmlfiles" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with XML files</title> -</head> -<body id="workingwithxmlfiles"><a name="workingwithxmlfiles"><!-- --></a> - - -<h1 class="topictitle1">Working with XML files</h1> - - -<div><p>This section contains information on the following:</p> -</div> - -<div> -<div class="linklist"> -<div><a href="ccreatxm.html" title="This section contains information on creating XML files:">Creating XML files</a></div> -<div><a href="txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -<div><a href="twxvalid.html" title="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed.">Validating XML files</a></div> -<div><a href="cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML -schema</a></div> -<div><a href="rxmlbicons.html" title="The following XML editor icons appear in the Outline and Design view.">Icons used in the XML editor</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkxml.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkxml.dita deleted file mode 100644 index a6fa3e16f2..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkxml.dita +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<?Pub Inc?>
-<concept id="workingwithxmlfiles" xml:lang="en-us">
-<title>Working with XML files</title>
-<shortdesc>This section contains information on the following:</shortdesc>
-<conbody></conbody>
-<related-links>
-<linklist>
-<link href="ccreatxm.dita"><linktext>Creating XML files</linktext></link>
-<link href="txedttag.dita"><linktext>Editing XML files</linktext>
-</link>
-<link href="twxvalid.dita"><linktext>Validating XML files</linktext></link>
-<link href="cxmlcat.dita"><linktext>XML file associations with DTDs and XML
-schema</linktext></link>
-<link href="rxmlbicons.dita"><linktext>Icons used in the XML editor</linktext>
-</link>
-</linklist>
-</related-links>
-</concept>
-<?Pub *0000000871?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.dita deleted file mode 100644 index 34a2e0f6d3..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="cwxmledt" xml:lang="en-us">
-<title>XML editor</title>
-<titlealts>
-<searchtitle>XML editor</searchtitle>
-</titlealts>
-<shortdesc>The XML editor is a tool for creating and viewing XML files.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>You can use it to perform a variety of tasks such as:</p>
-<ul>
-<li>Creating new, empty XML files or generating them from existing DTDs or
-existing XML schemas</li>
-<li>Editing XML files</li>
-<li>Importing existing XML files for structured viewing</li>
-<li>Associating XML files with DTDs or XML schemas</li>
-</ul>
-<p>The XML editor has two main views - the Source view and the Design view.
-You can also use the <b>Outline</b> view to insert and delete elements.</p>
-<section><title>Source view</title><p>The Source view enables you to view
-and work directly with a file's source code. Many of the XML editing features
-in the XML editor Source view are very similar to those available in the Source
-view of Page Designer.</p><p>The Source view has many text editing features,
-such as: <ul>
-<li> Syntax highlighting, unlimited undo/redo, and user-defined templates.</li>
-<li> Content assist, which uses the information in a DTD or schema content
-model to provide a list of acceptable continuations depending on where the
-cursor is located in an XML file, or what has just been type</li>
-<li>"Smart" double-clicking behavior. If your cursor is placed in an attribute
-value, one double-click selects that value, another double click selects the
-attribute-value pair, and a third double-click selects the entire tag. This
-makes it easier to copy and paste commonly used pieces of XML.</li>
-</ul></p></section>
-<section><title>Design view</title><p>The XML editor also has a Design view.
-In it: <ul>
-<li>The XML file is represented simultaneously as a table and a tree. This
-helps make navigation and editing easier.</li>
-<li>Content and attribute values can be edited directly in the table cells,
-while pop-up menus on the tree nodes give alternatives that are valid for
-that location. For example, the <uicontrol>Add child</uicontrol> menu item
-will list only those elements from a DTD or XML schema which would be valid
-children at that point (as long as grammar constraints are on).</li>
-</ul></p><p>The Design view is especially helpful if you are new to XML, or
-need to do form-oriented editing. For example, you could use the Create XML
-File wizard to create a template XML file for a job description form from
-a job description DTD. After those steps are completed, you would
-only have to fill in the form data using the Design view.</p><p>The following
-links provide more information about the XML editor:</p></section>
-</conbody>
-</concept>
-<?Pub *0000002994?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html deleted file mode 100644 index 0515a1de8c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html +++ /dev/null @@ -1,117 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML editor" /> -<meta name="abstract" content="The XML editor is a tool for creating and viewing XML files." /> -<meta name="description" content="The XML editor is a tool for creating and viewing XML files." /> -<meta content="XML editor, overview" name="DC.subject" /> -<meta content="XML editor, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexxsd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twxvalid.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwxmledt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML editor</title> -</head> -<body id="cwxmledt"><a name="cwxmledt"><!-- --></a> - - -<h1 class="topictitle1">XML editor</h1> - - - - -<div><p>The XML editor is a tool for creating and viewing XML files.</p> - -<p>You can use it to perform a variety of tasks such as:</p> - -<ul> -<li>Creating new, empty XML files or generating them from existing DTDs or -existing XML schemas</li> - -<li>Editing XML files</li> - -<li>Importing existing XML files for structured viewing</li> - -<li>Associating XML files with DTDs or XML schemas</li> - -</ul> - -<p>The XML editor has two main views - the Source view and the Design view. -You can also use the <strong>Outline</strong> view to insert and delete elements.</p> - -<div class="section"><h4 class="sectiontitle">Source view</h4><p>The Source view enables you to view -and work directly with a file's source code. Many of the XML editing features -in the XML editor Source view are very similar to those available in the Source -view of Page Designer.</p> -<div class="p">The Source view has many text editing features, -such as: <ul> -<li> Syntax highlighting, unlimited undo/redo, and user-defined templates.</li> - -<li> Content assist, which uses the information in a DTD or schema content -model to provide a list of acceptable continuations depending on where the -cursor is located in an XML file, or what has just been type</li> - -<li>"Smart" double-clicking behavior. If your cursor is placed in an attribute -value, one double-click selects that value, another double click selects the -attribute-value pair, and a third double-click selects the entire tag. This -makes it easier to copy and paste commonly used pieces of XML.</li> - -</ul> -</div> -</div> - -<div class="section"><h4 class="sectiontitle">Design view</h4><div class="p">The XML editor also has a Design view. -In it: <ul> -<li>The XML file is represented simultaneously as a table and a tree. This -helps make navigation and editing easier.</li> - -<li>Content and attribute values can be edited directly in the table cells, -while pop-up menus on the tree nodes give alternatives that are valid for -that location. For example, the <span class="uicontrol">Add child</span> menu item -will list only those elements from a DTD or XML schema which would be valid -children at that point (as long as grammar constraints are on).</li> - -</ul> -</div> -<p>The Design view is especially helpful if you are new to XML, or -need to do form-oriented editing. For example, you could use the Create XML -File wizard to create a template XML file for a job description form from -a job description DTD. After those steps are completed, you would -only have to fill in the form data using the Design view.</p> -<p>The following -links provide more information about the XML editor:</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating XML files</a></div> -<div><a href="../topics/tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from DTDs</a></div> -<div><a href="../topics/tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML schemas</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/twxvalid.html" title="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed.">Validating XML files</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.dita deleted file mode 100644 index fc8a56b76e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.dita +++ /dev/null @@ -1,123 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cxmlcat" xml:lang="en-us">
-<title>XML file associations with DTDs and XML schemas</title>
-<titlealts>
-<searchtitle>XML file associations with DTDs and XML schemas</searchtitle>
-</titlealts>
-<shortdesc>When an XML file is associated with a DTD or XML schema, it is
-bound by any structural rules contained in the DTD or XML schema. To be considered
-a valid XML file, a document must be accompanied by a DTD or an XML schema,
-and conform to all of the declarations in the DTD or the XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML catalog<indexterm>overview</indexterm></indexterm>
-<indexterm>XML files<indexterm>associations</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>There are two different ways to associate XML files with DTDs or XML schemas.</p>
-<ol>
-<li>Direct association - The XML file contains either the name of a DTD in
-its doctype declaration (for example, <!DOCTYPE root-element SYSTEM " <varname>dtdfile.dtd</varname>"
->, where <varname>dtdfile.dtd</varname> is the name of the DTD file) or it
-contains the path of an XML schema in the schemaLocation attribute of the
-XML file root element (for example, <xsi:schemaLocation="http://www.ibm.com
- <varname>schema.xsd</varname>">, where <varname>schema.xsd</varname> is
-the name of the XML schema.</li>
-<li>XML Catalog entry - You can register DTD and XML schema files in the XML
-Catalog and associate them with a <varname>Key</varname> that represents
-them. You can then refer to a DTD or XML schema file <varname>Key</varname> from
-an XML file instead of referring directly to the DTD or XML schema file. An
-XML Catalog entry contains two parts - the Key (which represents the DTD or
-XML schema) and a URI (which contains information about the DTD or XML schema
-location).</li>
-</ol>
-<section><title>How an association works</title><b>Associating an XML file
-with a DTD </b><p>If an XML file is associated with a DTD, a DOCTYPE tag such
-as the following one is included in the XML file:<codeblock><!DOCTYPE root-name PUBLIC "<varname>InvoiceId</varname>" "<varname>C:\mydtds\Invoice.dtd</varname
->">
-</codeblock></p><p><varname>InvoiceId</varname> is the public identifier of
-the DTD file. It is used to associate the XML file with a DTD file (in this
-case, the DTD file is <varname>Invoice.dtd</varname>). If the public identifier
-InvoiceId corresponds to the <varname>Key</varname> of the XML Catalog entry
-for Invoice.dtd, then the <varname>URI</varname> of the XML Catalog entry
-(which contains information about the location of Invoice.dtd) is used to
-locate the DTD. Otherwise, the DOCTYPE's system identifier ( <varname>"C:\mydtds\Invoice.dtd"</varname>),
-which refers directly to the file system location of the DTD, is used to locate
-the DTD.</p><p> <b>Note</b>: You can also use a system identifier as a Key
-in an XML Catalog entry. If you use a system identifier as a Key, a DOCTYPE
-tag such as the following one is included in an XML file:</p><codeblock><!DOCTYPE Root-name SYSTEM "<varname>MyDTD.dtd</varname>"> </codeblock
-><p>where <varname>MyDTD.dtd</varname> is the system identifier that corresponds
-to the Key of an XML Catalog entry.</p></section>
-<section><b>Associating an XML file with an XML schema</b><p>If an XML file
-is associated with an XML schema, one or more schema location attributes are
-included in the XML file. The information in the schemaLocation is provided
-as a "hint" to the XML processor. The following examples show schemaLocation
-attributes.</p><p> <b>Example 1 </b><codeblock><purchaseOrder xmlns="http://www.ibm.com"
-xsi:schemaLocation="http://www.ibm.com C:\myschemas\PurchaseOrder.xsd">
-<shipTo country="US">
-...</codeblock> </p><p><b>Example 2 </b><codeblock><purchaseOrder xmlns="http://www.ibm.com"
-xsi:schemaLocation="http://www.ibm.com PO.xsd">
-<shipTo country="US">
-....</codeblock> </p><p>In Example 1, the schemaLocation 'hint' ('C:\myschemas\PurchaseOrder.xsd')
-refers directly to the file system location or URI of the XML schema. In this
-case, the schema file will be located by the XML processor directly.</p><p>In
-Example 2, the schemaLocation 'hint' ('PO.xsd') refers to an XML Catalog entry.
-PO.xsd corresponds to the <varname>Key</varname> of the XML Catalog entry
-for PurchaseOrder.xsd, and the URI of the XML Catalog entry (which contains
-information about the location of PurchaseOrder.xsd) will be used to located
-the XML schema.</p><p>In both examples, <codeph>http://www.ibm.com</codeph> in
-the <codeph>xsi:schemaLocation</codeph> tag is a URI that identifies the namespace
-for the XML schema.</p><p>You can also use a namespace as a Key for an XML
-Catalog entry. If you use a namespace as a Key, a schemaLocation tag such
-as the following one is included in an XML file:<codeblock><purchaseOrder xmlns:="www.ibm.com"
-xsi:schemaLocation="http://www.ibm.com po/xsd/PurchaseOrder.xsd "></codeblock></p><p>The
-schemaLocation attribute points to both the Key and the actual location of
-the schema.</p><p><b>DTD or XML schema resides on a remote server</b></p><p>Several
-functions in the XML editor, such as validation and content assist, require
-the availability of a DTD or an XML schema. The product documentation provides
-usage information for cases when the DTD or XML schema resides on your local
-machine. However, in many cases, the DTD or XML schema can reside on a remote
-server, for example:</p><p><codeph><!DOCTYPE Catalog PUBLIC "abc/Catalog"
-"http://xyz.abc.org/dtds/catalog.dtd"></codeph></p><p>Normally, this case
-poses no problem, because the DTD or XML schema can be retrieved from the
-remote server. However, if you are behind a firewall, and do not have a SOCKSified
-system, the workbench currently does not provide a way for you to specify
-a socks server for retrieving a DTD or XML schema. If you are unable to SOCKSify
-your system, the workaround for this problem is to retrieve a copy of the
-DTD or XML schema (using a Web browser, for example) and save that copy on
-your local machine. Then, you can either place a local copy in the same project
-as your XML file, or use the XML Catalog to associate a public identifier
-with the DTD's (local) location.</p><p><b>Note</b>: If you have an XML file
-associated with an XML schema or DTD that is elsewhere in the network, and
-you are working on a machine disconnected from the network, you can follow
-the steps described previously if you want to use content assist or validate
-your XML file. </p></section>
-<section><title>Advantages of XML Catalog entry associations</title><p>If
-you create a direct association between an XML file and an XML schema or DTD
-file, any time you change the location of the schema or DTD you have to track
-down and update all of the referencing XML files with the new location of
-the DTD or schema. If, however, you associate an XML file with an XML schema
-or DTD Key, then, when you change the location of the schema or DTD, you only
-have to update the XML Catalog entry, instead of each individual XML file.</p><p>For
-example, you have a DTD called "Building.dtd", which is associated with five
-XML files - Office.xml, House.xml, Apartment.xml, Bank.xml, and PostOffice.xml.
-You move the DTD file Building.dtd to a new location. If you have a direction
-association between Building.dtd and all the XML files, you will have to update
-the <DOCTTYPE> declaration in each XML file to reflect the new location
-of Building.dtd. If, however, you have an XML Catalog association, and all
-the XML files just refer to the Key of Building.dtd, then you only have to
-update the URI and all the XML files will point to the new location of Building.dtd.</p></section>
-<section><title>Updating an entry in the XML Catalog</title><p>After you have
-updated an entry in the XML Catalog, you might need to refresh the XML editor
-view so that it uses the new information. To do this, click the <uicontrol>Reload
-Dependencies</uicontrol> toolbar button <image href="../images/rldgrmr.gif">
-<alt>This graphic is the Reload Dependencies toolbar button</alt></image> and
-the view will be updated using the current XML Catalog settings. You only
-need to refresh the XML editor view when you have an XML file open that references
-the XML Catalog entry that was updated.</p><p>For more information, refer
-to the related tasks.</p></section>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html deleted file mode 100644 index cb76c1432e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html +++ /dev/null @@ -1,198 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML file associations with DTDs and XML schemas" /> -<meta name="abstract" content="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema." /> -<meta name="description" content="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema." /> -<meta content="XML files, associating with DTDs, associating with XML schemas, XML catalog, overview" name="DC.subject" /> -<meta content="XML files, associating with DTDs, associating with XML schemas, XML catalog, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtproc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cxmlcat" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML file associations with DTDs and XML schemas</title> -</head> -<body id="cxmlcat"><a name="cxmlcat"><!-- --></a> - - -<h1 class="topictitle1">XML file associations with DTDs and XML schemas</h1> - - - - -<div><p>When an XML file is associated with a DTD or XML schema, it is -bound by any structural rules contained in the DTD or XML schema. To be considered -a valid XML file, a document must be accompanied by a DTD or an XML schema, -and conform to all of the declarations in the DTD or the XML schema.</p> - -<p>There are two different ways to associate XML files with DTDs or XML schemas.</p> - -<ol> -<li>Direct association - The XML file contains either the name of a DTD in -its doctype declaration (for example, <!DOCTYPE root-element SYSTEM " <var class="varname">dtdfile.dtd</var>" ->, where <var class="varname">dtdfile.dtd</var> is the name of the DTD file) or it -contains the path of an XML schema in the schemaLocation attribute of the -XML file root element (for example, <xsi:schemaLocation="http://www.ibm.com - <var class="varname">schema.xsd</var>">, where <var class="varname">schema.xsd</var> is -the name of the XML schema.</li> - -<li>XML Catalog entry - You can register DTD and XML schema files in the XML -Catalog and associate them with a <var class="varname">Key</var> that represents -them. You can then refer to a DTD or XML schema file <var class="varname">Key</var> from -an XML file instead of referring directly to the DTD or XML schema file. An -XML Catalog entry contains two parts - the Key (which represents the DTD or -XML schema) and a URI (which contains information about the DTD or XML schema -location).</li> - -</ol> - -<div class="section"><h4 class="sectiontitle">How an association works</h4><strong>Associating an XML file -with a DTD </strong><div class="p">If an XML file is associated with a DTD, a DOCTYPE tag such -as the following one is included in the XML file:<pre><!DOCTYPE root-name PUBLIC "<var class="varname">InvoiceId</var>" "<var class="varname">C:\mydtds\Invoice.dtd</var>"> -</pre> -</div> -<p><var class="varname">InvoiceId</var> is the public identifier of -the DTD file. It is used to associate the XML file with a DTD file (in this -case, the DTD file is <var class="varname">Invoice.dtd</var>). If the public identifier -InvoiceId corresponds to the <var class="varname">Key</var> of the XML Catalog entry -for Invoice.dtd, then the <var class="varname">URI</var> of the XML Catalog entry -(which contains information about the location of Invoice.dtd) is used to -locate the DTD. Otherwise, the DOCTYPE's system identifier ( <var class="varname">"C:\mydtds\Invoice.dtd"</var>), -which refers directly to the file system location of the DTD, is used to locate -the DTD.</p> -<p> <strong>Note</strong>: You can also use a system identifier as a Key -in an XML Catalog entry. If you use a system identifier as a Key, a DOCTYPE -tag such as the following one is included in an XML file:</p> -<pre><!DOCTYPE Root-name SYSTEM "<var class="varname">MyDTD.dtd</var>"> </pre> -<p>where <var class="varname">MyDTD.dtd</var> is the system identifier that corresponds -to the Key of an XML Catalog entry.</p> -</div> - -<div class="section"><strong>Associating an XML file with an XML schema</strong><p>If an XML file -is associated with an XML schema, one or more schema location attributes are -included in the XML file. The information in the schemaLocation is provided -as a "hint" to the XML processor. The following examples show schemaLocation -attributes.</p> -<div class="p"> <strong>Example 1 </strong><pre><purchaseOrder xmlns="http://www.ibm.com" -xsi:schemaLocation="http://www.ibm.com C:\myschemas\PurchaseOrder.xsd"> -<shipTo country="US"> -...</pre> - </div> -<div class="p"><strong>Example 2 </strong><pre><purchaseOrder xmlns="http://www.ibm.com" -xsi:schemaLocation="http://www.ibm.com PO.xsd"> -<shipTo country="US"> -....</pre> - </div> -<p>In Example 1, the schemaLocation 'hint' ('C:\myschemas\PurchaseOrder.xsd') -refers directly to the file system location or URI of the XML schema. In this -case, the schema file will be located by the XML processor directly.</p> -<p>In -Example 2, the schemaLocation 'hint' ('PO.xsd') refers to an XML Catalog entry. -PO.xsd corresponds to the <var class="varname">Key</var> of the XML Catalog entry -for PurchaseOrder.xsd, and the URI of the XML Catalog entry (which contains -information about the location of PurchaseOrder.xsd) will be used to located -the XML schema.</p> -<p>In both examples, <samp class="codeph">http://www.ibm.com</samp> in -the <samp class="codeph">xsi:schemaLocation</samp> tag is a URI that identifies the namespace -for the XML schema.</p> -<div class="p">You can also use a namespace as a Key for an XML -Catalog entry. If you use a namespace as a Key, a schemaLocation tag such -as the following one is included in an XML file:<pre><purchaseOrder xmlns:="www.ibm.com" -xsi:schemaLocation="http://www.ibm.com po/xsd/PurchaseOrder.xsd "></pre> -</div> -<p>The -schemaLocation attribute points to both the Key and the actual location of -the schema.</p> -<p><strong>DTD or XML schema resides on a remote server</strong></p> -<p>Several -functions in the XML editor, such as validation and content assist, require -the availability of a DTD or an XML schema. The product documentation provides -usage information for cases when the DTD or XML schema resides on your local -machine. However, in many cases, the DTD or XML schema can reside on a remote -server, for example:</p> -<p><samp class="codeph"><!DOCTYPE Catalog PUBLIC "abc/Catalog" -"http://xyz.abc.org/dtds/catalog.dtd"></samp></p> -<p>Normally, this case -poses no problem, because the DTD or XML schema can be retrieved from the -remote server. However, if you are behind a firewall, and do not have a SOCKSified -system, the workbench currently does not provide a way for you to specify -a socks server for retrieving a DTD or XML schema. If you are unable to SOCKSify -your system, the workaround for this problem is to retrieve a copy of the -DTD or XML schema (using a Web browser, for example) and save that copy on -your local machine. Then, you can either place a local copy in the same project -as your XML file, or use the XML Catalog to associate a public identifier -with the DTD's (local) location.</p> -<p><strong>Note</strong>: If you have an XML file -associated with an XML schema or DTD that is elsewhere in the network, and -you are working on a machine disconnected from the network, you can follow -the steps described previously if you want to use content assist or validate -your XML file. </p> -</div> - -<div class="section"><h4 class="sectiontitle">Advantages of XML Catalog entry associations</h4><p>If -you create a direct association between an XML file and an XML schema or DTD -file, any time you change the location of the schema or DTD you have to track -down and update all of the referencing XML files with the new location of -the DTD or schema. If, however, you associate an XML file with an XML schema -or DTD Key, then, when you change the location of the schema or DTD, you only -have to update the XML Catalog entry, instead of each individual XML file.</p> -<p>For -example, you have a DTD called "Building.dtd", which is associated with five -XML files - Office.xml, House.xml, Apartment.xml, Bank.xml, and PostOffice.xml. -You move the DTD file Building.dtd to a new location. If you have a direction -association between Building.dtd and all the XML files, you will have to update -the <DOCTTYPE> declaration in each XML file to reflect the new location -of Building.dtd. If, however, you have an XML Catalog association, and all -the XML files just refer to the Key of Building.dtd, then you only have to -update the URI and all the XML files will point to the new location of Building.dtd.</p> -</div> - -<div class="section"><h4 class="sectiontitle">Updating an entry in the XML Catalog</h4><p>After you have -updated an entry in the XML Catalog, you might need to refresh the XML editor -view so that it uses the new information. To do this, click the <span class="uicontrol">Reload -Dependencies</span> toolbar button <img src="../images/rldgrmr.gif" alt="This graphic is the Reload Dependencies toolbar button" /> and -the view will be updated using the current XML Catalog settings. You only -need to refresh the XML editor view when you have an XML file open that references -the XML Catalog entry that was updated.</p> -<p>For more information, refer -to the related tasks.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -<div><a href="../topics/tedtproc.html" title="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction.">Editing XML processing instructions</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.dita deleted file mode 100644 index 21aa5904d0..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.dita +++ /dev/null @@ -1,162 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<?Pub Inc?>
-<concept id="cxmlenc" xml:lang="en-us">
-<title>XML and HTML encodings</title>
-<titlealts>
-<searchtitle>XML and HTML encodings</searchtitle>
-</titlealts>
-<shortdesc>Encodings enable you to specify what character encoding your text
-is in.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>character encoding<indexterm>text in files</indexterm></indexterm>
-<indexterm>encodings<indexterm>supported character sets</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>The IANA name is used in the encoding statement of an XML file, or charset
-directive in an HTML file.</p>
-<p>The HTML and XML editors support the following encodings:</p>
-<table rowheader="firstcol">
-<tgroup cols="2"><colspec colname="COLSPEC0"/><colspec colname="COLSPEC1"/>
-<thead>
-<row>
-<entry colname="COLSPEC0" valign="top"> <p><b>XML Encoding (IANA Name)</b></p> </entry>
-<entry colname="COLSPEC1" valign="top"> <p><b>Description</b></p> </entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry> <p>BIG5</p> </entry>
-<entry> <p>Big5, Traditional Chinese</p> </entry>
-</row>
-<row>
-<entry> <p>EUC-JP</p> </entry>
-<entry> <p>EUC encoding, Japanese</p> </entry>
-</row>
-<row>
-<entry> <p>EUC-KR</p> </entry>
-<entry> <p>EUC encoding, Korean</p> </entry>
-</row>
-<row>
-<entry> <p>GB2312</p> </entry>
-<entry> <p>GBK, Simplified Chinese</p> </entry>
-</row>
-<row>
-<entry>GB18030</entry>
-<entry>National Standard, Chinese</entry>
-</row>
-<row>
-<entry>IBM864</entry>
-<entry>PC Arabic (encoding not supported by the Page Designer Design page.
-)</entry>
-</row>
-<row>
-<entry> <p>ISO-2022-JP</p> </entry>
-<entry> <p>ISO 2022, Japanese</p> </entry>
-</row>
-<row>
-<entry> <p>ISO-2022-KR</p> </entry>
-<entry> <p>ISO 2022, Korean</p> </entry>
-</row>
-<row>
-<entry> <p>ISO-8859-1</p> </entry>
-<entry> <p>ISO Latin-1</p> </entry>
-</row>
-<row>
-<entry>ISO-8859-2</entry>
-<entry>Central/East European (Slavic)</entry>
-</row>
-<row>
-<entry>ISO-8859-3</entry>
-<entry>Southern European</entry>
-</row>
-<row>
-<entry>ISO-8859-4</entry>
-<entry>ISO 8859-4, Cyrillic</entry>
-</row>
-<row>
-<entry>ISO-8859-5</entry>
-<entry>ISO 8859-5, Cyrillic</entry>
-</row>
-<row>
-<entry> <p>ISO-8859-6</p> </entry>
-<entry> <p>Arabic (Logical)</p> </entry>
-</row>
-<row>
-<entry>ISO-8859-7</entry>
-<entry>Greek</entry>
-</row>
-<row>
-<entry> <p>ISO-8859-8-I</p> </entry>
-<entry> <p>Hebrew (Logical)</p> </entry>
-</row>
-<row>
-<entry> <p>ISO-8859-8</p> </entry>
-<entry> <p>Hebrew (Visual)(encoding supported, but not supported by the Page
-Designer Design page)</p> </entry>
-</row>
-<row>
-<entry>ISO-8859-9</entry>
-<entry>Turkish</entry>
-</row>
-<row>
-<entry> <p>SHIFT_JIS</p> </entry>
-<entry> <p>Shift-JIS, Japanese</p> </entry>
-</row>
-<row>
-<entry>TIS-620</entry>
-<entry>TISI, Thai</entry>
-</row>
-<row>
-<entry> <p>US-ASCII</p> </entry>
-<entry> <p>US ASCII</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-8</p> </entry>
-<entry> <p>ISO 10646/Unicode, one-byte encoding</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-16</p> </entry>
-<entry> <p>ISO 10646/Unicode, two-byte encoding</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-16BE</p> </entry>
-<entry> <p>Unicode BigEndian</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-16LE</p> </entry>
-<entry> <p>Unicode LittleEndian</p> </entry>
-</row>
-<row>
-<entry>WINDOWS-874</entry>
-<entry>Thai, <tm tmclass="special" tmowner="Microsoft Corporation" tmtype="reg"
-trademark="Microsoft">Microsoft</tm></entry>
-</row>
-<row>
-<entry> <p>WINDOWS-1252</p> </entry>
-<entry> <p>ISO Latin-1</p> </entry>
-</row>
-<row>
-<entry> <p>WINDOWS-1255</p> </entry>
-<entry> <p>Hebrew</p> </entry>
-</row>
-<row>
-<entry> <p>WINDOWS-1256</p> </entry>
-<entry> <p>Arabic</p> </entry>
-</row>
-<row>
-<entry>X-EUC-JP</entry>
-<entry>EUC encoding, Japanese (alias for EUC-JP)</entry>
-</row>
-<row>
-<entry>X-SJIS</entry>
-<entry>Shift-JIS, Japanese (alias for SHIFT_JIS)</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-</conbody>
-</concept>
-<?Pub *0000003991?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html deleted file mode 100644 index 26b1018f71..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html +++ /dev/null @@ -1,320 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML and HTML encodings" /> -<meta name="abstract" content="Encodings enable you to specify what character encoding your text is in." /> -<meta name="description" content="Encodings enable you to specify what character encoding your text is in." /> -<meta content="Encodings, HTML, XML" name="DC.subject" /> -<meta content="Encodings, HTML, XML" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cxmlenc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML and HTML encodings</title> -</head> -<body id="cxmlenc"><a name="cxmlenc"><!-- --></a> - - -<h1 class="topictitle1">XML and HTML encodings</h1> - - - - -<div><p>Encodings enable you to specify what character encoding your text -is in.</p> - -<p>The IANA name is used in the encoding statement of an XML file, or charset -directive in an HTML file.</p> - -<p>The HTML and XML editors support the following encodings:</p> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<thead align="left"> -<tr> -<th valign="top" class="firstcol" id="N1007B"> <p><strong>XML Encoding (IANA Name)</strong></p> - </th> - -<th valign="top" id="N1008D"> <p><strong>Description</strong></p> - </th> - -</tr> - -</thead> - -<tbody> -<tr> -<th valign="top" class="firstcol" id="N100AB" headers="N1007B "> <p>BIG5</p> - </th> - -<td valign="top" headers="N100AB N1008D "> <p>Big5, Traditional Chinese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N100CB" headers="N1007B "> <p>EUC-JP</p> - </th> - -<td valign="top" headers="N100CB N1008D "> <p>EUC encoding, Japanese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N100EB" headers="N1007B "> <p>EUC-KR</p> - </th> - -<td valign="top" headers="N100EB N1008D "> <p>EUC encoding, Korean</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1010B" headers="N1007B "> <p>GB2312</p> - </th> - -<td valign="top" headers="N1010B N1008D "> <p>GBK, Simplified Chinese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1012B" headers="N1007B ">GB18030</th> - -<td valign="top" headers="N1012B N1008D ">National Standard, Chinese</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1013F" headers="N1007B ">IBM864</th> - -<td valign="top" headers="N1013F N1008D ">PC Arabic (encoding not supported by the Page Designer Design page. -)</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10153" headers="N1007B "> <p>ISO-2022-JP</p> - </th> - -<td valign="top" headers="N10153 N1008D "> <p>ISO 2022, Japanese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10173" headers="N1007B "> <p>ISO-2022-KR</p> - </th> - -<td valign="top" headers="N10173 N1008D "> <p>ISO 2022, Korean</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10193" headers="N1007B "> <p>ISO-8859-1</p> - </th> - -<td valign="top" headers="N10193 N1008D "> <p>ISO Latin-1</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101B3" headers="N1007B ">ISO-8859-2</th> - -<td valign="top" headers="N101B3 N1008D ">Central/East European (Slavic)</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101C7" headers="N1007B ">ISO-8859-3</th> - -<td valign="top" headers="N101C7 N1008D ">Southern European</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101DB" headers="N1007B ">ISO-8859-4</th> - -<td valign="top" headers="N101DB N1008D ">ISO 8859-4, Cyrillic</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101EF" headers="N1007B ">ISO-8859-5</th> - -<td valign="top" headers="N101EF N1008D ">ISO 8859-5, Cyrillic</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10203" headers="N1007B "> <p>ISO-8859-6</p> - </th> - -<td valign="top" headers="N10203 N1008D "> <p>Arabic (Logical)</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10223" headers="N1007B ">ISO-8859-7</th> - -<td valign="top" headers="N10223 N1008D ">Greek</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10237" headers="N1007B "> <p>ISO-8859-8-I</p> - </th> - -<td valign="top" headers="N10237 N1008D "> <p>Hebrew (Logical)</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10257" headers="N1007B "> <p>ISO-8859-8</p> - </th> - -<td valign="top" headers="N10257 N1008D "> <p>Hebrew (Visual)(encoding supported, but not supported by the Page -Designer Design page)</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10277" headers="N1007B ">ISO-8859-9</th> - -<td valign="top" headers="N10277 N1008D ">Turkish</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1028B" headers="N1007B "> <p>SHIFT_JIS</p> - </th> - -<td valign="top" headers="N1028B N1008D "> <p>Shift-JIS, Japanese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102AB" headers="N1007B ">TIS-620</th> - -<td valign="top" headers="N102AB N1008D ">TISI, Thai</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102BF" headers="N1007B "> <p>US-ASCII</p> - </th> - -<td valign="top" headers="N102BF N1008D "> <p>US ASCII</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102DF" headers="N1007B "> <p>UTF-8</p> - </th> - -<td valign="top" headers="N102DF N1008D "> <p>ISO 10646/Unicode, one-byte encoding</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102FF" headers="N1007B "> <p>UTF-16</p> - </th> - -<td valign="top" headers="N102FF N1008D "> <p>ISO 10646/Unicode, two-byte encoding</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1031F" headers="N1007B "> <p>UTF-16BE</p> - </th> - -<td valign="top" headers="N1031F N1008D "> <p>Unicode BigEndian</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1033F" headers="N1007B "> <p>UTF-16LE</p> - </th> - -<td valign="top" headers="N1033F N1008D "> <p>Unicode LittleEndian</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1035F" headers="N1007B ">WINDOWS-874</th> - -<td valign="top" headers="N1035F N1008D ">Thai, Microsoft<sup>®</sup></td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1037C" headers="N1007B "> <p>WINDOWS-1252</p> - </th> - -<td valign="top" headers="N1037C N1008D "> <p>ISO Latin-1</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1039C" headers="N1007B "> <p>WINDOWS-1255</p> - </th> - -<td valign="top" headers="N1039C N1008D "> <p>Hebrew</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N103BC" headers="N1007B "> <p>WINDOWS-1256</p> - </th> - -<td valign="top" headers="N103BC N1008D "> <p>Arabic</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N103DC" headers="N1007B ">X-EUC-JP</th> - -<td valign="top" headers="N103DC N1008D ">EUC encoding, Japanese (alias for EUC-JP)</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N103F0" headers="N1007B ">X-SJIS</th> - -<td valign="top" headers="N103F0 N1008D ">Shift-JIS, Japanese (alias for SHIFT_JIS)</td> - -</tr> - -</tbody> - -</table> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.dita deleted file mode 100644 index dbfc5b2589..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.dita +++ /dev/null @@ -1,38 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="cxmltool" xml:lang="en-us">
-<title>XML tools - overview</title>
-<titlealts>
-<searchtitle>XML tools - overview</searchtitle>
-</titlealts>
-<shortdesc>This product provides a comprehensive visual XML development environment.
-The tool set includes components for building DTDs, XML schemas, and XML files.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML tools<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>The following XML tools are available. </p>
-<p>The <b>XML editor</b> is a tool for creating and viewing XML files. You
-can use it to create new XML files, either from scratch, existing DTDs, or
-existing XML schemas. You can also use it to edit XML files, associate them
-with DTDs or schemas, and validate them. </p>
-<p> The <b>DTD editor</b> is a tool for creating and viewing DTDs. </p>
-<p>The <b>XML schema editor</b> is a tool for creating, viewing, and validating
-XML schemas. You can use the XML schema editor to perform tasks such as creating
-XML schema components and importing and viewing XML schemas. </p>
-<p><b>Notes:</b></p>
-<section>Exercise caution when opening large files with any of the XML editors.
-If the memory limits of the workbench are exceeded, it will abruptly close
-without saving any data (and without warning or error messages). The number
-of elements in an XML file, not its size, is the best indicator of how much
-memory will be required. Memory requirements also depend on what else is open
-in the workbench - in some cases you can open a fifteen megabytes file, but
-in other cases a one megabyte file might cause problems. Therefore, we recommend
-you save all data in the workbench before opening large XML files. This is
-a permanent restriction.</section>
-<section conref="rlimitations_slushXML.dita#rlimitations_slushXML/unresolv_URI"></section>
-</conbody>
-</concept>
-<?Pub *0000002064?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html deleted file mode 100644 index 76696338e6..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>XML tools - overview</title> -</head> -<body id="cxmltool"><a name="cxmltool"><!-- --></a> - -<h1 class="topictitle1">XML tools - overview</h1> -<div><p>This product provides a comprehensive visual XML development environment. -The tool set includes components for building DTDs, XML schemas, and XML files.</p><p>The following XML tools are available:</p> -<p>The <b>XML editor</b> is a tool for creating and viewing XML files. You -can use it to create new XML files, either from scratch, existing DTDs, or -existing XML schemas. You can also use it to edit XML files, associate them -with DTDs or schemas, and validate them.</p> -<p>The <b>DTD editor</b> is a tool for creating and viewing DTDs. </p> -<p>The <b>XML schema editor</b> is a tool for creating, viewing, and validating -XML schemas. You can use the XML schema editor to perform tasks such as creating -XML schema components and importing and viewing XML schemas. </p> -<div class="skipspace">Exercise caution when opening large files with any of the XML editors. -If the memory limits of the workbench are exceeded, it will abruptly close -without saving any data (and without warning or error messages). The number -of elements in an XML file, not its size, is the best indicator of how much -memory will be required. Memory requirements also depend on what else is open -in the workbench - in some cases you can open a 15 megabytes file, but in -other cases a one-megabyte file may cause problems. Therefore, we recommend -you save all data in the workbench before opening large XML files. This is -a permanent restriction.</div> -<div class="skipspace"><p>The -behavior of the XML parser when encountering an unresolvable URI (for example, -in a DOCTYPE declaration) is to report a fatal IO error and stop any further -processing. An unresolved URI is seen neither as a syntactic nor a semantic -error and as such, the parser does not attempt to handle it. Essentially, -the document remains unchecked. This is a known problem.</p> -</div> -</div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.dita deleted file mode 100644 index b2be71435d..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.dita +++ /dev/null @@ -1,25 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rextctn" xml:lang="en-us">
-<title>Editing XML documents with multiple namespaces</title>
-<titlealts>
-<searchtitle>Editing XML documents with multiple namespaces</searchtitle>
-</titlealts>
-<shortdesc>You can use the XML schema <codeph>any</codeph> element to extend
-the content model of an XML document.</shortdesc>
-<refbody>
-<section><p>For example, you have an XML schema file called Book.xsd that
-contains a complex type called BookType. BookType contains 4 elements (title,
-author, year, and ISBN) and one <codeph>any</codeph> element. The namespace
-for the <codeph>any</codeph> element is <codeph>##any</codeph>. This means
-that in an instance document, you can insert any XML element to extend the
-definition of the BookType.</p><p>You can also provide a more specific namespace.
-For example, you have another schema called My_Book.xsd, which contains a
-complex type called My_BookType. My_BookType contains 4 elements (title, author,
-year, and ISBN) and one <codeph>any</codeph> element, but in this case the
-namespace for the BookType element is www.wesley.com. This means that in
-an instance document, you can insert any XML element to extend the definition
-of the BookType, provided that they belong to the namespace http://www.wesley.com.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html deleted file mode 100644 index ee9086b236..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML documents with multiple namespaces" /> -<meta name="abstract" content="You can use the XML schema any element to extend the content model of an XML document." /> -<meta name="description" content="You can use the XML schema any element to extend the content model of an XML document." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rextctn" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML documents with multiple namespaces</title> -</head> -<body id="rextctn"><a name="rextctn"><!-- --></a> - - -<h1 class="topictitle1">Editing XML documents with multiple namespaces</h1> - - - -<div><p>You can use the XML schema <samp class="codeph">any</samp> element to extend -the content model of an XML document.</p> - -<div class="section"><p>For example, you have an XML schema file called Book.xsd that -contains a complex type called BookType. BookType contains 4 elements (title, -author, year, and ISBN) and one <samp class="codeph">any</samp> element. The namespace -for the <samp class="codeph">any</samp> element is <samp class="codeph">##any</samp>. This means -that in an instance document, you can insert any XML element to extend the -definition of the BookType.</p> -<p>You can also provide a more specific namespace. -For example, you have another schema called My_Book.xsd, which contains a -complex type called My_BookType. My_BookType contains 4 elements (title, author, -year, and ISBN) and one <samp class="codeph">any</samp> element, but in this case the -namespace for the BookType element is www.wesley.com. This means that in -an instance document, you can insert any XML element to extend the definition -of the BookType, provided that they belong to the namespace http://www.wesley.com.</p> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.dita deleted file mode 100644 index c7ee4b0777..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.dita +++ /dev/null @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rlimitations_slushXML" xml:lang="en-us">
-<title>Limitations of XML Editor</title>
-<titlealts>
-<searchtitle>Limitations of XML Editor</searchtitle>
-</titlealts>
-<shortdesc>This section describes known product aspect limitations and workarounds.</shortdesc>
-<refbody>
-<!--Use this template to single source the readme information. The content for the readme information is maintained in this topic and is inserted into the related topic using the conref attribute. This file will not be surfaced in your navigation.-->
-<section id="unresolv_URI"><!--No defect associated with this. It is from the 5.1. readme.--><p>The
-behavior of the XML parser when encountering an unresolvable URI (for example,
-in a DOCTYPE declaration) is to report a fatal IO error and stop any further
-processing. An unresolved URI is seen neither as a syntactic nor a semantic
-error and as such, the parser does not attempt to handle it. Essentially,
-the document remains unchecked. This is a known problem.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html deleted file mode 100644 index dfece6aae6..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Limitations of XML Editor" /> -<meta name="abstract" content="This section describes known product aspect limitations and workarounds." /> -<meta name="description" content="This section describes known product aspect limitations and workarounds." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rlimitations_slushXML" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Limitations of XML Editor</title> -</head> -<body id="rlimitations_slushXML"><a name="rlimitations_slushXML"><!-- --></a> - - -<h1 class="topictitle1">Limitations of XML Editor</h1> - - - -<div><p>This section describes known product aspect limitations and workarounds.</p> - - -<div class="section" id="rlimitations_slushXML__unresolv_URI"><a name="rlimitations_slushXML__unresolv_URI"><!-- --></a><p>The -behavior of the XML parser when encountering an unresolvable URI (for example, -in a DOCTYPE declaration) is to report a fatal IO error and stop any further -processing. An unresolved URI is seen neither as a syntactic nor a semantic -error and as such, the parser does not attempt to handle it. Essentially, -the document remains unchecked. This is a known problem.</p> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.dita deleted file mode 100644 index a398b072db..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.dita +++ /dev/null @@ -1,58 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<?Pub Inc?>
-<reference id="ricons" xml:lang="en-us">
-<title>Icons used in the XML editor</title>
-<titlealts>
-<searchtitle>Icons used in the XML editor</searchtitle>
-</titlealts>
-<shortdesc>The following XML editor icons appear in the Outline and Design
-view.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>icons</indexterm></indexterm></keywords>
-</metadata></prolog>
-<refbody>
-<table>
-<tgroup cols="2"><colspec colname="COLSPEC0"/><colspec colname="COLSPEC1"/>
-<tbody>
-<row>
-<entry colname="COLSPEC0" valign="bottom"><b>Icon</b></entry>
-<entry colname="COLSPEC1" valign="bottom"><b>Description</b></entry>
-</row>
-<row>
-<entry> <image href="../images/nattrib.gif"><alt>This graphic is the attribute
-icon</alt></image> </entry>
-<entry>attribute</entry>
-</row>
-<row>
-<entry> <image href="../images/cdatasection.gif"><alt>This graphic is the
-character data icon</alt></image></entry>
-<entry>character data (CDATA) section</entry>
-</row>
-<row>
-<entry> <image href="../images/comment_obj.gif"><alt>This graphic is the comment
-icon</alt></image></entry>
-<entry>comment</entry>
-</row>
-<row>
-<entry> <image href="../images/doctype.gif"><alt>This graphic is the DOCTYPE
-icon</alt></image></entry>
-<entry>DOCTYPE declaration</entry>
-</row>
-<row>
-<entry> <image href="../images/nelem.gif"><alt>This graphic is the element
-icon</alt></image> </entry>
-<entry>element</entry>
-</row>
-<row>
-<entry> <image href="../images/proinst_obj.gif"><alt>This graphic is the processing
-instructions icon</alt></image></entry>
-<entry>processing instructions</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-</refbody>
-</reference>
-<?Pub *0000001824?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html deleted file mode 100644 index 50087a8307..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html +++ /dev/null @@ -1,99 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Icons used in the XML editor" /> -<meta name="abstract" content="The following XML editor icons appear in the Outline and Design view." /> -<meta name="description" content="The following XML editor icons appear in the Outline and Design view." /> -<meta content="XML editor, icons" name="DC.subject" /> -<meta content="XML editor, icons" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ricons" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Icons used in the XML editor</title> -</head> -<body id="ricons"><a name="ricons"><!-- --></a> - - -<h1 class="topictitle1">Icons used in the XML editor</h1> - - - - -<div><p>The following XML editor icons appear in the Outline and Design -view.</p> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<tbody> -<tr> -<td valign="bottom"><strong>Icon</strong></td> - -<td valign="bottom"><strong>Description</strong></td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/nattrib.gif" alt="This graphic is the attribute icon" /> </td> - -<td valign="top">attribute</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/cdatasection.gif" alt="This graphic is the character data icon" /></td> - -<td valign="top">character data (CDATA) section</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/comment_obj.gif" alt="This graphic is the comment icon" /></td> - -<td valign="top">comment</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/doctype.gif" alt="This graphic is the DOCTYPE icon" /></td> - -<td valign="top">DOCTYPE declaration</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/nelem.gif" alt="This graphic is the element icon" /> </td> - -<td valign="top">element</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/proinst_obj.gif" alt="This graphic is the processing instructions icon" /></td> - -<td valign="top">processing instructions</td> - -</tr> - -</tbody> - -</table> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.dita deleted file mode 100644 index ad0b19e1e3..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.dita +++ /dev/null @@ -1,39 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tcretxml" xml:lang="en-us">
-<title>Creating XML files</title>
-<titlealts>
-<searchtitle>Creating XML files</searchtitle>
-</titlealts>
-<shortdesc>You can create a new XML file which you can then edit in the XML
-editor. You create a new XML file that is not associated with a DTD or XML
-schema file, so there are no restrictions on the kind of content it can contain.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To create a new
-XML file, follow these instructions:</p></context>
-<steps>
-<step><cmd>If necessary, create a project to contain the XML file.</cmd></step>
-<step><cmd>In the workbench, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Other</uicontrol><uicontrol>XML</uicontrol>
-<uicontrol>XML</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the project or folder that will contain the XML file.</cmd>
-</step>
-<step><cmd>In the <uicontrol>File name</uicontrol> field, type the name of
-the XML file, for example <userinput>MyXMLFile.xml</userinput>. The name of
-your XML file <varname>must</varname> end in <userinput>.xml</userinput>.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next.</uicontrol></cmd></step>
-<step><cmd>Click the <uicontrol>Create XML file from an XML template</uicontrol> radio
-button.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html deleted file mode 100644 index 63438a9c9a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating XML files" /> -<meta name="abstract" content="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain." /> -<meta name="description" content="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain." /> -<meta content="XML files, creating" name="DC.subject" /> -<meta content="XML files, creating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexxsd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcretxml" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating XML files</title> -</head> -<body id="tcretxml"><a name="tcretxml"><!-- --></a> - - -<h1 class="topictitle1">Creating XML files</h1> - - - - -<div><p>You can create a new XML file which you can then edit in the XML -editor. You create a new XML file that is not associated with a DTD or XML -schema file, so there are no restrictions on the kind of content it can contain.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To create a new -XML file, follow these instructions:</p> -</div> - -<ol> -<li><span>If necessary, create a project to contain the XML file.</span></li> - -<li><span>In the workbench, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span> > <span class="uicontrol">XML</span> - > <span class="uicontrol">XML</span></span> and click <span class="uicontrol">Next</span>.</span> -</li> - -<li><span>Select the project or folder that will contain the XML file.</span> -</li> - -<li><span>In the <span class="uicontrol">File name</span> field, type the name of -the XML file, for example <kbd class="userinput">MyXMLFile.xml</kbd>. The name of -your XML file <var class="varname">must</var> end in <kbd class="userinput">.xml</kbd>.</span> -</li> - -<li><span>Click <span class="uicontrol">Next.</span></span></li> - -<li><span>Click the <span class="uicontrol">Create XML file from an XML template</span> radio -button.</span></li> - -<li><span>Click <span class="uicontrol">Finish</span>.</span></li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from DTDs</a></div> -<div><a href="../topics/tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML schemas</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.dita deleted file mode 100644 index fe8a065d5e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.dita +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tcrexdtd" xml:lang="en-us">
-<title>Generating XML files from DTDs</title>
-<titlealts>
-<searchtitle>Generate an XML file from a DTD</searchtitle>
-</titlealts>
-<shortdesc>You can generate an XML file from your DTD if you want to quickly
-create an XML file based on your DTD file. Generating an XML file from your
-DTD saves you time by creating an XML file that is already associated with
-your DTD, and contains at least some of the elements and attributes in your
-DTD.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>generating from DTDs</indexterm></indexterm>
-<indexterm>DTD<indexterm>generating XML files</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>After you have generated your XML file, you can further customize
-it in the XML editor.</p><p>The following instructions were written for the
-Resource perspective, but they will also work in many other perspectives.</p><p>To
-create an XML file from a DTD file follow these steps:</p></context>
-<steps>
-<step><cmd>In the Navigator view, right-click the DTD file that you want to
-work with.</cmd></step>
-<step><cmd>From its pop-up menu click <menucascade><uicontrol>Generate</uicontrol>
-<uicontrol>XML File</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select a project or folder to contain the XML file and type a name
-for it.</cmd><info>The name of the file must end in <userinput>.xml</userinput>.</info>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Select the <uicontrol>Root element</uicontrol> of the XML file.</cmd>
-<info>The root element of an XML file is the element that contains all other
-elements in that file. All the elements that you have defined in the DTD will
-be shown in the <uicontrol>Root element</uicontrol> list.</info></step>
-<step><cmd>Select from the following content options: </cmd>
-<choices>
-<choice><uicontrol>Create optional attributes</uicontrol>. Both mandatory
-and optional attributes will be generated.</choice>
-<choice><uicontrol>Create optional elements</uicontrol>. Both mandatory and
-optional elements will be generated.</choice>
-<choice><uicontrol>Create first choice of required choice</uicontrol>. The
-first option of a required choice will be generated in your XML file.</choice>
-<choice><uicontrol>Fill elements and attributes with data</uicontrol>. Any
-elements and attributes generated will be filled with sample data.</choice>
-</choices>
-<info> <p>If you do not select any of these options, then only the minimum
-amount of content required for the XML file will be created.</p></info></step>
-<step><cmd>Specify the <uicontrol>Public ID</uicontrol> or <uicontrol>System
-ID</uicontrol>.</cmd><info>You do not need to specify both. If you do, the
-Public ID will be used before the System ID. </info></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<result><p>The XML file will only contain the selected root element and any
-elements or attributes contained in the root element. You can now add elements,
-attributes, entities, and notations to the XML file, however, they must follow
-the rules established in the DTD that you used to create the XML file.</p></result>
-</taskbody>
-</task>
-<?Pub *0000003334?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html deleted file mode 100644 index f4c76ce0bb..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html +++ /dev/null @@ -1,113 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Generating XML files from DTDs" /> -<meta name="abstract" content="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD." /> -<meta name="description" content="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD." /> -<meta content="XML files, generating from DTDs" name="DC.subject" /> -<meta content="XML files, generating from DTDs" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexxsd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcrexdtd" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Generate an XML file from a DTD</title> -</head> -<body id="tcrexdtd"><a name="tcrexdtd"><!-- --></a> - - -<h1 class="topictitle1">Generating XML files from DTDs</h1> - - - - -<div><p>You can generate an XML file from your DTD if you want to quickly -create an XML file based on your DTD file. Generating an XML file from your -DTD saves you time by creating an XML file that is already associated with -your DTD, and contains at least some of the elements and attributes in your -DTD.</p> - -<div class="section"><p>After you have generated your XML file, you can further customize -it in the XML editor.</p> -<p>The following instructions were written for the -Resource perspective, but they will also work in many other perspectives.</p> -<p>To -create an XML file from a DTD file follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Navigator view, right-click the DTD file that you want to -work with.</span></li> - -<li class="stepexpand"><span>From its pop-up menu click <span class="menucascade"><span class="uicontrol">Generate</span> - > <span class="uicontrol">XML File</span></span>.</span></li> - -<li class="stepexpand"><span>Select a project or folder to contain the XML file and type a name -for it.</span> The name of the file must end in <kbd class="userinput">.xml</kbd>. -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>Select the <span class="uicontrol">Root element</span> of the XML file.</span> - The root element of an XML file is the element that contains all other -elements in that file. All the elements that you have defined in the DTD will -be shown in the <span class="uicontrol">Root element</span> list.</li> - -<li class="stepexpand"><span>Select from the following content options: </span> -<ul> -<li><span class="uicontrol">Create optional attributes</span>. Both mandatory -and optional attributes will be generated.</li> - -<li><span class="uicontrol">Create optional elements</span>. Both mandatory and -optional elements will be generated.</li> - -<li><span class="uicontrol">Create first choice of required choice</span>. The -first option of a required choice will be generated in your XML file.</li> - -<li><span class="uicontrol">Fill elements and attributes with data</span>. Any -elements and attributes generated will be filled with sample data.</li> - -</ul> - - <p>If you do not select any of these options, then only the minimum -amount of content required for the XML file will be created.</p> -</li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Public ID</span> or <span class="uicontrol">System -ID</span>.</span> You do not need to specify both. If you do, the -Public ID will be used before the System ID. </li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> - -</ol> - -<div class="section"><p>The XML file will only contain the selected root element and any -elements or attributes contained in the root element. You can now add elements, -attributes, entities, and notations to the XML file, however, they must follow -the rules established in the DTD that you used to create the XML file.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating XML files</a></div> -<div><a href="../topics/tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML schemas</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.dita deleted file mode 100644 index 20df2b6ea4..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.dita +++ /dev/null @@ -1,85 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="tcrexxsd" xml:lang="en-us">
-<title>Generating XML files from XML schemas</title>
-<titlealts>
-<searchtitle>Generating an XML file from an XML schema</searchtitle>
-</titlealts>
-<shortdesc>You can generate an XML file from your XML schema if you want to
-quickly create an XML file based on your XML schema file. Generating an XML
-file from your XML schema saves you time by creating an XML file that is already
-associated with your XML schema, and contains at least some of the elements
-and attributes in your XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>generating from XML schemas</indexterm></indexterm>
-<indexterm>XML schemas<indexterm>generating XML files</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>After you have generated your XML file, you can further customize
-it in the XML editor.</p><p>The following instructions were written for the
-Resource perspective, but they will also work in many other perspectives.</p><p>To
-generate an XML file from a schema file follow these steps:</p></context>
-<steps>
-<step><cmd>In the Navigator view, right-click the XML schema file that you
-want to work with.</cmd></step>
-<step><cmd>From its pop-up menu click <menucascade><uicontrol>Generate</uicontrol>
-<uicontrol>XML File</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select a project or folder to contain the XML file, type a name
-for it and click <uicontrol>Next</uicontrol>.</cmd><info>The name of the file
-must end in<systemoutput>.xml.</systemoutput> </info></step>
-<step><cmd>Click the <uicontrol>Root element</uicontrol> of the XML file.</cmd>
-<info>The root element of an XML file is the element that contains all other
-elements in that file. All of the global elements you have defined in the
-XML schema will be included in the Root element list. If you do not have any
-global elements in your XML schema, you cannot create an XML file from it.</info>
-</step>
-<step><cmd>Select from the following content options:</cmd>
-<choices>
-<choice><uicontrol>Create optional attributes</uicontrol>. Both mandatory
-and optional attributes will be generated.</choice>
-<choice><uicontrol>Create optional elements</uicontrol>. Both mandatory and
-optional elements will be generated.</choice>
-<choice><uicontrol>Create first choice of required choice</uicontrol>. The
-first option of a required choice will be generated in your XML file.</choice>
-<choice><uicontrol>Fill elements and attributes with data</uicontrol>. Any
-elements and attributes generated will be filled with sample data.</choice>
-</choices>
-<info>If you do not select any of these options, then only the minimum amount
-of content required for the XML file will be created.</info></step>
-<step><cmd>The Namespace information section contains information about the
-target namespace of the XML schema, its prefix, and the schema location.</cmd>
-<info>For more information about namespaces and namespace prefixes, refer
-to the related references.</info></step>
-<step><cmd>Select the entry you want to edit and click <uicontrol>Edit</uicontrol>.</cmd>
-</step>
-<step><cmd>The value in the <uicontrol>Namespace Name</uicontrol> field is
-the target namespace of the XML schema.</cmd><info>Your XML file should be
-associated with the same namespace as its XML schema is associated with.</info>
-</step>
-<step><cmd>All qualified elements and attributes in the XML file associated
-with the namespace will be prefixed with the <uicontrol>Prefix</uicontrol> value.</cmd>
-</step>
-<step><cmd>The <uicontrol>Location Hint</uicontrol> field contains the location
-of the XML schema.</cmd></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>, then <uicontrol>Finish</uicontrol>.</cmd>
-</step>
-</steps>
-<result><p>The XML file will contain the selected root element and any elements
-or attributes contained in the root element. It also contains information
-about the XML file namespace and location. You can now add elements and attributes
-to the XML file.</p><p><b>Note:</b> In certain cases, when an XML file is
-generated from a complex XML schema file, the XML file might not be valid.
-If this occurs, you can open the generated file in the XML editor and correct
-any errors that occur. Usually, only a few errors need to be fixed. The following
-XML schema constructs might present problems:</p><ol>
-<li>Restrictions. Sometimes restricted elements are erroneously generated. </li>
-<li>Facets: Default generated data values might not conform to complex facets
-(for example, patterns).</li>
-<li>Abstract elements. abstract elements are sometimes erroneously generated.</li>
-</ol></result>
-</taskbody>
-</task>
-<?Pub *0000004757?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html deleted file mode 100644 index 0d32765702..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html +++ /dev/null @@ -1,147 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Generating XML files from XML schemas" /> -<meta name="abstract" content="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema." /> -<meta name="description" content="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema." /> -<meta content="XML files, generating from XML schemas" name="DC.subject" /> -<meta content="XML files, generating from XML schemas" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcrexxsd" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Generating an XML file from an XML schema</title> -</head> -<body id="tcrexxsd"><a name="tcrexxsd"><!-- --></a> - - -<h1 class="topictitle1">Generating XML files from XML schemas</h1> - - - - -<div><p>You can generate an XML file from your XML schema if you want to -quickly create an XML file based on your XML schema file. Generating an XML -file from your XML schema saves you time by creating an XML file that is already -associated with your XML schema, and contains at least some of the elements -and attributes in your XML schema.</p> - -<div class="section"><p>After you have generated your XML file, you can further customize -it in the XML editor.</p> -<p>The following instructions were written for the -Resource perspective, but they will also work in many other perspectives.</p> -<p>To -generate an XML file from a schema file follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Navigator view, right-click the XML schema file that you -want to work with.</span></li> - -<li class="stepexpand"><span>From its pop-up menu click <span class="menucascade"><span class="uicontrol">Generate</span> - > <span class="uicontrol">XML File</span></span>.</span></li> - -<li class="stepexpand"><span>Select a project or folder to contain the XML file, type a name -for it and click <span class="uicontrol">Next</span>.</span> The name of the file -must end in<tt class="sysout">.xml.</tt> </li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Root element</span> of the XML file.</span> - The root element of an XML file is the element that contains all other -elements in that file. All of the global elements you have defined in the -XML schema will be included in the Root element list. If you do not have any -global elements in your XML schema, you cannot create an XML file from it. -</li> - -<li class="stepexpand"><span>Select from the following content options:</span> -<ul> -<li><span class="uicontrol">Create optional attributes</span>. Both mandatory -and optional attributes will be generated.</li> - -<li><span class="uicontrol">Create optional elements</span>. Both mandatory and -optional elements will be generated.</li> - -<li><span class="uicontrol">Create first choice of required choice</span>. The -first option of a required choice will be generated in your XML file.</li> - -<li><span class="uicontrol">Fill elements and attributes with data</span>. Any -elements and attributes generated will be filled with sample data.</li> - -</ul> - - If you do not select any of these options, then only the minimum amount -of content required for the XML file will be created.</li> - -<li class="stepexpand"><span>The Namespace information section contains information about the -target namespace of the XML schema, its prefix, and the schema location.</span> - For more information about namespaces and namespace prefixes, refer -to the related references.</li> - -<li class="stepexpand"><span>Select the entry you want to edit and click <span class="uicontrol">Edit</span>.</span> -</li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">Namespace Name</span> field is -the target namespace of the XML schema.</span> Your XML file should be -associated with the same namespace as its XML schema is associated with. -</li> - -<li class="stepexpand"><span>All qualified elements and attributes in the XML file associated -with the namespace will be prefixed with the <span class="uicontrol">Prefix</span> value.</span> -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">Location Hint</span> field contains the location -of the XML schema.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>, then <span class="uicontrol">Finish</span>.</span> -</li> - -</ol> - -<div class="section"><p>The XML file will contain the selected root element and any elements -or attributes contained in the root element. It also contains information -about the XML file namespace and location. You can now add elements and attributes -to the XML file.</p> -<p><strong>Note:</strong> In certain cases, when an XML file is -generated from a complex XML schema file, the XML file might not be valid. -If this occurs, you can open the generated file in the XML editor and correct -any errors that occur. Usually, only a few errors need to be fixed. The following -XML schema constructs might present problems:</p> -<ol> -<li>Restrictions. Sometimes restricted elements are erroneously generated. </li> - -<li>Facets: Default generated data values might not conform to complex facets -(for example, patterns).</li> - -<li>Abstract elements. abstract elements are sometimes erroneously generated.</li> - -</ol> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating XML files</a></div> -<div><a href="../topics/tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from DTDs</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita deleted file mode 100644 index 63f1b5c77d..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita +++ /dev/null @@ -1,62 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtcnst" xml:lang="en-us">
-<title>Editing with DTD or XML schema constraints</title>
-<titlealts>
-<searchtitle>Editing with DTD or XML schema constraints</searchtitle>
-</titlealts>
-<shortdesc>In the Design view, when you edit an XML file that has a set of
-constraints (that is, a set of rules) defined by a DTD or an XML schema, you
-can turn the constraints on and off to provide flexibility in the way you
-edit, but still maintain the validity of the document periodically.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>editing with constraints</indexterm></indexterm>
-<indexterm>XML files<indexterm>editing with constraints</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> When the constraints are turned on, and you are working in the
-Design view, the XML editor prevents you from inserting elements, attributes,
-or attribute values not permitted by the rules of the XML schema or DTD, and
-from removing necessary or predefined sets of tags and values. In this mode,
-an element's content must be valid to use the XML editor's guided editing
-options.</p><p>You might want to turn the constraints off for an XML file
-if you need more flexibility. For example, you want to try working with elements
-or attributes not permitted by the associated DTD or XML schema, without actually
-removing the association with the DTD or XML schema.</p><p>To turn the constraints
-for an XML file off, click <uicontrol>XML > Turn Grammar Constraints Off</uicontrol>.
-After you have turned the constraints off for a file, you can insert or delete
-any element or attribute regardless of the DTD or XML schema rules. You can
-create new elements or attributes that are not in the DTD or schema - these
-Design view prompts will only appear when you have turned constraints off.
-The file might not be valid, however, if you do this. </p><p>The following
-instructions were written for the Resource perspective, but they will also
-work in many other perspectives.</p><p>The following example shows what you
-can do if you turn the constraints of a DTD off:</p></context>
-<steps>
-<step><cmd>Open the XML file in the XML editor (right-click the file in the
-Navigator view and click <uicontrol>Open With > XML Editor</uicontrol>). </cmd>
-</step>
-<step><cmd>You have a DTD that specifies that an element requires at least
-one of a specific child element: </cmd><info><codeblock><!ELEMENT parentElement (childElement+)>
-</codeblock></info></step>
-<step><cmd>If, in an XML file associated with your DTD, you attempt to remove
-the final child element of the element with the DTD constraints turned on,
-the editor will not allow you to do this, as it will make the document invalid.</cmd>
-<info>You can confirm this by using the element's pop-up menu to verify that
-the <uicontrol>Remove</uicontrol> option is grayed out.</info></step>
-<step><cmd>To turn the DTD constraints off, click <uicontrol>XML > Turn Grammar
-Constraints Off</uicontrol>. </cmd></step>
-<step><cmd>If you attempt to remove the same child element with constraints
-off, the editor will allow you to.</cmd></step>
-<step><cmd>To correct the invalid document, you will have to re-add the necessary
-element, or remove the invalid tagging or value.</cmd></step>
-</steps>
-<result>If you introduce errors into your files, you must save and validate
-the file in order to see a list of the errors you have introduced. They will
-be listed in the Problems view. After you fix the errors, you must save and
-validate your file again to see if the file is now valid.</result>
-</taskbody>
-</task>
-<?Pub *0000003854?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html deleted file mode 100644 index ab8acd73dd..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html +++ /dev/null @@ -1,113 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing with DTD or XML schema constraints" /> -<meta name="abstract" content="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically." /> -<meta name="description" content="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically." /> -<meta content="XML editor, editing, with DTD or XML schema constraints, XML files, with DTD or XML schema constraints" name="DC.subject" /> -<meta content="XML editor, editing, with DTD or XML schema constraints, XML files, with DTD or XML schema constraints" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtcnst" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing with DTD or XML schema constraints</title> -</head> -<body id="tedtcnst"><a name="tedtcnst"><!-- --></a> - - -<h1 class="topictitle1">Editing with DTD or XML schema constraints</h1> - - - - -<div><p>In the Design view, when you edit an XML file that has a set of -constraints (that is, a set of rules) defined by a DTD or an XML schema, you -can turn the constraints on and off to provide flexibility in the way you -edit, but still maintain the validity of the document periodically.</p> - -<div class="section"><p> When the constraints are turned on, and you are working in the -Design view, the XML editor prevents you from inserting elements, attributes, -or attribute values not permitted by the rules of the XML schema or DTD, and -from removing necessary or predefined sets of tags and values. In this mode, -an element's content must be valid to use the XML editor's guided editing -options.</p> -<p>You might want to turn the constraints off for an XML file -if you need more flexibility. For example, you want to try working with elements -or attributes not permitted by the associated DTD or XML schema, without actually -removing the association with the DTD or XML schema.</p> -<p>To turn the constraints -for an XML file off, click <span class="uicontrol">XML > Turn Grammar Constraints Off</span>. -After you have turned the constraints off for a file, you can insert or delete -any element or attribute regardless of the DTD or XML schema rules. You can -create new elements or attributes that are not in the DTD or schema - these -Design view prompts will only appear when you have turned constraints off. -The file might not be valid, however, if you do this. </p> -<p>The following -instructions were written for the Resource perspective, but they will also -work in many other perspectives.</p> -<p>The following example shows what you -can do if you turn the constraints of a DTD off:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file in the XML editor (right-click the file in the -Navigator view and click <span class="uicontrol">Open With > XML Editor</span>). </span> -</li> - -<li class="stepexpand"><span>You have a DTD that specifies that an element requires at least -one of a specific child element: </span> <pre><!ELEMENT parentElement (childElement+)> -</pre> -</li> - -<li class="stepexpand"><span>If, in an XML file associated with your DTD, you attempt to remove -the final child element of the element with the DTD constraints turned on, -the editor will not allow you to do this, as it will make the document invalid.</span> - You can confirm this by using the element's pop-up menu to verify that -the <span class="uicontrol">Remove</span> option is grayed out.</li> - -<li class="stepexpand"><span>To turn the DTD constraints off, click <span class="uicontrol">XML > Turn Grammar -Constraints Off</span>. </span></li> - -<li class="stepexpand"><span>If you attempt to remove the same child element with constraints -off, the editor will allow you to.</span></li> - -<li class="stepexpand"><span>To correct the invalid document, you will have to re-add the necessary -element, or remove the invalid tagging or value.</span></li> - -</ol> - -<div class="section">If you introduce errors into your files, you must save and validate -the file in order to see a list of the errors you have introduced. They will -be listed in the Problems view. After you fix the errors, you must save and -validate your file again to see if the file is now valid.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.dita deleted file mode 100644 index 5f5a6820c8..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtdoc" xml:lang="en-us">
-<title>Editing DOCTYPE declarations</title>
-<titlealts>
-<searchtitle>Editing DOCTYPE declarations</searchtitle>
-</titlealts>
-<shortdesc>The DOCTYPE declaration in an XML file is used at the beginning
-of it to associate it with a DTD file. You can edit your DOCTYPE declaration
-to change the DTD file your XML file is associated with.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DOCTYPE declarations<indexterm>XML editor</indexterm></indexterm>
-<indexterm>XML editor<indexterm>DOCTYPE declarations</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit your DOCTYPE
-declaration, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Design view of the XML editor, right-click <uicontrol>DOCTYPE</uicontrol> and
-click <uicontrol>Edit DOCTYPE</uicontrol>.</cmd></step>
-<step><cmd>The value in the <uicontrol>Root element name</uicontrol> field
-should match the root element of your XML file exactly.</cmd><info>You should
-only edit the value in this field if your root element changes.</info></step>
-<step><cmd>You can select a Public ID for any existing XML Catalog entries
-by clicking <uicontrol>Browse</uicontrol>. </cmd><info>The value in the <uicontrol>Public
-ID</uicontrol> field is the Public Identifier. It is used to associate the
-XML file (using an XML Catalog entry) with a DTD file. For more information
-on XML Catalog entries, refer to the related tasks.</info></step>
-<step><cmd>The value in the <uicontrol>System ID</uicontrol> field is the
-DTD the XML file is associated with. Type the path of the DTD file (or browse
-for it) you want the XML file associated with in this field. </cmd><info> <b>Note</b>:
-When the XML file is processed by the XML processor, it will first try to
-use the Public ID to locate the DTD, and if this fails, it will use the System
-ID to find it.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq>If you do not have a DOCTYPE declaration in your XML file, you can
-right-click in the Design view and click <uicontrol>Add DTD Information</uicontrol> to
-add one.</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html deleted file mode 100644 index 4d877a3400..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html +++ /dev/null @@ -1,88 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing DOCTYPE declarations" /> -<meta name="abstract" content="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with." /> -<meta name="description" content="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with." /> -<meta content="XML editor, editing, DOCTYPE declarations, XML files" name="DC.subject" /> -<meta content="XML editor, editing, DOCTYPE declarations, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtdoc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing DOCTYPE declarations</title> -</head> -<body id="tedtdoc"><a name="tedtdoc"><!-- --></a> - - -<h1 class="topictitle1">Editing DOCTYPE declarations</h1> - - - - -<div><p>The DOCTYPE declaration in an XML file is used at the beginning -of it to associate it with a DTD file. You can edit your DOCTYPE declaration -to change the DTD file your XML file is associated with.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit your DOCTYPE -declaration, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view of the XML editor, right-click <span class="uicontrol">DOCTYPE</span> and -click <span class="uicontrol">Edit DOCTYPE</span>.</span></li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">Root element name</span> field -should match the root element of your XML file exactly.</span> You should -only edit the value in this field if your root element changes.</li> - -<li class="stepexpand"><span>You can select a Public ID for any existing XML Catalog entries -by clicking <span class="uicontrol">Browse</span>. </span> The value in the <span class="uicontrol">Public -ID</span> field is the Public Identifier. It is used to associate the -XML file (using an XML Catalog entry) with a DTD file. For more information -on XML Catalog entries, refer to the related tasks.</li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">System ID</span> field is the -DTD the XML file is associated with. Type the path of the DTD file (or browse -for it) you want the XML file associated with in this field. </span> <strong>Note</strong>: -When the XML file is processed by the XML processor, it will first try to -use the Public ID to locate the DTD, and if this fails, it will use the System -ID to find it.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section">If you do not have a DOCTYPE declaration in your XML file, you can -right-click in the Design view and click <span class="uicontrol">Add DTD Information</span> to -add one.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.dita deleted file mode 100644 index 92ec6ed1fb..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.dita +++ /dev/null @@ -1,36 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtenc" xml:lang="en-us">
-<title>Specifying XML default encoding line delimiters</title>
-<titlealts>
-<searchtitle>Specifying line delimiters</searchtitle>
-</titlealts>
-<shortdesc>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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>specifying line delimiters</indexterm></indexterm>
-<indexterm>line delimiters<indexterm>XML files</indexterm></indexterm>
-</keywords>
-<keywords></keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To specify the line delimiter you want to use:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>In the <uicontrol>Line delimiter</uicontrol> list, select the operating
-system that applies to your development or deployment platform. </cmd></step>
-<step><cmd>From the <uicontrol>Encoding</uicontrol> field, specify
-the default character encoding set that is used when creating XML related
-files (DTDs, XML files, XML schemas). Changing the encoding causes any new,
-XML related files that are created from scratch to use the selected encoding.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Apply</uicontrol>, then <uicontrol>OK</uicontrol>.</cmd>
-</step>
-</steps>
-<result></result>
-</taskbody>
-</task>
-<?Pub *0000001698?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html deleted file mode 100644 index 4f0cfd729c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Specifying XML default encoding line delimiters" /> -<meta name="abstract" content="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." /> -<meta name="description" content="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." /> -<meta content="XML files, specifying, line delimiters, encoding" name="DC.subject" /> -<meta content="XML files, specifying, line delimiters, encoding" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtenc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Specifying line delimiters</title> -</head> -<body id="tedtenc"><a name="tedtenc"><!-- --></a> - - -<h1 class="topictitle1">Specifying XML default encoding line delimiters</h1> - - - - -<div><p>This page lets you specify the line delimiter and the text encoding -that will be used when you create or save an XML related file.</p> - -<div class="section"><p>To specify the line delimiter you want to use:</p> -</div> - -<ol> -<li><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span></span>.</span> -</li> - -<li><span>In the <span class="uicontrol">Line delimiter</span> list, select the operating -system that applies to your development or deployment platform. </span></li> - -<li><span>From the <span class="uicontrol">Encoding</span> field, specify -the default character encoding set that is used when creating XML related -files (DTDs, XML files, XML schemas). Changing the encoding causes any new, -XML related files that are created from scratch to use the selected encoding.</span> -</li> - -<li><span>Click <span class="uicontrol">Apply</span>, then <span class="uicontrol">OK</span>.</span> -</li> - -</ol> - -<div class="section" /> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.dita deleted file mode 100644 index 83dc689aea..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtgram" xml:lang="en-us">
-<title>Updating XML files with changes made to DTDs and schemas</title>
-<titlealts>
-<searchtitle>Updating XML files with changes made to DTDs and schemas</searchtitle>
-</titlealts>
-<shortdesc>If you make changes to a DTD file or XML schema associated with
-an XML file (that is currently open), click <uicontrol>XML > Reload Dependencies</uicontrol> to
-update the XML file with these changes. The changes will be reflected in the
-guided editing mechanisms available in the editor, such as content assist.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>updating XML files</indexterm></indexterm>
-<indexterm>XML files<indexterm>updating with associated changes</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>For example, you have a DTD file called "Contact.dtd" and an XML
-file called "Contact.xml" associated with it. Contact.dtd contains a root
-element called <uicontrol>Contact</uicontrol> that can contain any of the
-following children elements: <uicontrol>Name</uicontrol>, <uicontrol>PostalAddress</uicontrol>,
- <uicontrol>Email</uicontrol>. If you remove the child element <uicontrol>Email</uicontrol> from
-the DTD, you will no longer be able to add an <uicontrol>Email</uicontrol> child
-element to your root element Contact in your Contact.xml file. This change,
-however, will not come into effect until you save your changes in the DTD
-and click <uicontrol>XML > Reload Dependencies</uicontrol> in the XML editor.
-Until you click it, you will still be able to add <uicontrol>Email</uicontrol> elements
-to Contact.xml.</p><p>This feature is very handy when you are making updates
-to both DTDs and XML schemas and XML files that are associated with DTDs and
-XML schemas.</p></context>
-</taskbody>
-</task>
-<?Pub *0000002040?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html deleted file mode 100644 index d1aba1d921..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html +++ /dev/null @@ -1,73 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Updating XML files with changes made to DTDs and schemas" /> -<meta name="abstract" content="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist." /> -<meta name="description" content="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist." /> -<meta content="XML editor, updating, XML files with associated changes, XML files, updating with associated changes" name="DC.subject" /> -<meta content="XML editor, updating, XML files with associated changes, XML files, updating with associated changes" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtgram" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Updating XML files with changes made to DTDs and schemas</title> -</head> -<body id="tedtgram"><a name="tedtgram"><!-- --></a> - - -<h1 class="topictitle1">Updating XML files with changes made to DTDs and schemas</h1> - - - - -<div><p>If you make changes to a DTD file or XML schema associated with -an XML file (that is currently open), click <span class="uicontrol">XML > Reload Dependencies</span> to -update the XML file with these changes. The changes will be reflected in the -guided editing mechanisms available in the editor, such as content assist.</p> - -<div class="section"><p>For example, you have a DTD file called "Contact.dtd" and an XML -file called "Contact.xml" associated with it. Contact.dtd contains a root -element called <span class="uicontrol">Contact</span> that can contain any of the -following children elements: <span class="uicontrol">Name</span>, <span class="uicontrol">PostalAddress</span>, - <span class="uicontrol">Email</span>. If you remove the child element <span class="uicontrol">Email</span> from -the DTD, you will no longer be able to add an <span class="uicontrol">Email</span> child -element to your root element Contact in your Contact.xml file. This change, -however, will not come into effect until you save your changes in the DTD -and click <span class="uicontrol">XML > Reload Dependencies</span> in the XML editor. -Until you click it, you will still be able to add <span class="uicontrol">Email</span> elements -to Contact.xml.</p> -<p>This feature is very handy when you are making updates -to both DTDs and XML schemas and XML files that are associated with DTDs and -XML schemas.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.dita deleted file mode 100644 index 0450ec76de..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtproc" xml:lang="en-us">
-<title>Editing XML processing instructions</title>
-<titlealts>
-<searchtitle>Editing XML processing instructions</searchtitle>
-</titlealts>
-<shortdesc>If you have instructions you want to pass along to an application
-using an XML document, you can use a processing instruction. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>processing instructions</indexterm></indexterm>
-<indexterm>XML files<indexterm>processing instructions</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit a processing
-instruction, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Design view of the XML editor, right-click your processing
-instruction, and click <uicontrol>Edit Processing Instruction</uicontrol>.</cmd>
-</step>
-<step><cmd>The <uicontrol>Target</uicontrol> field is used to identify the
-application the instructions belongs to.</cmd></step>
-<step><cmd>The <uicontrol>Data</uicontrol> field contains the instructions.</cmd>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq>To create a new processing instruction, right-click in the Design
-view, and click <uicontrol>Add Child</uicontrol>, <uicontrol>Add Before</uicontrol> or <uicontrol>Add
-After</uicontrol>, then click <uicontrol>Add Processing Instruction</uicontrol>.</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html deleted file mode 100644 index c00534aade..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html +++ /dev/null @@ -1,67 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML processing instructions" /> -<meta name="abstract" content="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction." /> -<meta name="description" content="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction." /> -<meta content="XML editor, editing, processing instructions, editing, XML files" name="DC.subject" /> -<meta content="XML editor, editing, processing instructions, editing, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtproc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML processing instructions</title> -</head> -<body id="tedtproc"><a name="tedtproc"><!-- --></a> - - -<h1 class="topictitle1">Editing XML processing instructions</h1> - - - - -<div><p>If you have instructions you want to pass along to an application -using an XML document, you can use a processing instruction. </p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit a processing -instruction, follow these steps:</p> -</div> - -<ol> -<li><span>In the Design view of the XML editor, right-click your processing -instruction, and click <span class="uicontrol">Edit Processing Instruction</span>.</span> -</li> - -<li><span>The <span class="uicontrol">Target</span> field is used to identify the -application the instructions belongs to.</span></li> - -<li><span>The <span class="uicontrol">Data</span> field contains the instructions.</span> -</li> - -<li><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section">To create a new processing instruction, right-click in the Design -view, and click <span class="uicontrol">Add Child</span>, <span class="uicontrol">Add Before</span> or <span class="uicontrol">Add -After</span>, then click <span class="uicontrol">Add Processing Instruction</span>.</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.dita deleted file mode 100644 index f016bfcb52..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.dita +++ /dev/null @@ -1,54 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtsch" xml:lang="en-us">
-<title>Editing namespace information</title>
-<titlealts>
-<searchtitle>Editing namespace information</searchtitle>
-</titlealts>
-<shortdesc>Your namespace information is used to provide various information
-about the XML file, such as the XML schema and namespace it is associated
-with. If desired, you can change the schema and namespace your XML file is
-associated with or add a new association. Modifying any associations can impact
-what content is allowed in the XML file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>namespace information</indexterm></indexterm>
-<indexterm>XML files<indexterm>namespace information</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit your schema
-information, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Design view of the XML editor, right-click your root element
-and click <uicontrol>Edit Namespaces</uicontrol>.</cmd></step>
-<step><cmd>Your XML file can be associated with more than one namespace or
-schema.</cmd><info>Select the entry you want to edit and click <uicontrol>Edit</uicontrol>.</info>
-</step>
-<step><cmd>The value in the <uicontrol>Namespace Name</uicontrol> field is
-a namespace the XML file is associated with.</cmd><info>Your XML file should
-be associated with the same namespace(s) its XML schema is associated with.
-For more information about namespaces, refer to the related reference.</info>
-</step>
-<step><cmd>All qualified elements and attributes in the XML file associated
-with the namespace will be prefixed with the <uicontrol>Prefix</uicontrol> value.</cmd>
-</step>
-<step><cmd>The <uicontrol>Location Hint</uicontrol> field contains the location
-of the XML schema the XML file is associated with.</cmd><info>An XML Catalog
-Key or a namespace name can be specified in this field. Click <uicontrol>Browse</uicontrol> to
-view all XML schemas in the workbench and XML Catalog.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>, then click <uicontrol>OK</uicontrol> again.</cmd>
-</step>
-</steps>
-<result><p>If you want to create a new association, click <uicontrol>Add</uicontrol> instead
-of <uicontrol>Edit</uicontrol>. You can then either click the <uicontrol>Specify
-From Registered Namespace</uicontrol> radio button and select the namespace
-declarations you want to add or click the <uicontrol>Specify New Namespace</uicontrol> radio
-button and fill in the fields as necessary.</p></result>
-<postreq>If you do not have namespace information in your XML file, you can
-right-click your root element in the Design view and click <uicontrol>Edit
-Namespaces</uicontrol> to add it. If you do not have a root element, you must
-create one before you can add the namespace information.</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html deleted file mode 100644 index d26938188e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html +++ /dev/null @@ -1,105 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing namespace information" /> -<meta name="abstract" content="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file." /> -<meta name="description" content="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file." /> -<meta content="XML editor, editing, namespace information, XML files" name="DC.subject" /> -<meta content="XML editor, editing, namespace information, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtsch" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing namespace information</title> -</head> -<body id="tedtsch"><a name="tedtsch"><!-- --></a> - - -<h1 class="topictitle1">Editing namespace information</h1> - - - - -<div><p>Your namespace information is used to provide various information -about the XML file, such as the XML schema and namespace it is associated -with. If desired, you can change the schema and namespace your XML file is -associated with or add a new association. Modifying any associations can impact -what content is allowed in the XML file.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit your schema -information, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view of the XML editor, right-click your root element -and click <span class="uicontrol">Edit Namespaces</span>.</span></li> - -<li class="stepexpand"><span>Your XML file can be associated with more than one namespace or -schema.</span> Select the entry you want to edit and click <span class="uicontrol">Edit</span>. -</li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">Namespace Name</span> field is -a namespace the XML file is associated with.</span> Your XML file should -be associated with the same namespace(s) its XML schema is associated with. -For more information about namespaces, refer to the related reference. -</li> - -<li class="stepexpand"><span>All qualified elements and attributes in the XML file associated -with the namespace will be prefixed with the <span class="uicontrol">Prefix</span> value.</span> -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">Location Hint</span> field contains the location -of the XML schema the XML file is associated with.</span> An XML Catalog -Key or a namespace name can be specified in this field. Click <span class="uicontrol">Browse</span> to -view all XML schemas in the workbench and XML Catalog.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>, then click <span class="uicontrol">OK</span> again.</span> -</li> - -</ol> - -<div class="section"><p>If you want to create a new association, click <span class="uicontrol">Add</span> instead -of <span class="uicontrol">Edit</span>. You can then either click the <span class="uicontrol">Specify -From Registered Namespace</span> radio button and select the namespace -declarations you want to add or click the <span class="uicontrol">Specify New Namespace</span> radio -button and fill in the fields as necessary.</p> -</div> - -<div class="section">If you do not have namespace information in your XML file, you can -right-click your root element in the Design view and click <span class="uicontrol">Edit -Namespaces</span> to add it. If you do not have a root element, you must -create one before you can add the namespace information.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.dita deleted file mode 100644 index 2f5d1b51e8..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="xmlsourcesuggestionstrategy" xml:lang="en-us">
-<title>Setting the XML source suggestion strategy used by content assist</title>
-<shortdesc>You can customize the formatting of the suggestions given by content
-assist by choosing a suggestion strategy preference. When the suggestion strategy
-is set to "Strict", suggestions that are 'strictly' grammatically valid will
-be displayed first in the list of options and highlighted by bold icons. Other
-suggestions that are applicable to this element's scope but are not grammatically
-valid, will be displayed lower in the list with de-emphasized icons. When
-the suggestion strategy is set to "Lax", all suggestions will displayed in
-the list with de-emphasized icons.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>source suggestion strategy</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>To set the suggestion strategy used by content assist:</context>
-<steps>
-<step><cmd>From the menu bar, Click <menucascade><uicontrol>Window</uicontrol>
-<uicontrol>Preferences</uicontrol></menucascade></cmd></step>
-<step><cmd>Select <menucascade><uicontrol>Web and XML</uicontrol><uicontrol>XML
-Files</uicontrol><uicontrol>XML Source</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Beside Suggestion strategy in the Content assist section, select
-the appropriate setting (for example, <uicontrol>Strict</uicontrol>).</cmd>
-</step>
-</steps>
-<example><p>The following screen capture demonstrates content assist with
-the suggestion strategy set to "Strict":</p><image href="../images/suggestion.gif"
-placement="break"><alt>Example of Strict Suggestion Strategy</alt></image></example>
-</taskbody>
-</task>
-<?Pub *0000001917?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.html deleted file mode 100644 index 274ff98f5e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.html +++ /dev/null @@ -1,66 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting the XML source suggestion strategy used by content assist" /> -<meta name="abstract" content="You can customize the formatting of the suggestions given by content assist by choosing a suggestion strategy preference. When the suggestion strategy is set to "Strict", suggestions that are 'strictly' grammatically valid will be displayed first in the list of options and highlighted by bold icons. Other suggestions that are applicable to this element's scope but are not grammatically valid, will be displayed lower in the list with de-emphasized icons. When the suggestion strategy is set to "Lax", all suggestions will displayed in the list with de-emphasized icons." /> -<meta name="description" content="You can customize the formatting of the suggestions given by content assist by choosing a suggestion strategy preference. When the suggestion strategy is set to "Strict", suggestions that are 'strictly' grammatically valid will be displayed first in the list of options and highlighted by bold icons. Other suggestions that are applicable to this element's scope but are not grammatically valid, will be displayed lower in the list with de-emphasized icons. When the suggestion strategy is set to "Lax", all suggestions will displayed in the list with de-emphasized icons." /> -<meta content="XML editor, setting, source suggestion strategy" name="DC.subject" /> -<meta content="XML editor, setting, source suggestion strategy" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twcdast.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="xmlsourcesuggestionstrategy" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting the XML source suggestion strategy used by content assist</title> -</head> -<body id="xmlsourcesuggestionstrategy"><a name="xmlsourcesuggestionstrategy"><!-- --></a> - - -<h1 class="topictitle1">Setting the XML source suggestion strategy used by content assist</h1> - - - -<div><p>You can customize the formatting of the suggestions given by content -assist by choosing a suggestion strategy preference. When the suggestion strategy -is set to "Strict", suggestions that are 'strictly' grammatically valid will -be displayed first in the list of options and highlighted by bold icons. Other -suggestions that are applicable to this element's scope but are not grammatically -valid, will be displayed lower in the list with de-emphasized icons. When -the suggestion strategy is set to "Lax", all suggestions will displayed in -the list with de-emphasized icons.</p> - -<div class="section">To set the suggestion strategy used by content assist:</div> - -<ol> -<li><span>From the menu bar, Click <span class="menucascade"><span class="uicontrol">Window</span> - > <span class="uicontrol">Preferences</span></span></span></li> - -<li><span>Select <span class="menucascade"><span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML -Files</span> > <span class="uicontrol">XML Source</span></span>.</span></li> - -<li><span>Beside Suggestion strategy in the Content assist section, select -the appropriate setting (for example, <span class="uicontrol">Strict</span>).</span> -</li> - -</ol> - -<div class="example"><p>The following screen capture demonstrates content assist with -the suggestion strategy set to "Strict":</p> -<br /><img src="../images/suggestion.gif" alt="Example of Strict Suggestion Strategy" /><br /></div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/twcdast.html" title="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code.">Using XML content assist</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.dita deleted file mode 100644 index d1506978e4..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="ttaghilt" xml:lang="en-us">
-<title>Setting source highlighting styles</title>
-<titlealts>
-<searchtitle>Setting source highlighting styles</searchtitle>
-</titlealts>
-<shortdesc>If desired, you can change various aspects of how the XML source
-code is displayed in the Source view of the XML editor, such as the colors
-the tags will be displayed in.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>setting source highlighting styles</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To set highlighting styles for the XML code, follow these steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol><uicontrol> XML
-Styles</uicontrol></menucascade>.</cmd></step>
-<step><cmd>In the <uicontrol>Content type</uicontrol> list, select the source
-tag type that you wish to set a highlighting style for. You can also click
-text in the sample text to specify the source tag type that you wish to set
-a highlighting style for.</cmd></step>
-<step><cmd>Click the <uicontrol>Foreground</uicontrol> box.</cmd></step>
-<step><cmd>Select the color that you want the text of the tag to appear in
-and click <uicontrol>OK</uicontrol>.</cmd></step>
-<step><cmd>Click the <uicontrol>Background</uicontrol> box.</cmd></step>
-<step><cmd>Select the color that you want to appear behind the tag and click <uicontrol>OK</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the <uicontrol>Bold</uicontrol> check box if you want to
-make the type bold.</cmd></step>
-<step><cmd>Click <uicontrol>Restore Default</uicontrol> to set the highlighting
-styles back to their default values. If you only want to reset the value for
-a particular content type, select it in the <uicontrol>Content type </uicontrol> field,
-the click the <uicontrol>Restore Default</uicontrol> button next to it. </cmd>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to save your changes.</cmd></step>
-</steps>
-<result></result>
-</taskbody>
-</task>
-<?Pub *0000002262?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html deleted file mode 100644 index de2dd481fe..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html +++ /dev/null @@ -1,81 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting source highlighting styles" /> -<meta name="abstract" content="If desired, you can change various aspects of how the XML source code is displayed in the Source view of the XML editor, such as the colors the tags will be displayed in." /> -<meta name="description" content="If desired, you can change various aspects of how the XML source code is displayed in the Source view of the XML editor, such as the colors the tags will be displayed in." /> -<meta content="XML editor, setting source highlighting styles" name="DC.subject" /> -<meta content="XML editor, setting source highlighting styles" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ttaghilt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting source highlighting styles</title> -</head> -<body id="ttaghilt"><a name="ttaghilt"><!-- --></a> - - -<h1 class="topictitle1">Setting source highlighting styles</h1> - - - - -<div><p>If desired, you can change various aspects of how the XML source -code is displayed in the Source view of the XML editor, such as the colors -the tags will be displayed in.</p> - -<div class="section"><p>To set highlighting styles for the XML code, follow these steps:</p> -</div> - -<ol> -<li><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol"> XML -Styles</span></span>.</span></li> - -<li><span>In the <span class="uicontrol">Content type</span> list, select the source -tag type that you wish to set a highlighting style for. You can also click -text in the sample text to specify the source tag type that you wish to set -a highlighting style for.</span></li> - -<li><span>Click the <span class="uicontrol">Foreground</span> box.</span></li> - -<li><span>Select the color that you want the text of the tag to appear in -and click <span class="uicontrol">OK</span>.</span></li> - -<li><span>Click the <span class="uicontrol">Background</span> box.</span></li> - -<li><span>Select the color that you want to appear behind the tag and click <span class="uicontrol">OK</span>.</span> -</li> - -<li><span>Select the <span class="uicontrol">Bold</span> check box if you want to -make the type bold.</span></li> - -<li><span>Click <span class="uicontrol">Restore Default</span> to set the highlighting -styles back to their default values. If you only want to reset the value for -a particular content type, select it in the <span class="uicontrol">Content type </span> field, -the click the <span class="uicontrol">Restore Default</span> button next to it. </span> -</li> - -<li><span>Click <span class="uicontrol">OK</span> to save your changes.</span></li> - -</ol> - -<div class="section" /> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.dita deleted file mode 100644 index 16ba4e3736..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.dita +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="twcdast" xml:lang="en-us">
-<title>Using XML content assist</title>
-<titlealts>
-<searchtitle>Using XML content assist</searchtitle>
-</titlealts>
-<shortdesc>You can use content assist to help you finish a tag or line of
-code in the Source view of the XML editor. You can also use content assist
-to insert templates into your XML code.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>content assist</indexterm></indexterm>
-<indexterm>XML files<indexterm>content assist</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The placement of the cursor in your source file provides the context
-for the content assist to offer suggestions for completion.</p><p>You can
-launch content assist in either of the following ways:</p><ul>
-<li>From the <uicontrol>Edit</uicontrol> menu, click <uicontrol>Content Assist</uicontrol>,
-or</li>
-<li>Press Ctrl+Space</li>
-</ul><p>In addition, you can set up an option that causes content assist to
-pop up automatically when certain characters are typed. To set up this option,
-click <menucascade><uicontrol>Window</uicontrol><uicontrol> Preferences</uicontrol>
-</menucascade> to open the Preferences window, then click <menucascade><uicontrol>Web
-and XML</uicontrol><uicontrol>XML Files </uicontrol><uicontrol>XML Source</uicontrol>
-</menucascade> . In the <uicontrol>Content assist</uicontrol> group box, select
-the <uicontrol>Automatically make suggestions</uicontrol> check box, and supply
-any additional characters that should trigger content assist.</p><p>If your
-cursor is in a position where content assist is available, a pop-up list of
-available choices is displayed when you launch content assist. The list is
-based on the context and whether a DTD or XML schema is associated with the
-XML file being edited. For example, if you have an Address element that can
-contain any of the following children elements: Name, Street, City, Zip Code,
-Country, and Province, and you place your cursor after any of them and launch
-content assist, all of the child elements will be listed in the content assist
-list.</p><p>The content assist list displays all valid tags for the current
-cursor position, including templates. If your grammar constraints are turned
-off, all available tags, not just valid ones are displayed. </p><p> </p><p>As
-you type the first one or two letters of the tag that you want, the list automatically
-refreshes with alphabetized choices that match your input.</p><p><b>Note</b>:
-The list only refreshes as described if you first type <userinput><</userinput> before
-prompting for content assist.</p><p>Scroll down and select the tag that you
-want to use by double-clicking on it. </p></context>
-</taskbody>
-</task>
-<?Pub *0000003061?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html deleted file mode 100644 index f70e050243..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html +++ /dev/null @@ -1,89 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Using XML content assist" /> -<meta name="abstract" content="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code." /> -<meta name="description" content="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code." /> -<meta content="XML editor, editing, content assist, XML files" name="DC.subject" /> -<meta content="XML editor, editing, content assist, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twmacro.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tsugstrat.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twcdast" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Using XML content assist</title> -</head> -<body id="twcdast"><a name="twcdast"><!-- --></a> - - -<h1 class="topictitle1">Using XML content assist</h1> - - - - -<div><p>You can use content assist to help you finish a tag or line of -code in the Source view of the XML editor. You can also use content assist -to insert templates into your XML code.</p> - -<div class="section"><p>The placement of the cursor in your source file provides the context -for the content assist to offer suggestions for completion.</p> -<p>You can -launch content assist in either of the following ways:</p> -<ul> -<li>From the <span class="uicontrol">Edit</span> menu, click <span class="uicontrol">Content Assist</span>, -or</li> - -<li>Press Ctrl+Space</li> - -</ul> -<p>In addition, you can set up an option that causes content assist to -pop up automatically when certain characters are typed. To set up this option, -click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol"> Preferences</span> -</span> to open the Preferences window, then click <span class="menucascade"><span class="uicontrol">Web -and XML</span> > <span class="uicontrol">XML Files </span> > <span class="uicontrol">XML Source</span> -</span> . In the <span class="uicontrol">Content assist</span> group box, select -the <span class="uicontrol">Automatically make suggestions</span> check box, and supply -any additional characters that should trigger content assist.</p> -<p>If your -cursor is in a position where content assist is available, a pop-up list of -available choices is displayed when you launch content assist. The list is -based on the context and whether a DTD or XML schema is associated with the -XML file being edited. For example, if you have an Address element that can -contain any of the following children elements: Name, Street, City, Zip Code, -Country, and Province, and you place your cursor after any of them and launch -content assist, all of the child elements will be listed in the content assist -list.</p> -<p>The content assist list displays all valid tags for the current -cursor position, including templates. If your grammar constraints are turned -off, all available tags, not just valid ones are displayed. </p> -<p> </p> -<p>As -you type the first one or two letters of the tag that you want, the list automatically -refreshes with alphabetized choices that match your input.</p> -<p><strong>Note</strong>: -The list only refreshes as described if you first type <kbd class="userinput"><</kbd> before -prompting for content assist.</p> -<p>Scroll down and select the tag that you -want to use by double-clicking on it. </p> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/twmacro.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time.">Working with XML templates</a></div> -<div><a href="../topics/tsugstrat.html" title="You can customize the formatting of the suggestions given by content assist by choosing a suggestion strategy preference. When the suggestion strategy is set to "Strict", suggestions that are 'strictly' grammatically valid will be displayed first in the list of options and highlighted by bold icons. Other suggestions that are applicable to this element's scope but are not grammatically valid, will be displayed lower in the list with de-emphasized icons. When the suggestion strategy is set to "Lax", all suggestions will displayed in the list with de-emphasized icons.">Setting the XML source suggestion strategy used by content assist</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.dita deleted file mode 100644 index c7ebd9a297..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="twmacro" xml:lang="en-us">
-<title>Working with XML templates</title>
-<titlealts>
-<searchtitle>Working with XML templates</searchtitle>
-</titlealts>
-<shortdesc>XML content assist provides a comment template, a chunk of predefined
-code that you can insert into a file. You may find a template useful when
-you have a certain piece of code you want to reuse several times, and you
-do not want to write it out every time.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML templates<indexterm>working with predefined code</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>You can use a default template as provided, customize that template,
-or create your own templates.</p>For example, you can 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 <uicontrol>Pattern</uicontrol> field.)
-Then select the name of the template from a content assist proposal list whenever
-you want to insert your custom table into an XML file.<p>To create a new XML
-template follow these steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol><uicontrol>XML
-Templates</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Click <uicontrol>New</uicontrol> if you want to create a completely
-new template.</cmd></step>
-<step><cmd>Supply a new template <uicontrol>Name</uicontrol> and <uicontrol>Description</uicontrol>.</cmd>
-</step>
-<step><cmd>Specify the <uicontrol>Context</uicontrol> for the template.</cmd>
-<info>This is the context in which the template is available in the proposal
-list when content assist is requested. </info></step>
-<step><cmd>Specify the <uicontrol>Pattern</uicontrol> for your template using
-the appropriate tags, attributes, or attribute values to be inserted by content
-assist.</cmd></step>
-<step><cmd>If you want to insert a variable, click the <uicontrol>Insert Variable</uicontrol> button
-and select the variable to be inserted. </cmd><info>For example, the <b>date</b> variable
-indicates the current date will be inserted. </info></step>
-<step><cmd>Click <uicontrol>Apply</uicontrol> and then <uicontrol>OK</uicontrol> to
-save your changes.</cmd></step>
-</steps>
-<postreq>You can edit, remove, import, or export a template by using the same
-preferences page. If you have modified a default template, you can restore
-it to its default value. You can also restore a removed template if you have
-not exited from the workbench since it was removed. <p>If you have a template
-that you do not want to remove but you no longer want it to appear in the
-content assist list, go to the <b>XML Templates</b> preferences page and clear
-its check box.</p></postreq>
-</taskbody>
-</task>
-<?Pub *0000003427?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html deleted file mode 100644 index 5cfc5198e7..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html +++ /dev/null @@ -1,95 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Working with XML templates" /> -<meta name="abstract" content="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time." /> -<meta name="description" content="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time." /> -<meta content="XML templates, creating, editing, XML templates, removing, importing, exporting" name="DC.subject" /> -<meta content="XML templates, creating, editing, XML templates, removing, importing, exporting" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twcdast.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twmacro" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with XML templates</title> -</head> -<body id="twmacro"><a name="twmacro"><!-- --></a> - - -<h1 class="topictitle1">Working with XML templates</h1> - - - - -<div><p>XML content assist provides a comment template, a chunk of predefined -code that you can insert into a file. You may find a template useful when -you have a certain piece of code you want to reuse several times, and you -do not want to write it out every time.</p> - -<div class="section"><p>You can use a default template as provided, customize that template, -or create your own templates.</p> -For example, you can 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>To create a new XML -template follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML -Templates</span></span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">New</span> if you want to create a completely -new template.</span></li> - -<li class="stepexpand"><span>Supply a new template <span class="uicontrol">Name</span> and <span class="uicontrol">Description</span>.</span> -</li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Context</span> for the template.</span> - This is the context in which the template is available in the proposal -list when content assist is requested. </li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Pattern</span> for your template using -the appropriate tags, attributes, or attribute values to be inserted by content -assist.</span></li> - -<li class="stepexpand"><span>If you want to insert a variable, click the <span class="uicontrol">Insert Variable</span> button -and select the variable to be inserted. </span> For example, the <strong>date</strong> variable -indicates the current date will be inserted. </li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Apply</span> and then <span class="uicontrol">OK</span> to -save your changes.</span></li> - -</ol> - -<div class="section">You can edit, remove, import, or export a template by using the same -preferences page. If you have modified a default template, you can restore -it to its default value. You can also restore a removed template if you have -not exited from the workbench since it was removed. <p>If you have a template -that you do not want to remove but you no longer want it to appear in the -content assist list, go to the <strong>XML Templates</strong> preferences page and clear -its check box.</p> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/twcdast.html" title="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code.">Using XML content assist</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.dita deleted file mode 100644 index 09e77a0ed9..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.dita +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twxvalid" xml:lang="en-us">
-<title>Validating XML files</title>
-<titlealts>
-<searchtitle>Validating XML files</searchtitle>
-</titlealts>
-<shortdesc>When you validate your XML file, the XML validator will check to
-see that your file is valid and well-formed.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>validating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The XML editor will process XML files that are invalid or not
-well-formed. The editor uses heuristics to open a file using the best interpretation
-of the tagging that it can. For example, an element with a missing end tag
-is simply assumed to end at the end of the document. As you make updates to
-a file, the editor incrementally reinterprets your document, changing the
-highlighting, tree view, and so on. Many formation errors are easy to spot
-in the syntax highlighting, so you can easily correct obvious errors on-the-fly.
-However, there will be other cases when it will be beneficial to perform formal
-validation on your documents.</p></context>
-<steps>
-<step><cmd>You can validate your file by selecting it in the Navigator view,
-right-clicking it, and clicking <uicontrol>Validate</uicontrol>.</cmd>
-</step>
-</steps>
-<result><p>Any validation problems are indicated in the Problems view. </p></result>
-<postreq><p>In the Problems view, you can double-click on individual errors,
-and you will be taken to the invalid tag in the file, so that you can make
-corrections. </p><p><b>Note</b>: If you receive an error message indicating
-that the Problems view is full, you can increase the number of error messages
-allowed by selecting <menucascade><uicontrol>Properties</uicontrol><uicontrol>Validation</uicontrol>
-</menucascade> from the project's pop-up menu and specifying the maximum number
-of error messages allowed. You must select the <uicontrol>Override validation
-preferences</uicontrol> check box in order to be able to do this.</p><p>As
-well, you can set up a project's properties so that different types of project
-resources are automatically validated when you save them. From a project's
-pop-up menu select <uicontrol>Properties</uicontrol>, then select <uicontrol>Validation</uicontrol>.
-Any validators you can run against your project will be listed in the Validation
-page.</p></postreq>
-</taskbody>
-<related-links>
-<link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
-<linktext>Validating code in enterprise applications</linktext></link>
-</related-links>
-</task>
-<?Pub *0000002727?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html deleted file mode 100644 index 0b9ab90023..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html +++ /dev/null @@ -1,83 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Validating XML files" /> -<meta name="abstract" content="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed." /> -<meta name="description" content="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed." /> -<meta content="XML files, validating" name="DC.subject" /> -<meta content="XML files, validating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twxvalid" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Validating XML files</title> -</head> -<body id="twxvalid"><a name="twxvalid"><!-- --></a> - - -<h1 class="topictitle1">Validating XML files</h1> - - - - -<div><p>When you validate your XML file, the XML validator will check to -see that your file is valid and well-formed.</p> - -<div class="section"><p>The XML editor will process XML files that are invalid or not -well-formed. The editor uses heuristics to open a file using the best interpretation -of the tagging that it can. For example, an element with a missing end tag -is simply assumed to end at the end of the document. As you make updates to -a file, the editor incrementally reinterprets your document, changing the -highlighting, tree view, and so on. Many formation errors are easy to spot -in the syntax highlighting, so you can easily correct obvious errors on-the-fly. -However, there will be other cases when it will be beneficial to perform formal -validation on your documents.</p> -</div> - - -<div class="p"><span>You can validate your file by selecting it in the Navigator view, -right-clicking it, and clicking <span class="uicontrol">Validate</span>.</span> -</div> - - -<div class="section"><p>Any validation problems are indicated in the Problems view. </p> -</div> - -<div class="section"><p>In the Problems view, you can double-click on individual errors, -and you will be taken to the invalid tag in the file, so that you can make -corrections. </p> -<p><strong>Note</strong>: If you receive an error message indicating -that the Problems view is full, you can increase the number of error messages -allowed by selecting <span class="menucascade"><span class="uicontrol">Properties</span> > <span class="uicontrol">Validation</span> -</span> from the project's pop-up menu and specifying the maximum number -of error messages allowed. You must select the <span class="uicontrol">Override validation -preferences</span> check box in order to be able to do this.</p> -<p>As -well, you can set up a project's properties so that different types of project -resources are automatically validated when you save them. From a project's -pop-up menu select <span class="uicontrol">Properties</span>, then select <span class="uicontrol">Validation</span>. -Any validators you can run against your project will be listed in the Validation -page.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html">Validating code in enterprise applications</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.dita deleted file mode 100644 index c0b5f94e9a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.dita +++ /dev/null @@ -1,94 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="txedtdes" xml:lang="en-us">
-<title>Editing in the Design view</title>
-<titlealts>
-<searchtitle>Editing in the Design view</searchtitle>
-</titlealts>
-<shortdesc>The XML editor has a Design view, which represents the XML file
-simultaneously as a table and a tree. This helps make navigation and editing
-easier. Content and attribute values can be edited directly in the table cells,
-while pop-up menus on the tree elements give alternatives that are valid for
-that particular element.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>Design view</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> For example, the <uicontrol>Add child</uicontrol> menu item will
-list only those elements from a DTD or XML schema which would be valid children
-at that point.</p><p>When you have an XML file associated with an XML schema
-or DTD file, certain tags and rules for that file have already been established,
-which is why the Design view can provide prompts (via a pop-up menu) for those
-tags. When you create an XML file that is not associated with an XML schema
-or DTD file, it has no tags or rules associated with it, so the Design view
-cannot provide prompts for specific tags, but it can provide prompts to create
-new elements and attributes.</p><p>For any XML file associated with an XML
-schema or DTD file, you can use the Design view to add any items defined in
-the XML schema or DTD (such as elements and attributes) to the XML file. You
-can also use it to add processing instructions and comments to all XML files.</p><p>For
-more information on the icons used in the Design view, refer to the related
-reference.</p><p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives.</p><p>To
-edit an XML file in the Design view, follow these steps:</p></context>
-<steps>
-<step><cmd>Open the XML file that you want to work with in the XML editor
-(right-click the file in the Navigator view and click <uicontrol>Open With
-> XML Editor</uicontrol>). If necessary, click the <uicontrol>Design</uicontrol> tab.</cmd>
-</step>
-<step><cmd>To expand all the items in your XML file, click the <uicontrol>Expand
-All</uicontrol> toolbar button <image href="../images/expand_all.gif"><alt>This
-graphic is the Expand All toolbar button</alt></image>.</cmd></step>
-<step><cmd>To collapse them, click the <uicontrol>Collapse All</uicontrol> toolbar
-button <image href="../images/collapse_all.gif"><alt>This graphic is the
-Collapse All toolbar button</alt></image>.</cmd></step>
-<step><cmd>Right-click the item that you want to work with.</cmd><info>Some
-or all of the following options (as applicable) will be available from the
-pop-up menu that appears:<ul>
-<li> <uicontrol>Add DTD Information</uicontrol> - Click this if you want to
-associate the XML file with a DTD.</li>
-<li> <uicontrol>Edit DOCTYPE</uicontrol> - Click this if you want to edit
-the DOCTYPE declaration. Refer to the related task for more details.</li>
-<li> <uicontrol>Edit Namespaces</uicontrol> - Click this if you want to edit
-the existing namespace information or create a new association with a namespace.
-Refer to the related task for more details.</li>
-<li> <uicontrol>Edit Processing Instruction</uicontrol> - Click this if you
-want to edit the processing instruction. Refer to the related task for more
-details.</li>
-<li> <uicontrol>Remove</uicontrol> - Click this if you want to remove the
-item that you have selected from the XML file. This option will not be available
-if the item you want to remove must exist (for example, in your DTD, you have
-declared that "One or more" of the item must always exist in your XML file,
-and the item you have selected is the only one that exists in your XML file).</li>
-<li> <uicontrol>Add Attribute</uicontrol> - Click this if you want to add
-an attribute to the element that you selected. Any attributes you are allowed
-to add to the element will be listed. After you have added the attribute to
-the XML file, you can click in the right-hand column to change the value of
-the attribute. If the attribute has set values, they will appear in a list.</li>
-<li> <uicontrol>Add Child</uicontrol> - Click this to add another element,
-a comment, or a processing instruction as a child of the parent element.</li>
-<li> <uicontrol>Add Before</uicontrol> - Click this to add a child element,
-comment, or processing instruction that can go before the item you have selected.
-For example, if you have a parent element called "CD Collections" that can
-contain an unlimited amount of children called "CD", you could click a CD
-element and click <menucascade><uicontrol>Add Before</uicontrol><uicontrol> CD</uicontrol>
-</menucascade> , as a CD element can go before another CD element.</li>
-<li> <uicontrol>Add After</uicontrol> - Click this to add a child element,
-comment, or processing instruction that can go after the item you have selected.
-For example, if you have a parent element called "CD Collections" that can
-contain an unlimited amount of children called "CD", you could click a CD
-element and click <menucascade><uicontrol>Add After</uicontrol><uicontrol> CD</uicontrol>
-</menucascade>, as a CD element can go after another CD element.</li>
-<li> <uicontrol>Replace With</uicontrol> - Click this if you want to replace
-one item with another. This option is not available if you turn grammar constraints
-off or if there are no valid alternatives for you to replace the item with.</li>
-</ul></info></step>
-<step><cmd>Click the appropriate option.</cmd></step>
-</steps>
-<result><p>Any changes you make in the Design view are also reflected in the
-Source view and the Outline view.</p></result>
-</taskbody>
-</task>
-<?Pub *0000005971?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html deleted file mode 100644 index ace05b2314..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html +++ /dev/null @@ -1,157 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing in the Design view" /> -<meta name="abstract" content="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element." /> -<meta name="description" content="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element." /> -<meta content="XML editor, editing, in the Design view" name="DC.subject" /> -<meta content="XML editor, editing, in the Design view" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtproc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rxmlbicons.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txedtdes" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing in the Design view</title> -</head> -<body id="txedtdes"><a name="txedtdes"><!-- --></a> - - -<h1 class="topictitle1">Editing in the Design view</h1> - - - - -<div><p>The XML editor has a Design view, which represents the XML file -simultaneously as a table and a tree. This helps make navigation and editing -easier. Content and attribute values can be edited directly in the table cells, -while pop-up menus on the tree elements give alternatives that are valid for -that particular element.</p> - -<div class="section"><p> For example, the <span class="uicontrol">Add child</span> menu item will -list only those elements from a DTD or XML schema which would be valid children -at that point.</p> -<p>When you have an XML file associated with an XML schema -or DTD file, certain tags and rules for that file have already been established, -which is why the Design view can provide prompts (via a pop-up menu) for those -tags. When you create an XML file that is not associated with an XML schema -or DTD file, it has no tags or rules associated with it, so the Design view -cannot provide prompts for specific tags, but it can provide prompts to create -new elements and attributes.</p> -<p>For any XML file associated with an XML -schema or DTD file, you can use the Design view to add any items defined in -the XML schema or DTD (such as elements and attributes) to the XML file. You -can also use it to add processing instructions and comments to all XML files.</p> -<p>For -more information on the icons used in the Design view, refer to the related -reference.</p> -<p>The following instructions were written for the Resource -perspective, but they will also work in many other perspectives.</p> -<p>To -edit an XML file in the Design view, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file that you want to work with in the XML editor -(right-click the file in the Navigator view and click <span class="uicontrol">Open With -> XML Editor</span>). If necessary, click the <span class="uicontrol">Design</span> tab.</span> -</li> - -<li class="stepexpand"><span>To expand all the items in your XML file, click the <span class="uicontrol">Expand -All</span> toolbar button <img src="../images/expand_all.gif" alt="This graphic is the Expand All toolbar button" />.</span></li> - -<li class="stepexpand"><span>To collapse them, click the <span class="uicontrol">Collapse All</span> toolbar -button <img src="../images/collapse_all.gif" alt="This graphic is the Collapse All toolbar button" />.</span></li> - -<li class="stepexpand"><span>Right-click the item that you want to work with.</span> Some -or all of the following options (as applicable) will be available from the -pop-up menu that appears:<ul> -<li> <span class="uicontrol">Add DTD Information</span> - Click this if you want to -associate the XML file with a DTD.</li> - -<li> <span class="uicontrol">Edit DOCTYPE</span> - Click this if you want to edit -the DOCTYPE declaration. Refer to the related task for more details.</li> - -<li> <span class="uicontrol">Edit Namespaces</span> - Click this if you want to edit -the existing namespace information or create a new association with a namespace. -Refer to the related task for more details.</li> - -<li> <span class="uicontrol">Edit Processing Instruction</span> - Click this if you -want to edit the processing instruction. Refer to the related task for more -details.</li> - -<li> <span class="uicontrol">Remove</span> - Click this if you want to remove the -item that you have selected from the XML file. This option will not be available -if the item you want to remove must exist (for example, in your DTD, you have -declared that "One or more" of the item must always exist in your XML file, -and the item you have selected is the only one that exists in your XML file).</li> - -<li> <span class="uicontrol">Add Attribute</span> - Click this if you want to add -an attribute to the element that you selected. Any attributes you are allowed -to add to the element will be listed. After you have added the attribute to -the XML file, you can click in the right-hand column to change the value of -the attribute. If the attribute has set values, they will appear in a list.</li> - -<li> <span class="uicontrol">Add Child</span> - Click this to add another element, -a comment, or a processing instruction as a child of the parent element.</li> - -<li> <span class="uicontrol">Add Before</span> - Click this to add a child element, -comment, or processing instruction that can go before the item you have selected. -For example, if you have a parent element called "CD Collections" that can -contain an unlimited amount of children called "CD", you could click a CD -element and click <span class="menucascade"><span class="uicontrol">Add Before</span> > <span class="uicontrol"> CD</span> -</span> , as a CD element can go before another CD element.</li> - -<li> <span class="uicontrol">Add After</span> - Click this to add a child element, -comment, or processing instruction that can go after the item you have selected. -For example, if you have a parent element called "CD Collections" that can -contain an unlimited amount of children called "CD", you could click a CD -element and click <span class="menucascade"><span class="uicontrol">Add After</span> > <span class="uicontrol"> CD</span> -</span>, as a CD element can go after another CD element.</li> - -<li> <span class="uicontrol">Replace With</span> - Click this if you want to replace -one item with another. This option is not available if you turn grammar constraints -off or if there are no valid alternatives for you to replace the item with.</li> - -</ul> -</li> - -<li class="stepexpand"><span>Click the appropriate option.</span></li> - -</ol> - -<div class="section"><p>Any changes you make in the Design view are also reflected in the -Source view and the Outline view.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -<div><a href="../topics/tedtproc.html" title="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction.">Editing XML processing instructions</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rxmlbicons.html" title="The following XML editor icons appear in the Outline and Design view.">Icons used in the XML editor</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.dita deleted file mode 100644 index a453b108c6..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.dita +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="txedtsrc" xml:lang="en-us">
-<title>Editing in the Source view</title>
-<titlealts>
-<searchtitle>Editing in the Source view</searchtitle>
-</titlealts>
-<shortdesc>You can use the Source view to view and work with a file's source
-code directly.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>Source view</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> The Source view has many text editing features, such as:</p><dl>
-<dlentry>
-<dt>Syntax highlighting</dt>
-<dd>Each tag type is highlighted differently, enabling you to easily find
-a certain kind of tag for editing. In addition, syntax highlighting is valuable
-in locating syntax errors. For example, if you begin a comment in the middle
-of the document with <codeph><!--</codeph> everything until the next <codeph>--></codeph> is
-considered a comment, and will be highlighted accordingly. The large highlighted
-area will indicate that you need to add <codeph>--></codeph> to close the
-comment.<p>You can customize the syntax highlighting. Refer to the related
-tasks for more information.</p></dd>
-</dlentry></dl><dl><dlentry>
-<dt>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>
-</dlentry><dlentry>
-<dt>Content assist</dt>
-<dd>Content assist helps you finish tags and insert macros. Refer
-to the related task for more details.</dd>
-</dlentry><dlentry>
-<dt>Template</dt>
-<dd>You can access templates (using content assist) to help you quickly add
-regularly-used tagging combinations. Refer to the related task for more details.</dd>
-</dlentry><dlentry>
-<dt>Node selection</dt>
-<dd>Based on the location of your cursor (or selection in the Outline view),
-the node selection indicator highlights the line numbers that include a node
-(for example, an element or attribute), in the vertical ruler in the left
-area of the Source view.</dd>
-</dlentry><dlentry>
-<dt>Pop-up menu options</dt>
-<dd>From the editor's pop-up menu, you have many of the same editing options
-available as you do from the workbench <b>Edit</b> menu. You can select menu
-options such as: <uicontrol>Cleanup Document,</uicontrol> to open the <uicontrol>Cleanup</uicontrol>
-dialog, which contains settings to update a document so that it is well-formed
-and formatted and <uicontrol>Format,</uicontrol> which formats either the
-entire document or selected elements.</dd>
-</dlentry><dlentry>
-<dt>"Smart" double clicking</dt>
-<dd>You can use double-click to select attribute values, attribute-value pairs,
-and entire tag sets to quickly update, copy, or remove content.</dd>
-</dlentry></dl><p>To edit an XML file in the Source view, follow these steps:</p></context>
-<steps>
-<step><cmd>Open the XML file you want to work with in the XML editor (right-click
-the file in the Navigator view and click <uicontrol>Open With > XML Editor</uicontrol>). </cmd>
-<info>You might need to click the <uicontrol>Source</uicontrol> tab. Typically,
-all that you will need to do to open the file is to double-click it in the
-Navigator view. If this does not work, right-click it and click <uicontrol>Open
-With > XML Editor</uicontrol>.</info></step>
-<step><cmd>Edit the code as necessary, using any of the available features.</cmd>
-<info>As you move the cursor within your XML file (or select items from the
-Outline view), the node selection indicator will highlight the line numbers
-that encompass the node (for example, an element or attribute). You can use
-smart double-clicking behavior to select attribute values, attribute-value
-pairs, and entire tag sets to quickly update, copy, or remove content.</info>
-</step>
-<step><cmd>At intervals, you might wish to format individual nodes, or the
-entire XML file to restore element and attribute indentation to see nesting
-hierarchies more clearly in the file.</cmd></step>
-<step><cmd>If desired, validate and save the XML file.</cmd></step>
-</steps>
-<result><p>Any changes you make in the Source view are also reflected in the
-Design view and the Outline view.</p></result>
-</taskbody>
-</task>
-<?Pub *0000004423?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html deleted file mode 100644 index c96c43dc37..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html +++ /dev/null @@ -1,145 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing in the Source view" /> -<meta name="abstract" content="You can use the Source view to view and work with a file's source code directly." /> -<meta name="description" content="You can use the Source view to view and work with a file's source code directly." /> -<meta content="XML editor, editing, in the Source view" name="DC.subject" /> -<meta content="XML editor, editing, in the Source view" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twcdast.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twmacro.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/ttaghilt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txedtsrc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing in the Source view</title> -</head> -<body id="txedtsrc"><a name="txedtsrc"><!-- --></a> - - -<h1 class="topictitle1">Editing in the Source view</h1> - - - - -<div><p>You can use the Source view to view and work with a file's source -code directly.</p> - -<div class="section"><p> The Source view has many text editing features, such as:</p> -<dl> - -<dt class="dlterm">Syntax highlighting</dt> - -<dd>Each tag type is highlighted differently, enabling you to easily find -a certain kind of tag for editing. In addition, syntax highlighting is valuable -in locating syntax errors. For example, if you begin a comment in the middle -of the document with <samp class="codeph"><!--</samp> everything until the next <samp class="codeph">--></samp> is -considered a comment, and will be highlighted accordingly. The large highlighted -area will indicate that you need to add <samp class="codeph">--></samp> to close the -comment.<p>You can customize the syntax highlighting. Refer to the related -tasks for more information.</p> -</dd> - -</dl> -<dl> -<dt class="dlterm">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="dlterm">Content assist</dt> - -<dd>Content assist helps you finish tags and insert macros. Refer -to the related task for more details.</dd> - - -<dt class="dlterm">Template</dt> - -<dd>You can access templates (using content assist) to help you quickly add -regularly-used tagging combinations. Refer to the related task for more details.</dd> - - -<dt class="dlterm">Node selection</dt> - -<dd>Based on the location of your cursor (or selection in the Outline view), -the node selection indicator highlights the line numbers that include a node -(for example, an element or attribute), in the vertical ruler in the left -area of the Source view.</dd> - - -<dt class="dlterm">Pop-up menu options</dt> - -<dd>From the editor's pop-up menu, you have many of the same editing options -available as you do from the workbench <strong>Edit</strong> menu. You can select menu -options such as: <span class="uicontrol">Cleanup Document,</span> to open the <span class="uicontrol">Cleanup</span> -dialog, which contains settings to update a document so that it is well-formed -and formatted and <span class="uicontrol">Format,</span> which formats either the -entire document or selected elements.</dd> - - -<dt class="dlterm">"Smart" double clicking</dt> - -<dd>You can use double-click to select attribute values, attribute-value pairs, -and entire tag sets to quickly update, copy, or remove content.</dd> - -</dl> -<p>To edit an XML file in the Source view, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file you want to work with in the XML editor (right-click -the file in the Navigator view and click <span class="uicontrol">Open With > XML Editor</span>). </span> - You might need to click the <span class="uicontrol">Source</span> tab. Typically, -all that you will need to do to open the file is to double-click it in the -Navigator view. If this does not work, right-click it and click <span class="uicontrol">Open -With > XML Editor</span>.</li> - -<li class="stepexpand"><span>Edit the code as necessary, using any of the available features.</span> - As you move the cursor within your XML file (or select items from the -Outline view), the node selection indicator will highlight the line numbers -that encompass the node (for example, an element or attribute). You can use -smart double-clicking behavior to select attribute values, attribute-value -pairs, and entire tag sets to quickly update, copy, or remove content. -</li> - -<li class="stepexpand"><span>At intervals, you might wish to format individual nodes, or the -entire XML file to restore element and attribute indentation to see nesting -hierarchies more clearly in the file.</span></li> - -<li class="stepexpand"><span>If desired, validate and save the XML file.</span></li> - -</ol> - -<div class="section"><p>Any changes you make in the Source view are also reflected in the -Design view and the Outline view.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/twcdast.html" title="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code.">Using XML content assist</a></div> -<div><a href="../topics/twmacro.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time.">Working with XML templates</a></div> -<div><a href="../topics/ttaghilt.html" title="If desired, you can change various aspects of how the XML source code is displayed in the Source view of the XML editor, such as the colors the tags will be displayed in.">Setting source highlighting styles</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.dita deleted file mode 100644 index df24fd5cb4..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.dita +++ /dev/null @@ -1,46 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="txedttag" xml:lang="en-us">
-<title>Editing XML files</title>
-<titlealts>
-<searchtitle>Editing XML files</searchtitle>
-</titlealts>
-<shortdesc>This file contains information about editing XML files.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>XML files</indexterm></indexterm>
-<indexterm>XML files<indexterm>editing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To open an XML file in the XML editor, right-click it in the Navigator
-view and click <menucascade><uicontrol>Open With</uicontrol><uicontrol>XML
-Editor</uicontrol></menucascade>. </p><p>We recommend working in the Resource
-perspective when you are developing XML files. The views that appear by default
-in this perspective (such as the Outline view) help facilitate XML development.</p><p>The
-XML editor enables you to directly edit XML files. There are several different
-views you can use to edit your files:</p><ul>
-<li><b>Source view</b> - you can manually insert, edit, and delete elements
-and attributes in the Source view of the XML editor. To facilitate this effort,
-you can use content assist while you are in the Source view.</li>
-<li><b>Design view</b> - you can insert, delete, and edit elements, attributes,
-comments, and processing instructions in this view.</li>
-<li><b>Outline view </b>- you can insert and delete elements attributes, comments,
-and processing instructions in this view.</li>
-</ul><p>Often, you may find that you have more than one way to perform a specific
-task. For example, you have an XML file "MySchoolSubjects.xml" associated
-with an XML schema file "SchoolSubjects.xsd", which list all the subjects
-taught in a school. You want to insert a new element "Math" into your file.
-You can do so in the following ways:</p><ul>
-<li>In the Outline or Design view, right-click the appropriate parent element
-and select <uicontrol>Math</uicontrol> from the <uicontrol>Add Child</uicontrol> pop-up
-menu.</li>
-<li>In the Source view, use content assist to help you find the appropriate
-location and code for the <uicontrol>Math</uicontrol> element.</li>
-<li>In the Source view, type the code for the <uicontrol>Math</uicontrol> element
-in the file.</li>
-</ul></context>
-<postreq>The following links provide more information about the XML editor
-and editing XML files:</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html deleted file mode 100644 index af6b692b85..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html +++ /dev/null @@ -1,90 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML files" /> -<meta name="abstract" content="This file contains information about editing XML files." /> -<meta name="description" content="This file contains information about editing XML files." /> -<meta content="XML files, editing, XML editor" name="DC.subject" /> -<meta content="XML files, editing, XML editor" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txedttag" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML files</title> -</head> -<body id="txedttag"><a name="txedttag"><!-- --></a> - - -<h1 class="topictitle1">Editing XML files</h1> - - - - -<div><p>This file contains information about editing XML files.</p> - -<div class="section"><p>To open an XML file in the XML editor, right-click it in the Navigator -view and click <span class="menucascade"><span class="uicontrol">Open With</span> > <span class="uicontrol">XML -Editor</span></span>. </p> -<p>We recommend working in the Resource -perspective when you are developing XML files. The views that appear by default -in this perspective (such as the Outline view) help facilitate XML development.</p> -<p>The -XML editor enables you to directly edit XML files. There are several different -views you can use to edit your files:</p> -<ul> -<li><strong>Source view</strong> - you can manually insert, edit, and delete elements -and attributes in the Source view of the XML editor. To facilitate this effort, -you can use content assist while you are in the Source view.</li> - -<li><strong>Design view</strong> - you can insert, delete, and edit elements, attributes, -comments, and processing instructions in this view.</li> - -<li><strong>Outline view </strong>- you can insert and delete elements attributes, comments, -and processing instructions in this view.</li> - -</ul> -<p>Often, you may find that you have more than one way to perform a specific -task. For example, you have an XML file "MySchoolSubjects.xml" associated -with an XML schema file "SchoolSubjects.xsd", which list all the subjects -taught in a school. You want to insert a new element "Math" into your file. -You can do so in the following ways:</p> -<ul> -<li>In the Outline or Design view, right-click the appropriate parent element -and select <span class="uicontrol">Math</span> from the <span class="uicontrol">Add Child</span> pop-up -menu.</li> - -<li>In the Source view, use content assist to help you find the appropriate -location and code for the <span class="uicontrol">Math</span> element.</li> - -<li>In the Source view, type the code for the <span class="uicontrol">Math</span> element -in the file.</li> - -</ul> -</div> - -<div class="section">The following links provide more information about the XML editor -and editing XML files:</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.dita deleted file mode 100644 index 828484fcc1..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.dita +++ /dev/null @@ -1,115 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="txmlcat" xml:lang="en-us">
-<title>Adding entries to the XML Catalog</title>
-<titlealts>
-<searchtitle>Adding entries to the XML Catalog</searchtitle>
-</titlealts>
-<shortdesc>An XML Catalog entry contains two parts - a Key (which represents
-a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains
-information about a DTD or XML schema's location). You can place the Key in
-an XML file. When the XML processor encounters it, it will use the XML Catalog
-entry to find the location of the DTD or XML schema associated with the Key</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML catalog<indexterm>adding entries</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>XML Catalog entries can be used in various situations. For example,
-you are working on an XML file on your main desktop computer and point its <codeph>schemaLocation</codeph> towards
-a schema called <codeph>c:\MySchema.xsd</codeph>. You then save it to your
-laptop computer so you can work on it later. When you open the file on your
-laptop, however, you encounter a problem - the XML editor cannot find the <codeph>MySchema.xsd</codeph> schema
-because it is actually installed on your D drive. You will have to edit the <codeph>schemaLocation</codeph> to
-point to <codeph>d:\MySchema.xsd</codeph>. When you have finished editing
-the XML file and are ready to publish it on the Web, you will need to edit
-the URI again so that it points to a resource that is accessible on the Web.
-By now, the problem is obvious. A URI used within an XML file is not as portable
-as you would like it to be. To avoid making frequent changes to your XML document,
-you can use the XML Catalog.</p><p>An XML Catalog entry is used by an XML
-processor when resolving entity references. You can provide rules to the catalog
-to specify how entities should be resolved. If you consider the preceding
-example, you could specify a rule that redirects an Internet resource reference
-(for example, <codeph>"http://www.ibm.com/published-schemas/MySchema.xsd"</codeph>)
-so that it points to a resource on the developer's local machine (for example,
- <codeph>"file:///C:/MySchema.xsd"</codeph>). Now, instead of frequently editing
-XML documents to update the URIs (especially when there are many documents
-in your project), you only need to update a single rule in your XML Catalog.</p><p>The
-following instructions were written for the Resource perspective, but they
-will also work in many other perspectives.</p><p>To add an entry to the XML
-Catalog, follow these steps:</p></context>
-<steps>
-<step><cmd>Open the XML file that you want to associate with a DTD or XML
-schema.</cmd></step>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Catalog</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>The <uicontrol>XML Catalog Entries</uicontrol> field contains
-a list of any user-defined and plug-in defined catalog entries.</cmd>
-<substeps>
-<substep><cmd>Select any entry to see details about it in the <uicontrol>Details</uicontrol> field. </cmd>
-</substep>
-<substep><cmd>Click <uicontrol>Add</uicontrol> to create a new catalog entry.</cmd>
-</substep>
-</substeps>
-</step>
-<step><cmd>In the <uicontrol>URI</uicontrol> field, type the location of the
-DTD or XML schema or browse for it.</cmd></step>
-<step><cmd>If you specified a DTD in the <uicontrol>URI</uicontrol> field,
-you can select either <uicontrol>Public ID</uicontrol> or <uicontrol>System
-ID</uicontrol> from the <uicontrol>Key Type</uicontrol> field.</cmd><info>If
-you select <uicontrol>Public ID,</uicontrol> the value you enter in the <uicontrol>Key</uicontrol> field
-should be the same as the Public ID in the XML file's DOCTYPE declaration.
-If you select <uicontrol>System ID</uicontrol>, the value you enter should
-correspond to the System ID in an XML file's DOCTYPE declaration.</info></step>
-<step><cmd>If you specified an XML schema in the <uicontrol>URI</uicontrol> field,
-you can select either <uicontrol>Namespace Name</uicontrol> or <uicontrol>Schema
-Location</uicontrol> from the <uicontrol>Key Type</uicontrol> field.</cmd>
-<info>If the schema defines a target namespace, it will automatically appear
-in the <uicontrol>Key</uicontrol> field. Otherwise, you can enter the schema
-location in the <uicontrol>Key</uicontrol> field.</info></step>
-<step><cmd>Select the <uicontrol>Specify alternative Web address</uicontrol> check
-box if you want to be able to specify an alternate Web address for the resource.</cmd>
-<info>This Web address is used when an XML instance is generated from this
-catalog entry. <b>Note</b>: This option is only available if you select <uicontrol>Public
-ID</uicontrol> (for a DTD) or <uicontrol>Namespace Name</uicontrol> (for
-a schema) in the <uicontrol>Key type</uicontrol> field.</info></step>
-<step><cmd>If you want to refer to another catalog without importing it into
-the workbench, click <uicontrol>Next Catalog</uicontrol>. Type or browse for
-the XML catalog you want to refer to. </cmd></step>
-<step><cmd>When you are done creating catalog entries, click <uicontrol>OK</uicontrol> to
-close the Add XML Catalog Entry dialog. </cmd></step>
-<step><cmd>Click <uicontrol>Advanced</uicontrol> if you want to import or
-export any XML Catalog settings.</cmd></step>
-<step><cmd>Click <uicontrol>Export</uicontrol> if you want to persist the
-XML Catalog information. Only your user specified entries will be exported.</cmd>
-<substeps>
-<substep><cmd>You will be prompted to select a project and provide a file
-name to store your catalog entries in an .xmlcatalog file, which can be opened
-from the Navigator view. Snce your catalog entries are stored in an .xmlcatalog
-file, you can check them in and out and share them like any other project
-resource. </cmd></substep>
-<substep><cmd>Click <uicontrol>OK</uicontrol>.</cmd></substep>
-</substeps>
-</step>
-<step><cmd>Click <uicontrol>Import</uicontrol> if you want to import an .xmlcatalog
-file. You will be prompted to select the file you want to import.</cmd>
-<substeps>
-<substep><cmd>When you import a .xmlcatalog file, any entries in it will be
-loaded into the XML Catalog (and any existing entries will be overwritten). </cmd>
-</substep>
-<substep><cmd>Click <uicontrol>OK</uicontrol>.</cmd></substep>
-</substeps>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to close the Advanced XML Catalog
-Preferences dialog.</cmd></step>
-<step><cmd>Make sure the XML file is in focus and click the <uicontrol>Reload
-dependencies</uicontrol> toolbar button. </cmd></step>
-</steps>
-<result>The XML file is now associated with the latest version of the XML
-schema or DTD.</result>
-</taskbody>
-</task>
-<?Pub *0000007087?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html deleted file mode 100644 index 2d172b4c26..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html +++ /dev/null @@ -1,181 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding entries to the XML Catalog" /> -<meta name="abstract" content="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key" /> -<meta name="description" content="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key" /> -<meta content="XML catalog, adding entries, importing entries, exporting entries" name="DC.subject" /> -<meta content="XML catalog, adding entries, importing entries, exporting entries" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txmlcat" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding entries to the XML Catalog</title> -</head> -<body id="txmlcat"><a name="txmlcat"><!-- --></a> - - -<h1 class="topictitle1">Adding entries to the XML Catalog</h1> - - - - -<div><p>An XML Catalog entry contains two parts - a Key (which represents -a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains -information about a DTD or XML schema's location). You can place the Key in -an XML file. When the XML processor encounters it, it will use the XML Catalog -entry to find the location of the DTD or XML schema associated with the Key</p> - -<div class="section"><p>XML Catalog entries can be used in various situations. For example, -you are working on an XML file on your main desktop computer and point its <samp class="codeph">schemaLocation</samp> towards -a schema called <samp class="codeph">c:\MySchema.xsd</samp>. You then save it to your -laptop computer so you can work on it later. When you open the file on your -laptop, however, you encounter a problem - the XML editor cannot find the <samp class="codeph">MySchema.xsd</samp> schema -because it is actually installed on your D drive. You will have to edit the <samp class="codeph">schemaLocation</samp> to -point to <samp class="codeph">d:\MySchema.xsd</samp>. When you have finished editing -the XML file and are ready to publish it on the Web, you will need to edit -the URI again so that it points to a resource that is accessible on the Web. -By now, the problem is obvious. A URI used within an XML file is not as portable -as you would like it to be. To avoid making frequent changes to your XML document, -you can use the XML Catalog.</p> -<p>An XML Catalog entry is used by an XML -processor when resolving entity references. You can provide rules to the catalog -to specify how entities should be resolved. If you consider the preceding -example, you could specify a rule that redirects an Internet resource reference -(for example, <samp class="codeph">"http://www.ibm.com/published-schemas/MySchema.xsd"</samp>) -so that it points to a resource on the developer's local machine (for example, - <samp class="codeph">"file:///C:/MySchema.xsd"</samp>). Now, instead of frequently editing -XML documents to update the URIs (especially when there are many documents -in your project), you only need to update a single rule in your XML Catalog.</p> -<p>The -following instructions were written for the Resource perspective, but they -will also work in many other perspectives.</p> -<p>To add an entry to the XML -Catalog, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file that you want to associate with a DTD or XML -schema.</span></li> - -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Catalog</span></span>.</span> -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">XML Catalog Entries</span> field contains -a list of any user-defined and plug-in defined catalog entries.</span> -<ol type="a"> -<li><span>Select any entry to see details about it in the <span class="uicontrol">Details</span> field. </span> -</li> - -<li><span>Click <span class="uicontrol">Add</span> to create a new catalog entry.</span> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>In the <span class="uicontrol">URI</span> field, type the location of the -DTD or XML schema or browse for it.</span></li> - -<li class="stepexpand"><span>If you specified a DTD in the <span class="uicontrol">URI</span> field, -you can select either <span class="uicontrol">Public ID</span> or <span class="uicontrol">System -ID</span> from the <span class="uicontrol">Key Type</span> field.</span> If -you select <span class="uicontrol">Public ID,</span> the value you enter in the <span class="uicontrol">Key</span> field -should be the same as the Public ID in the XML file's DOCTYPE declaration. -If you select <span class="uicontrol">System ID</span>, the value you enter should -correspond to the System ID in an XML file's DOCTYPE declaration.</li> - -<li class="stepexpand"><span>If you specified an XML schema in the <span class="uicontrol">URI</span> field, -you can select either <span class="uicontrol">Namespace Name</span> or <span class="uicontrol">Schema -Location</span> from the <span class="uicontrol">Key Type</span> field.</span> - If the schema defines a target namespace, it will automatically appear -in the <span class="uicontrol">Key</span> field. Otherwise, you can enter the schema -location in the <span class="uicontrol">Key</span> field.</li> - -<li class="stepexpand"><span>Select the <span class="uicontrol">Specify alternative Web address</span> check -box if you want to be able to specify an alternate Web address for the resource.</span> - This Web address is used when an XML instance is generated from this -catalog entry. <strong>Note</strong>: This option is only available if you select <span class="uicontrol">Public -ID</span> (for a DTD) or <span class="uicontrol">Namespace Name</span> (for -a schema) in the <span class="uicontrol">Key type</span> field.</li> - -<li class="stepexpand"><span>If you want to refer to another catalog without importing it into -the workbench, click <span class="uicontrol">Next Catalog</span>. Type or browse for -the XML catalog you want to refer to. </span></li> - -<li class="stepexpand"><span>When you are done creating catalog entries, click <span class="uicontrol">OK</span> to -close the Add XML Catalog Entry dialog. </span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Advanced</span> if you want to import or -export any XML Catalog settings.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Export</span> if you want to persist the -XML Catalog information. Only your user specified entries will be exported.</span> -<ol type="a"> -<li><span>You will be prompted to select a project and provide a file -name to store your catalog entries in an .xmlcatalog file, which can be opened -from the Navigator view. Snce your catalog entries are stored in an .xmlcatalog -file, you can check them in and out and share them like any other project -resource. </span></li> - -<li><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Import</span> if you want to import an .xmlcatalog -file. You will be prompted to select the file you want to import.</span> -<ol type="a"> -<li><span>When you import a .xmlcatalog file, any entries in it will be -loaded into the XML Catalog (and any existing entries will be overwritten). </span> -</li> - -<li><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span> to close the Advanced XML Catalog -Preferences dialog.</span></li> - -<li class="stepexpand"><span>Make sure the XML file is in focus and click the <span class="uicontrol">Reload -dependencies</span> toolbar button. </span></li> - -</ol> - -<div class="section">The XML file is now associated with the latest version of the XML -schema or DTD.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.dita deleted file mode 100644 index 1fa7ac53ca..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.dita +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="txprefs" xml:lang="en-us">
-<title>Defining XML editor preferences</title>
-<titlealts>
-<searchtitle>Defining XML editor preferences</searchtitle>
-</titlealts>
-<shortdesc>You can set various preferences for the Source view of the XML
-editor such as the formatter indentation style, line wrapping rules, and content
-assist rules. To apply the formatting styles, right-click in in the Source
-view for your XML document, and click <menucascade><uicontrol>Format</uicontrol>
-<uicontrol>Document</uicontrol></menucascade>.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>preferences</indexterm></indexterm>
-<indexterm>preferences<indexterm>XML editor</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To define XML preferences, perform the following steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol><uicontrol>XML
-Source</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Enter a maximum width for formatted lines in the <uicontrol>Line
-width</uicontrol> field</cmd><info>The default value is 72.</info></step>
-<step><cmd>Select <uicontrol>Split multiple attributes each on a new line</uicontrol> to
-start every attribute on a new line.</cmd></step>
-<step><cmd>If you want blank lines to be removed when the document is formatted,
-select the <uicontrol>Clear all blank lines</uicontrol> check box. </cmd>
-<info>By default, blank lines are preserved in a formatted document.</info>
-</step>
-<step><cmd>Select <uicontrol>Indent using tabs</uicontrol> if you want to
-use tab characters (\t) as the standard formatting indentation, or, if you
-prefer to use spaces, select <uicontrol>Indent using spaces</uicontrol>.</cmd>
-</step>
-<step><cmd>You can also specify the <uicontrol>Indentation size</uicontrol> which
-is the number of tabs or space characters used for formatting indentation.</cmd>
-</step>
-<step><cmd>You can specify certain characters ('<' is default) that will
-cause the content assist list to pop up automatically. Ensure the <uicontrol>Automatically
-make suggestions</uicontrol> check box is selected and specify the characters
-in the <uicontrol>Prompt when these characters are inserted</uicontrol> field. </cmd>
-</step>
-<step><cmd>If you select <b>Strict</b> from the <b>Suggestion strategy</b> list,
-suggestions that are grammatically valid will be shown first (with bold icons)
-in the content assist list. Other suggestions that are applicable to the element
-scope, but not grammatically valid, will be shown below them with a de-emphasized
-icon. The default value for this field is <b>Strict</b>.</cmd></step>
-<step><cmd>The <uicontrol>Use inferred grammar in absence of DTD/Schema</uicontrol> check
-box is selected by default. </cmd><info>If this box is selected, when you
-have an XML file that is not associated with a DTD or XML schema, you will
-still be able to get content assist - the tool will infer what should come
-next in your file based on the existing content.</info></step>
-<step><cmd>Click <uicontrol>Apply</uicontrol> and then <uicontrol>OK</uicontrol> to
-save your changes.</cmd></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html deleted file mode 100644 index c14d8f95c8..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html +++ /dev/null @@ -1,91 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Defining XML editor preferences" /> -<meta name="abstract" content="You can set various preferences for the Source view of the XML editor such as the formatter indentation style, line wrapping rules, and content assist rules. To apply the formatting styles, right-click in in the Source view for your XML document, and click Format > Document." /> -<meta name="description" content="You can set various preferences for the Source view of the XML editor such as the formatter indentation style, line wrapping rules, and content assist rules. To apply the formatting styles, right-click in in the Source view for your XML document, and click Format > Document." /> -<meta content="XML editor, setting, line wrapping rules, content assist rules, indentation style" name="DC.subject" /> -<meta content="XML editor, setting, line wrapping rules, content assist rules, indentation style" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txprefs" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Defining XML editor preferences</title> -</head> -<body id="txprefs"><a name="txprefs"><!-- --></a> - - -<h1 class="topictitle1">Defining XML editor preferences</h1> - - - - -<div><p>You can set various preferences for the Source view of the XML -editor such as the formatter indentation style, line wrapping rules, and content -assist rules. To apply the formatting styles, right-click in in the Source -view for your XML document, and click <span class="menucascade"><span class="uicontrol">Format</span> - > <span class="uicontrol">Document</span></span>.</p> - -<div class="section"><p>To define XML preferences, perform the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML -Source</span></span>.</span></li> - -<li class="stepexpand"><span>Enter a maximum width for formatted lines in the <span class="uicontrol">Line -width</span> field</span> The default value is 72.</li> - -<li class="stepexpand"><span>Select <span class="uicontrol">Split multiple attributes each on a new line</span> to -start every attribute on a new line.</span></li> - -<li class="stepexpand"><span>If you want blank lines to be removed when the document is formatted, -select the <span class="uicontrol">Clear all blank lines</span> check box. </span> - By default, blank lines are preserved in a formatted document. -</li> - -<li class="stepexpand"><span>Select <span class="uicontrol">Indent using tabs</span> if you want to -use tab characters (\t) as the standard formatting indentation, or, if you -prefer to use spaces, select <span class="uicontrol">Indent using spaces</span>.</span> -</li> - -<li class="stepexpand"><span>You can also specify the <span class="uicontrol">Indentation size</span> which -is the number of tabs or space characters used for formatting indentation.</span> -</li> - -<li class="stepexpand"><span>You can specify certain characters ('<' is default) that will -cause the content assist list to pop up automatically. Ensure the <span class="uicontrol">Automatically -make suggestions</span> check box is selected and specify the characters -in the <span class="uicontrol">Prompt when these characters are inserted</span> field. </span> -</li> - -<li class="stepexpand"><span>If you select <strong>Strict</strong> from the <strong>Suggestion strategy</strong> list, -suggestions that are grammatically valid will be shown first (with bold icons) -in the content assist list. Other suggestions that are applicable to the element -scope, but not grammatically valid, will be shown below them with a de-emphasized -icon. The default value for this field is <strong>Strict</strong>.</span></li> - -<li class="stepexpand"><span>The <span class="uicontrol">Use inferred grammar in absence of DTD/Schema</span> check -box is selected by default. </span> If this box is selected, when you -have an XML file that is not associated with a DTD or XML schema, you will -still be able to get content assist - the tool will infer what should come -next in your file based on the existing content.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Apply</span> and then <span class="uicontrol">OK</span> to -save your changes.</span></li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.dita deleted file mode 100644 index 15a6bda6ac..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.dita +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="txsityp" xml:lang="en-us">
-<title>Using xsi:type</title>
-<titlealts>
-<searchtitle>Using xsi:type</searchtitle>
-</titlealts>
-<shortdesc>If you have elements in your XML file whose type is a complex type,
-xsi:type support in the XML editor lets you choose between the complex type
-and any other complex types derived from it.</shortdesc>
-<taskbody>
-<context><p>The XML Schema specification allows you to derive types by extension.
-For example, you have an XML schema and you create a complex type for it called
- <userinput>Address</userinput>. You then add some basic elements to <userinput>Address</userinput>,
-such as <userinput>streetName</userinput> and <userinput>city</userinput>.</p><p>After
-this, you derive (by extension) two new complex types from <userinput>Address</userinput> - <userinput>USAddress</userinput> and <userinput>UKAddress</userinput
-> You add a new element to <userinput>USAddress</userinput> called <userinput>state</userinput>,
-and also a new element to <userinput>UKAddress</userinput> called <userinput>postcode</userinput>.</p><p>After
-you have done this, you create two more elements - <userinput>billTo</userinput> and <userinput>shipTo</userinput> -
-as <systemoutput>Address</systemoutput> types.</p><p>When you create an XML
-instance document for an element such as <systemoutput>billTo</systemoutput> or
- <userinput>Address</userinput>, an xsi:type attribute will automatically
-be added to it. For example:</p><codeblock><billTo xsi:type="ipo:Address"></codeblock><p>The
-xsi:type attribute is used to identify derived complex types (as well as complex
-types that have been derived from).</p><p>In the Design view of the XML editor,
-a list will be available, letting you select the appropriate type definition
-(<uicontrol>Address</uicontrol>, <uicontrol>USAddress</uicontrol>, or <uicontrol>UKAddress</uicontrol>).
-The guided editing for the content model will reflect the type definition
-that you choose. For example, if you select <uicontrol>USAddress</uicontrol> ,
-your <codeph>billTo</codeph> element can contain a <codeph>state</codeph> element,
-but it cannot contain a <codeph>postcode</codeph> element.</p><p>The XML example
-"Editing and validating XML files" demonstrates <b>xsi:type</b> support.</p><p>For
-more information about xsi:type, refer to the <b>Using Derived Types in Instance
-Documents</b> section in <xref format="html" href="http://www.w3.org/TR/xmlschema-0/#UseDerivInInstDocs"
-scope="external">XML Schema Part 0: Primer.</xref></p><p>For more information
-about validation semantics when xsi:type is used, refer to the <b>Schema-Related
-Markup in Documents Being Validated</b> section in <xref format="html" href="http://www.w3.org/TR/xmlschema-1/#xsi_type"
-scope="external">XML Schema Part 1: Structures</xref> </p></context>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html deleted file mode 100644 index 87ed2c68f7..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html +++ /dev/null @@ -1,70 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Using xsi:type" /> -<meta name="abstract" content="If you have elements in your XML file whose type is a complex type, xsi:type support in the XML editor lets you choose between the complex type and any other complex types derived from it." /> -<meta name="description" content="If you have elements in your XML file whose type is a complex type, xsi:type support in the XML editor lets you choose between the complex type and any other complex types derived from it." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txsityp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Using xsi:type</title> -</head> -<body id="txsityp"><a name="txsityp"><!-- --></a> - - -<h1 class="topictitle1">Using xsi:type</h1> - - - -<div><p>If you have elements in your XML file whose type is a complex type, -xsi:type support in the XML editor lets you choose between the complex type -and any other complex types derived from it.</p> - -<div class="section"><p>The XML Schema specification allows you to derive types by extension. -For example, you have an XML schema and you create a complex type for it called - <kbd class="userinput">Address</kbd>. You then add some basic elements to <kbd class="userinput">Address</kbd>, -such as <kbd class="userinput">streetName</kbd> and <kbd class="userinput">city</kbd>.</p> -<p>After -this, you derive (by extension) two new complex types from <kbd class="userinput">Address</kbd> - <kbd class="userinput">USAddress</kbd> and <kbd class="userinput">UKAddress</kbd> You add a new element to <kbd class="userinput">USAddress</kbd> called <kbd class="userinput">state</kbd>, -and also a new element to <kbd class="userinput">UKAddress</kbd> called <kbd class="userinput">postcode</kbd>.</p> -<p>After -you have done this, you create two more elements - <kbd class="userinput">billTo</kbd> and <kbd class="userinput">shipTo</kbd> - -as <tt class="sysout">Address</tt> types.</p> -<p>When you create an XML -instance document for an element such as <tt class="sysout">billTo</tt> or - <kbd class="userinput">Address</kbd>, an xsi:type attribute will automatically -be added to it. For example:</p> -<pre><billTo xsi:type="ipo:Address"></pre> -<p>The -xsi:type attribute is used to identify derived complex types (as well as complex -types that have been derived from).</p> -<p>In the Design view of the XML editor, -a list will be available, letting you select the appropriate type definition -(<span class="uicontrol">Address</span>, <span class="uicontrol">USAddress</span>, or <span class="uicontrol">UKAddress</span>). -The guided editing for the content model will reflect the type definition -that you choose. For example, if you select <span class="uicontrol">USAddress</span> , -your <samp class="codeph">billTo</samp> element can contain a <samp class="codeph">state</samp> element, -but it cannot contain a <samp class="codeph">postcode</samp> element.</p> -<p>The XML example -"Editing and validating XML files" demonstrates <strong>xsi:type</strong> support.</p> -<p>For -more information about xsi:type, refer to the <strong>Using Derived Types in Instance -Documents</strong> section in <a href="http://www.w3.org/TR/xmlschema-0/#UseDerivInInstDocs" target="_blank">XML Schema Part 0: Primer.</a></p> -<p>For more information -about validation semantics when xsi:type is used, refer to the <strong>Schema-Related -Markup in Documents Being Validated</strong> section in <a href="http://www.w3.org/TR/xmlschema-1/#xsi_type" target="_blank">XML Schema Part 1: Structures</a> </p> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file |