XMLmind XML Editor V2.6 Patch 1 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml

===========================
V2.6 Patch 1 (June 18, 2004)

Enhancements: (see technical details below)
-------------------------------------------

   * The caret is now displayed as a little red
     triangle when the text node containing its is
     not rendered on screen (its ancestor is
     collapsed or the text node has no view at
     all). The basic idea here is not never ``loose
     the caret''.

     This enhancement is also specially useful for
     authors who prefer to use the styled view and
     the tree view side by side. With this
     enhancement, it is now possible to hide the
     details of the text nodes in the tree view
     (Options|Show Text Characters in the Tree
     View) and still know where is the caret.

   * User Request: it is now possible to remove an
     attribute directly from the attribute table
     (i.e. the upper side of the Attribute tool) :
     simply right-click on the attribute row and
     use the displayed popup menu.

     Previously the only way to remove an attribute
     was to use the ``minus'' button of the
     attribute form (i.e. the lower side of the
     Attribute tool).

   * The Attribute tool has now special support for
     hexBinary and base64Binary types.

   * The special file chooser dialog box displayed
     to let the user browse FTP or WebDAV
     directories can now also be used to delete
     files and directories on FTP and WebDAV
     servers.

     In order to do that, right-click on the name
     of the file or directory to be deleted and use
     the Delete item of the displayed popup menu.

   * Improved the usability of File|Save Copy.

   * The node path bar now displays
     processing-instructions as
     "#processing-instruction(target)".

   * Improved the XXE configuration used to edit
     W3C XML Schemas. It is now possible to
     document W3C XML Schemas in XHTML.

     For example, the tool bar created by this XXE
     configuration has a ``book icon'' which
     inserts a xs:annotation/xs:documentation
     containing a html:body inside explicitly
     selected schema component.

     Demo file
     XXE_install_dir/demo/bugreport/bugreport.xsd
     can be opened in XXE to give this new feature
     a try.

Bug fixes:
----------

   * Use of non-managed entities such as
     <!ENTITY foo "<b>Foo</b>">, that is an
     internal entity containing a single element,
     caused XXE to throw a
     ArrayIndexOutOfBoundsException. This exception
     prevented XXE from opening files that XXE V2.5
     was able to open.

   * Fully qualified names used in XPath
     expressions of macro-commands were not
     properly parsed, when these macro-commands
     were defined in files included from a ``main''
     XXE configuration file.

     Example:
--------------------------------------------------------
<sequence>
   <match context="$selected" pattern="html:li" />
   <command name="insertNode" parameter="sameElementAfter"/>
</sequence>
--------------------------------------------------------
     is used in a macro-command defined in file
     macros.incl, included by xhtml.xxe.

     In such case, "html:li" is parsed as
     "{}html:li" and not as
     "{http://www.w3.org/1999/xhtml}li";. Such macro
     cannot work because li elements are never
     matched.

     This bug did not occur when such
     macro-commands were directly defined in a
     ``main'' XXE configuration file.

   * It was not possible to insert a newline
     character in DocBook programlisting or
     literallayout when these elements had a para
     as their parent element. (Instead these
     elements were split in two parts.)

   * Mac: ``right-clicking'' with a single-button
     mouse (that is, Ctrl-Click) on an image didn't
     display the resource dialog box allowing to
     choose an image.

   * XML schema: an element with a content model
     having an attribute wildcard could get
     attribute default values from this wildcard.

   * XML Schema: ``placeholder groups'' such as:
--------------------------------------------------------
<xs:group name="Misc.extra">
   <xs:choice/>
</xs:group>
--------------------------------------------------------
     caused our W3C XML Schema validation engine to
     throw a NullPointerException.

   * XML Schema: identity constraints found in
     element declarations themselves contained in
     groups, like for example,

--------------------------------------------------------
<xs:group name="general">
    <xs:sequence>
       <xs:element name="general" type="general">
         <xs:unique name="generalUnique">
            <xs:selector xpath="*"/>
            <xs:field xpath="@uniqueElementName"/>
         </xs:unique>
       </xs:element>
    </xs:sequence>
</xs:group>
--------------------------------------------------------
     caused the W3C XML Schema validation engine to
     report false errors (the error message was: an
     identity-constraint with the same name "XXX"
     has already been defined).

