Skip to main content

This CGIT instance is deprecated, and repositories have been moved to Gitlab or Github. See the repository descriptions for specific locations.

summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita')
-rw-r--r--docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita64
1 files changed, 0 insertions, 64 deletions
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 c3d43ce9f0..0000000000
--- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita
+++ /dev/null
@@ -1,64 +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="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 or 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 <menucascade><uicontrol>XML</uicontrol><uicontrol>Turn
-Grammar Constraints Off</uicontrol></menucascade> in the toolbar. 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 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>&lt;!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><?Pub Caret?><p>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.</p><p>These
-instructions were written for the Resource perspective, but they will also
-work in many other perspectives.</p></result>
-</taskbody>
-</task>
-<?Pub *0000003814?>

Back to the top