XMLmind Assembly Processor, which passed all non-regression tests, is now officially supported on Java™ 11 platforms.
Minor internal changes needed to make XMLmind Assembly Processor compatible with XMLmind XML Editor v8.2.
XMLmind Assembly Processor, which passed all non-regression tests, is now officially supported on Java™ 10 platforms.
Minor internal changes needed to make XMLmind Assembly Processor compatible with XMLmind XML Editor v8.
XMLmind Assembly Processor, which passed all non-regression tests, is now officially supported on Java™ 9 platforms.
Changed "Licensor" from "Pixware SARL" to "XMLmind Software" in all licenses.
Info elements copied from the assembly to the realized document
were not given proper
In practice, due to this bug, it was not possible to successfully
convert to other formats an assembly where some
info elements contained
XMLmind Assembly Processor v1.0 is the first version to fully support
processing DocBook 5.1
assemblies. This includes XInclude 1.1, DocBook
Transclusion and assembly features such as
relationships is now processed.
linking attribute of element
instance is supported with the following values:
none, with the same semantics as the
linking attribute of
type of elements
relationship is still ignored.
revhistory child of the
structure element was ignored.
omittitles now discards
from the included resource. Previously, setting this attribute to
true discarded all the metadata just like
structure and in
merge are used in the same way. These elements may
be used to add or replace metadata in the realized
The implementation of
filterout is completely different from what it was
in previous versions. More information in Section 5.2.1, “About filtering”.
XMLmind Assembly Processor can now check the realized document for
cross-reference errors, missing image resources, etc. This is done by
-check option to the
Note that if your document requires conditional processing (that is, profiling), then this check step may report false errors. These false errors are caused by the fact that the conditional processing step has not been applied to the realized document prior to the check step.
-profile allows to specify a profiling
attribute. Therefore passing one or more
options to the assembly command-line allows to apply
a profile to the realized document prior to checking it.
Example: two of the chapters referenced by assembly
First chapter has also
os="windows". Second chapter
If you run
assembly -check book.xml -, you'll
get a duplicate ID warning caused by
On the other hand, if you run
assembly -check -profile os windows book.xml -,
you'll not have this duplicate ID error. Why that? Because by applying
os="windows", second chapter (having
os="mac") is excluded from the realized document
prior to checking it.
Transclusion Processor: removed
targetptr from the IDREF-list.
Now uses a built-in XInclude 1.1 processor rather than the XInclude 1.0 implementation provided by the XML parser (that is, Xerces). Note that for now, this built-in XInclude 1.1 processor only supports the XPointer element() scheme.
Now uses a built-in DocBook 5
Transclusion Processor to process
trans:linkscope attributes possibly set on
Bug fix: in some cases, a processing-instruction was moved (in the realized document) to the beginning of the element containing it and this, no matter its actual location within this parent element.
Minor internal changes.