Re: [XeTeX] [EXT] Re: XeTeX terminates with inscrutable diagnostic "! Emergency stop"

David Carlisle wrote: the same error is in classic tex (with the same fixed value) tex.ch has The length of |dvi_file| should not exceed |@"7FFF|; So I'm stuffed. OK, thank you David. -- ** Phil. This email, its contents and any attachments are intended solely for the add

[XeTeX] XeTeX terminates with inscrutable diagnostic "! Emergency stop"

320] [10321] [10322] [10323] [10324 ! Emergency stop. ...box \pagebox } \shipout \box \pagebox \global \colcount = 0 \glo... \XML element: /qp ->\endgraf \Endgroup {qp} l.9423 ...ities in its past. dvi length exceeds &quo

[XeTeX] \openout \append ?

y of achieving this than opening the existing file for reading, copying it to a temporary file, closing both, re-opening the temporary file for reading, re-opening the existing file for writing, copying the former to the latter, and then and only then performing the desired \writes ? -- Philip Tay

Re: [XeTeX] [EXT] Re: [texworks] Bug in SyncTeX

Stefan Löffler wrote: On 04.07.24 12:09, Philip Taylor (RHBNC) via texworks wrote: If SyncTeX (called from XeTeX via TeXworks) is asked to handle a file with a U+2019 : RIGHT SINGLE QUOTATION MARK {single comma quotation mark} in its name rather than an apostrophe, it reports the following

[XeTeX] Bug in SyncTeX

or.html#39782> More information about the tex-live mailing list<http://tug.org/mailman/listinfo/tex-live> -- Philip Taylor This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certai

Re: [XeTeX] XeTeX : request for enhancement

Philip Taylor wrote: [...] Once we realise this, we are in a position to write the code : % !TeX Program=XeTeX \pdfpageheight = 210 mm \pdfpagewidth = 297 mm \hsize = \pdfpagewidth \vsize = \pdfpageheight \parindent = 1 cm \output = {\advance \hoffset by -1 in

Re: [XeTeX] XeTeX : request for enhancement

David Carlisle for his suggestion which led to my being able to develop this code. -- /Philip Taylor/ Example-image-3.pdf Description: Adobe PDF document

Re: [XeTeX] XeTeX OpenType Features bug?

this thread, Stephen.  Anyhow, as a non-user of Apple products, I simply downloaded those version that were easily found online.  In practice these turned out to be in .ttf and .otf formats. -- /Philip Taylor/

Re: [XeTeX] XeTeX OpenType Features bug?

would want to have included ? -- /Philip Taylor/

[XeTeX] XeTeX : request for enhancement

⟩ | yscaled ⟨int⟩ | width ⟨dimen⟩ | height ⟨dimen⟩ | rotated ⟨decimal⟩ ] Insert (pages of) a PDF. See below for explanation -- /Philip Taylor/

Re: [XeTeX] XeTeX wish list ...

On 14/08/2023 17:28, Zdeněk Wagner wrote: You can ask xdvipdfmx to add title, author, subject, keywords, creator, and producer. It is done by hyperref and also by my zwpagelayout which is shorter. Both packages do it for pdflatex, luatex, and xelatex. You can remove

[XeTeX] XeTeX wish list ...

as at present. It would (IMHO) be more elegant to make \jobname read/write, but that would introduce an unnecessary deviation from TeX. -- Philip Taylor This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certain circumst

