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

=============================
V2.5 Patch 3 (March 10, 2004)

Enhancements:
-------------

   * User Request: the DocBook menu contains two
     new commands: Increase Section Level and
     Decrease Section Level.

     These commands require one or several section,
     sect1, sect2, sect3, sect4 or sect5 elements
     to be explicitly selected.

      Increase Section Level
             This command will increase the level
             of selected sections by giving them a
             new parent section.

      Decrease Section Level
             This command will decrease the level
             of selected sections by moving them
             out of their parent section.

     Of course, these two commands will do
     everything needed to keep the document valid.

     Note that these two new commands,
     incrSectionLevel and decrSectionLevel, are not
     strictly DocBook-specific. They can be used
     for other document types, provided that:

        + these commands are properly parametrized
         (see Power User's Guide) ;

        + the content model of the sections in the
         non-DocBook document type is similar to
         the content model of the DocBook
         sections.

     For example, it is possible to use these
     commands with APT documents (see
     http://www.xmlmind.com/aptconvert.html).

   * User Request: new command toggleCollapsed can
     be used to collapse/expand collapsible views,
     both in the tree view and in the styled view.

     This generic, flexible, command can be used to
     define custom keyboard shortcuts, custom
     toolbar buttons and custom menus.

     Example: after opening a large DocBook
     document, the user often just wants to see the
     outline of the document.

---
<binding>
  <keyPressed code="ESCAPE" />
  <charTyped char="0" />
  <command name="toggleCollapsed"
    parameter="collapseAll+expand" />
</binding>
---

     After adding the above binding to
     XXE_user_preferences_dir/config/customize.xxe,
     the user, by typing Escape then typing 0, will
     recursively collapse the whole document and
     then expand one level of sections.

     Many useful keyboard bindings, including the
     above one are found in
     XXE_install_dir/docs/poweruser/samples2/customize.xxe.
     More generally, customizing XXE is
     described in the Power User's Guide.

   * In the Options dialog box, Schema tab, the DTD
     catalogs frame which was used to specify XML
     catalogs other that the bundled
     XXE_install_dir/config/catalog.xml has been
     suppressed.

     The XXE_CATALOGS environment variable and the
     xml.catalog.files system property which were
     used to specify XML catalogs are now ignored.

     Now XML catalogs are dynamically discovered at
     XXE startup like all other configuration
     files.

     XML catalogs are expected to be files with
     names ending with "atalog.xml". Like other
     configuration files, these files are first
     recursively searched in
     XXE_user_preferences_dir/config/ and then in
     XXE_install_dir/config/. (See Power User's
     Guide for a thorough description of how XML
     catalogs are dynamically discovered.)

     The goal is to allow to deploy an XXE
     configuration based on a custom DTD by
     simpling telling the user to unzip the
     configuration distribution in his/her
     XXE_user_preferences_dir/config/.

     An XXE configuration based on a custom DTD
     almost always requires a custom XML catalog.

     Previously this meant that the user not only
     had to unzip the configuration distribution in
     his XXE_user_preferences_dir/config/, but also
     to manually add the custom catalog to the list
     of all XML catalogs using the Options dialog
     box.

   * Spell-checker dictionaries, that is .dar
     files, are now searched, not only in
     XXE_install_dir/spell/, but also in
     XXE_user_preferences_dir/spell/.

   * Deployment of XXE using Java[tm] Web Start now
     allows the user to work offline.

     Previously, configuration files and associated
     resources (DTD/XML-Schema, CSS, XSLT, icons,
     etc) were kept on the deployment server and
     therefore, were not cached on the PC of the
     XXE user.

     Now everything needed to run XXE
     (configuration files, core code, plug-ins,
     dictionaries, etc) is by default downloaded
     and cached on the PC of the XXE user.

     Note that the previous behaviour -- keeping
     configuration files on the deployment server
     -- is still supported but requires the
     deploywebstart command line tool to be run
     with option -online.

   * Linux only: even when deployed using Java[tm]
     Web Start, ugly Metal look is automatically
     replaced by cool Kunststoff look
     (http://www.incors.org/).

   * User Request: XXE now really supports multiple
     node selection in the
     <copyDocument selection="true"> process
     command child element. See Power User's Guide.

   * The <transform> process command child element
     has a new attribute cacheStylesheet which
     allows to cache a precompiled form of the XSLT
     style sheet used to transform a copy of the
     document. See Power User's Guide.

     Caching XSLT style sheets is useful to speed
     up the execution of highly interactive process
     commands.

   * User Request: changed the order of traversal
     of fields and buttons in the Attribute tool.
     Ctrl-E gives the focus to the Attribute name
     field. Pressing the tab key gives the focus to
     the attribute Value field and then to the
     List, Browse, Remove, Add/Change and Cancel
     buttons.

   * Upgraded XMLmind Spell-Checker to version
     1.1p4.

   * Upgraded Enterprise Distributed Technologies's
     Java FTP client library to version 1.2.3
     ([3]http://www.enterprisedt.com/).

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

   * External entities defined in the external DTD
     subset or in external parameter entities and
     then referenced in the body of the document
     were not always properly managed by XXE.

     Note that XXE considers that external entities
     defined in the external DTD subset or in
     external parameter entities are logically part
     of the DTD. That is, it does not consider this
     kind of external entities as being resources
     which are logically part of the document. For
     example, during a Save As operation, XXE will
     not attempt to copy this kind of external
     entities along with the document to the new
     location.

   * In CSS style sheets, the identifier used as
     the argument of pseudo-funtion attr() is now
     case sensitive. This is allowed by the W3C
     recommendation because the ``document
     language'' is XML (case sensitive elements and
     attributes) and not HTML (case insensitive
     elements and attributes).

   * Fixed the following bug: simply moving the
     keyboard focus to date-field or number-field
     controls embedded in the document view was
     sufficient to mark the document as being
     modified.

   * XML Schema: the validation engine implemented
     the original "Schema Component Constraint:
     Type Derivation OK (Simple)" specification,
     not the one fixed in "XML Schema 1.0
     Specification Errata". This caused valid
     substitution groups where the type of the head
     was xs:anyType to be rejected by the engine.

   * XML Schema: a substitution group containing
     just a single non-abstract member was ignored.

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

   * In CSS style sheets, the identifier used as
     the argument of pseudo-funtion attr() is now
     case sensitive.

   * The XXE_CATALOGS environment variable and the
     xml.catalog.files system property which were
     used to specify XML catalogs are now ignored.
     These variables have been replaced by another
     environment variable called XXE_CATALOG. See
     Power User's Guide for a thorough description
     of how XML catalogs are dynamically discovered
     by XXE.

   * Option -online must be used to tell
     deploywebstart to keep configuration files and
     associated resources (DTD/XML-Schem, CSS,
     XSLT, icons, etc) on the deployment server.
     Now the default behaviour of deploywebstart is
     to allow the user to work offline.




Reply via email to