more active in supporting TeX4ht,
Help is always good. There are plenty of open bugs at
https://puszcza.gnu.org.ua/bugs/?group=tex4ht=browse=open
That's probably the simplest place to start.
Thanks,
Karl
NMA> From: "Nasser M. Abbasi"
NMA> Date: Mon, 28 Mar 2016 03:20:50 -0500
NMA> I just finished new timings on the same above file, after removing
NMA> the package titlesec which was the cause of the slowdown (thanks for
NMA> finding it goes toJagath ARâ)
I wonder why titlesec
On 3/26/2016 2:21 AM, Nasser M. Abbasi wrote:
I put the latex file
and all the needed include files I use and the .cfg and main.mk
and the command in one zip file. Here it is, in this folder:
http://12000.org/tmp/032616/
There is file call compile.sh which has this line:
make4ht --lua -u -c
On 27 March 2016 at 04:50, Nasser M. Abbasi wrote:
> On 3/26/2016 5:44 PM, Karl Berry wrote:
>
>>
>> I have many many latex files this large
>>
>> Is the one you provided already one of the smaller ones? The smaller
>> the file that still exhibits the problem, the easier to
make:htlatex()
make:htlatex()
make:htlatex()
P.S. The texi2dvi script implements one way to check how many runs are
needed: it compares auxiliary files and keeps running TeX until they
stabilize. I suspect latexmk and others do the
What are these rules?
I just explained it.
(that is why we need design documents)
There's no use in continuing to repeat this wish. We all agree. What's
needed is more people to do work, not more work to be done! -k
On 3/27/2016 5:13 PM, Karl Berry wrote:
I call make4ht to compile the file
I don't know anything about make4ht, that's Michal's bag ... Perhaps it
is already smart enough to avoid multiple runs when it's not necessary.
(I'm having deja vu, did we already discuss this, Michal?) -k
The
But I do not know how to decide if I need one run or two or three?
You need three runs if you are starting from scratch.
After the first time, in general, you only need one run unless you are
modifying the things that go into the cross-references (section names,
labels, bib entries, etc.).
Hi Nasser,
TL is more optimized for native Linux vs. cygwin.
Just to remark: TL specifically is not "optimized" for any particular
platform (all binaries are built natively). I think the difference you
are seeing here is an inevitable consequence of running a
resource-intensive job on an
On Sat, Mar 26, 2016 at 3:38 PM, Nasser M. Abbasi wrote:
>
> The zip file is much larger, about 270 MB :( But now it
> contains everything to compile this one latex file.
>
I have downloaded the previous archive. Will download this if needed. I
will temporarily suspend svg
Thanks for the offer to look into it. I put the latex file
and all the needed include files I use and the .cfg and main.mk
and the command in one zip file. Here it is, in this folder:
http://12000.org/tmp/032616/
opps. I am sorry, I forgot to also inlcude the svg images for use
by tex4ht in
On 3/26/2016 1:11 AM, Radhakrishnan CV wrote:
On Sat, Mar 26, 2016 at 3:23 AM, Nasser M. Abbasi wrote:
[...]
For example, for one file, using Vbox, it took 14 hrs
for make4ht to compile the file to html. On cygwin, it took
little less than than. About 10 hrs. This is on
On 2016-03-25 at 16:53:40 -0500, Nasser M. Abbasi wrote:
> I have lots of large latex files, with lots of pages in
> them with large number of equations, generated by
> computer algebra systems. I also have lots of includegraphics
> in these files for svg images.
>
> I noticed that tex4ht
13 matches
Mail list logo