Activity for Akira Kakuto
-
Akira Kakuto posted a comment on ticket #175
I have applied the patch in the TeX Live: revision 55737.
-
I have applied the patch in the TeX Live: revision 55737.
-
The problem is related with the graphics package. XeTeX is not changed since January, 2019.
-
I think that pstricks for XeTeX is an experimental and limitted subset of that for dvips. In these cases I'll use pstricks for dvips + ps2pdf to obtain necessary images and include them in XeTeX.
-
I think that the problem is in the TikZ driver pgfsys-dvipdfmx.def used by XeTeX.
-
This one seems to be missed in texlive-20180414-source.tar.xz Applied the patch by Stefan for dvipdfm-x in TeX Live SVN: r47469. Please note the date: r47469 was done on 2018/04/28 after the release of TL2018. Best, Akira
-
Applied the patch by Stefan for dvipdfm-x in TeX Live SVN: r47469.
-
I think that an attached patch XeTeX_ext.c.diff fixes the problem. There are no crashes for badutf.tgz and x3badfile.zip Best, Akira
-
The following comment may not help, sorry. It seems that the actual crash occurs at or near the line 8348 in xetex.web: cur_cmd:=eq_type(cur_cs); cur_chr:=equiv(cur_cs); Akira
-
I have just committed a change that should fix this, afaics -- if the driver fails, xetex should exit with a new status of 4 (to distinguish this, fwiw, from the existing TeX-level error statuses). Thanks a lot. I have imported in the TeX Live: r44834. I think the actual exit code is 1 by if ( ( history != 0 ) && ( history != 1 ) ) uexit ( 1 ) ; else uexit ( 0 ) ; I have confirmed on W32, by forcing an error in xdvipdfmx, that xetex exits with the code 1. Many thanks, Akira
-
Type1 fonts as native fonts are almost useless. They can be used only in cases with...
1