Karl:

What is the functional specification for tex4ht? Can it survive in its current 
form?

This is a good example of one concern that I have (and probably you as well): 
the long-term viability of a system built on custom non-standard specifications 
by hundreds if not thousands of persons each doing boutique independent 
installation and development is simply not clear. Will LaTeX survive? LaTeX3 is 
going to possibly fix this, but I am totally confused by it (since I haven't 
really looked into it, it might be less confusing if I did).
________________________________________
From: tex4ht [[email protected]] on behalf of Karl Berry 
[[email protected]]
Sent: Tuesday, March 19, 2013 4:26 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [tex4ht] TeX4ht upgrading: doesn't work

    here are the instructions to upgrade tex4ht 
(http://tug.org/applications/tex4ht/mn-upgrade.html).

Which Eitan wrote years ago, and it's not been touched since.  I guess I
better eradicate that page.  Advising people to replace anything in
/usr/bin is a terrible idea.  I have no specific idea why it fails, but
I am not at all surprised it does, since it's replacing the
distro-built binaries with others.

In any event, tex4ht has not seen a full update since Eitan died.  (I
should probably delete that .zip file too.)  CVR and I are still hoping
that will happen at some point, but there is no ETA.  Meanwhile, some of
the *.4ht, etc., files have been updated by CVR and you can get the
current versions from TeX Live.  There have been no other substantive
changes.

Best,
karl
-----------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
privileged and confidential information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.


Reply via email to