Jerry James writes:
Ah, so it turns out that my version of texi2html is actually
"texi2any
--html" in disguise from the texinfo 5.1 distribution. It probably
behaves quite differently from the (apparently obsolete) "real"
texi2html.
Yes it does, and yes it's obsolete. We should make that clear in our
requirements since texi2any --html does a better job -- I don't think
it's worth trying to support older texi2html. Better to spend the
effort on providing those files in HTML on the website.
On Sun, May 11, 2014 at 12:57 PM, Stephen J. Turnbull
<stephen(a)xemacs.org> wrote:
> I'll see if I can clean a few of these up but it will take a
couple
> days before I can get to that.
If you would rather spend your time on moving services to the new
server, I can try to look at this.
Sounds good. FWIW, my approach to texi2html for the Japanese .texi
files is "iconv -t utf-8 -f iso-2022-jp". For now, please do that on
the fly, and leave the files in their original ISO 2022 encoding. I
need to think whether there's any real downside to just converting
those files to UTF-8 (probably not enough to prevent it, but XEmacs
21.4 can't handle UTF-8 without Mule-UCS).
Steve
_______________________________________________
XEmacs-Patches mailing list
XEmacs-Patches(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-patches