XMLmind XML Editor V2.8 Patch 1 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml
================================
V2.8 Patch 1 (November 29, 2004)
Enhancements: (see technical details below)
-------------------------------------------
* DocBook 4.3 is now the version of the DocBook
DTD which is used by default.
HTML tables as well as CALS tables (i.e.
traditional DocBook tables) are fully
supported. The only limitation is that mixing
both HTML and CALS content models in the same
table or informaltable is absolutely not
supported by table rendering code and by table
editing commands, even if this is allowed
according to the DTD V4.3.
Example 1: an informaltable contains tr child
elements. In such case, the informaltable is
an HTML table. Setting attribute frame to
topbot on this informaltable will have
absolutely no visual effect.
Example 2: a table has a child tgroup element
which itself contains a tbody with row/entry
descendants. In such case, the table is a CALS
table. Adding a thead having tr/td descendants
before the tbody of the tgroup would lead to
catastrophic results. Fortunately, the updated
DocBook configuration makes it hard to do this
unintentionally.
* The behavior of macro-commands has been
improved.
Example 1: The DocBook toolbar has a menu with
an item allowing to convert selected text to
emphasis with role="bold". After using this
menu item, it was necessary to use command
undo (i.e. Ctrl-Z) twice in order to undo the
conversion (once to remove attribute role and
another time to undo conversion to emphasis).
Now using Ctrl-Z once is sufficient.
Example 2: After using the menu item of
example 1, repeating the command (i.e. Ctrl-A)
on another selected text just converted this
text to emphasis and did not add attribute
role="bold". This made Ctrl-A unusable for
such commands. This is fixed now: Ctrl-A now
repeats all the steps of such commands.
* User Request: the URL chooser dialog box
displayed by Convert menu items now suggests a
save file name/file URL with the proper
extension.
For example, if you convert a Slides document
called xslt_course.xml to PDF, the dialog box
now suggests to output file xslt_course.pdf in
the directory containing xslt_course.xml. And
if you convert this document to
WordprocessingML, it will suggest
xslt_course.word.xml.
* The popup menu of the node path bar has a new
"Copy XPath" item.
* Upgraded Norman Walsh's DocBook XSL style
sheets to version 1.67.0.
* A plug-in is now available for XEP 4+. XEP
3.7-3.8 users need to download and install a
plug-in (xep37_foprocessor) which is different
from the plug-in for XEP 4+ (xep_foprocessor).
* Updated Czech localization thanks to Martin
Kolar?k (kolarik AT mii DOT cz).
* Added a demo for the integrated spreadsheet
engine:
XXE_install_dir/demo/spreadsheet-demo.xhtml.
Technical details about the enhancements (for
local gurus):
----------------------------------------------
* Macro-commands can now be marked as being
repeatable and/or undoable.
* The usability of command selectFile has been
improved.
A variant of this command called
selectConvertedFile, which is aware of the
document being converted, has been created in
order to be used in Convert macros such as
docb.convertToHTML1, slides.convertToPS, etc.
* Command pick can now read its arguments from a
file.
* Added XPath extension functions: join,
replace, matches.
* Generated content object label() now supports
an xpath argument. Previous, label() only
supported an attribute argument. XHTML
example:
+--------------------------------------------------------+
a.showtarget {
content: icon(pop-right)
label(xpath,
"//a...@name = substring-after(current()/@href, '#')]",
text-decoration, underline);
}
+--------------------------------------------------------+
* New generated content object indicator() is
similar to label() except that it is rendered
using a set of images rather than text. XHTML
examples (one with an attribute argument, the
other with an xpath argument):
+--------------------------------------------------------+
p.msg:before {
content: indicator(attribute, title,
state, info, icon, url(info.gif),
state, warning, icon, url(warning.gif),
state, error, icon, url(error.gif));
display: marker;
}
div.hotel span.with_stars:after {
content: " "
indicator(xpath,
"substring-after(ancestor::d...@class='hotel']/@title,\
'stars')",
state, "not_rated", icon, icon(diamond),
color, gray,
state, "0", icon, url(0star.gif),
state, "1", icon, url(1star.gif),
state, "2", icon, url(2star.gif),
state, "3", icon, url(3star.gif),
state, "4", icon, url(4star.gif),
state, "5", icon, url(5star.gif));
display: inline;
}
+--------------------------------------------------------+
* CSS pseudo-class
:contains-element(element_name) (a proprietary
extension) can be used to style elements
containing specific a child element.
Bug fixes:
----------
* Printing with XXE now gives decent results
with Java[tm] 1.5+. Previously, horizontal text
layout was incorrect when printing lines
mixing several fonts.
Note that unless you use Java[tm] 1.5+ (Java[tm]
1.4.2_05+ on Mac), printing with XXE may be
even worse than before.
* Fixed a bug that prevented publishing
documents on a WebDAV server using a port
other than 80 (the standard HTTP port).
* Publishing documents on a WebDAV server now
uses simple PUTs. The method previously used
-- PUT temporary file and then, if first step
was successful, MOVE temporary file to target
file -- prevented version control systems such
as subversion from doing their job.
* Made it easy to publish documents on a WebDAV
server using HTTPS.
Previously, the only way to make this work was
to manually add the server certificate to a
keystore using standard Java[tm] tool keytool,
and then to pass the location of this keystore
to XXE using the javax.net.ssl.trustStore
system property.
Now, all this is done automatically by XXE the
first time the HTTPS server is used. Of
course, the user is asked if he/she accepts
the server certificate.
* Configuration elements like
<load location="xxe-config:xhtml/xhtml.jar"/>
reported a false error.
* XML catalogs are no longer used to resolve the
locations found in the href attribute of
xi:include. This is a functional regression
but at least now the behavior of XXE is
consistent. Previously, it was possible to use
XML catalogs to resolve XIncludes but, in such
case, Edit|Document Reference|Edit Referenced
Document (among other things) did not work.
Regressions:
------------
* Previously, it was possible to click in the
gray margin found at the left and at the right
of the document view in order to directly
select the block (paragraph, row, row group,
table) which is ``in front of the mouse
click''.
This feature, though making XXE slightly
easier to use, has been removed because it was
found to make the author less productive.
Because this way of selecting blocks is so
easy to use, it tends to ``cannibalize'' the
other ways of selecting nodes, especially the
implicit element selection.
If you are a mouse-oriented user, try
Ctrl-clicking (Command-clicking on the Mac)
several times on a node without moving the
mouse. More info in the tutorial.
Possible incompatibilities:
---------------------------
* XML catalogs are no longer used to resolve the
locations found in the href attribute of
xi:include.
* The encoding attribute of the read element of
a process command is now required. Use special
value "default" to specify the native encoding
of the platform, for example Windows-1252 on
an US Windows? machine.
* XMLmind XML Editor is installed on Windows?
using new installer and new launcher
technologies.
Installer technology is provided by
Inno Setup (http://www.jrsoftware.org/isinfo.php),
an excellent and free-to-use tool.
It should work on any Windows? version, including
on Windows? 9x.
The new launcher, xxe.exe and its parameter
file xxe.jstart, is the work of XMLmind. It
has been successfully tested on Windows? NT,
2000 and XP. It does not work on Windows? 9x.
