Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Unknown Newsgroups: alt.os.linux.debian Subject: Re: Rendering ? Date: Thu, 2 Feb 2017 00:04:15 -0000 (UTC) Organization: A noiseless patient Spider Lines: 32 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Thu, 2 Feb 2017 00:04:15 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="1e2aec8da1b5cdf2d9e40fd4e6b573f1"; logging-data="17016"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18iuF42Wl3griRu8FzsmZk/DOw2QafZiAE=" User-Agent: Pan/0.133 (House of Butterflies) Cancel-Lock: sha1:MsuXqOKajvYWZLY2ew4nzgnHH6g= Xref: csiph.com alt.os.linux.debian:8654 On Wed, 01 Feb 2017 10:20:02 +0000, Dan Purgert wrote: > Unknown wrote: >> Being located in a remote location, with problematic inet access, I've >> accumulated many text-files containing some . >> fetched while I to get my emails. >> >> [...] >> >> How would I be able to read these text files', >> apparently latex contents? >> >> > Assuming they're otherwise properly formatted latex documents, running > them through the latex parser should do it for you. IIRC, the package is > simply named 'latex'. > > Note that depending on what features they're using, it may require > additional libraries beyond the base 'latex' package. > > HTH No, blindly putting standard *.tex throught standard LaTex tools won't suffice. It needs the original *.html which has been converted to text, to have the appropriate header and tail to be added to make a valid *.tex file. But how? I need to speak with the idian-year, not the sales clerk!