home *** CD-ROM | disk | FTP | other *** search
- --------------------------------------------------------
- README for Microsoft XML Notepad Beta 1
- July 21st, 1998
- --------------------------------------------------------
- (c) Copyright Microsoft Corporation, 1998
- All rights reserved.
-
- This document provides complementary or late-breaking information to
- supplement the documentation. You can also visit the Microsoft(R) Web site
- for the latest information on XML Notepad at http://microsoft.com/xml.
-
- ========
- CONTENTS
- ========
-
- 1. Installation Requirements:
- 1.1 Internet Explorer 4.01 SP1 or later is required
-
- 2. IE 4/5 DOM Issues
- 2.1 Element/Attribute Tag Name Case issues
- 2.2 Well Formed XML source issues.
- 2.3 Tag name short representation.
- 2.4 Validation issues.
-
-
- 3. Known Bugs:
- 3.1 Uninstall doesn't remove icons from the Start Menu.
- 3.2 Namespaces are stripped out on loading.
- 3.3 Invalid XML Namespace declaration can result in GPF
-
- =============================
- 1. Installation Requirements
- =============================
- 1.1 Internet Explorer 4.01 SP1 or later is required
- Internet Explorer 4.01 with SP1 or later is necessary to run XML
- Notepad. If you have IE5 installed, you will be able to take advantage
- of features offered in both IE4 as well as IE5. See section 2 for more
- information on DOM related issues. NOTE: you do not need to have
- IE4/IE5 set as your default browser for XML Notepad to run.
-
- =============================
- 2. IE 4/5 DOM Issues
- =============================
- Note: if you have IE5 installed, you can force XML Notepad to revert to the
- IE4 DOM by deselecting the "Use IE 5DOM on existing XML Documents" option
- from the Tools->Option menu.
-
- 2.1 Element/Attribute Tag Name Case issues:
- If you are using XML Notepad on a system that has Microsoft Internet
- Explorer 4.01 w/SP1 installed, all Element and Attribute tag names will
- be converted to uppercase on loading a file. On saving a file, all tag
- names are saved as displayed.
-
- If you are using XML Notepad on a system that has Microsoft Internet
- Explorer 5 installed, case sensitivity is maintained on loading and
- saving a file.
-
- 2.2 Well Formed XML source:
- Under both the IE4 and IE5 DOMs, a file has to be well formed if it is
- to be saved. The most common cause of a file not being well formed is a
- missing element or attribute name, or invalid characters in the tag
- name. XML Notepad will point you to the source of non-conformance when
- you attempt to save a document.
-
- 2.3 Shortcut Tag Names:
- If you are running XML Notepad under the IE4 DOM, you can open files
- that are neither well formed nor valid. The IE4 DOM lets you end XML
- tags with </> rather than </elementname>. Files with shortcuts are
- converted into well formed XML on loading under the IE4 DOM. Opening
- and Saving a file that uses shortcut Tag names, will result in a well
- formed XML file.
-
- Tag name shortcuts are not allowed in the XML 1.0 standard. Under the
- IE5 DOM, files with shortcuts cannot be opened.
-
- 2.4 Validation issues:
- Under the IE4 DOM: DTD validation is unavailable.
-
- Under the IE5 DOM:
- * DTD (Document Type Definition) validation occurs on loading a file.
- Since validation only occurs on loading a file (and not on save) it
- is possible to open a valid XML file, make non-DTD-conforming
- changes and then get an error on opening the file.
-
- * If the XML source does not conform to the DTD, a dialogue pointing
- to the source of non-conformance will appear.
-
- * If the DTD is invalid, an error dialogue will appear pointing to the
- source of non-conformance.
-
- =============================
- 3. Known Bugs:
- =============================
- 3.1 Uninstall doesn't remove icons from the Start Menu.
-
- 3.2 Namespaces are stripped out from Element Tags on loading.
- If you are using Namespace declarations in your XML file, under the IE5
- DOM, the namespace prefix for each tag is stripped out on loading; this
- can cause problems if you are using namespaces in your script. Under
- the IE4 DOM, namespaces are preserved (though validation does not
- occur.)
-
- 3.3 Invalid XML Namespace declaration can result in GPF
- If your XML Namespaces declaration is invalid e.g. using two valid
- namespace declarations that overlap the same tag e.g.
- "<old:title>Sir<new:title>" will result in a General Protection Fault.
-
-
-
-