v0.4.0

This release is phased out due to a critical bug (fixed in 0.4.1)

In this minor release (#8), the re-implementation of some classes, packages, etc. provided by sile·x no longer takes over that of SILE.
Users have to enforce the use of these replacements explicitly:

• require("silex") to enforce all of sile·x
• require("silex.override") to only enforce the replacements

The resilient.sile module already does the first when the resilient classes are used, so the latter get all of the sile·x features enabled. There's no change for users there.

Other classes and modules are nevertheless no longer affected without the user explicit will and intent, so there is now far less risks of breaking anyone's workflow when installing sile·x and using other modules. They get back the behavior they were used to with "bare" SILE, and can decide whether to opt-in for sile·x or not in their workflow.

Additionally, the re-implemented sile·x typesetter is re-aligned on SILE 0.14.15, meaning it benefits from its new features:

• Soft hyphen support
• Speaker change support in dialogues

Obviously, all its "special" experimental or advanced features are still there.

As a reminder, running SILE with -d silex enables debugging, so one can check what sile·x does.