# [tex4ht] Three questions about errors when using mk4ht to create MathJax compatible files

Michal Hoftich michal.h21 at gmail.com
Mon Sep 30 09:37:33 CEST 2013

Hello,
I just realized that error message

/usr/bin/t4ht: fork: retry: No child processes

could mean that t4ht application cannot be started. t4ht is used
to generate css files and running external commands, like image
conversion, maybe this is the source of your problems, not NoFonts
option. You can try to run

t4ht filename.dvi

yourself, to see whether the css file is generated.

Reagards,
Michal

2013/9/27 Steven Dunbar <sdunbar1 at unl.edu>:
> Thanks to Michal Hoftich and Karl Berry for gracious answers to my
> questions.
>
> 1.   In reply to Michal's answer, I can't see that I am explicitly using
> NoFonts on the command line or in the configuration file.  Perhaps I am
> using it implicitly somehow.  I will continue to investigate, perhaps I will
> find it or something equivalent.  (I don't need accented characters, so I
> don't need to use this feature.) I have a clumsy work-around by re-using the
> old *.css file, so good enough until I figure out what is happening.
>
> 2.  In reply to Karl's answer:  It's probably a Good Thing that the old
> wrapper scripts disappeared, for me at least.  The disappearance of the
> wrappers forced me out of my rut, and made me learn how to do something I
> should have learned a long time ago.  I'm just glad to know that the package
> or my installation of it was not damaged.
>
> 3.  Still no answer on why the multitude of complaints from the shell when I
> run
> mk4ht xhmlatex $1 "/path/to/ht5mathjax" > I will continue to study, learn, think and watch. Maybe the answer will > become apparent.... > > Thanks! -- Steve Dunbar > > ________________________________ > From: Steven Dunbar > Sent: Monday, September 23, 2013 5:57 AM > To: tex4ht at tug.org > Subject: Three questions about errors when using mk4ht to create MathJax > compatible files > > In mid-summer, I upgraded to the most recent Fedora 19 distribution of > Linux. As part of the upgrade, I installed the corresponding 2013 TeXLive > package from Fedora. > > Previously (with Fedora 17 and the previous TeXLive version, probably > 2011 or possibly 2012), I had used mzlatex to process LaTeX source files to > XHTML > 1.1 plus MathML 2.0. > > After the upgrade I no longer had mzlatex as a script. After some > searching and learning, I started using the command > mk4ht xhmlatex$1 "/path/to/ht5mathjax"
> where ht5mathjax.cfg is the configuration file suggested by Michal
> Hoftich and William Hammond.
>
> This command mostly works,  it creates the an html/MathJax file that
> problems:
>
> 1.  Most text formatting no longer exists, for instance, no boldface, a
> font change using \texttt{} results in a the same roman font as all
> other text, and the macro
> \newcommand{\sectiontitle}[1]{\begin{center} {\Large #1} \end{center}}
> results in left-justified text at the same size as all other
> text.
>
> After some investigating, I see that the old mzlatex processing
> created a *.css file of size 6,335 characters, while the new command
> creates a *.css file of size 15 characters.  Substituting the old
> *.css file restores the text formatting.
>
> Question:  Why doesn't the new command create an appropriate CSS
> file? How can I force the processing to create an appropriate CSS?
>
> 2.  During the processing, I get a lot of error messages of the form:
> tex4ht.c (2012-07-25-19:36 kpathsea)
> tex4ht
> --- error --- improper command line
> tex4ht [-f<path-separator-ch>]in-file[.dvi]
>
> This scrolls past too many times to count, the many identical errors fly by.
> But there don't seem to be any problems with the *.html files.
>
> Question:  What's happening?  How to fix?
>
> 3.  At the end of the processing, I get the following:
> /usr/bin/t4ht: fork: retry: No child processes
> /usr/bin/t4ht: fork: retry: No child processes
> /usr/bin/t4ht: fork: retry: No child processes
> /usr/bin/t4ht: fork: retry: No child processes
> /usr/bin/t4ht: fork: Resource temporarily unavailable
> --- error --- failed to execute command
>
> Again, there don't seem to be any problems with the *.html files.
>
> Question:  What's happening?  How to fix?
>
>
> Thanks!
>
> Steve Dunbar
>