|XMLmind Ebook Compiler|
lib/resolver.jar) by the XMLResolver (
ebookc-N_N_N-plus-fop.zipnow contains Apache FOP 2.8 (including hyphenation and MathML support). This XSL-FO processor is automatically declared and thus, ready to be used to generate PDF or PostScript.
ebookc-N_N_N-plus-fop.zipnow contains Apache FOP 2.7 (including hyphenation and MathML support). This XSL-FO processor is automatically declared and thus, ready to be used to generate PDF or PostScript.
ebookc-N_N_N-plus-fop.zipnow contains Apache FOP 2.6 (including hyphenation and MathML support). This XSL-FO processor is automatically declared and thus, ready to be used to generate PDF or PostScript.
<pre class="role-listing-1-c-tab4">) contained in an admonition (e.g. <
blockquote class="role-important">), the line numbers are rendered completely outside the listing, at the left of the listing block.
Did not find a workaround for what seems to be a FOP bug. There is no such problem with other XSL-FO processors (e.g. RenderX XEP, XMLmind XSL-FO Converter). This problem is not a regression of FOP 2.6. It was already there with older versions of FOP.
ebookc-N_N_N-plus-fop.zipnow contains Apache FOP 2.5 (including hyphenation and MathML support). This XSL-FO processor is automatically declared and thus, ready to be used to generate PDF or PostScript.
ebookc-N_N_N-plus-fop.zipnow contains Apache FOP 2.4 (including hyphenation and MathML support). This XSL-FO processor is automatically declared and thus, ready to be used to generate PDF or PostScript.
headof a source HTML page were not copied to the output file.
Example, source HTML page
which is part of
manual.ebook, contains MathML equations
and thus requires the use of the MathJax support script:
ebookc -f html1 manual.ebook
out/manual.html did not create an
file making used of the MathJax support script. This prevented
out/manual.html to be correctly displayed in any Web
browser other than Firefox (which natively supports MathML).
bug which occurred when parsing a certain combination of
true". This very simple setting guarantees to effortlessly create a nicely formatted book. More information about this new attribute in Leveraging
base.css, the stock CSS stylesheet.
-p wh---navigation-background-color "#F6F8FA") may be used to override most fonts and colors used in the generated Web Help.
wh-ui-languagemay be used to specify the language used by the messages of the generated Web Help (tab labels, button tool tips, etc). The default is to use the language of the Web browser.
Upgraded XMLmind Web Help
Compiler (whc for short) to version 2.3.2 because the the
Web Help having the
classic layout generated using
whc v2.3.1 did not work in Google Chrome version
ebookc_install_dir/schema/ebook.xsdis now based on the HTML Living Standard (starting from the 2019-07-18 update). Previously it was based on the HTML 5.x W3C Recommendation.
window-1252on a Western PC). In previous version of ebookc, this default encoding was
UTF-8whatever the platform. If you want to explicitly specify the encoding of a Markdown file, please save your file with a
UTF-16BOM or add an encoding directive inside a comment anywhere at the beginning of your file. Example:
<!-- -*- coding: iso-8859-1 -*- --> Heading ======= ## Sub-heading Paragraphs are separated by a blank line.
The above example should work fine because ebookc now
understands the GNU Emacs file variable called
blockquoteelements (especially those having attribute
class="role-ADMONITION") are converted to RTF, WML, DOCX and ODT.
This enhancement makes use of XMLmind XSL-FO Converter v6 new extension
xfc:render-as-table. If you want to restore the
previous behavior, pass new XSLT stylesheet parameter
-p xfc-render-as-table ""
(its default value being "
load.markdown.more-extensionsis no longer needed nor supported.
If you want to revert to the minimal set of extensions
which was enabled by default in the previous version of XMLmind Ebook
Compiler, pass parameter
-p load.markdown.less-extensions true to
-rtf.target=MSWordis automatically passed to
fo2rtf. This option is needed to circumvent an obscure bug in the RTF loader of MS-Word, which does not handle table cell padding tags correctly.
Many “Markdown dialects” and many Markdown syntax extensions are supported, thanks to flexmark-java, the software component used to implement Markdown support in ebookc.
However for this to work, you must be using a Java 1.8+ runtime. More information in Markdown support.
<pre class="role-listing-XXX">, tab characters are now expanded by default to up to 8 space characters. “Tab stops” may be controlled using new
<pre class="role-listing-1-java-tab4">means expand tabs to up to 4 space characters in this line-numbered Java listing. Other example:
<pre class="role-listing-tab0-shell">means: do not replace tabs in this Bourne shell listing. More information in Program listings.
ebookc-N_N_N-plus-fop.zipnow contains Apache FOP 2.3 (including hyphenation and MathML support). This XSL-FO processor is automatically declared and thus, ready to be used to generate PDF or PostScript.
texture.png" in "
background-image: url(images/texture.png);" or file "
core_styles.css" in "
@import url(lib/core_styles.css);") are now automatically detected and processed by XMLmind Ebook Compiler.
<?pagebreak?>processing-instruction in the XHTML5 source between paragraphs, notes, tables, lists, etc, may be used to force a page break when generating any of the output formats which uses XSL-FO as an intermediate format (PDF, RTF, DOCX, etc)..
<revised modified="2018-04-27"/>was formatted as "2018 April 27" instead of expected "April 27, 2018".
"foo.html"pointing as follows:
<a href="bar.html#gee"/>to another HTML resource called
"bar.html"caused a file called
"bar.html#gee"(and not just
"bar.html") to be created in the resource subdirectory of the output directory.
window.sessionStoragerather than cookies to store the internal state of the Web Helps it generates.
nn(Norwegian Nynorsk) and
nb(Norwegian Bokmål), thanks to a contribution made by Leif Halvard Silli.
XML Editor v7.5 integration issue: the following warning
the"role-index-term" element has an "data-end-range" attribute:
ignoring any other content was reported for an end-range index term
just containing an empty text node.