Re: [XeTeX] Confused (why are ignored characters not "removed from the input" as per Eijkhout's TeX by Topic ?)

On 16/04/2023 19:30, Zdeněk Wagner wrote: The mouth reads the input and assigns categories, thus it sees ^^I as the character with code 0x09, assigns category 9 to it (ignored character) and sends this token to the stomach. Wel, that's not what Knuth says at Exercise 7.3, Zdeněk  — [Q] Some

Re: [XeTeX] Confused (why are ignored characters not "removed from the input" as per Eijkhout's TeX by Topic ?)

Having consulted Eijkhout first, I did then search the TeXbook to see if I could find a definitive statement concerning the treatment of ignored characters but failed to do so — perhaps I should search the PDF version rather than the printed ... -- /Philip Taylor/

[XeTeX] Confused (why are ignored characters not "removed from the input" as per Eijkhout's TeX by Topic ?)

-mail I represent them here as ^^I. The ^^I in the transcript is genuine. -- Philip Taylor This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certain circumstances, it may also be subject to legal privilege. Any

Re: [XeTeX] Tonos v. oxia

nformation. \font \greekfont = "Palatino Linotype" \font \greekfont = "Arial Unicode MS" \greekfont U+1F7D : GREEK SMALL LETTER OMEGA WITH OXIA — ώ \par U+03CE : GREEK SMALL LETTER OMEGA WITH TONOS — ώ \par \end -- /Philip Taylor/

[XeTeX] Tonos v. oxia

re, please ? -- Philip Taylor This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certain circumstances, it may also be subject to legal privilege. Any unauthorised use, disclosure, or copying is not permitted. If you have rec

Re: [XeTeX] XeTeX \openin — bug or feature

On 20/09/2022 17:36, Jonathan Kew wrote: Have you compared other engines? My TL installation is woefully out-of-date, but with the versions I have on hand, I see similar behavior in tex/pdftex/luatex. No, I confess that I haven't, Jonathan — XeTeX is the only engine I ever use, and has been

Re: [XeTeX] XeTeX \openin — bug or feature

On 20/09/2022 17:29, David Carlisle wrote: feature, and not xetex specific Thank you, David.  Evil, nonetheless, and highly counter-intuitive. -- /** Phil./

[XeTeX] XeTeX \openin — bug or feature

Given \newread \standin \openin \standin = MM3.dat I had expected XeTeX to open MM3.dat for input — instead, it opened MM3.dat.tex Bug or feature ? -- /Philip Taylor/

Re: [XeTeX] Σχετ: Re: Σχετ: Re: Off topic (interesting) question

On 20/08/2022 13:23, Julian Bradfield wrote: I have no axe to grind in this intra-Hellenic debate, but may I ask the two protagonists whether they view the current American practice of both Come, come: you mean "the protagonist and deuteragonist" ! Sir, I can only adduce the OED in my humble d

Re: [XeTeX] Σχετ: Re: Σχετ: Re: Off topic (interesting) question

, but may I ask the two protagonists whether they view the current American practice of both pronouncing and spelling the phrase "want to" as "wanna" (as in "I wanna go to the mall" — see Youtube captions, for countless examples) as evolution or crass ignorance ? -- /Philip Taylor/

Re: [XeTeX] Off topic (interesting) question

er/ ); the length of the stem vowel of the Old English word is uncertain, and the phonology is difficult to explain (see further A. Campbell /Old Eng. Gram./ (1959) §§507, 516, 545, 565, and (for a summary of views) A. H. Feulner /Die griechischen Lehnwörter im Altenglischen/ (2000) 248–51): Philip Taylor

[XeTeX] XeTeX cannot open secured PDF

" when open in Adobe Acrobat DC], it can then be opened by XeTeX. -- Philip Taylor This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certain circumstances, it may also be subject to legal privilege. Any unautho

Re: [XeTeX] Support of variable OpenType fonts

Thank you for both responses, Werner — most informative and much appreciated. -- /Philip Taylor/

Re: [XeTeX] Support of variable OpenType fonts

t into attempting to support the technology that underlies Zapfino Ink <https://tug.org/TUGboat/tb28-2/tb89hagen.pdf>. -- /Philip Taylor/

Re: [XeTeX] Disable "mktextfm" and/or use of TFM-based fonts ?

On 08/06/2022 09:55, Ulrike Fischer wrote: Sorry but I think it is one of the nice features of a modern tex system that it creates tfm or pk fonts on the fly. That's fine; we can agree to differ on such philosophical points. xetex is doing that internally too for your open type fonts: it is sti

Re: [XeTeX] Disable "mktextfm" and/or use of TFM-based fonts ?

On 08/06/2022 08:51, Ulrike Fischer wrote: Am Tue, 7 Jun 2022 11:44:28 +0100 schrieb Philip Taylor (Hellenic Institute): As I /never/ want XeTeX to attempt to create a seemingly-missing TFM file, can I configure XeTeX and/or TeXworks to inhibit this undesired behaviour ? Perhaps by setting

Re: [XeTeX] Disable "mktextfm" and/or use of TFM-based fonts ?

On 08/06/2022 08:51, Ulrike Fischer wrote: Perhaps by setting MKTEXTFM = 0, but I never tried if xetex honors that. Yes, a great improvement thank you — D:\ XeTeX Font-error This is XeTeX, Version 3.141592653-2.6-0.94 (TeX Live 2022) (preloaded format=xetex)  restricted \write18 enabled

[XeTeX] Disable "mktextfm" and/or use of TFM-based fonts ?

behaviour ?  And for that matter, can I configure XeTeX and/or TeXworks to inhibit any attempt to use TFM-based fonts ? -- /Philip Taylor/

Re: [XeTeX] Uppercase in Armenian

On 01/05/2022 13:27, Zdenek Wagner wrote: Hi all, as I wrote, my knowledge is based just on facebook and youtube and texts and videos on Omniglot. I can send you exact links to youtube videos but you should be fast, it is displayed for a second or two. Youtube URLs can include a timestamp, so

Re: [XeTeX] [EXT] Re: AMS/CM fonts in OpenType/CFF format

On 17/11/2021 11:04, Marcel Fabian Krüger wrote: Looking at the code again I realized that the quotes actually *do* make a difference: If the name is quoted XeTeX will first look for a system font and use a TFM font only if no system font is found, if the name is not quoted it will forst look fo

Re: [XeTeX] AMS/CM fonts in OpenType/CFF format

user ! Oh, and \font \cmr = "CMR9:" fails, so at least I have a way of forcing a system font to be used, even if I have to upper-case the name.  But I am still very concerned that \font \cmr = "CMR10.xyz:" finds the font and reports no error. -- /Philip Taylor/

Re: [XeTeX] AMS/CM fonts in OpenType/CFF format

On 16/11/2021 11:54, Philip Taylor (Hellenic Institute) wrote: [M]ust I write (/e.g.,/) \font \cmr = "[cmr10.otf]" to force XeTeX to use /only/ your OTF versions and to report "Font not found" if the relevant font(s) is/are not installed ? Rather worryingly, the follow

Re: [XeTeX] AMS/CM fonts in OpenType/CFF format

.g.,/) \font \cmr = "[cmr10.otf]" to force XeTeX to use /only/ your OTF versions and to report "Font not found" if the relevant font(s) is/are not installed ?  TeX Live and XeTeX lists cc'd for comment. -- /Philip Taylor/ The public repository i

Re: [XeTeX] Guaranteed Unicode replacement glyph in every TeX installation?

de - July 2021 Win10 78.43% Win716.03% Win8.1 3.49% Win81.17% WinXP 0.59% WinVista0.26% but 16% still represents a /very/ large number of people, perhaps even in excess of 100x10^6 <https://www.theverge.com/2021/1/6/22217052/microsoft-windows-7-109-million-pcs-usage-stats-

Re: [XeTeX] Guaranteed Unicode replacement glyph in every TeX installation?

CMD prompt did not recognise the command. -- /Philip Taylor/

Re: [XeTeX] Guaranteed Unicode replacement glyph in every TeX installation?

under Windows 7 Ultimate, the command "albatross" is unknown — Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation.  All rights reserved. d:\Users\Philip Taylor>albatross -d 0xFFFD 'albatross' is not recognized as an internal or external comma

Re: [XeTeX] strange case of overlapping graphics

In both Windows Preview and in Adobe Illustrator CC, the PNG file is roughly twice as tall (relative to its width) as it appears in the PDF. -- /Philip Taylor/

Re: [XeTeX] 64-bit binaries

Bobby.  I supposed that I am used to seeing directories ("folders") clustered together either at the top or at the bottom of a directory listing, and failed to realise that in this instance files and directories are intermixed. -- /Philip Taylor/

Re: [XeTeX] [EXT] Re: [dvipdfmx] Sub-optimal diagnostic from XeTeX/xdvipdfmx when including non-existent page from PDF

Shunsaku Hirata wrote: Sorry for the late reply. I'm going to change the error message as suggested. Thanks for your suggestion. Thanks, Shunsaku Hirata Thank you very much for agreeing to take this on board, Shunsaku-san — /arigato gozaimasu. / 2021/05/02 5:14、Philip Taylor

Re: [XeTeX] 64-bit binaries

sbalance.ring.gr.jp/archives/text/TeX/ptex-win32/current/TLW64/>; could you give the URL at which the "win64" folder is visible, please ? -- /Philip Taylor/

Re: [XeTeX] Adobe PDF, Adobe Acrobat/Reader, Microsoft Word, XeTeX, and (x)dvipdfm(x).

t PDF...", the latter before calling XeTeX), then that would address at least a part of the current problem. -- /Philip Taylor/

Re: [XeTeX] Adobe PDF, Adobe Acrobat/Reader, Microsoft Word, XeTeX, and (x)dvipdfm(x).

`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 ... -- /Philip Taylor/

Re: [XeTeX] Adobe PDF, Adobe Acrobat/Reader, Microsoft Word, XeTeX, and (x)dvipdfm(x).

Philip Taylor wrote: Thank you for that information, George.  Is "AcroRead" "Acrobat Reader" or another program ?  I ask because I have just tried "pdfclose" here, with a PDF open in Adobe Acrobat (not Acrobat Reader) and it fails as follows : C:\Windows\S

Re: [XeTeX] Adobe PDF, Adobe Acrobat/Reader, Microsoft Word, XeTeX, and (x)dvipdfm(x).

at (not Acrobat Reader) and it fails as follows : C:\Windows\System32>pdfclose "Hoi-An vegan menu (separate pages).pdf" pdfclose: non existent file Hoi-An vegan menu (separate pages).pdf Cannot contact a server. C:\Windows\System32> -- /Philip Taylor/

Re: [XeTeX] Adobe PDF, Adobe Acrobat/Reader, Microsoft Word, XeTeX, and (x)dvipdfm(x).

msk...@ansuz.sooke.bc.ca wrote: Seems like it will need some kind of Windows-specific handling to resolve, then. Yes, that was my belief, Matthew. -- /** Phil./

[XeTeX] Adobe PDF, Adobe Acrobat/Reader, Microsoft Word, XeTeX, and (x)dvipdfm(x).

Acrobat (and probably Adobe Reader) to close the PDF and then re-open it once the changes have been made. Is there any reason why the (x)dvipdfm(x) back-end to XeTeX cannot [be enhanced to] do the same ? -- /Philip Taylor/

[XeTeX] Sub-optimal diagnostic from XeTeX/xdvipdfmx when including non-existent page from PDF

more pages. It would therefore be very helpful if XeTeX/xdvipdfmx could report that the problem occurred when trying to access page 4, rather than merely stating that « Image inclusion failed for "./Hoi-An vegan menu (separate pages).pdf" ». -- Philip Taylor This email, its conten

Re: [XeTeX] Follow-up to previous mail about hyphenation

Yannis Haralambous wrote: In fact, Arabic is not hyphenated. That is presumably because of the existence of the /kashida/, Yanni.  What is interesting is that the W3C notes that the Arabic /script/ (as opposed to the /language) /may  be hyphenated, and offers Uyghur as example — When shap

Re: [XeTeX] Follow-up to previous mail about hyphenation

Not being an Arabist, I have no idea whether the output from the following is correct or not, but I thought that it would be fun to run Bruno's code on some 'real' Arabic rather than just on sequences — % !TeX Program = Ini-XeTeX \let \dump = \relax \input xelatex.ini \begingroup      \l

Re: [XeTeX] Follow-up to previous mail about hyphenation

What is the reason for the \makeatletter at line~29, Bruno ?  It appears to behave identically without it. -- /** Phil./

Re: [XeTeX] Follow-up to previous mail about hyphenation

And now, thanks to Jonathan, only one page — % !TeX Program=Ini-XeTeX \catcode `\ = 10 \catcode `\{ = 1 \catcode `\} = 2 \catcode `\# = 6 \catcode `\^ = 7 \catcode `\^^I = 10 \catcode `\% = 14 \let \bgroup = { \let \egroup = } \let \endgraf = \par \tracingonline = 1 \tracinglostchars = 2 \dim

Re: [XeTeX] Follow-up to previous mail about hyphenation

Jonathan Kew wrote: I don't see what \dimen 10 is doing in any of this. It never seems to get set, so I assume it remains zero. Ah, I took this from plain.tex's definition of \maxdimen, but it is possible (nay, probable, if not absolutely certain) that in the absence of plain.tex being \inpu

Re: [XeTeX] Follow-up to previous mail about hyphenation

Jonathan Kew wrote: See https://tug.org/pipermail/xetex/2014-January/025129.html Thank you, Jonathan.  Now formatted and included in the next iteration (code below, with "showhyphens.tex" attached).  I /believe/ that "showhyphens.tex" is functionally equivalent to David's code, but as he ap

Re: [XeTeX] Follow-up to previous mail about hyphenation

Jonathan Kew wrote: The output you're getting shows that the hyphenation is in fact happening as expected. (To get a hyphen rather than a box, you need to set the font's \hyphenchar appropriately.) So what am I missing in my code, Jonathan ?  I have added a \hyphenchar, removed the pointless

Re: [XeTeX] Follow-up to previous mail about hyphenation

for a replacement \showhypens buried deep in the file "xltxtra.dtx" (attached).  However, the code is completely incomprehensible to me, I have no idea how to convert a .dtx file into anything usable, and I cannot find a plain XeTeX equivalent. -- /Philip Tay

Re: [XeTeX] Follow-up to previous mail about hyphenation

Yannis Haralambous wrote: No, I have the font in the same directory Still doesn't work for me after copying the four ttfs there — instead, if I don't want to use system font syntax, I have to use — \font \tenrm = [./Amiri-Regular.ttf] Then I get the following reports — This is XeTeX, Ve

Re: [XeTeX] Follow-up to previous mail about hyphenation

Yannis Haralambous wrote: No, I have the font in the same directory OK, I installed it as a system font.  I will try copying the .ttfs to the source directory.

Re: [XeTeX] Follow-up to previous mail about hyphenation

Yannis Haralambous wrote: When I run the same file with Amiri: % !TeX Program=Ini-XeTeX \catcode `\ = 10 \catcode `\         = 10 \catcode `\{ = 1 \catcode `\} = 2 \catcode `\^ = 7 \font\tenrm="Amiri-Regular.ttf" Does your hacked version of my code not generate this error for you, Yanni ? Th

Re: [XeTeX] Follow-up to previous mail about hyphenation

Philip Taylor wrote: And I see no significant font using Amiri — "no significant /*difference */...".

Re: [XeTeX] Follow-up to previous mail about hyphenation

And I see no significant font using Amiri — % !TeX Program=Ini-XeTeX \catcode `\ = 10 \catcode `\ = 10 \catcode `\{ = 1 \catcode `\} = 2 \catcode `\^ = 7 \font \tenrm = "Amiri" \tenrm \lccode "200D = "200D \patterns {200d1200d} \def \showhyphens     {     \setbo

Re: [XeTeX] Follow-up to previous mail about hyphenation

rance = -1     \tolerance = -1     \hbadness = 0     \showboxdepth = 0 \ #1     }     } \lccode "200D = "200D \catcode "200D = 11 bla200d200dbla \showhyphens {bla200d

Re: [XeTeX] Building a XeLaTeX format

. -- /** Phil (Philip Taylor)/ This is XeTeX, Version 3.141592653-2.6-0.93 (TeX Live 2021/W32TeX) (INITEX) 25 MAR 2021 08:14 entering extended mode restricted \write18 enabled. %&-line parsing enabled. **XeLaTeX.ini (c:/TeX/Live/2021/texmf-dist/tex/generic/tex-ini-files/xelatex.ini (c:/TeX/Live/

Re: [XeTeX] Coloured fonts

ligatures for (e.g.,) Adobe Caslon Pro or Garamond while it does so for Adobe Minion Pro.  Question raised on LuaTeX list. -- /Philip Taylor/

Re: [XeTeX] Coloured fonts

David Carlisle wrote: I see colour here in windows firefox, widows chrome  and xpdf using cygwin X attached luahbtex file and result in Chrome it looks like this image.png OK, so it could be the TeXworks previewer that is failing to shew the colour.  But to get your plain LuaTeX code to

Re: [XeTeX] Coloured fonts

David Carlisle wrote: Sigh, I thought you'd like the challenge:-) with luahbtex: \input luaotfload.sty \font\chess=BabelStoneXiangqiColour.ttf:mode=harf testing {\chess ^^01fa64} \bye But does that give a coloured glyph, as did your LuaLaTeX version ? I ask because I have integrate

Re: [XeTeX] Coloured fonts

Hallo Ross — The colour doesn’t show in Phil’s example PDF, neither in Adobe’s  Illustrator, nor Acrobat Pro, despite Adobe being one of the instigators of this font format. So presumably the font isn’t installed correctly into the PDF. Yes, I'd agree with that. Unfortunately the link to ge

Re: [XeTeX] Coloured fonts

David Carlisle wrote: Not sure if xetex can do colour fonts currently, You can always experiment with luatex which gets this if using harfbuzz image.png \documentclass{article} \usepackage{fontspec} \newfontfamily\chess[Renderer=HarfBuzz]{BabelStoneXiangqiColour.ttf} \begin{document} testi

[XeTeX] Coloured fonts

r "1FA65\relax \ \char "1FA66\relax} \centerline {\strut} \centerline {\blackpieces \char "1FA67\relax \ \char "1FA68\relax \ \char "1FA69\relax \ \char "1FA6A\relax \ \char "1FA6B\relax \ \char "1FA6C\relax \ \char "1FA6D\relax} \end -- Philip Taylor Th

Re: [XeTeX] Background colour for some (but not all) rows of an \halign (UNIV: XeTeX, not XeLaTeX)

year planner code and let you know how I get on. ** Phil -- /Philip Taylor/

[XeTeX] Background colour for some (but not all) rows of an \halign (UNIV: XeTeX, not XeLaTeX)

May I ask if there is a simple way to apply a background colour to some (but not all) rows of an \halign.  UNIV = plain XeTeX, not XeLaTeX. -- Philip Taylor

Re: [XeTeX] Color changing under graphic inclusion with graphicx

[Just realised that the XeTeX list should have been cc'd, so doing so now and will forward Paulo's original images as attachments] Philip Taylor wrote: Ulrike Fischer wrote: I can't reproduce your problem with the files you provided. How do you compile? Which TeX-System d

Re: [XeTeX] asterisk in font name - font error

as to install the font in the first place. Philip Taylor

Re: [XeTeX] asterisk in font name - font error

used with XeTeX, the problem should be reported to the authors of the "fontspec" and "LaTeX2e" packages, as it is probable that the problem lies solely therein. /Philip Taylor/

Re: [XeTeX] asterisk in font name - font error

n untitled-1.pdf (1 page). SyncTeX written on untitled-1.synctex.gz. Transcript written on untitled-1.log. It may therefore be that the problem lies with "fontspec" or with the XeLaTeX format. /Philip Taylor/ Carlos Franke wrote: Hello! I'm having trouble using

Re: [XeTeX] how to suppress doted circle next to a glyph

May I ask for an example that produces the dotted circle but not the error message ? Philip Taylor François Patte wrote: Bonjour, I want to use some glyph using the command \symbol. In some case I get a glyph with a dotted circle, how ca

Re: [XeTeX] Colour specials for XeTeX

LES Philip Taylor

Re: [XeTeX] Problem with ifpdf switch

Zdenek Wagner wrote: Hi John, the reason is somewhere before you read eplain.tex because within the lines from your original mail you close more files than you open. By which Zdeněk is referring to : (d:/TEXFILES/TEXINPUT/TEXDOCS/UNIDEFS/UHYPHENS.TEX))

Re: [XeTeX] [tex-implementors] Proposal : that TeX engines generating PDF directly should be able to close the output file without terminating.

as a bit set) which a user could elect to set as he or she wishes, indicating which elements are to be carried over and which elements are to be re-set. Philip Taylor

Re: [XeTeX] [tex-implementors] Proposal : that TeX engines generating PDF directly should be able to close the output file without terminating.

Ross Moore wrote: Of course another possibility for Phil is to put all the pages of *both* his desired PDFs into the same “master PDF”, then use a command-line tool like  pdftk  to extract the relevant pages for one or o

Re: [XeTeX] startup time

than style-file reading that is the root cause.  From an elevated TeX Live 2020 command prompt, type "fc-cache -r -v", wait for it to finish, and then try your TeX compilation again. Philip Taylor

Re: [XeTeX] [tex-implementors] Proposal : that TeX engines generating PDF directly should be able to close the output file without terminating.

Jonathan Kew wrote: For your example, I was going to suggest that a simpler solution than "make" ought to work: all it requires is a two-line batch file or shell script (or similar: tools like Lua or Python or Perl would be fine) that performs the

Re: [XeTeX] Proposal : that TeX engines generating PDF directly should be able to close the output file without terminating.

Thank you, Bruno/Ross, for that most useful suggestion.  I am delighted to confirm that with the following modification to "Hoi-An TA Menu (combine pages).tex", all works as intended : % !TeX Program=XeTeX-W18 \immediate \write 18 {XeTeX "Hoi-An TA menu (se

Re: [XeTeX] Proposal : that TeX engines generating PDF directly should be able to close the output file without terminating.

27;"Hoi-An TA menu (separate pages).pdf"'.    } l.28 ... - 0,666 \rulewidth \relax height \vsize }           \relax ? Philip Taylor

Re: [XeTeX] Proposal : that TeX engines generating PDF directly should be able to close the output file without terminating.

not it is enabled, so debugging the root cause of the problem is not easy. Philip Taylor Zdenek Wagner wrote: Hi, I have never tried but could not you use \write18 to run XeTeX from X

[XeTeX] Proposal : that TeX engines generating PDF directly should be able to close the output file without terminating.

a proposal to extend the PDF-generating family of TeX-derived engines to support this feature ? Philip Taylor

Re: [XeTeX] XeTeX, colour, \special, \shipout

Jonathan Kew wrote: [...] To work, the background \special must have already been seen by the driver at the time the page is shipped out, or it must be part of the content of the page. Aha, perfect, fully understood and that explains everything.  Thank you Jonathan, I can now revert to shi

Re: [XeTeX] XeTeX, colour, \special, \shipout

Ross Moore wrote: Hi Philip. On 20 Jun 2020, at 12:08 am, Philip Taylor <mailto:p.tay...@hellenic-institute.uk>> wrote: XeTeX does what is expected if one uses \special {background cmyk 0.83 0.82 0.21 0.60} and ships out pages in the normal way; however, if \shipout is invoked

[XeTeX] XeTeX, colour, \special, \shipout

be specified ? /Philip Taylor/

Re: [XeTeX] Colour specials for XeTeX

On 08/06/2020 10:28, Zdeněk Wagner wrote: The request of supporting dvips specials in xdvipdfmx is not very fair. PDF is modelled after PostScript but not the same. PostScript is a linear language, PDF lacks programming structures but makes use of streams, even indirect streams and indirect

Re: [XeTeX] Colour specials for XeTeX

Hallo again Benct — Dijkstra was a great theoretician, and in principle it is of course right that the spec/documentation should dictate the behavior, but as we all know there is usually, for practical reasons, more or less distance between theory and practice, and in practice a piece of s

Re: [XeTeX] Colour specials for XeTeX

VIPS" and thus the documentation for the latter can serve as reference for the former. /Philip Taylor/

Re: [XeTeX] Colour specials for XeTeX

works, but \special {color push }) does, as do the other two, yet I cannot find out where their behaviour is defined other than in the source code. /Surely /they must be defined somewhere, and not just have sprung into existence of their own volition ... Philip Taylor

Re: [XeTeX] Colour specials for XeTeX

Apostolos Syropoulos wrote: When I was trying to include spot color support I had to read the source code... Apostolos I can only synpathise ...

Re: [XeTeX] Colour specials for XeTeX

David Carlisle wrote: Phil wrote 'However, it would seem that while the "xdv2pdf" driver was happy with \special {color push}, the "xdvipdfmx" driver is not. ' I doubt that ever worked, the semantics of "push" on any stack mean you have to say what you are putting on the stack, unlike pop

Re: [XeTeX] Colour specials for XeTeX

Zdenek Wagner wrote: The short answer for TeX Live users: texdoc dvipdfmx But that is the very document at which I am looking, and I cannot find them defined there.  Could you possibly quote a short fragment or give a page ref ?

Re: [XeTeX] Colour specials for XeTeX

Philip Taylor wrote : Well, perhaps I spoke too soon.  Having commented out the x:rulecolor specials and left in thecolor equivalents, I now see in the transcript : [snip] xdvipdfmx:warning: Interpreting special command push (color) failed. xdvipdfmx:warning: >> at page="

Re: [XeTeX] Colour specials for XeTeX

Philip Taylor wrote: Excellent, many thanks to Akira-san and David.  All now perfect. Well, perhaps I spoke too soon.  Havinf commented out the x:rulecolor specials and left in thecolor equivalents, I now see in the transcript : This is XeTeX, Version 3.14159265-2.6-0.92 (TeX Live

Re: [XeTeX] Colour specials for XeTeX

Excellent, many thanks to Akira-san and David.  All now perfect.  I will update my TeXworks configuration accordingly. ** Phil. Akira Kakuto wrote: xetex -output-driver="xdvipdfmx -E" file.tex or  xetex -output-driver="xdvipdfmx -v -E" file.tex  (verbose) Default is "xdvipdfmx -q -E"

  1   2   3   4   5   6   7   8   9   10   >