[tex4ht-commits] [SCM] tex4ht updated: r688 - in trunk/doc: . tex4ht-doc tex4ht-doc/section [more]

michal_h21 at gnu.org.ua michal_h21 at gnu.org.ua
Tue May 5 21:54:36 CEST 2020

Author: michal_h21
Date: 2020-05-05 22:54:36 +0300 (Tue, 05 May 2020)
New Revision: 688

Added missing closing paren in HTML listing

Modified: trunk/doc/tex4ht-configure1.tex
--- trunk/doc/tex4ht-configure1.tex	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-configure1.tex	2020-05-05 19:54:36 UTC (rev 688)
@@ -47,7 +47,7 @@
    {\EndP\IgnorePar\Tg<section id="sec\thesection">}
-   {\EndP\Tg</section}
+   {\EndP\Tg</section>}

Modified: trunk/doc/tex4ht-doc/Makefile
--- trunk/doc/tex4ht-doc/Makefile	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/Makefile	2020-05-05 19:54:36 UTC (rev 688)
@@ -1,6 +1,10 @@
-mode = final
+mode = draft
 engine = 
+outputdir = out
+IMAGESUBDIRS := $(wildcard images/*/.)
 ifeq (lualatex, lualatex)
 	engine = -l
@@ -9,21 +13,27 @@
 	engine = -x
-sections = sections/tex4ht-commands.tex
+# sections = sections/tex4ht-commands.tex sections/tex4ht-options.tex sections/webfonts.tex sections/configuration-files.tex sections/tex4ht-development.tex sections/calling-commands.tex sections/graphics.tex
+sections = $(wildcard sections/*.tex)
+filters = $(wildcard filters/*.lua)
-all: tex4ht-doc.pdf tex4ht-doc.html
+all: $(IMAGESUBDIRS) tex4ht-doc.pdf tex4ht-doc.html 
-.PHONY: final
+	$(MAKE) -C $@
+.PHONY: final all $(IMAGESUBDIRS)
 tex4ht-doc.pdf: tex4ht-doc.tex tex4ht-styles.sty ${sections}
-	lualatex tex4ht-doc.tex
+	lualatex -shell-escape tex4ht-doc.tex
-tex4ht-doc.html: tex4ht-doc.tex config.cfg tex4ht-styles.sty ${sections}
-	make4ht -um $(mode) -c config $(engine) -f html5+common_domfilters -e build.mk4  tex4ht-doc.tex
+tex4ht-doc.html: tex4ht-doc.tex config.cfg tex4ht-styles.sty build.mk4 ${sections} ${filters}
+	make4ht -usm $(mode) -c config $(engine) -d $(outputdir) -f html5+common_domfilters -e build.mk4  tex4ht-doc.tex
 # use only one LaTeX run by default, request three compilations with final rule
-final: mode=final
-final: tex4ht-doc.html
+final: tex4ht-doc.html 
+	make4ht -usm final -c config $(engine) -d $(outputdir) -f html5+common_domfilters -e build.mk4  tex4ht-doc.tex
 	rm *.html *.aux *.4tc *.4ct *.xref 

Modified: trunk/doc/tex4ht-doc/README
--- trunk/doc/tex4ht-doc/README	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/README	2020-05-05 19:54:36 UTC (rev 688)
@@ -2,5 +2,7 @@
 Clone this repository and run `make` command to get the documentation in PDF and HTMl formats.
-At least `make4ht` version 0.2 is necessary to compile the HTML version.
+## Requirements
+Full TeX distribution, GNU Make and [Pygments](http://pygments.org/).

Modified: trunk/doc/tex4ht-doc/build.mk4
--- trunk/doc/tex4ht-doc/build.mk4	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/build.mk4	2020-05-05 19:54:36 UTC (rev 688)
@@ -1,81 +1,21 @@
-local domobject = require "luaxml-domobject"
+-- local domobject = require "luaxml-domobject"
 local filter = require "make4ht-filter"
+local domfilter = require "make4ht-domfilter"
--- return toc element type and it's id
-local function get_id(el)
-  local name =  el:get_attribute "class"
-  local a = el:query_selector "a" or {}
-  local first = a[1]
-  local href = first:get_attribute "href"
-  local id = href:match("#(.+)$")
-  return name, id
+-- this probably isn't necessary anymore, as we replaced listings with minted
+local fix_code_blocks = require "filters.fix_code_blocks"
+-- Keep only top section levels from other than current chapter
+local toc_sections = require "filters.collapse_toc"
+-- clean CSS file from duplicate colors
+local join_colors = require "filters.join_colors"
-local function remove_sections(part_elements, currentpart)
-  -- we need to remove toc entries from the previous part if the 
-  -- current document isn't part of it
-  if currentpart == false then
-    for _, part in ipairs(part_elements) do
-      part:remove_node()
-    end
-  end
+filter_settings "collapsetoc" {
+  toc_query = "nav.TOC"
+-- local process = domfilter{toc_sections, fix_code_blocks, join_colors}
+local process = domfilter{"collapsetoc", fix_code_blocks, join_colors}
-local process = filter{ function(s)
-  local dom = domobject.parse(s)
-  -- search sectioning elements
-  local titles = dom:query_selector(".partHead a, .chapterHead a, .sectionHead a")
-  local section_ids = {}
-  for _, x in ipairs(titles) do
-    -- get their id attributes and save them in a table
-    section_ids[#section_ids+1] = x:get_attribute("id")
-  end
-  -- we need to retrieve the first table of contents
-  local toctables = dom:query_selector(".tableofcontents") or {}
-  -- process only when we got a TOC
-  if #toctables > 0 then
-    local tableofcontents = toctables[1]
-    -- all toc entries are in span elements
-    local toc = tableofcontents:query_selector("span")
-    local currentpart = false
-    local part_elements = {}
-    for _, el in ipairs(toc) do
-      -- get sectioning level and id of the current TOC entry
-      local name, id = get_id(el)
-      -- change span to div
-      el._name = "div"
-      if name == "partToc" then
-        remove_sections(part_elements,currentpart)
-        -- resert toc list
-        currentpart = false
-        part_elements = {}
-      else
-        -- add child elements of part to table
-        part_elements[#part_elements+1] = el
-      end
-      for _, sectid in ipairs(section_ids) do
-        -- detect if the current TOC entry match some sectioning element in the current document
-        if id == sectid then
-          currentpart = true
-          print("match", id)
-        end
-      end
-    end
-    -- remove sections from the last part
-    remove_sections(part_elements,currentpart)
-    -- remove unneeded br elements
-    local br = tableofcontents:query_selector("br")
-    for _, el in ipairs(br) do el:remove_node() end
-    -- remove unneded whitespace
-    for _, el in ipairs(tableofcontents:get_children()) do
-      if el:is_text() then el:remove_node() end
-    end
-  end
-  return dom:serialize()
-end }
 -- it removed the whole TOC. What is the issue?
--- Make:match("html$", process)
+Make:match("html$", process)

Modified: trunk/doc/tex4ht-doc/config.cfg
--- trunk/doc/tex4ht-doc/config.cfg	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/config.cfg	2020-05-05 19:54:36 UTC (rev 688)
@@ -1,10 +1,57 @@
-\special{t4ht+ at File: style.css}
-\Configure{@HEAD}{\HCode{<link rel="stylesheet" type="text/css" href="style.css" />}}
+% Logical elements
+\SetBlockProperty{codesample}{role}{doc-example}% set dPub property
+% external stylesheet
+% Declare graphics extensions
+% Mini TOC
+  \bgroup
+  % container for the page toc
+  \Configure{tableofcontents}{\IgnorePar\EndP\HCode{<nav class="TOC">}\IgnorePar}
+  {\HCode{\Hnewline}}{\IgnorePar\HCode{</nav>\Hnewline}\ShowPar}{}{}%
+  \TableOfContents[chapter,section,subsection]% Print table of contents before crosslinks
+  \egroup
+  \ifvmode\IgnorePar\fi\EndP%
+  \HCode{<main class="main-content">\Hnewline<nav class="crosslinks-top">} }
+  {\HCode{</nav>\Hnewline}}
+  \HCode{<nav class="crosslinks-bottom">}}{\HCode{</nav>}}{}{}
+% configuration for TOC on the main page
+\Configure{tableofcontents}{\IgnorePar\EndP\HCode{<nav class="TOC">}\IgnorePar}
+{}{\IgnorePar\HCode{</nav>\Hnewline<main class="main-content">\Hnewline}\ShowPar}{}{}%
+% close the <main> element started in \Configure{crosslinks+}
+% show only crosslinks to prev, main and next pages
-\ConfigureEnv{texsource}{\ifvmode\IgnorePar\fi\EndP\HCode{<figure class="texsource">}}{\ifvmode\IgnorePar\fi\EndP\HCode{</figure>}}{}{}

Modified: trunk/doc/tex4ht-doc/sections/tex4ht-commands.tex
--- trunk/doc/tex4ht-doc/sections/tex4ht-commands.tex	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/sections/tex4ht-commands.tex	2020-05-05 19:54:36 UTC (rev 688)
@@ -1,3 +1,39 @@
+\subsection{Low-level \texfourht\ Commands}
+This command allows only for the expansion of macros, before sending its content to the output. The instruction \texcommand{\Hnewline} may be introduced there for requesting line breaks, and the command \texcommand{\#} may be used for the sharp symbol ‘\#’.
+ Two lines of text      \HCode{<br />}
+ separated by a horizontal line.
+ You probably don't want a '<br>'.
+\texcommand{\Link[target-file arguments]{target-loc}{cur-loc}anchor\EndLink}
+This command requests an anchor that links to \verb|‘target-file#target-loc’|, and marks the current location with the name \texttt{‘cur-loc’}.
+The component \texttt{‘[...]’} is optional when it is empty, and the target file need not be mentioned if it is created from the current source file.
+\subsection{Paragraph Handling}
+% https://tex.stackexchange.com/a/66172/2891
+\subsection{Logical Document Structure Commands}
 I've created some alternative commands to \texcommand{\HCode} or \texcommand{\Tg}. The idea is to define
 semantic names for logical elements of the document, such as titles, authors,
 sections etc. It is possible to assign HTML elements and attributes to these
@@ -25,8 +61,6 @@
@@ -38,8 +72,19 @@
 The \texcommand{\NewLogicalBlock} creates a new logical element. The used tag is configured
 using \texcommand{\SetTag}, the attributes are set using \texcommand{\SetBlockProperty}. The blocks are
-inserted to the document using \texcommand{\InlineElementStart} ...  \texcommand{\InlineElementEnd} or
-\texcommand{\BlockElementStart} ... \texcommand{\BlockElementEnd} pairs. The start commands take two
+inserted to the document using 
+\InlineElementStart ... \InlineElementEnd
+\noindent or
+\BlockElementStart ... \BlockElementEnd 
+\noindent pairs. The start commands take two
 parameters, first is the logical block name, the second can be local
 parameters which shouldn't be used for the given logical block globally.

Modified: trunk/doc/tex4ht-doc/style.css
--- trunk/doc/tex4ht-doc/style.css	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/style.css	2020-05-05 19:54:36 UTC (rev 688)
@@ -1,5 +1,127 @@
-body{max-width:50rem;margin:0 auto;}
+Color scheme 
+ */
+/* ************** */
+/* *** Fonts  *** */
+/* ************** */
+/* Font size tricks from https://www.madebymike.com.au/writing/precise-control-responsive-typography/ 
+ * The font size will be adjusted to the screen size.
+ * */
+  font-size: 16px;
+/* the min width is calculated as:
+ * font-size / ( number of viewport units / 100 )
+ * it means 16 / (1.5/100)
+ */
+ at media (min-width: 1200px){
+  :root {
+    font-size: 1.5vw;
+  }
+/* Maximal font size should be 24px, so stop font scalling at some point (24 / (1.5/100)) */
+ at media (min-width: 1500px){
+  :root {
+    font-size: 20px;
+  }
+/* ************** */
+/* *** Layout *** */
+/* ************** */
+  /* max-width:52rem; */
+  margin:0;
+  padding:0;
+  /* display:grid; */
+  /* grid-auto-rows: auto; */
+ at media screen and (min-width: 57rem) {
+  body{
+    display:grid;
+    grid-template-columns: 15rem 1fr;
+  }
+  main.main-content{max-width:40rem;}
+  nav.TOC{
+    grid-row:1;
+    min-height:100vh;
+  }
+/* ****************** */
+/* *** Formatting *** */
+/* ****************** */
+  padding:1rem;
 p.indent, p.noindent{text-indent:0}
-figure pre.listings{font-size: 1.4em;}
+/* code{font-size:1.4rem;} */
+/* figure pre.listings{font-size: 1.4rem;} */
+figure.texsource, figure.shellcommand, figure.htmlsource{
+  margin:0.5rem; 
+  padding-left:0.5rem; 
+  overflow:auto;
+figure pre.listings{font-size: 1em;}
+.chapterToc, .sectionToc, .subsectionToc{margin:0;padding:0;}
+  padding:0.5rem;
+  font-size:0; /* trick to remove vertical space above TOC entries */
+ .chapterToc ~ .likesectionToc, .chapterToc ~ .sectionToc, .likechapterToc ~ .likesectionToc, .likechapterToc ~ .sectionToc {padding-left:2em;margin-left:0}
+ .chapterToc ~ .likesectionToc ~ .likesubsectionToc, .chapterToc ~ .likesectionToc ~ .subsectionToc, .chapterToc ~ .sectionToc ~ .likesubsectionToc, .chapterToc ~ .sectionToc ~ .subsectionToc, .likechapterToc ~ .likesectionToc ~ .likesubsectionToc, .likechapterToc ~ .likesectionToc ~ .subsectionToc, .likechapterToc ~ .sectionToc ~ .likesubsectionToc, .likechapterToc ~ .sectionToc ~ .subsectionToc {padding-left:4em;margin-left:0;}
+nav.TOC span{
+  display:block;
+  margin-top:0;
+  font-size:0.8rem;
+nav.TOC a, nav.TOC a:visited{
+  text-decoration:none;
+/* ************** */
+/* *** Colors *** */
+/* ************** */
+/* body{background-color:#dce8d0;} */
+/* It seems that dark background is better to my eyes */
+  background-color:white;
+nav.TOC,nav.TOC a, nav.TOC a:visited{
+  background-color:#22211f;
+  color:#cec1aa;
+nav.TOC span:hover, nav.TOC span:hover *{
+  background-color:#66635d;
+figure.texsource, figure.shellcommand, figure.htmlsource{
+  border:1px solid #cec1aa; 
+  background-color:#d5e3c6;

Modified: trunk/doc/tex4ht-doc/tex4ht-doc.tex
--- trunk/doc/tex4ht-doc/tex4ht-doc.tex	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/tex4ht-doc.tex	2020-05-05 19:54:36 UTC (rev 688)
@@ -1,8 +1,18 @@
+% \usepackage[T1]{fontenc}
 \title{TeX4ht Documentation}
@@ -12,26 +22,158 @@
+% Don't introduce table of contents in the HTML mode, as it introduces another page
-\chapter{Basic tutorial}
-\chapter{Basic usage}
-\section{Calling commands}
-\section{Output Formats}
-\section{Command Line Options}
+This work was supported with a financial support from \href{https://cstug.cz/}{CSTUG}.
+\chapter{Basic Tutorial}
+\chapter{Calling Commands}
+\chapter{Output Formats}
+\chapter{\texfourht\ Options}
-\section{tex4ht commands}
-\section{Configuration files}
+\section{tex4ht Commands}
 \section{Styling the Document}
-\section{Use Webfonts}
+\texfourht\ provides several commands that can be used for changing of the
+document appearance using Cascading Style Sheets (\css). Only basic styling for
+the document is provided by default. Additional styles are added by configurations for the
+fonts, packages and commands used in the document. Full control of the document
+styling can be achieved using following commands and configurations.
+This command sends its content to the CSS file of the document. 
+The CSS file \texfourht\ used by default initially consists just
+a single line,  \texcommand{/* css.sty */}. This line is later
+replaced with the code submitted by the \texcommand{\Css{...}} commands.
+The \texcommand{\CssFile} command allows to specify an alternative to the initial CSS file.
+The alternative file consists of the code loaded from listed files, and of the
+content explicitly specified in its body.
+{\HCode{<div class="mylist">}} {\HCode{</div>}} {* }{} 
+/* css.sty */ 
+.mylist { color : red; } 
+The names in the list of files should be separated by commas, and the rectangular brackets are optional when the list is empty.
+The file should include a line having the content of \verb|/* css.sty */|. If
+more than one such line is included, the content of the \texcommand{\Css{...}} commands
+replace the first occurrence of this line. Arbitrary many space characters may
+appear around the substrings ‘/*’ and ‘*/’. 
+\DocConfigure{AddCss} {CSS file name}\EndDoc
+Require external CSS file.
 \section{Use JavaScript}
 \section{Document Navigation}
+The following configurations modify behaviour of cross-links between pages in a multi page document.
+\DocConfigure{crosslinks} {left-delimiter} {right-delimiter} {next} {prev} {prev-tail} {front} {tail} {up}\EndDoc
+This command configures the appearance of the cross-links between hypertext pages obtained for sectioning commands.
+ \Configure{crosslinks}
+   {}{}{$\scriptstyle\Rightarrow$}
+   {$\scriptstyle\Leftarrow$}
+   {}{}{}{$\scriptstyle\Uparrow$}
+\DocConfigure{crosslinks*} {1--7 arguments}\EndDoc
+  Links to be included and their order. Available
+  options: next, prev, prevtail, tail, front, up.
+  The last argument must be empty.
+  Default:
+   {prev}{prevtail}
+   {tail}{front}
+   {up}{}
+\DocConfigure{crosslinks+} {before-top-links} {after-top-links} {before-bottom-links} {after-bottob-links}\EndDoc
+The top cross links are omitted, if both \verb|#1| and \verb|#2| are empty.
+The bottom cross links are omitted, if both \verb|#3| and \verb|#4| are empty.
+\DocConfigure{next} {the anchor of the next button of the front page}\EndDoc
+Default: The value provided in \texcommand{\Configure{crosslinks}}
+\DocConfigure{next+}{before} {after}\EndDoc
+  \item[\#1]  before the next button of the front page, when the `next'
+       option is active.
+  \item[\#2]  after the button
+    Default: The values provided in \texcommand{\Configure{crosslinks}}
+  \verb|#1| local configurations for the delimiters and hooks
+\DocConfigure{crosslinks-}{before} {after}\EndDoc
+Asks to show linkless buttons with the following insertions.
+The default values are used, if both \verb|#1| and \verb|#2| are empty
+   Examples:
+    {\HCode{<span class="hidden">}[}
+    {]\HCode{</span>} }
+\Css{span.hidden {visibility:hidden;}}
 \section{Tables of Contents}
@@ -41,147 +183,219 @@
 \subsection{Basic font commands}
-Information about the \option{fonts} option and \term{MathML} issues. Example configuration:
+Information about the \option{fonts} option and \term{MathML} issues. 
+Example configuration:
-\section{TikZ }
+\section{Multi-lingual support}
-Animations using Animate package: \url{https://tex.stackexchange.com/a/404600/2891}
+RTL support in the ODT output: \url{https://tex.stackexchange.com/a/470434/2891}.
+\subsection{Right-to-left text}
+There is a difference in the RTL support for HTML and ODT output formats. In HTML, RTL can be requested using:
-\chapter{Make4ht Build Files}
-\section{Calling commands}
+\DocConfigure{LRdir} { value for the dir attribute}\EndDoc
-Some samples:
-  \item Render math by Mathjax during tex4ht compilation \url{https://tex.stackexchange.com/a/402159/2891}
-\section{Image conversion}
+{\Configure{LRdir}{ dir="rtl"}}
-\chapter{For developers}
+This configuration sets the direction to \term{rtl} inside the \term{arab} environment and resets it after the environment end.
-\section{Writing basic support for a new package}
-  \item \url{https://tex.stackexchange.com/a/402283/2891}
+In the ODT output, different mechanism is used:
-\section{Two types of .4ht files}
-\subsection{Inserting configurable hooks for packages}
-\subsection{Configure the hooks in output format configuration files}
+Generally speaking, \texfourht\ supports \term{Unicode}, but there are some
+issues to be aware of. Most complete support exists for Lua\LaTeX, thanks to
+special Lua script which is automatically loaded during the compilation. No
+additional packages are necessary.
-\section{How to add support for a package to the \texfourht\ literate sources}
+PDF\LaTeX\ doesn't support nativelly, but it is possible to emulate it using the
+\package{inputenc} and \package{fontenc} packages:
-To add a proper support for a new package, it is necessary to edit the 
-\texfourht\ literate sources. The configurable hooks need to be placed in the \file{tex4ht-4ht.tex},
-the configuration of these hooks must be added to the output format configuration files.
-The most common output format is \HTML, which can be configured in \file{tex4ht-html4.tex}, or 
-\file{tex4ht-html5.tex} if \HTMLV\ features are used. It is also necessary to update the
+Unicode text
+Xe\LaTeX\ is an Unicode format, similarly to Lua\LaTeX. The supporting
+mechanism for \texfourht\ is different in this case and full Unicode range is
+not supported out of the box. By default, only most Latin based characters are
+supported. For other scripts, such as Greek or Cyrillic, two ways to enable
+support exists. 
-Given following package \file{sample.sty}:
+First option is to define new font family using \package{fontspec} \texcommand{\newfontfamily} with the \texttt{Script} option.
+\newfontfamily\greekfont{Linux Libertine O}[Script=Greek]
-This simple package defines command \texcommand{\hello}, which simply prints the word \textit{hello} when used in a document.
-Let's say that we want to insert some \HTML\ tags before and after the text content printed by the command.
+The second option is to declare load support for a script in the custom config
+file using the \texcommand{\xeuniuseblock}:
-Basic template for \file{tex4ht-4ht.tex}
-% examples/basicpackage/sample.4ht
-% sample.4ht (|version), generated from |jobname.tex
-% Copyright 2017 TeX Users Group
-|<TeX4ht license text|>
->>> \AddFile{9}{sample}
-Configuration for each package must follow this basic template. The \ProTeX\ system is used as system for literate programming.
+The block names are based on \href{https://en.wikipedia.org/wiki/Unicode_block}{Unicode blocks}.
-The \texcommand{\<name\><<<code>>>} block defines new macro which can be then called using \texcommand{|<name|>}. The license text
-is included in the example this way. In order to generate the \file{sample.4ht} file, we need to use \texttt{sample.4ht} as a name
-in the code block and command \texcommand{\AddFile{9}{sample}} after the block definition\footnote{I have no idea what the number
-in the first parameter means.}.
+It is also possible to declare all characters in an Unicode range. The command
+\texcommand{\xeuniregisterblockhex} takes two hexadecimal parameters with
+Unicode range to be declared.
-Each package configuration  must include \texcommand{\Hinput{packagename}}, in order to load the configurations for the package.
-The command \texcommand{\NewConfigure{hello}{2}} declares new configuration \texttt{hello}, with two configurable hooks. 
-These hooks are named  \texcommand{\a:hello} and \texcommand{\b:hello}. The hooks must be inserted into the 
-\texcommand{\hello}, which can be easily done using the \texcommand{\pend:def} and \texcommand{\append:def} commands. These
-commands can insert code  at the beginning, respective at the end of the redefined command.
+Individual character can be declared using the \texcommand{\xeuniregisterchar} command:
-The configuration for \HTML\ must be placed in the \file{tex4ht-html4.tex} file:
+In contrast to \texcommand{\xeuniregisterblockhex}, it uses decimal numbers by
+default, so it is necessary to use the \texttt{"} character in front of
+a hexadecimal number.
-% examples/basicpackage/config.cfg
+It is possible to run into issues because of the way how Xe\LaTeX\ Unicode
+support works. Common problem is filename support, for example in included
+graphics. In general, it is better to avoid such filenames. If it is not possible, try to use the \texcommand{\detokenize} command.
-\<configure html4 sample\><<<
-\Configure{hello}{\HCode{<span class="hello">}}{\HCode{</span>}}
+  \includegraphics{\detokenize{háček.jpg}}
-The configuration for a package must be placed in \texcommand{\<configure html4 packagename\>} block.
-% ToDo: write more info
+Information about the \texcommand{\color} command:
+Example of possible configuration for the \texcommand{\color} command: 
-The package name must be also included in \file{mktex4ht-cnf.tex}:
+Example of extracting color information to the CSS and custom color environment support:
+\url{https://tex.stackexchange.com/a/422281/2891}. Extracting of color information to the HTML attributes:
+\section{Graphics and Pictures}
+\section{TikZ }
+Animations using Animate package: \url{https://tex.stackexchange.com/a/404600/2891}
+Issues with drivers: \url{https://tex.stackexchange.com/a/471460/2891}.
+\subsection{Default math handling}
+\mathml\ is a XML markup for the math encoding. It is supported in many
+aplications including OpenOffice Writer or Firefox web browser. 
+The advantage over use of images % Todo: write about advantages of MathML.
+The \mathml\ code produced by \texfourht\ may contain some issues. For example,
+one common issue may happen when the math contain unmatched delimiters:
+ Mail address: $\lparen$hello at world.com$\rparen$
-The \file{.4ht} files can be generated simply using 
+In such cases, the \option{matml-} may help. 
+It is also advisable to always use \extension{common\_domfilters}
+\term{make4ht} extension (see section \ref{sec:make4ht-extensions} for more
+information about \term{make4ht} extensions), as it fixes some common \mathml\
+errors that cannot be easily fixed on the \TeX\ level.
-The following sample \TeX\ file:
+Add information about the \url{https://github.com/pshihn/math-ml} - it adds
+support for MathML in all modern web browsers with HTML 5.
-% examples/basicpackage/hello.tex
+The \term{MathJax} processing can be required using \option{mathjax} option.
+The address of \term{MathJax} script with its configuration string can be
+specified in \configuration{MathjaxSource}. The default value of this configuration is:
-  \hello\ world.
-Produces a following \HTML\ code:
+By default, inline and display math, as well as math environments, are kept as
+raw LaTeX code in the \HTML\ output. \term{MathJax} then transforms this code
+and displays it. In the \term{MathML} mode, \term{MathJax} is used only for the
+rendering in browsers without \term{MathML} support. 
-<!--l. 4--><p class="noindent" >
-<span class="hello">world</span> world. 
+The additional configuration for \term{MathJax} can be provided in special
+script environment in the \HTML\ page header. The following example provides
+support for some custom \LaTeX\ macros.
+<script type="text/x-mathjax-config">                                           
+  MathJax.Hub.Config({
+    TeX: {           
+      Macros: {     
+        sc : "\\small\\rm",
+        sl: "\\it", 
+      }        
+    },        
+    }                   
+  );                  
+The \texcommand{\detokenize} macro is used to avoid issues with backslash
+characters used in the macro definitions. Backslashes must be doubled in the
+JavaScript strings.
+\section{OpenDocument Format}
+\chapter{Make4ht Build Files}
+\section{Commands execution}
+Some samples:
+  \item Render math by Mathjax during tex4ht compilation \url{https://tex.stackexchange.com/a/402159/2891}
+\section{Image conversion}
+\chapter{For developers}

Modified: trunk/doc/tex4ht-doc/tex4ht-styles.sty
--- trunk/doc/tex4ht-doc/tex4ht-styles.sty	2020-05-05 19:50:14 UTC (rev 687)
+++ trunk/doc/tex4ht-doc/tex4ht-styles.sty	2020-05-05 19:54:36 UTC (rev 688)
@@ -1,28 +1,54 @@
-% shortcuts 
 % formatting commands
 % this trick will enable us to take verbatim arguments
 % https://tex.stackexchange.com/a/45292/2891
+% shortcuts 
+\newcommand\cfgfile{\term{custom configuration file}}
+% this was used by CVR in the options page
+% Document \Configure commands. They have variable number of arguments, so it is necessary to process them as a list
+\def\DocConfigure#1#2\EndDoc{\par\bigskip\noindent\texttt{\textbf{\textbackslash Configure}\{\textit{#1}\}\PrintConfigures#2{}\@nil}}

More information about the tex4ht-commits mailing list.