Posted by Victor Ivrii on 10/24/07 07:08

On Oct 23, 6:27 pm, Peter Flynn <peter.n...@m.silmaril.ie> wrote:
> vasan...@hotmail.com wrote:
> > Basically, it should do all that any of the tools below and in
> > addition,
>
> You've already asked this, and been given the answer, but in case you
> didn't see it...
>
> XSLT.
>
> Run your HTML through Tidy to produce XHTML.
> Then write an XSLT script to transform it to LaTeX.
> This gives you 100% control and ensures robustness.
>
> However, handling all the stupid things HTML authors do may make it
> long-winded if you want to cope with them all. On the other hand, if
> you are dealing with a reasonably consistent subset, it's probably the
> most reliable method.

One should remember that while tex parser (tex/latex/...) can run in
quiet mode, it is not a default and finished tex document normally
does not contain any tex errors. Meanwhile few html parsers (web
browsers) even advise about errors. As a result absolute majority of
html sources contain errors, from few to few hundreds (the latter is
the case usually with commercial web pages, produced by community
colleges graduates, who check their pages only against a specific
version of MSIE). The task of converting of such html sources to error-
free tex ones seems to be a really daunting




>
> ///Peter

[Back to original message]