Re: [tex4ht] Too many DVI errors. stack empty at pop command, conficts, bm package, siunitx, dvilualatex

[Nasser M. Abbasi]

On 1/1/2016 5:31 AM, Michal Hoftich wrote:

Hi Nasser,

it seems that it is caused by the xfrac package. A really minimal
example is following:


\documentclass[12pt]{report}%
\usepackage[T1]{fontenc}
\usepackage{xfrac}

\begin{document}
\[ \sfrac{a}{b} \]
\end{document}


compiled with

latex minimal.tex
dvisvgm minimal.dvi

we got:

processing page 1
   page size: 12.0124pt x 548.966pt (4.22189mm x 192.94mm)
   page written to minimal.svg
1 of 1 page converted in 0.34971 seconds
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])

(yes that Czech message is about unauthorized memory access)

In this simple case the svg file seems fine, but in your more
complicated case it is really garbage. So I think it should be
reported to dvisvgm maintainers.

To temporarily fix your code, I would add something like:

\renewcommand\sfrac[2]{#1/#2}

until it's fixed.

Best regards,
Michal



Thanks but I am not getting the core dump on my end? TL 2015
fresh update.

-

cat foo.tex


\documentclass[12pt]{report}%
\usepackage[T1]{fontenc}
\usepackage{xfrac}

\begin{document}
\[ \sfrac{a}{b} \]
\end{document}


latex foo.tex


This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded 
format=latex)
 restricted \write18 enabled.
entering extended mode
.
Output written on foo.dvi (1 page, 700 bytes).



dvisvgm foo.dvi

pre-processing DVI file (format 2)
processing page 1
  page size: 12.0124pt x 548.966pt (4.22189mm x 192.94mm)
  page written to foo.svg
1 of 1 page converted in 0.272353 seconds



ls -l foo.dvi


-rwxrwxrwx 1 me me 700 Jan  1 13:54 foo.dvi
---

Here is the file listing

*File List*
  report.cls2014/09/29 v1.4h Standard LaTeX document class
  size12.clo2014/09/29 v1.4h Standard LaTeX file (size option)
 fontenc.sty
   t1enc.def2005/09/27 v1.99g Standard LaTeX file
   xfrac.sty2015/12/20 v6326 L3 Experimental split-level fractions
   expl3.sty2015/12/20 v6326 L3 programming layer (loader)
expl3-code.tex2015/12/20 v6326 L3 programming layer
 l3dvips.def2015/11/11 v6250 L3 Experimental driver: dvips
 amstext.sty2000/06/29 v2.01
  amsgen.sty1999/11/30 v2.0
graphicx.sty2014/10/28 v1.0g Enhanced LaTeX Graphics (DPC,SPQR)
  keyval.sty2014/10/28 v1.15 key=value parser (DPC)
graphics.sty2014/10/28 v1.0p Standard LaTeX Graphics (DPC,SPQR)
trig.sty1999/03/16 v1.09 sin cos tan (DPC)
graphics.cfg2010/04/23 v1.9 graphics configuration of TeX Live
   dvips.def2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
l3keys2e.sty2015/12/20 v6326 LaTeX2e option processing using LaTeX3 keys
textcomp.sty2005/09/27 v1.99g Standard LaTeX package
  ts1enc.def2001/06/05 v3.0e (jk/car/fm) Standard LaTeX file
  xparse.sty2015/12/20 v6326 L3 Experimental document command parser
xtemplate.sty2015/12/20 v6326 L3 Experimental prototype document functions
  ts1cmr.fd2014/09/29 v2.5h Standard LaTeX font definitions
 ***


which dvisvgm

/usr/local/texlive/2015/bin/x86_64-linux/dvisvgm


If you like me to try something else, please let me know.

btw, there is new version of dvisvgm by Martin Gieseking just
annouced. Current version we are using on TL 2015 is 1.9.2,
but the new versio is 1.14  2015-12-28. But TL will not
update to new one until TL 2016. So it needs to be manually
build for TL 2015 if we to use it now. Binaries only for
windows and mac. I might have some bug fixes also.

--Nasser

Re: [tex4ht] Too many DVI errors. stack empty at pop command, conficts, bm package, siunitx, dvilualatex

[Nasser M. Abbasi]

On 1/1/2016 3:08 PM, Michal Hoftich wrote:

Thanks but I am not getting the core dump on my end? TL 2015
fresh update.



That's weird, I have freshly updated TL as well..



If you like me to try something else, please let me know.


I've got the SIGSEGV error also with your sample file


That is strange. We have different setup somewhere?



