Re: [tex4ht] Can one use tex4ht log file to check if more runs are needed?

2023-12-05 Thread Michal Hoftich 
Hi Nasser,

>
> Hello Michal. I am little confused. You say tex4ht does not generate
> such messages, but then you say log checking is safer.
>
> Can I check for same messages when compiling with tex4ht as
> I do with lulatex? This is my question.
>

The running script that I gave you checks for the AUX file, XREF file
and TOC, and it continues  the compilation until they don't change -
so when you don't change sections, cross-references and other stuff
that is written to these files, it should do only one compilation. If
these files change between compilations, it will run as many
compilations as specified in max_compilations variable. Check how
large it is, maybe we were experimenting with it and it is too large.
Value of 3 should be enough.

> I do not want to use rerunfilecheck package as I do not understand it.
>
> I just want a simple method, which is to to check myself for messages
> in the log file, that is why I asked.
>
> I assumed tex4ht generates its own messages different
> from lualatex to indicate more runs are needed or not.
>
> Ofcourse, I can try and find out, but the problem is that it is hard to
> know by looking at the HTML pages sometimes if the build was
> complete or not.
>

The problem is mostly with hyperlinks and large  tables. But all of
this depends on the auxilary files the script checks, so you won't get
any better results with the log parsing.

> I am asking all this, because one build with tex4ht
> takes 24 and more hours on some of my large files and was
> wondering if it is calling tex4ht more times than needed.

Yes, it is too much. You can try to print the number of compilations
used in the checksum script by adding this line before return status
in Make:add("myhtlatex", ...) function:

print("Number of compilations: " .. compilation_count)

I am not sure which version of this file you use now, I know there are
multiple versions and I am afraid that I cannot find the most recent
one, so I cannot post the whole function here. Anyway, if the number
is too large, it can be caused by some bug in the script.

Best regards,
Michal

Re: [tex4ht] Can one use tex4ht log file to check if more runs are needed?

2023-12-04 Thread Nasser M. Abbasi 

On 12/4/2023 5:29 AM, Michal Hoftich wrote:

Hi Nasser,


My question here is this: Could I use similar method
for tex4ht and just check the tex4ht log file for messages?

This is easier for me to do, since I can use the same
"grep -E" command.


TeX4ht on its own doesn't produce such messages, AFAIK. The method
with log checking should be safer. 


Hello Michal. I am little confused. You say tex4ht does not generate
such messages, but then you say log checking is safer.

Can I check for same messages when compiling with tex4ht as
I do with lulatex? This is my question.


Also the rerunfilecheck package is
also based on checksums of temporary files, so it should work
similarly.



I do not want to use rerunfilecheck package as I do not understand it.

I just want a simple method, which is to to check myself for messages
in the log file, that is why I asked.

I assumed tex4ht generates its own messages different
from lualatex to indicate more runs are needed or not.

Ofcourse, I can try and find out, but the problem is that it is hard to
know by looking at the HTML pages sometimes if the build was
complete or not.

I am asking all this, because one build with tex4ht
takes 24 and more hours on some of my large files and was
wondering if it is calling tex4ht more times than needed.


Best,
Michal


Thanks
--Nasser

Re: [tex4ht] Can one use tex4ht log file to check if more runs are needed?

2023-12-04 Thread Michal Hoftich 
Hi Nasser,

> My question here is this: Could I use similar method
> for tex4ht and just check the tex4ht log file for messages?
>
> This is easier for me to do, since I can use the same
> "grep -E" command.

TeX4ht on its own doesn't produce such messages, AFAIK. The method
with log checking should be safer. Also the rerunfilecheck package is
also based on checksums of temporary files, so it should work
similarly.

Best,
Michal