much faster than using Vbox or cygwin or miktex on windows.
I wonder if the issue is dvisvgm needing to call out to an external gs
process on these Windows machines, instead of linking against libgs.
Anyway, if you want to pursue it further, the author of dvisvgm is
Martin Gieseking
On 4/7/2018 1:28 AM, Nasser M. Abbasi wrote:
May someone who knows more about this program can comment
on this. It is version 2.3.2 on windows:
X:\data\public_html\latex\slow_svg_example>dvisvgm --version
dvisvgm 2.3.2
X:\data\public_html\latex\slow_svg_example>make4ht --version
make4ht
On 4/6/2018 2:30 AM, Michal Hoftich wrote:
The full compilation took 10 minutes on my computer (Core i3-3220
with 4 GB RAM, without SSD, native Linux), so I think there must be
something that really slows down the compilation on Windows, as you
have much more powerful computer and it takes two
> Are you saying it should be
>
> Make:htlatex{}
> Make:htlatex{}
> #Make:htlatex{} --> remove this?
> Make:tex4ht{}
> Make:t4ht{}
>
Yes. There is another Make:htlatex {} before this block. Or even
if mode=="draft" then
Make:htlatex {}
else
Make:htlatex {}
Make:htlatex {}
Make:htlatex {}
end
On 4/6/2018 2:30 AM, Michal Hoftich wrote:
Hi Nasser,
May be I just have to switch to Linux. But I have apps
I need to use on windows, that is why I am stuck on windows.
one slight issue I've found with your setup is that you use
Make:htlatex {} four times in your setup, which is more than
Hi Nasser,
> May be I just have to switch to Linux. But I have apps
> I need to use on windows, that is why I am stuck on windows.
one slight issue I've found with your setup is that you use
Make:htlatex {} four times in your setup, which is more than
necessary, you need three compilations on
On 4/5/2018 7:02 PM, Nasser M. Abbasi wrote:
The slow down starts after where it says
Make4ht: dvisvgm -n etc...
as follows
-
Entering report.lg
Entering report.css
Entering report.tmp
Make4ht: dvisvgm -n --exact -c 1.225,1.225 -p 1- report.idv
pre-processing DVI file (format
On 4/5/2018 5:05 PM, Karl Berry wrote:
Hi Nasser,
The above phase of the compile is the one that takes for ever.
I'm not surprised that running dvisvgm on a 13000+ page DVI file (even
if many pages are empty) takes a long time. Let's see, 5515 seconds
means it's doing better than a page
Hi Nasser,
The above phase of the compile is the one that takes for ever.
I'm not surprised that running dvisvgm on a 13000+ page DVI file (even
if many pages are empty) takes a long time. Let's see, 5515 seconds
means it's doing better than a page in a half-second, it just adds up to
90+
On 4/5/2018 3:59 AM, Michal Hoftich wrote:
It took me about one week to compile 205 latex files. Some are
few thousands of pages with lots of math. I have 16 GB RAM PC,
intel i7-3930k CPU running windows 7. Using cygwin to build now.
Lualatex finishes very fast. may be Few minutes. But tex4ht
> It took me about one week to compile 205 latex files. Some are
> few thousands of pages with lots of math. I have 16 GB RAM PC,
> intel i7-3930k CPU running windows 7. Using cygwin to build now.
>
> Lualatex finishes very fast. may be Few minutes. But tex4ht is
> the one that takes sooo long.
>
Hi Nasser,
On Thu, Apr 5, 2018 at 2:43 AM, Nasser M. Abbasi wrote:
> I am just curious, why sometimes I see, when compiling
> with tex4ht, using SVG for math, messages that says
>
> processing page n
> page is empty -->
>
> I see so many of them. Interspersed
I am just curious, why sometimes I see, when compiling
with tex4ht, using SVG for math, messages that says
processing page n
page is empty -->
I see so many of them. Interspersed between not empty pages.
I am now compiling one large file and seeing these. But I see
them on many
13 matches
Mail list logo