btw, there is new version of dvisvgm by Martin Gieseking just
annouced. Current version we are using on TL 2015 is 1.9.2,
but the new versio is 1.14  2015-12-28. But TL will not
update to new one until TL 2016. So it needs to be manually
build for TL 2015 if we to use it now. Binaries only for
windows and mac. I might have some bug fixes also.


Are you using the new version?
Michal



No. dvisvgm needs to be build from sources for Linux which I
did not do. Still using TL 2015 version. 1.9.2 as is.

Here is screen shot of my terminal, and the log file and the
dvi file here if you like to verify

http://12000.org/tmp/010116/

I am using 64 bit linux mint:


lsb_release -a

No LSB modules are available.
Distributor ID: LinuxMint
Description:Linux Mint 17.2 Rafaela
Release:17.2
Codename:   rafaela

You might be using different build of dvisvgm, i.e. different OS
and this could cause this difference?

--Nasser

 

Re: [tex4ht] Too many DVI errors. stack empty at pop command, conficts, bm package, siunitx, dvilualatex

[Michal Hoftich]

> Thanks but I am not getting the core dump on my end? TL 2015
> fresh update.
>

That's weird, I have freshly updated TL as well..

>
> If you like me to try something else, please let me know.

I've got the SIGSEGV error also with your sample file
>
> btw, there is new version of dvisvgm by Martin Gieseking just
> annouced. Current version we are using on TL 2015 is 1.9.2,
> but the new versio is 1.14  2015-12-28. But TL will not
> update to new one until TL 2016. So it needs to be manually
> build for TL 2015 if we to use it now. Binaries only for
> windows and mac. I might have some bug fixes also.

Are you using the new version?
Michal

Re: [tex4ht] tex4ht puts the wrong link when splitting document. How to make the top of the page visible?

[Nasser M. Abbasi]

On 1/1/2016 11:36 AM, William F Hammond wrote:

Happy New Year!

On Fri, Jan 1, 2016 at 2:02 AM, Michal Hoftich  wrote:


. . . The solution I gave to Nasser is
fragile, every sectioning command used in the document must be
reconfigured.



While generally I prefer unified html documents (if only because searching
is easier), my thought about splitting has always been to use an sgml or
xml transformation library to do the splitting from a unified html file.

   -- Bill



Could you please explain what you mean by a

   "unified html documents (if only because searching)"

do you mean one large html page, vs. many smaller ones?

thanks,
--Nasser

is easier)

Re: [tex4ht] Too many DVI errors. stack empty at pop command, conficts, bm package, siunitx, dvilualatex

[Karl Berry]

I'm not sure if you determined if all of this is a dvisvgm bug,
but if not:

Here is a MWE, which shows the issue. What happens is that
DVI creates corrupted DVI file or has an error making the dvi.

When dviluatex (or any engine) creates a corrupted DVI file (i.e.,
dvitype cannot successfully read it), under any reasonable
circumstances, it's certainly an error.

However, the LuaTeX developers fixed the previous DVI-generation bug,
and it could well be related.  Unfortunately, we'd have to compile from
the original source to get the fix, and I don't see that happening.
I could report it to them to try, except:

Here is MWE

As discussed last time: to debug, the LuaTeX people need an invocation
of dvilua(la)tex, not an invocation of make4ht.

Best,
Karl

Re: [tex4ht] Too many DVI errors. stack empty at pop command, conficts, bm package, siunitx, dvilualatex

[Michal Hoftich]

>
> No. dvisvgm needs to be build from sources for Linux which I
> did not do. Still using TL 2015 version. 1.9.2 as is.
>

I have the same version

>
> You might be using different build of dvisvgm, i.e. different OS
> and this could cause this difference?
>

I am using Fedora 23, but binaries are provided by TL, so it should be
identical. Could anyone else report their results?

>

Re: [tex4ht] Too many DVI errors. stack empty at pop command, conficts, bm package, siunitx, dvilualatex

[Michal Hoftich]

Hi Nasser,

it seems that it is caused by the xfrac package. A really minimal
example is following:


\documentclass[12pt]{report}%
\usepackage[T1]{fontenc}
\usepackage{xfrac}

\begin{document}
\[ \sfrac{a}{b} \]
\end{document}


compiled with

latex minimal.tex
dvisvgm minimal.dvi

we got:

processing page 1
  page size: 12.0124pt x 548.966pt (4.22189mm x 192.94mm)
  page written to minimal.svg
1 of 1 page converted in 0.34971 seconds
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])

(yes that Czech message is about unauthorized memory access)

In this simple case the svg file seems fine, but in your more
complicated case it is really garbage. So I think it should be
reported to dvisvgm maintainers.

To temporarily fix your code, I would add something like:

\renewcommand\sfrac[2]{#1/#2}

until it's fixed.

Best regards,
Michal