[tex-live] Re: tex4ht bugfix

Staszek Wawrykiewicz StaW@gust.org.pl
Thu, 23 Jan 2003 07:45:01 +0100 (CET)

Eitan Gurari wrote:
EG> Is `@texmf@' literally used that way anywhere?

I'm still messed with tex4htk... In TL sources/TeX/tex4htk/tex4ht.in:

% dvi-to-gif
Gdvips -mode ibmvga -D 110 -f %%1 -pp %%2  > tex4ht.ps
% G@imbindir@\convert -crop 0x0 -density 110x110 -transparency "#FFFFFF" tex4ht.ps %%3
which, after compilation, gives tex4ht.env:
     =         =      =        = ?
and conversion section goes as it is in tex4ht.in.

I'm not so sure that tex4ht.env which *really* goes to the TL's texmf stuff
can be sometimes broken because of the above things.

EG> Instead of `@texmf@', one can put `~' or `~~' or a full path.

The problem is that web2c/kpathsea compiled versions completely ignores
such notation, as well as @texmf@. Giving full path works only on Linux
(compilation from the the current source.development touched by Thomas),
but not on Win32 (I still use TL7 binaries).

EG>   i~~/ht-fonts/iso8859/2/!
EG>   i~~/ht-fonts/alias/!
EG>A `~' takes a base path from an environment variable named HOME. A
EG>`~~' takes a base path provided through an environment variable named
EG>TEX4HTHTF. Can TEX4HTHTF be assigned the path of `@texmf@'?  If not,
EG>any suggestion on how to incorporate @texmf@ into tex4ht.c?

It would be nice having configurable `i' entries in tex4ht.env, using
~~ (for $TEXMF) or some kind of it. Since TEX4HTHTF (mn45.html) is ignored 
(as well as TEX4HTENV, mn39.html), we have instead in TL's texmf.cnf:


The last two not documented at all! But, hopefully, the user can modify
TEX4HTFONTSET, giving, e.g., `alias,win1251' or `alias,iso8859/2', etc.

I observed that `ht latex foo' doesn't work on Windows (as docs say):
  ht: error, invalid combination of options, exiting.
ht.exe, htlatex.exe and httexi.exe are just the same files. 


To conclude:
1. TL source should be corrected (preferably with the new sources from 
2. tex4ht.env: the `i' and `t' lines should be also modifiable by the user,
   as he can have tex4ht.env, e.g., in the working directory.
3. standard texht.env for TL can have picture making part which use convert
   (I think so common on linux boxes), as well some variants like
   tex4t-imagick-win32.env, tex4ht-netpbm-win32.env.

Staszek Wawrykiewicz
email: staw@gust.org.pl