Re: [XeTeX] 64-bit binaries
Dear Bobby, On 2021/06/05 2:36, Bobby de Vos wrote: TeX Live and W32TeX differs in directory structure and versions of binaries. Please use files in TLW64 folder for TeX Live and don't use files in win64 folder. I am confused by this. I am currently using W32TeX as a minimal TeX installation [0] that is used by another application (so not TeX Live as installed by [1]). You can see from the update script [2] that I use that I download ... In the case of W32TeX, please use files in the folder win64. In the case of TeX Live, please use files in the folder TLW64. In W32TeX, binaries are latest ones, but large number of packages and fonts are missing. Best, Akira
Re: [XeTeX] 64-bit binaries
On 2021/06/03 5:01, Bobby de Vos wrote: I noticed that there are two download locations for 64 bit binaries mentioned at http://w32tex.org/ One is in a section called /64bit Windows binaries for TeX Live/ and links to https://ctan.org/tex-archive/systems/win32/w32tex/TLW64 The other is location is present in the various mirrors (such as Ring Server 1) in the win64 folder. Which location should I be getting 64 bit binaries from? TLW64 folder is for TeX Live. win64 folder is for W32TeX. TeX Live and W32TeX differs in directory structure and versions of binaries. Please use files in TLW64 folder for TeX Live and don't use files in win64 folder. Best, Akira
Re: [XeTeX] Adobe PDF, Adobe Acrobat/Reader, Microsoft Word, XeTeX, and (x)dvipdfm(x).
Dear Philip, On 2021/05/28 20:44, Philip Taylor wrote: Thank you Ulrike — in fact, I had just done that, but I learned as a side-effect that "only documents opened by `pdfopen' can be closed by `pdfclose'", which is something of a bummer in that almost all of my PDFs will have been opened either by the (x)dvipdfm(x) back-end of XeTeX, or by TeXworks ... pdfclose --help shows on Windows: --- Usage: pdfopen --file [--page ] pdfopen [--page ] Opens (at page if available) in Adobe Acrobat or Adobe Reader. pdfclose --file pdfclose Closes in Adobe Acrobat or Adobe Reader. pdfclose --all Closes all documents in Adobe Acrobat or Adobe Reader. Beware: only documents opened by `pdfopen' can be closed by `pdfclose'. Option: --rx : Prefer the server Adobe Reader X. --ax : Prefer the server Adobe Acrobat X. --rxi : Prefer the server Adobe Reader XI. --axi : Prefer the server Adobe Acrobat XI. --rxv : Prefer the server Adobe Reader XV. --axv : Prefer the server Adobe Acrobat XV. --r10 : Same as --rx. --a10 : Same as --ax. --r11 : Same as --rxi. --a11 : Same as --axi. --r15 : Same as --rxv. --a15 : Same as --axv. If you see a message 'Cannot contact a server.' you have to specify the DDE server name in a file `pdfddeservername.txt' which is in a directory where pdfdde.exe exists, --- Please see comments in bin/win32/pdfddeservername.txt and edit the file if necessary. Probably the default value will be AcroViewR20 I updated yeasterday as AcroViewR21 for the latest free Adobe Reader. In the case of non-free Adobe Acrobat, the name is such as AcroViewA20 If you have non-free Adobe Acrobat, and you do not know the DDE server name, try the following until you succeeds: AcroView AcroViewA10 AcroViewA11 AcroViewA15 AcroViewA17 AcroViewA18 AcroViewA19 AcroViewA20 AcroViewA21 Best, Akira
Re: [XeTeX] XeLaTeX for files using pstricks
Dear Herbert, On 2021/04/24 5:55, Herbert Schulz wrote: The xelatexTR engine used by those files does exactly that. Many thanks. I should have noticed TR. Thanks, Akira
Re: [XeTeX] XeLaTeX for files using pstricks
On 2021/04/24 5:55, Ulrike Fischer wrote: with -i dvipdfmx-unsafe.cfg it compiles but the output is wrong. Some of the red lines aren't where they should be if one compare with the dvips output. But they are also wrong in tl2020, so I don't think that it is related to the changes in the binaries. PSTricks on XeTeX is a limited subset of PSTricks for dvi -->ps -->pdf. It is known that rather many examples do not work with XeTeX. If possible, it is recommended in the XeTeX case to embed images obtained by dvi --> ps --> pdf. Best, Akira
Re: [XeTeX] XeLaTeX for files using pstricks
Dear Roussanka Loukanova, On 2021/04/24 3:58, Roussanka Loukanova wrote: I'm attaching the sources of the pdfs. I was hesitant because of the additional sty files, which are not in TeX Live, and I do not know what is the practice in this case. I'm attaching them too. In TeX Live 2021, PSTricks for XeTeX is not supported in the default case for a security problem. (Any program can be executed by a malicious source on Windows if we allow it.) An option -output-driver="xdvipdfmx -i dvipdfmx-unsafe.cfg -E -q" enables the PSTricks for XeTeX: Try xelatex -output-driver="xdvipdfmx -i dvipdfmx-unsafe.cfg -E -q" rotating_trees-xelatex.tex Best, Akira
Re: [XeTeX] xetex, pstricks, dvipdfmx-unsafe.cfg
Dear Bruno, On 2021/03/19 7:40, Bruno Voisin via XeTeX wrote: With up-to-date pretest MacTeX-2021 I get the same as Herbert, and cannot reproduce your output: Sorry, I'm not so familiar with Ghostscript and I don't understand the difference. The reported security problem is for Windows, so I think it is OK. In the latest dvipdfmx.cfg, I added -dSAFER explicitly in order not to allow dangerous sources on Windows. Best, Akira
Re: [XeTeX] xetex, pstricks, dvipdfmx-unsafe.cfg
Dear Herbert,
On 2021/03/17 21:43, Herbert Schulz wrote:
With the pstricks transparency example I supplied xelatex alone---default
parameters for xdvipdfmx alone, -dALLOWTRANSPARENCY, no need for forcing
-dNOSAFER---works just fine.
Probably you are using an old dvipdfmx.cfg.
Or using an old Ghostscript in which NOSAFER is the default.
For the new one in TL2021 pretest, with gs-9.53.3, where SAFER mode
is the default, I can confirm on W32:
xdvipdfmx TransparencyTest.xdv
Error: /invalidfileaccess in --run--
Operand stack:
(c:/usr/SVN/tlmaster3/texmf-dist/dvips/pstricks/pstricks.pro) (r)
Execution stack:
%interp_exit .runexec2 --nostringval-- run --nostringval-- 2
%stopped_push --nostringval-- run run false 1 %stopped_push 2022
1 3 %oparray_pop 2021 1 3 %oparray_pop 2009 1 3
%oparray_pop 1865 1 3 %oparray_pop --nostringval-- %errorexec_pop
.runexec2 --nostringval-- run --nostringval-- 2 %stopped_push
--nostringval-- 2022 1 3 %oparray_pop run
Dictionary stack:
--dict:763/1123(ro)(G)-- --dict:0/20(G)-- --dict:77/200(L)--
Current allocation mode is local
Last OS error: Permission denied
Current file position is 66
Apparently it is needed to read pstricks.pro given by fullpath,
that is impossible in SAFER mode.
If I use the new additional dvipdfmx-unsafe.cfg:
xdvipdfmx -i dvipdfmx-unsafe.cfg TransparencyTest.xdv
WARNING: .setopacityalpha is deprecated (as of 9.53.0) and will be
removed in a future release
See .setfillconstantalpha/.setalphaisshape for the improved solution
WARNING: .setopacityalpha is deprecated (as of 9.53.0) and will be
removed in a future release
See .setfillconstantalpha/.setalphaisshape for the improved solution
The resulting TransparencyTest.pdf is fine.
Thanks,
Akira
Re: [XeTeX] xetex, pstricks, dvipdfmx-unsafe.cfg
Dear Herbert, On 2021/03/16 22:31, Herbert Schulz wrote: Xelatex seems to compile the enclosed document, which uses transparency with pstricks, fine now (aside from some gs 9.53.3 warnings about opacity being dpericated). But latex->dvipdmx fails. Is that expected? Indeed. PSTricks is not supported in latex --> dvi --> dvipdfmx. PSTricks on [x]dvipdfmx needs XeTeX: xelatex -no-pdf TransparencyTest.tex dvipdfmx -i dvipdfmx-unsafe.cfg TransparencyTest.xdv or xdvipdfmx -i dvipdfmx-unsafe.cfg TransparencyTest.xdv Best, Akira
Re: [XeTeX] Ghostscript 9.53
On 2021/02/22 2:44, Richard Koch wrote: Jean-Francois sent the source for his sample xetex program which caused a hang of xetex with multiple complaints of the form WARNING: .setopacityalpha is deprecated (as of 9.53.0) and will be removed in a future release See .setfillconstantalpha/.setalphaisshape for the improved solution Since I make the TeX Live 2021 binaries for Macs (Arm and Intel) and since I made new binaries two days ago from the latest sources, I could add those binaries to a copy of TeX Live 2020, rebuild formats, and then test his source. I'm sorry to report that the bug still exists, at least on the Mac. Probablly the example does not work still in XeTeX in TeX Live 2021. Anyway, PSTricks on XeTeX is a limited subset of the full PSTricks on dvi+dvips. It is known that there are fairly many examples of PSTricks which do not work on XeTeX. In such cases, please obtain an image by PSTricks+dvi+dvips+ps2pdf, and embed the image by XeTeX. Thanks, Akira
Re: [XeTeX] Ghostscript 9.53
On 2021/02/21 2:55, jfbu wrote: It seems xelatex compilation stalls and possibly never completes on some documents which I have been given and use pstricks. Here is a shortened console output xdvipdfmx in TeX Live 2020 does not fully support gs-9.53.3. I believe that it is already fixed in the new binary which will be in TeX Live 2021. Thanks, Akira
Re: [XeTeX] asterisk in font name - font error
On 2020/12/15 0:31, Ulrike Fischer wrote: It doesn''t work for me in windows. With plain + xetex I still get error because of the * kpathsea:make_tex: Invalid filename `Jost*', contains '*' Loading the font by file name works fine: \font\test="[Jost-500-Medium.otf]" Recent installer adds $LOCALAPPDATA/Microsoft/Windows/Fonts// for OSFONTDIR on Windows. Thus XeTeX can find font there if used by file name. In this case, non-ascii characters in file path are allowd. However, in order to use by font name, users should add c:/Users/username/AppData/Local/Microsoft/Windows/Fonts in fonts.conf, if the computer is not used by multiusers. My port of fontconfig for Windows does not allow non-ascii characters in file path. So if "username" contains non-ascii characters, it should be replaced by a symbolic link which contains ascii characters only. My port of fontconfig for Windows does not allow config dir for users for simplicity. So in multiuser system, there is no way to use fonts in .../AppData/Local/Microsoft/Windows/Fonts by font name. Anyway it is best to install fonts in c:/Windows/Fonts for all users. Best, Akira
Re: [XeTeX] Colour specials for XeTeX
Dear Philip, Is there any way (perhaps through a command-line option to XeTeX) that one could obtain those most usedful diagnostics using XeTeX in "standard" mode xetex -output-driver="xdvipdfmx -E" file.tex or xetex -output-driver="xdvipdfmx -v -E" file.tex (verbose) Default is "xdvipdfmx -q -E" (quiet). Best, Akira
Re: [XeTeX] Colour specials for XeTeX
Dear Philip,
xdv2pdf was a driver for MacOS by Jonathan.
If you use -no-pdf option and apply xdvipdfmx to a created
.xdv file, you can see messages like
xdvipdfmx:warning: xetex-style \special{x:rulecolorpush} is
not supported by this driver;
I don't know details, perhaps \special{x:something}
may not be supported in xdvipdfmx except for a few ones.
Best,
Akira
Re: [XeTeX] \font "":color=FFFFFF produces black, not white glyphs \font "":color=FFFFFF produces black, not white glyphs, re-visited
Hi Jonathan,
What's unclear to me -- because I don't remember, if I ever
knew -- is quite why the driver wanted to treat FF(FF)
specially, and therefore what the implications of removing that
behavior might be.
In dvi.c, 0x was used as a sign that the font is not
colored, I don't know why. So opacity range was 0-254.
I simply introduced rgba_used to indicate the font is colored or not:
--- trunk/Build/source/texk/dvipdfm-x/dvi.c2020-05-26 00:59:53 UTC (rev
55283)
+++ trunk/Build/source/texk/dvipdfm-x/dvi.c2020-05-26 13:45:50 UTC (rev
55284)
@@ -147,6 +147,10 @@
spt_t size;
int source; /* Source is either DVI or VF */
uint32_t rgba_color;
+ uint8_t rgba_used;
+/* Indicates that rgba_color is used or not.
+ * It enables full range of opacity: 0-255.
+ */
int xgs_id; /* Transparency ExtGState */
struct tt_longMetrics *hvmt;
int ascent;
@@ -180,6 +184,10 @@
intused;
intnative; /* boolean */
uint32_t rgba_color; /* only used for native fonts in XeTeX */
+ uint8_t rgba_used;
+/* Indicates that rgba_color is used or not.
+ * It enables full range of opacity: 0-255.
+ */
uint32_t face_index;
intlayout_dir; /* 1 = vertical, 0 = horizontal */
intextend;
@@ -554,6 +562,7 @@
def_fonts[num_def_fonts].used= 0;
def_fonts[num_def_fonts].native = 0;
def_fonts[num_def_fonts].rgba_color = 0x;
+ def_fonts[num_def_fonts].rgba_used = 0;
def_fonts[num_def_fonts].face_index = 0;
def_fonts[num_def_fonts].layout_dir = 0;
def_fonts[num_def_fonts].extend = 0x0001; /* 1.0 */
@@ -599,6 +608,7 @@
def_fonts[num_def_fonts].layout_dir = 0;
def_fonts[num_def_fonts].rgba_color = 0x;
+ def_fonts[num_def_fonts].rgba_used = 0;
def_fonts[num_def_fonts].extend = 0x0001;
def_fonts[num_def_fonts].slant = 0;
def_fonts[num_def_fonts].embolden= 0;
@@ -606,8 +616,10 @@
if (flags & XDV_FLAG_VERTICAL)
def_fonts[num_def_fonts].layout_dir = 1;
- if (flags & XDV_FLAG_COLORED)
-def_fonts[num_def_fonts].rgba_color = get_unsigned_quad(dvi_file);
+ if (flags & XDV_FLAG_COLORED) {
+def_fonts[num_def_fonts].rgba_color = get_unsigned_quad(dvi_file);
+def_fonts[num_def_fonts].rgba_used = 1;
+ }
if (flags & XDV_FLAG_EXTEND)
def_fonts[num_def_fonts].extend = get_signed_quad(dvi_file);
@@ -1492,8 +1504,9 @@
def_fonts[i].point_size);
}
loaded_fonts[font_id].rgba_color = def_fonts[i].rgba_color;
-/* Opacity: 0xff is fully opaque. */
-if ((loaded_fonts[font_id].rgba_color & 0xff) == 0xff) {
+loaded_fonts[font_id].rgba_used = def_fonts[i].rgba_used;
+/* if rgba_used == 0, not a colored font */
+if (loaded_fonts[font_id].rgba_used == 0) {
loaded_fonts[font_id].xgs_id = -1;
} else {
pdf_obj *xgs_dict;
@@ -1716,7 +1729,7 @@
yloc[i] = get_buffered_signed_quad();
}
- if (font->rgba_color != 0x) {
+ if (font->rgba_used == 1) {
pdf_color color;
pdf_color_rgbcolor(,
(double)((unsigned char)(font->rgba_color >> 24) & 0xff) / 255,
@@ -1787,7 +1800,7 @@
glyph_width, font->font_id, -1);
}
- if (font->rgba_color != 0x) {
+ if (font->rgba_used == 1) {
if (font->xgs_id >= 0) {
graphics_mode();
pdf_dev_grestore();
Thanks,
Akira
Re: Polyglossia: renaming figurname stopped working
This happened after the recent upgrade of the Debian packages to texlive
2018.20190227-2. Any suggestions?
Here it seems to work by the following change:
\begin{document}
\gappto\captionspolish{\renewcommand{\figurename}{Il.}}
--->
\gappto\captionspolish{\renewcommand{\figurename}{Il.}}
\begin{document}
that is, writing
\gappto\captionspolish{\renewcommand{\figurename}{Il.}}
in the preamble.
Best,
Akira
Re: [XeTeX] [tex-k] e-TeX \lastnodetype initialization problem
Hi Hironobu, A patch for * etexdir/tex.ech * pdftexdir/pdftex.ch * xetexdir/xetex.ch is attached. Many thanks. Applied in r47096. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pst-fill boxfill failure when compiling with XeLaTeX
Dear Daniel, Indeed. I am very happy with and thankful for all the hard work ... Almost all of pstricks on XeTeX was done by Herbert Voss, S. Miyata, and Denis Girou. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pst-fill boxfill failure when compiling with XeLaTeX
Dear Daniel, Indeed. I am very happy with and thankful for all the hard work you and others have done to make quite a large portion of pstricks available in the XeTeX environment. In the environment of the very recent graphics and graphics-def, a large portion of pstricks on XeTeX may not work. I expect that it will be improved soon. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pst-fill boxfill failure when compiling with XeLaTeX
Dear Daniel, I have been having trouble with the pst-fill package's "boxfill" (tiling) for some time when compiling with XeLaTeX. pstricks for XeTeX is a limited subset of the full set for dvips. Please consider it is happy if pstricks for XeTeX works ok. If you need graphics by pstricks in XeTeX, please create a pdf image for the graphics in other process by dvips + ps2pdf, and include the image by XeTeX. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX/xdvipdfmx: PDF text copying with double encoded fonts
Hi Jiang, Thank you for building this. I'm not familiar with w32tex, can users replace the same file from their TexLive 2017 installation? Yes, I think that dvipdfmx.dll in the TeX Live 2017 can be replaced by the new dvipdfmx.dll. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX/xdvipdfmx: PDF text copying with double encoded fonts
Hi Jiang, So there might still be value to fix the ToUnicode map, don't you think? I have an experimental patch at https://github.com/jjgod/texlive/commit/f01557d549aaf27584f624fa540f6b4b05349bf3 in case you would like to build a w32tex binary for him to test. I confirmed that after applying your patch, ToUnicode map becomes correct, and copy is fine for the example with \XeTeXgenerateactualtext=0. Interested users can replace binary for 32bit windows bin/win32/dvipdfmx.dll by downloading: http://www.w32tex.org/toolsw32/dvipdfmx.dll Please commit your patch after Karl starts 2018/dev. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX/xdvipdfmx: PDF text copying with double encoded fonts
% luatex-plain test.tex
% luatex-plain is in the ConTeXt
\font\1="SourceHanSansSC-Regular.otf"
\font\2="SourceHanSerifSC-Regular.otf"
\font\3="msyh.ttf"
{\1 孤立子 ABC} \par
{\2 孤立子 ABC} \par
{\3 孤立子 ABC} \par
\bye
In the case of "luatex-plain" in the ConTeXt package,
copy was OK by Adobe Reader DC for all
fonts (1), (2), and (3).
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX/xdvipdfmx: PDF text copying with double encoded fonts
Dear Jiang,
There has been a report
https://github.com/CTeX-org/ctex-kit/issues/286
% XeTeX
\XeTeXgenerateactualtext=1
\font\1="Source Han Sans SC"
\font\2="Source Han Serif SC"
\font\3="Microsoft YaHei"
{\1 孤立子 ABC} \par
{\2 孤立子 ABC} \par
{\3 孤立子 ABC} \par
\bye
I tested the above example on Windows 7.
Used fonts are
(1) SourceHanSansSC-Regular.otf
(2) SourceHanSerifSC-Regular.otf
(3) msyh.ttf
I'm afraid that I don't understand the problem correctly.
My Results:
In the case of \XeTeXgenerateactualtext=0, copy
is wrong for "立" in fonts (1) and (2), in Adobe Reader DC.
In the case of \XeTeXgenerateactualtext=1, copy
is OK in Adobe Reader DC for all fonts (1), (2) and (3).
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xetex.def
Dear Joseph,
Following a bug report for (x)dvipdfmx box scaling, we are talking a
look at xetex.def and dvidpfmx.def to fix that and related issues. This
raises a question: what is the reason for having two .def files here. A
quick test suggests that XeTeX (xdvipdfmx) can happily use dvipdfmx.def
with the exception of a few lines at the end of the file: those could
easily be made conditional.
I'm not familiar with the drivers, but I think that the independent
xetex.def is definitely needed.
I think that images png, jpg, pdf, are efficiently embedded in XeTeX,
probably by using primitives, while dvipdfmx requires an external
program extractbb to obtain sizes of the images.
For example,
%
% xelatex test.tex(xetex.def)
%
\documentclass[12pt]{article}
\usepackage{graphicx}
\usepackage{pdfpages}
\begin{document}
\includepdf[pages={1-9}]{xtst.pdf}
\end{document}
is far faster than
%
% xelatex test.tex (dvipdfmx.def)
%
\documentclass[12pt,dvipdfmx]{article}
\usepackage{graphicx}
\usepackage{pdfpages}
\begin{document}
\includepdf[pages={1-9}]{xtst.pdf}
\end{document}
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] error: can't allocate region with xelatex
I have tested tcsh, ksh and bash and all fail to show the problem. It seems to depend on the version of xelatex.fmt. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] error: can't allocate region with xelatex
I encountered the following situation with xelatex. $ echo x | xelatex \\showthe\\everyjob This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) In r43113 in TeX Live SVN, I have changed texmfmp.c a little: --- texmfmp.c.origMon Nov 14 16:21:07 2016 +++ texmfmp.cWed Feb 01 13:27:04 2017 @@ -2818,6 +2818,8 @@ unsigned bytesToWrite = 0; poolpointer len, i, j; string name; + if (strstart[s + 1 - 65536L] < strstart[s - 65536L]) +return NULL; len = strstart[s + 1 - 65536L] - strstart[s - 65536L]; name = xmalloc(len * 3 + 1); /* max UTF16->UTF8 expansion (code units, not bytes) */ in order to avoid the crash. The change must not give bad effects. It is not a fix but a stopgap for the problem. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] error: can't allocate region with xelatex
I encountered the following situation with xelatex.
$ echo x | xelatex \\showthe\\everyjob
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016)
It seems that in the given example,
s = 0 and len < 0 in the following:
/* texmfmp.c */
2815: string
2816: gettexstring (strnumber s)
2817: {
2818: unsigned bytesToWrite = 0;
2819: poolpointer len, i, j;
2820: string name;
2821: len = strstart[s + 1 - 65536L] - strstart[s - 65536L];
2822: name = xmalloc(len * 3 + 1); /* max UTF16->UTF8 expansion
2823: (code units, not bytes) */
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [tex-live] fc-cache documentation ?
Dear Philip, [I]f you find a delay of time, run fc-cache -v. If messages invalid cache file: ... are shown, run fc-cache -v once more. May I ask if, since this discussion last took place (September 2016) there has been any progress in resolving the underlying problem ? There has been no progress in that. I think that probably a cache file to be renamed is not closed when requested from the XeTeX itself, thus it cannot be renamed on Windows. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Random number primitives
Dear Joseph, - \(pdf)uniformdeviate - \(pdf)normaldeviate - \(pdf)randomseed - \(pdf)setrandomseed (LuaTeX drops the 'pdf' part of the names.) H. Kitagawa, the author of eptex, has added \pdfuniformdeviate \pdfnormaldeviate \pdfrandomseed \pdfsetrandomseed in eptex and euptex (r42506 in TL). Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] updating xe(la)tex?
Dear Leon, Is there any possibility to update xe(la)tex in TL 2016 from the development sources anytime soon? The sources in the TeX Live repository are synced with the development sources. You can update xetex by compiling it yourself. For new binaries in TeX Live, wait for the next TL 2017. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [tex-live] fc-cache documentation ?
Dear Philip,
The suggestion by Akira-san resolves the problem :
It seems that I was wrong:
By experiments, I found that the renaming,
cachefile.NEW --> cachefile, almost always
fails if executed from the XeTeX binary even
in a user's writable directory.
Thus if you find a delay of time, run
fc-cache -v.
If messages
invalid cache file: ...
are shown, run
fc-cache -v
once more.
--- related function ---
FcBool
FcAtomicReplaceOrig (FcAtomic *atomic)
{
#ifdef _WIN32
unlink ((const char *) atomic->file);
/* fails always if executed from the XeTeX binary */
#endif
if (rename ((char *) atomic->new, (char *) atomic->file) < 0)
return FcFalse;
return FcTrue;
}
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to reduce terminal output from xelatex?
Hi David,
> xelatex -max-print-line=2048 -c-style-errors -interaction=batchmode
> "\def\istwocol{1} \input{./tmpmyfile.tex}"
The option -max-print-line does not exist. The env. variable
max_print_line can be used:
max_print_line=2048 xelatex -c-style-errors -interaction=...
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX with new Graphite engine?
Dear Lorna, I was thinking I had seen a message that Jonathan had updated XeTeX to use the newest Graphite engine and that someone else had built a Windows binary. XeTeX win32 in TeX Live 2016 pretest is built with Graphite2 1.3.8. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Hyphenation of strings of more than 63 characters
I have just pushed a new experimental branch named "max-hyph-len" to the xetex repository. The changes here implement a new integer parameter \XeTeXhyphenatablelength Users of windows can test xetex-0.6 by obtaining a 32bit binary: http://members2.jcom.home.ne.jp/wt1357ak/xetex-6-w32.zip It may run on TeX Live 2015. I'll remove the file in due time. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [texworks] Overfull boxes return status of 0 in XeTeX
Dear Philip, As Stefan says: SL> However, it can be worked around relatively easily by manually SL> opening the console (which should then remain open until closed manually). I think it is best to open the console window manually by CTRL+\. Then the console window is not closed, and you can jump to errors, warnings, or badboxes. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] potential new feature: \XeTeXgenerateactualtext
SumatraPDF on windows 10 was similar to Foxit Reader - using the glyph stream instead of the actualtext - in case of devanagari text. Thanks a lot for correcting my mistake. I confirmed by using accsupp package by Heiko that SumatraPDF on windows does not use the ActualText for "select, copy", but use the glyph stream. Thank you again ShreeDevi Kumar. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] potential new feature: \XeTeXgenerateactualtext
Dear ShreeDevi Kumar, SumatraPDF on windows 10 was similar to Foxit Reader - using the glyph stream instead of the actualtext - in case of devanagari text. Thanks a lot for correcting my mistake. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] potential new feature: \XeTeXgenerateactualtext
Ah, right... as there are no spaces between the kanji, they'll end up in the same text object. If I set, \XeTeXlinebreaklocale="ja-JP" \XeTeXlinebreakskip=0pt plus 1pt minus 0pt even an individual kanji can be 'selected', 'copied' and 'pasted', even in the case of Adobe Acrobat XI Pro. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] potential new feature: \XeTeXgenerateactualtext
Using Akira-san's "actest.pdf" as sample, Adobe Acrobat Pro 7.1 allows me to select only half of the text whereas Adobe Reader DC allows me to select it all; neither allows me to select individual kanji. I have found that 'SumatraPDF' for windows can select, copy even an individual kanji in XeTeX 0.5 with \XeTeXgenerateactualtext=1. SumatraPDF is better than Adobe Acrobat XI Pro with respect to /ActualText. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] potential new feature: \XeTeXgenerateactualtext
The code for the \XeTeXgenerateactualtext feature (it's an integer parameter; set it to 1 to get ActualText added to the PDF, for better copy/paste and search in Acrobat) is now on sourceforge, in an "actualtext" branch, for anyone who wants to try building and experimenting with it. Windows 32bit binary for tests based on Jonathan's 845506 is available in: http://members2.jcom.home.ne.jp/wt1357ak/xetex-ac-txt.zip I'll remove the file in due time. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] potential new feature: \XeTeXgenerateactualtext
Hi Jonathan, Akira, if you could check that the patch seems OK, that would be great. I've not really looked at dvipdfm-x code in a long time. I haven't pushed this it to TL yet, as it's all rather experimental, but I hope we can safely include it for TL'16. Thanks very much. I think it is OK, so I installed as r39835. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] Why XeTeX runs are non-deterministic?
Why is it so? And what generates this difference? The question has been lingering on SX for a while http://tex.stackexchange.com/questions/292675/why-does-xelatex-produce-different-files-from-the-same-deterministic-sources but with no reasonable answer! I wrote a possible answer on SX. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] New feature planned for xetex
Dear Philip, Unable to update the static FcBlanks: 0x0600 Unable to update the static FcBlanks: 0x0601 Unable to update the static FcBlanks: 0x0602 Unable to update the static FcBlanks: 0x0603 Unable to update the static FcBlanks: 0x06dd Unable to update the static FcBlanks: 0x070f Unable to update the static FcBlanks: 0x2028 Unable to update the static FcBlanks: 0x2029 Unable to update the static FcBlanks: 0xfff9 Unable to update the static FcBlanks: 0xfffa Unable to update the static FcBlanks: 0xfffb I think those are messages from the "old" fontconfig, in TeX Live 2014 or former ones. I expect that the new xetex.exe probably runs on TeX Live 2015. (1) save the original 4 files dvipdfmx.dll, kpathsea621.dll, xdvipdfmx.exe, xetex.exe (2) copy all 6 files to bin/win32 to test the new feature. (xelatex.exe is the same one as that in 2015, so it is not necessary to copy it.) After tests, copy saved 4 files to bin/win32 to recover the original TeX Live 2015. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Graphite vulnerability
Will the next TeX Live distro's version of xetex use >= v.1.3.5? Yes, TeX Live 2016 will use Graphite2-version >= 1.3.5. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] New feature planned for xetex
Currently, this feature is implemented only in the "contextual-space" branch of the code at sourceforge; anyone interested in testing it will need to check out and build the code from there. I have tried to build a binary for win32: http://members2.jcom.home.ne.jp/wt1357ak/xetex-ctx-spc.zip I don't yet test myself. I'll remove this file in due time. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX 0.99994 and xeCJK
Dear Jonathan, Akira, if you could update your build for people to test, that would be great -- thanks! I uploaded the new binary for windows. It will be available after a day or so. Two tests by Qing were OK. It seems that xeCJK works. However I was not able to create a format file for ConTeXt mkii. See an attached cont-en.log. Best, Akira cont-en.log Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] not enough \XeTeXcharclass registers
Dear Philip, Regret this will take some time to upload to Dropbox; it is circa 1Gb in size. I may not be able to test 1Gb size file. Please recover the old binaries. Sorry. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] not enough \XeTeXcharclass registers
Dear Philip, Please try copy xdvipdfmx.exe extractbb.exe in the bin/win32 dir. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] not enough \XeTeXcharclass registers
Dear Philip, (./Master.tex (./B5-Master.tex A5-Master processing is now complete [1] ) ) Error -1073741515 (driver return code) generating output; file ../Dynamic-content/Master.pdf may not be valid. SyncTeX written on ../Dynamic-content/Master.synctex.gz. Transcript written on ../Dynamic-content/Master.log. There may be a bug in the dvipdfmx.dll. Is it possible for me to study Master.pdf? Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] not enough \XeTeXcharclass registers
Some interesting (and new, and unexpected) diagnostics, Akira-san; as far as I can tell, no PDF was produced : You have to replace "all" included binaries, by saving the old ones. Note that size of xdvipdfmx.exe, which is a wrapper of dvipdfmx.dll, is 1536 bytes. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX-MNWE.zip now uploaded (was: not enough \XeTeXcharclass registers)
Dear Philip,
To produce the alternative error message, uncomment % \end at line 116
of B5-Master.tex
In this case, the new XeTeX worked fine here:
--
(SUSY)# xetex --synctex=1 --output-dir=../Dynamic-content Master.tex
This is XeTeX, Version 3.14159265-2.6-0.3 (TeX Live 2016/W32TeX/dev)
(preloaded format=xetex)
restricted \write18 enabled.
entering extended mode
(./Master.tex (./B5-Master.tex A5-Master processing is now complete [1] ) )stdin
-> ../Dynamic-content/Master.pdf
[1]
1388 bytes written
Output written on ../Dynamic-content/Master.pdf (1 page).
SyncTeX written on ../Dynamic-content/Master.synctex.gz.
Transcript written on ../Dynamic-content/Master.log.
--
In the case of full B5-Master.tex, XeTeX complains that the image
'../Images/HMD/PDF/image-12-green-walk-sprivers-larkin.pdf' does not exist:
--
(SUSY)# xetex --synctex=1 --output-dir=../Dynamic-content Master.tex
This is XeTeX, Version 3.14159265-2.6-0.3 (TeX Live 2016/W32TeX/dev)
(preloaded form
at=xetex)
restricted \write18 enabled.
entering extended mode
(./Master.tex (./B5-Master.tex A5-Master processing is now complete
(./Captions.tex) (./Image-float.tex) (./Catalogue.tex (./collating-sequence.tex
) (./XML-Elements-CW.tex XML-Elements-CW processing complete)
(./XML-Elements-MA.tex XML-Elements-MA processing complete)
(./XML-Elements-PT.tex XML-Elements-PT processing complete)
(./XML-Elements-Shared.tex XML-Elements-Shared processing complete)
(c:/usr/local/share/texmf-dist/tex/eplain/eplain.tex)
(c:/usr/local/share/texmf-dist/tex/plain/graphics-pln/miniltx.tex)
(c:/usr/local/share/texmf-dist/tex/latex/graphics/color.sty
(c:/usr/local/share/texmf-dist/tex/latex/config/color.cfg)
(c:/usr/local/share/texmf-dist/tex/xelatex/xetex-def/xetex.def
(c:/usr/local/share/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(c:/usr/local/share/texmf-dist/tex/generic/oberdiek/ltxcmds.sty
(./Prelims.tex (../Dynamic-content/Master.aux) [1] [2] [3] [4]
(../Dynamic-content/Master.toc
\tocentry {T A B L E\ \ \ O F\ \ \ C O N T E N T S}{\hlidxpage{}{5}}
(../Dynamic-content/TOC.aux About to process TOC.aux))) (./Inline-images.tex)
(./XML-list.tex [5] (./XML/Prelims/Foreword.xml
(../Dynamic-content/Foreword.aux About to process Foreword.aux)) [6stdin ->
../Dynamic-c
ontent/Master.pdf
[1
xdvipdfmx:warning: Version of PDF file (1.6) is newer than version limit
specification.
xdvipdfmx:warning: pdf_open: Not a PDF 1.[1-5] file.
xdvipdfmx:warning: Trying to include PDF file which has newer version number
than output
PDF: 1.5.
][2][3
xdvipdfmx:warning: Version of PDF file (1.6) is newer than version limit
specification.
xdvipdfmx:warning: pdf_open: Not a PDF 1.[1-5] file.
xdvipdfmx:warning: Trying to include PDF file which has newer version number
than output
PDF: 1.5.
][4][5][6]
(./XML/Chapters/1.xml) [7][7] (./XML/Chapters/2.xml
Indexing "Gladys Hook" as [Hook,~Gladys]
Indexing "Diamond Field" as [Diamond Field]
Indexing "Hazel Street" as [Hazel Street] Indexing "1934" as [1934]
Indexing "Jasper Hubbard" as [Hubbard,~Jasper] Indexing "1923" as [1923]
Indexing "Horsmonden" as [Horsmonden] Indexing "Matfield" as [Matfield]
Indexing "1953" as [1953] Indexing "Horsmonden" as [Horsmonden]
Indexing "Matfield" as [Matfield] Indexing "Brenchley" as [Brenchley]
Indexing "Lewis Heath" as [Lewis Heath]
Indexing "full-time workers" as [agriculture]
Overfull \hbox (330.57619pt too wide) in paragraph at lines 20--21
\bodyfont Well,|
Overfull \hbox (366.91896pt too wide) in paragraph at lines 20--21
[][][]\bodyfont Horsmonden|
Overfull \hbox (325.43459pt too wide) in paragraph at lines 20--21
\bodyfont was|
Indexing "Trixie Barr" as [Barr,~Trixie] Indexing "1920" as [1920]
Indexing "Schoolhouse Farm" as [Schoolhouse Farm] Indexing "1945" as [1945]
Overfull \hbox (203.21193pt too wide) in paragraph at lines 23--23
[][][]\bodyfont Trixie|
Overfull \hbox (195.3799pt too wide) in paragraph at lines 23--23
\bodyfont Barr|
Indexing "Jobey Crouch" as [Crouch,~Jobey]
Indexing "Fred Sinden" as [Sinden,~Fred]
Indexing "Schoolhouse Farm" as [Schoolhouse Farm] Indexing "baker" as [baker]
Indexing "Horsmonden" as [Horsmonden] Indexing "Weekes" as [Weekes]
Indexing "Goudhurst" as [Goudhurst]
Indexing "Margaret Weekes" as [Weekes,~Margaret]
Indexing "John Stevens" as [Stevens,~John] Indexing "grocers" as [grocers]
Indexing "laundry service" as [laundry service]
Overfull \hbox (178.07228pt too wide) in paragraph at lines 27--28
\bodyfont go|
Overfull \hbox (191.91017pt too wide) in paragraph at lines 27--28
\bodyfont shop-|
Overfull \hbox (189.8545pt too wide) in paragraph at lines 27--28
\bodyfont ping.|
Indexing "Chris Lambert" as [Lambert,~Chris]
Indexing "Schoolhouse Farm" as [Schoolhouse Farm]
Indexing "Horsmonden station" as [Horsmonden station]
Indexing "Fred Bromley" as [Bromley,~Fred]
Indexing "Goudhurst station" as [Goudhurst station]
Indexing "Staplehurst" as [Staplehurst] [8][8]
Indexing "Sheep Fair" as [Sheep Fair]
Re: [XeTeX] XeTeX-MNWE.zip now uploaded
Dear Philip, OK, many thanks for the explanation, Akira-san : presumably these messages indicate that I should take some action in order to eliminate them and allow the job to run to completion without warnings, but what action should I take ? The first type of messages will be eliminated in TeX Live 2015, or 2016. The second type of messages are due to not good fonts. Just ignore them. If you want not to see the second type of messages, xetex --output-driver="xdvipdfmx -q -E" ... ... works, -q means really quiet in the present TeX Live source of xdvipdfmx. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX-MNWE.zip now uploaded (was: not enough \XeTeXcharclass registers)
Dear Philip, I don't know why there are problems in your case. My mistake. I forgot to include an important DLL which you don't have. Please get once more: http://members2.jcom.home.ne.jp/wt1357ak/xetex-exp-w32.zip Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX-MNWE.zip now uploaded
Dear Philip, Unable to update the static FcBlanks: 0x0600 Unable to update the static FcBlanks: 0x0601 ... ... These messages come because of old fonts.conf for fontconfig. ][307]No Unicode mapping available: GID=308 No Unicode mapping available: GID=281 ... ... These messages are normal now, where xdvipdfmx is not in quiet mode by default in TeX Live to show some messages. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] not enough \XeTeXcharclass registers
I use XeTeX on a daily basis, Jonathan ('tho XeTeXcharclass far less
frequently) and would be happy to test your version on my production
suites, but in order to do so I would require a Win64 (or Win32) build.
You can test the new experimental XeTeX on win32 by
http://members2.jcom.home.ne.jp/wt1357ak/xetex-exp-w32.zip
The file will be removed in due time.
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] help with pgf xelatex issue
Dear Stefan, Some questions from the non-expert. I'm also a non-expert. The previous one is only an experiment. Sorry. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] help with pgf xelatex issue
Dear Stefan,
I filed a bug report, but nothing happend:
http://sourceforge.net/p/pgf/bugs/354/
The issue is related to pgf drivers, pgfsys-xetex.def and
pgfsys-dvipdfmx.def which is called by the former.
Your example works if you use the other driver: pgfsys-dvipdfm.def,
see below. However, don't expect that the way is always ok.
%
% xelatex
%
\documentclass{article}
%deceive the driver
\def\pdftexversion{140}
%use the old driver for dvipdfm
\def\pgfsysdriver{pgfsys-dvipdfm.def}
\usepackage{tikz}
\usetikzlibrary{tikzmark}
\begin{document}
x\pgfmark{tA}some text \pgfmark{tB} some text
\begin{tikzpicture}[remember picture]
\draw (0,0)node (A){A} rectangle (1,1)node (B){B};
\end{tikzpicture}
\begin{tikzpicture}[remember picture]
\draw (0,0)node {\pgfmark{nA}} rectangle (1,1)node {\pgfmark{nB}};
\end{tikzpicture}
\vspace{3cm}\centering
\begin{tikzpicture}[overlay,remember picture]
\draw[red,->] (0,0)--(pic cs:tA) (0,0)--(pic cs:tB);
\draw[blue,->](0,0)--(pic cs:nA) (0,0)--(pic cs:nB); %nB faulty
\draw[green,->](0,0)--(A) (0,0)--(B);
\end{tikzpicture}
\end{document}
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Support request for /Rotate in pdf
Hironobu-san, If not, is there any chance of adding rungs to shell_escape_commands list? I think there is no chance. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Support request for /Rotate in pdf
If some messages are prefered, the -q option may be removed: xdvipdfmx -E. Done in r38784. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Support request for /Rotate in pdf
We don't get any warnings in inclusion of pdf which has /Rotate: XeTeX says nothing, and xdvipdfmx says nothing because default output-driver is 'xdvipdfmx -q -E' in TL2015. I think this is harmful, because there is no chance for users to notice unrotated figures before they see output directly. At least in TL2014 xdvipdfms shows warning like "<< /Rotate 90 >> found. (not supported yet)" Jonathan had decided the default option of the driver xdvipdfmx to be '-q -E'. In TL 2014, the option -q (quiet) was not complete. In TL2015, the option -q is improved to be really quiet. If some messages are prefered, the -q option may be removed: xdvipdfmx -E. In this case, xdvipdfmx:warning: << /Rotate 90 >> found. (Not supported yet) is shown if /Rotate command is found. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Strange tikz behaviour with xetex
\documentclass{article}
\usepackage[cmyk]{xcolor}
\usepackage{tikz}
\usepackage{pgf}
\usetikzlibrary{fadings}
\usepackage{pgfpages}
\pgfpagesuselayout{resize to}[a4paper]
\begin{document}
\begin{tikzpicture}[remember picture,overlay]
\shade [top color=yellow,bottom color=red!50] (current page.north west)
rectangle (current page.south east);%
\end{tikzpicture}
\centerline{\Huge Hi Parsi\LaTeX{}}
\end{document}
It didn't produce the result of pdflatex! and it is so weird!
A similar output as that of pdflatex is obtained by xelatex
with the following for your special example.
Don't expect that it is applicable to other cases.
%
% xelatex
%
\documentclass{article}
\usepackage[cmyk]{xcolor}
%
%
\def\pdftexversion{140}
\def\pgfsysdriver{pgfsys-dvipdfm.def}
%
%
\usepackage{tikz}
\usepackage{pgf}
%
%
\makeatletter
\def\pgfsys@papersize#1#2{%
\pdfpageheight#2\relax%
\pdfpagewidth#1\relax}
\makeatother
%
%
\usetikzlibrary{fadings}
\usepackage{pgfpages}
\pgfpagesuselayout{resize to}[a4paper]
\begin{document}
\begin{tikzpicture}[remember picture,overlay]
\shade [top color=yellow,bottom color=red!50] (current page.north west)
rectangle (current page.south east);%
\end{tikzpicture}
\centerline{\Huge Hi Parsi\LaTeX{}}
\end{document}
--
Best regards,
Akira KAKUTO
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Strange tikz behaviour with xetex
Dear Vafa Khalighi,
\documentclass{article}
\usepackage{atbegshi}
\usepackage{tikz}
\AtBeginShipout{%
\AtBeginShipoutUpperLeft{%
\put(0,0){%
\tikz[remember picture, overlay]\shade[top color=blue!15, bottom
color=blue!80] (current page.north east) rectangle +(-5,-28);
}}}
\begin{document}
This is a test
\newpage
This is a test
\newpage
This is a test
\newpage
This is a test
\end{document}
You see that shaded rectangle on every single page of the document.
However, if you run xelatex, that rectangle does not appear on the
first and second pages. What is wrong?
Probably because pgfsys-xetex.def and/or pgfsys-dvipdfmx.def,
which are used by XeTeX, are incomplete.
I think there are other tikz examples in which XeTeX cannot
reproduce results by pdfTeX.
--
Best regards,
Akira KAKUTO
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX - PDF-x1a
The only way is to call xelatex -no-pdf ... and xdvipdfmx -V4 ... (default is PDF 1.5 but PDX/x-1a:2003 requires PDF 1.4). or xelatex -output-driver="xdvipdfmx -q -V 4 -E" foo.tex -- Best regards, Akira KAKUTO -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Strange issue with tanwin, arabxetex
Hi, Thanks for this suggestion. Unfortunately, utf simply prints the text as it finds it, so the first part of my file (see below) appears as I intended to use \textarabic usually, and to use \textarabic[utf] when it is necessary. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Strange issue with tanwin, arabxetex
Hi, The previous set up of arabxetex compiled with TeXlive 2014 handled this situation fine, but for some reason it is not working with TeXLive 2015. The arabxetex is not changed. Also I think that TECkit is not changed. I don't understand anything about the problem, but note that the xelatex kernel is different compared with that in TL 2014. -- Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Strange issue with tanwin, arabxetex
Hi,
When I compile this document, a tanwin in the unicode input (etc., خطًا) is
stripped out in the output.
I don't know arabxetex, but I think
\textarabic[utf]{Arabic in UTF-8}
can be a solution in this case.
That is, the option [utf] for the command \textarabic
when you input directly by UTF-8.
--
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] \(pdf)mdfivesum
Dear Joseph, I have a request for a new primitive in XeTeX, not directly related to typesetting by I think useful. To understand why I'm asking, a bit of background would be useful. The XeTeX in the latest TeX Live repository has a new primitive \pdfmdfivesum imported from pdfTeX. However the name and the implementation itself, are still volatile. Best regards, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] \(pdf)mdfivesum
Dear Joseph, However the name and the implementation itself, are still volatile. Best regards, Akira Thanks: hope it was not too much effort. \pdfmdfivesum in XeTeX is renamed as \mdfivesum in revision 37831, to be consistent with \strcmp and \shellescape. Best regards, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Is the colorshadow special yet supported?
Dear Marcel,
1. Is \special{x:colorshadow…} still not supported in TeXLive?
It is not implemented in xdvipdfmx:
{shadow, spc_handler_xtx_unsupported},
{colorshadow, spc_handler_xtx_unsupported},
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] datetime2 package and XeTeX
Dear Daniel, However, the package documentation states that this information is not available from XeTeX (see page 5 of version 1.00 documentation): ...unless you are using XELATEX in which case the seconds and time zone are omitted. (XELATEX doesn’t provide this information.) I don't know the new datetime2 package, but probably it depends on primitives such as \pdfcreationdate, and \pdffilemoddate. At present they are only in the pdfTeX engine. But it will not be hard for Khaled to introduce them in XeTeX, if he admits its usefulness, and if he has time. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] datetime2 package and XeTeX
I don't know the new datetime2 package, but probably it depends on primitives such as \pdfcreationdate, and \pdffilemoddate. At present they are only in the pdfTeX engine. eptex and euptex also have the primitives. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] geometry a3paper option error
When I use the a3paper size option or papersize={297mm,420mm} with the
geometry package, graphics seem to get cut off to the right of 210mm
from the left edge (where the A4 right paper edge should be).
http://tex.stackexchange.com/questions/157216/xetex-pstricks-larger-page-size-is-cropped-to-a4/157281#157281
That was already fixed in the present TeX Live 2014. Please update.
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wrong dimensions when using \XeTeXpicfile with CMYKimage
Maybe problems are in xdvipdfmx, FYI, the problem in xdvipdfmx was fixed in the TeX Live repository (r36287). Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wrong dimensions when using \XeTeXpicfile with CMYKimage
Dear Marcel, I have discarded my changes on 2015-02-09, and have recovered the previous XeTeX_pic.c and jpegimage.c, since sizes calculated by XeTeX were correct. Maybe problems are in xdvipdfmx, or cmyk colors in jpeg are not supported. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wrong dimensions when using \XeTeXpicfile with CMYKimage
Dear Marcel, Do you get the point? Or do you simply disagree? ;) I am not so familiar with bitmap images. I simply am satisfied because xetex became to show the same behavior as pdftex for jpeg image inclusion. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wrong dimensions when using \XeTeXpicfile with CMYKimage
Dear Marcel,
Thanks for the patch. I can confirm it works as expected.
However, when not specifying width nor height nor [x|y]scaled I think
the internal size (i.e., DPI setting) should be used.
I have confirmed that xelatex and pdflatex
give the same results for both of test1.tex
and test2.tex below.
Thus I assume that my changes in XeTeX are correct.
Thanks,
Akira
%
% test1.tex
% xelatex test1
% or
% pdflatex test1
%
\documentclass{article}
\usepackage{graphicx}
\begin{document}
\includegraphics[width=8cm]{test-cmyk300.jpg}
\includegraphics[width=8cm]{test-cmyk72.jpg}
\includegraphics[width=8cm]{test-rgb300.jpg}
\end{document}
%
% test2.tex
% xelatex test2
% or
% pdflatex test2
%
\documentclass{article}
\usepackage{graphicx}
\begin{document}
\includegraphics{test-cmyk300.jpg}
\includegraphics{test-cmyk72.jpg}
\includegraphics{test-rgb300.jpg}
\end{document}
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wrong dimensions when using \XeTeXpicfile with CMYK image
Dear Marcel,
At tex.stackexchange.com a moderator thinks it's a bug in xdvipdfmx.
If so, where to report it?
The bug may not be in xdvipdfmx, but it may be in XeTeX itself.
See below.
%
% xelatex test.tex
% sizes are calculated internally by xetex itself,
% and they are incorrect
%
\documentclass{article}
\usepackage{graphicx}
\begin{document}
\includegraphics[width=8cm]{test-cmyk300.jpg}
\includegraphics[width=8cm]{test-cmyk72.jpg}
\includegraphics[width=8cm]{test-rgb300.jpg}
\end{document}
%
% latex --shell-escape test.tex
% dvipdfmx test
% sizes are calculated by dvipdfmx (extractbb) and they are correct
%
\documentclass{article}
\usepackage[dvipdfmx]{graphicx}
\begin{document}
\includegraphics[width=8cm]{test-cmyk300.jpg}
\includegraphics[width=8cm]{test-cmyk72.jpg}
\includegraphics[width=8cm]{test-rgb300.jpg}
\end{document}
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] widowpenalty
Dear Alexey, I have recently installed Ubuntu 14.04, which includes XeTeX v. 3.14159265-2.6-0.1 (TeX Live 2014/Debian) and noticed that compiling my current project produces some incorrect line breaks. My investigations have shown that XeTeX seems to ignore the current \widowpenalty value (\clubpenalty is respected though). That was fixed by Khaled in the TeX Live repository. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xdvipdfmx.cfg
Dear Herbert, running this example with xelatex it will be fine if I disable the -dEPScrop option for the ghostscript run and use the alternative one: D rungs -q -dNOPAUSE -dBATCH -sPAPERSIZE=a0 -sDEVICE=pdfwrite -dCompatibilityLevel=%v -dAutoFilterGrayImages=false -dGrayImageFilter=/FlateEncode -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -sOutputFile='%o' '%i' -c quit The -dEPSCrop option is chosen for various reasonings in the case of eps image inclusion. Fortunately the case of PSTricks is independent of eps image inclusion. In r35693, I changed xdvipdfmx to use -sPAPERSIZE=a0 in the case of PSTricks. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xdvipdfmx.cfg
Dear Herbert,
In r35693, I changed xdvipdfmx to use -sPAPERSIZE=a0 in
the case of PSTricks.
Here the example by Germain Boyer works ok by using
the new xdvipdfmx:
\documentclass[a4paper,landscape,french,10pt]{article}
\usepackage{amssymb}
\usepackage{amsmath}
\usepackage{amsfonts}
\usepackage{fourier}
\usepackage[scaled=0.875]{helvet}
\renewcommand{\ttdefault}{lmtt}
\usepackage{fontspec}
\usepackage{graphicx}
\usepackage[french]{babel}
\usepackage{pst-plot}
\usepackage{geometry}
\usepackage{pdflscape}
\geometry{nohead,nofoot,left=1cm,right=1cm,top=1cm,bottom=1cm}
\begin{document}
\psset{linewidth=0.25mm , tickwidth=1pt , ticksize=-1mm 1mm ,
labelsep=1mm , arrowinset=0}
\begin{pspicture}(-5,-3)(20,7)
\psset{gridcolor=gray , gridwidth=0.15mm , gridlabels=0pt , subgriddiv=1}
\psgrid
\psaxes[linewidth=1pt]{-}(0,0)(-5,-3)(20,7)[$x$,0][$y$,90]
\uput[225](0,0){O}
\end{pspicture}
\end{document}
Thanks,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xdvipdfmx.cfg
Dear Herbert, In r35693, I changed xdvipdfmx to use -sPAPERSIZE=a0 in the case of PSTricks. In r35694, I recovered the previous xdvipdfmx, since it is not necessary to change it. It is better to write both of -dEPSCrop and -sPAPERSIZE=a0 in the D section in dvipdfmx.cfg: D rungs -q -dNOPAUSE -dBATCH -dEPSCrop -sPAPERSIZE=a0 -sDEVICE=pdfwrite -dCompatibilityLevel=%v -dAutoFilterGrayImages=false -dGrayImageFilter=/FlateEncode -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -sOutputFile='%o' '%i' -c quit Karl, please change dvipdfmx.cfg as above. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] Graphics overwriting text
Dear Johann, What is going on here? It may be possible that XeTeX failed to get size information of DSC_3936.JPG. It is helpful if you attach DSC_3936.JPG. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Gentium Book / Book Basic + TeX Ligatures = memory leak
Hi Khaled,
OK, this is an odd one. Here's my test document:
\documentclass{book}
\usepackage{fontspec}
\setromanfont{Gentium:Ligatures=TeX}
This not the correct syntax; Ligatures=TeX is a fontspec option and
should be passed to it: \setmainfont[Ligatures=TeX]{Gentium}.
I also think that the correct syntax is
\setromanfont[Ligatures=TeX]{Gentium Book Basic}.
However,
\setromanfont{Gentium Book Basic:Ligatures=TeX}
also works here and Ligature=TeX seems to be effective.
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Gentium Book / Book Basic + TeX Ligatures = memory leak
Hi Khaled,
However,
\setromanfont{Gentium Book Basic:Ligatures=TeX}
also works here and Ligature=TeX seems to be effective.
I don’t think it has any effect. The latest fontspec enables it by
default for main and sans fonts, though.
OK! Agreed. It was the default.
Thanks,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Gentium Book / Book Basic + TeX Ligatures = memory leak
Dear Simon,
\setmainfont{Gentium Basic:Ligatures=TeX} % Slow
It shows that the syntax is incorrect in the log file:
Unknown feature `Ligatures=TeX' in font `Gentium Basic'.
Unknown feature `Ligatures=TeX/OT' in font `Gentium Basic'.
Unknown feature `Ligatures=TeX/BI/OT' in font `Gentium Basic'.
Unknown feature `Ligatures=TeX/B/OT' in font `Gentium Basic'.
Unknown feature `Ligatures=TeX/I/OT' in font `Gentium Basic'.
But it should not be slow.
It may be a bug, which will hopefully be fixed by Khaled.
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Gentium Book / Book Basic + TeX Ligatures = memory leak
Dear Simon, % time xelatex -no-pdf test ... xelatex -no-pdf test 118.87s user 0.91s system 99% cpu 2:00.26 total 60x slowdown! Memory usage rises to 318M. Try once more, then you will have the same order of performance as that for the Gentium. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [texworks] Alternative location for output PDF files (and, ideally, all non-source files)
Dear Philip, What /is/ interesting, Akira-san, is that although this does indeed work perfectly, I can no longer re-compile by clicking on the Typeset icon in the PDF window; I have instead to click on the Typeset icon in the source window as it would seem that TeXworks no longer knows which file to re-compile in order to re-generate the PDF ... Confirmed! Thanks a lot. Best regards, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [texworks] Alternative location for output PDF files (and, ideally, all non-source files)
Dear Philip, This does indeed work as hoped, but it introduces two new problems, one of which I have solved (TeX no longer finds the generated auxiliary files -- solution : add parent directory of output directory and all sub-directories thereof to TEXINPUTS.xetex in texmf.cnf) and one of which is causing real problems : TeXworks no longer knows where the output file is, so no longer refreshes the previewer after a successful compilation. Can anyone advise how to work around this, please ? After a compilation, open the PDF in the output directory manually by TeXworks, since TeXworks cannot find the PDF as you experienced. And continue editing and compiling. Here preview window is refreshed by this way. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [texworks] Alternative location for output PDF files (and, ideally, all non-source files)
Dear Philip, This does indeed work as hoped, but it introduces two new problems, one of which I have solved (TeX no longer finds the generated auxiliary files -- solution : add parent directory of output directory and all sub-directories thereof to TEXINPUTS.xetex in texmf.cnf) If an output directory is defined by a user, the TeX library first searches for files to read in the output directory. Therefore files such as foo.aux should be read successfully with the default TEXINPUTS.xetex etc. In fact, it is working like this here. Please try once more with the default TEXINPUTS.xetex. Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeLaTeX generated pdf metadata
So although the producer fields provides evidence that I am using XeLaTeX, the creator field erroneously implies that I have typeset using LaTeX. Hence, there will be a high probability that my paper will either be removed by an automated server at arXiv.org or a human administrator. /Creator is the same as in the case of pdfLaTeX: /Creator(LaTeX with hyperref package)/Producer(pdfTeX-1.40.15). However /Producer is erroneously overwritten by xdvipdfmx in TeX Live 2014. Sorry for this feature. The latest XeLaTeX and xdvipdfmx in the repository give /Creator(LaTeX with hyperref package)/Producer(XeTeX 0.2). Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeLaTeX generated pdf metadata
Would it be possible that some qualified person could correct the
creator metadata output of XeLaTeX? I am currently using xelatex from
TeXLive 2014 running on Windows.
The /Producer cannot be changed in TeX Live 2014, as
I stated previously.
I think /Creator is right, but if you want to change it, try
\usepackage[xetex]{hyperref}
\hypersetup{pdfcreator={XeLaTeX with hyperref package}}
Best,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
[XeTeX] font license
I'd expect it to be looking at the fsType field in the OS/2 table: I have found by otfinfo that http://www.bpdb.gov.bd/bpdb/images/fonthelp/Nikosh.zip has fsType = 0x0100 (No subsetting). Best, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] r34804 fails to typeset a vertical Japanese, for which r34711 works fine
Hi Jiang, Please let me know if there are any further issues. I think r34832 is great. Thanks a lot. However, if I use TrueType fonts in XeTeX (.ttf or .ttc), xdvipdfmx crashes with the message: otf_cmap Creating ToUnicode CMap for c:/Windows/fonts/msmincho.ttc... I attach a ttctest.tex and ttftest.tex for the test. Thanks, Akira ttctest.tex Description: Binary data ttftest.tex Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] r34804 fails to typeset a vertical Japanese, for which r34711 works fine
Hi Jiang, I will look into these crashes tonight if no one beats me to it. Fixed as r34836. Thanks very much for your great work. r34836 is working fine. Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] r34804 fails to typeset a vertical Japanese, for which r34711 works fine
Hi Khaled, Jiang, I found that r34804 of dvipdfmx could not create a pdf for a simple vertical text by using SourceHanSansJP, while r34711 of dvipdfmx could create a fine pdf for the same text. I attach a file dvipdfmx-test.tar.gz which contains (1) UniSourceHanSansJP-UTF16-H (2) UniSourceHanSansJP-UTF16-V (3) r34711-message.txt (4) r34804-message.txt (5) sample.dvi (6) sample.pdf (7) sample.tex (8) test.map (1),(2): CMap files written by Y. Terada (3): message by r34711 for dvipdfmx -f test.map sample (4): message by r34804 for dvipdfmx -f test.map sample (5): a dvi file made by uplatex sample (6): a pdf file created by r34711, which is fine. (7): a source file (8): a map file for the test Thanks, Akira dvipdfmx-test.tar.gz Description: GNU Zip compressed data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] r34804 fails to typeset a vertical Japanese, for which r34711 works fine
Hi Jiang, I have committed a better fix as r34805. Thanks a lot, Jiang. It works fine for the example. Thanks, Akira -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] r34804 fails to typeset a vertical Japanese, for which r34711 works fine
Hi Jiang,
Anyone feel like trying out the following patches?
https://gist.github.com/jjgod/0d4b6339d761a5423f82
Patch 1 will fix the ToUnicode generation for all non-subst glyphs in
a non-XeTeX generated dvi. In our case, non-subst glyphs are the
glyphs that are *NOT* changed by applying OpenType vertical layout
features. To fix this I merely applied the same strategy I used to fix
XeTeX generated PDF documents. It's a small change and should be safe
to commit.
In patch 2 I tried out a more interesting approach and it supersedes
the efforts in patch 1: this patch utilize the cmap we provided in the
map file to do CID - Unicode lookup. In your test case the cmap is
UniSourceHanSansJP-UTF16-V.
To do this reverse lookup I have to extend CMap structure a little bit
to store reverse mapping information, with that it's quite easy to
simply generate ToUnicode stream with all used cids. The commit
message has more details.
Since these patches are relatively experimental I'm hesitate to commit
them right away, would be nice if any of you can try it out or review
them. With my limited testing it doesn't show any problem and we can
produce perfectly copyable PDF from the sample.dvi in this test case.
Hi Jiang,
Please commit both of patch1 and patch2!! I think that is great.
Users of W32TeX know that it is always experimental.
BTW, there is late declaration of a variable in c99
around line 1123 in tt_cmap.c:
for (j = 0; j 8; j++) {
unsigned int cid;
gid = 8 * i + j;
if (!is_used_char2(used_glyphs, gid))
continue;
cid = cff_charsets_lookup_inverse(cffont, gid);
int ch = CMap_reverse_decode(cmap_loaded, cid);
---
for (j = 0; j 8; j++) {
unsigned int cid;
int ch;
gid = 8 * i + j;
if (!is_used_char2(used_glyphs, gid))
continue;
cid = cff_charsets_lookup_inverse(cffont, gid);
ch = CMap_reverse_decode(cmap_loaded, cid);
Thanks,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] r34804 fails to typeset a vertical Japanese, for which r34711 works fine
Hi Jiang , I have committed a better fix as r34805. Thanks a lot, Jiang. It works fine for the example. However, unfortunately, invalid toUnicode problem for non-CJK fonts, fixed by Khaled, has reappeared. I attach a sample.tex. Thanks, Akira sample.tex Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] CID-keyed font support?
Hi Khaled, I have found the location where the crash occurs: --- type0.c.origMon Jul 28 19:38:13 2014 +++ type0.cFri Aug 01 09:06:25 2014 @@ -132,7 +132,7 @@ if (font-descriptor) ERROR(%s: FontDescriptor unexpected for Type0 font., TYPE0FONT_DEBUG_STR); if (!(font-flags FLAG_USED_CHARS_SHARED) font-used_chars) - RELEASE(font-used_chars); + RELEASE(font-used_chars); /* The crash occurs here */ if (font-used_glyphs) RELEASE(font-used_glyphs); if (font-encoding) In the case of the example on Windows, font-used_chars seems to be broken, though it is not NULL. Can you send me the DVI file? (I just discovered that, for some reason, I don't have any of the CJK collections installed. I'm installing them now but my connection is not that fast...). I attach sample.tar.gz. Japanese font is needed to typeset sample.dvi, though Japanese characters are not written explicitly. ( If I remove the above RELEASE(font-used_chars); the example works ok on Windows.) Thanks, Akira sample.tar.gz Description: GNU Zip compressed data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
