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

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

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

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

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,

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

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

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

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

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

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

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

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}

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

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.}}

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.:

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

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

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

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

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

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

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

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

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:

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

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).

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.

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

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

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

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:

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

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,

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

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,

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

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

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

[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,

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

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

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

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.:

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

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

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

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

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 --

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

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

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,

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.

Re: [XeTeX] Strange tikz behaviour with xetex

);% \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

-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

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 -- Subscription

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

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

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

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

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

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,

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

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 --

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).

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

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 --

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

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 %

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

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

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}

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

[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.:

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

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

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

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

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

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

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

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

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

[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

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

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.:

[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)

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

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

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

  1   2   >