Josef Kleber <
josef....@nurfuerspam.de> writes:
>Am 13.06.2013 22:21, schrieb jon:
>> On Jun 13, 7:20 am, Fastian <
abdulbasit.f...@gmail.com> wrote:
>>> Do you know any stable good program that can help me convert HTML file to Tex file?
>>
>> 'equivalent' is unclear to me in this context, but you could try
>> pandoc <
http://johnmacfarlane.net/pandoc/>, which can read
>> html (among other things) and write latex and context (among
>> other things -- even beamer slides, apparently). it is actively
>> developed and maintained.
>
>That's true for simple documents. For a complex LaTeX document, the
>conversion to HTML is somehow disappointing. You really can't blame
>pandoc for that because it is complex! Maybe HTML -> LaTeX works better,
>as HTML is defined and more limited.
On the other hand, much (I would hazard, very much) of the
"HTML" found on the web fails in some (often, many) ways
to accord with the definitions of HTML. Thanks to (or maybe
better, merely "due to") the way browsers are written,
non-conformant HTML often *appears* to be conformant (to
something; which may differ between browsers) when displayed.
What is an HTML -> LaTeX engine to do in such cases? Make
whatever guesses some fixed choice of browser makes, so as
to produce LaTeX that compiles to *something*, plus a log
full of LaTeX warnings? Make no guesses, and produce
non-compilable code plus a log full of LaTeX error
messages? Either situation leaves an engine-user
who does not have control of the original HTML (which
I assume is the original poster's situation) with an
enormous amount of post-engine manual labour, and
even then with no guarantee of having captured the
(badly implemented) intent of the author of the original
HTML. The situation is somewhat different if the same
person wrote the HTML (first), then converted it to
TeX; but I don't think all that different in quality
(just, with luck, different in quantity of manual
labour).
Lee Rudolph