Technical details about the enhancements (for
local gurus):
---------------------------------------------

   * User request: it is now possible to use XML
     catalogs to resolve URLs found in the
     following places:

        + Schema locations in xsi:schemaLocation
         and in xsi:noNamespaceSchemaLocation.
        + Schema locations in xs:include,
         xs:redefine, xs:import.
        + Document locations in xi:include.
        + Document locations passed to the
         document() XPath function.
        + CSS style sheet locations in @import.
        + XXE configuration files in
         <include location="XXX"/>.
        + XSLT style sheets in the transform child
         element of a process command.
        + Resources in the copyProcessResource
         child element of a process command.
        + XSLT style sheets included or imported by
         other XSLT style sheets (that is, the XML
         catalogs used by XXE are passed to
         Saxon, the XSLT engine bundled with
         XXE).

     Previously XML catalogs were only used to
     resolve the locations of the DTD and other
     external entities.

   * The following rule has been added to the XML
     catalog bundled with XXE,
     XXE_install_dir/config/catalog.xml:
--------------------------------------------------------
<rewriteURI uriStartString="xxe-config:"
             rewritePrefix="."/>
--------------------------------------------------------
     This means that any URI which starts with
     xxe-config: is understood as being relative to
     XXE_install_dir/config/.

     For example, this feature can be used to
     customize the DocBook CSS style sheet bundled
     with XXE:
--------------------------------------------------------
@import url(xxe-config:docbook/css/docbook.css);
    .
    .
my customization here
    .
--------------------------------------------------------

   * Changed details in the CSS implementation to
     follow W3C document Errata in
     REC-CSS2-19980512.

        + The underscore character '_' is now
         allowed in identifiers. It is no longer
         needed to quote this character like in
         "element\_name".

   * It is now possible to interleave @namespace
     and @import at the beginning of a CSS style
     sheet.

   * User Request: added attribute showProgress to
     process commands. Setting this attribute to
     value false suppresses the dialog box normally
     displayed during the execution of a process
     command to show the user what is happening.

   * Upgraded XMLmind FO Converter, used to
     convert XSL-FO to RTF, to version 1.3.

   * Upgraded Enterprise Distributed
     Technologies FTP client library to version
     1.3.2.

   * Upgraded the XML catalog resolver used by XXE
     to Apache XML Commons Resolver version 1.1.

   * XML Schema: the W3C XML Schema validation
     engine now supports xs:import elements without
     a schemaLocation attribute, if an xs:import
     element for the same namespace but this time
     having a schemaLocation attribute has
     previously been processed.

     Example:
--------------------------------------------------------
<xs:import namespace="foo"
          schemaLocation="http://foo.com/schema1.xsd"; />

<!-- Later, typically inside an included module. -->
<xs:import namespace="foo" />
--------------------------------------------------------

     Note that the other example below will not
     work because the W3C XML Schema validation
     engine cannot guess which of schema1.xsd or
     schema2.xsd needs to be imported.
--------------------------------------------------------
<xs:import namespace="foo"
          schemaLocation="http://foo.com/schema1.xsd"; />

<!-- Later, typically inside an included module. -->
<xs:import namespace="foo"
          schemaLocation="http://foo.com/schema2.xsd"; />

<!-- Later, typically inside another included module. -->
<xs:import namespace="foo" />
--------------------------------------------------------

   * XML Schema: upgraded the Schema for Schemas to
     the version included in "XML Schema Part 1:
     Structures Second Edition - W3C Proposed
     Edited Recommendation 18 March 2004".

     This version of the Schema for Schemas allows
     to add attributes with non-schema namespaces
     to annotate most schema components.

     Slightly edited this normative schema to allow
     spaces before and after path alternatives in
     the xpath attributes of elements selector and
     field. Example:
--------------------------------------------------------
<xs:key name="truck1" >
   <xs:selector xpath="truck" />
   <xs:field xpath="@number | @plate" />
</xs:key>
--------------------------------------------------------

   * Standard Edition now supports
     "http://www.w3.org/1999/xhtml"; as the target
     namespace of W3C XML Schemas, in addition to
     "http://www.w3.org/2001/XMLSchema";,
     "http://www.w3.org/XML/1998/namespace"; and any
     namespace with an URI starting with
     "http://www.xmlmind.com/xmleditor/schema/";.

   * The modular W3C XML Schema for XHTML included
     in "Modularization of XHTML(TM) 1.0 -
     Second Edition - W3C Working Draft 18 February
     2004" is now available in
     XXE_install_dir/config/common/xsd/xhtml11/.

     This schema is used to document W3C XML
     Schemas in XHTML and also for the bugreport
     demo.

Possible incompatibilities:
---------------------------

   * Use of XXE configuration element
     <cfg:include location="XXX" system="true"/> is
     deprecated.

     Example:
--------------------------------------------------------
<cfg:include location="docbook/docbook.xxe"
              system="true"/>
--------------------------------------------------------

     must be replaced by:
--------------------------------------------------------
<cfg:include location="xxe-config:docbook/docbook.xxe"/>
--------------------------------------------------------



Reply via email to