Re: [XeTeX] XeTeX : request for enhancement

On Sun, 15 Oct 2023 at 19:49, Philip Taylor < philip.tay...@hellenic-institute.uk> wrote: > At the moment, one can include a PDF file using the following syntax : > > \XeTeXpdffile ⟨filename⟩ [ page ⟨int⟩ ] [ crop | media | bleed | trim | > art ] > [ scaled ⟨int⟩ | xscaled ⟨int⟩ | yscaled ⟨int⟩ |

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

Like most things, it's an option see try_std_extension_first in section 6.2 of texdoc kpathsea On Tue, 20 Sept 2022 at 17:33, Philip Taylor (Hellenic Institute) < p.tay...@hellenic-institute.uk> wrote: > On 20/09/2022 17:29, David Carlisle wrote: > > feature, and not xetex spe

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

feature, and not xetex specific $ ls MM* MM3.dat MM3.dat.tex $ kpsewhich MM3.dat ./MM3.dat.tex $ kpsewhich --all MM3.dat ./MM3.dat.tex ./MM3.dat If both are available kpsearch prefers the .tex as shown by the first call to kpsewhich David On Tue, 20 Sept 2022 at 16:40, Philip Taylor

Re: [XeTeX] XeTeX development, issues?

On Thu, 28 Jul 2022 at 08:32, Nico Schlömer wrote: > Hi everyone, > > Where can I file bugs about XeTeX? Is there a GitHub repo perhaps? > sourceforge git, there are bug and feature reporting links at http://xetex.sourceforge.net/ David > > Cheers, > Nico >

Re: [XeTeX] Support of variable OpenType fonts

On Tue, 12 Jul 2022 at 22:03, David Jones wrote: > STIX Two is distributed in OTF, TTF, and WOFF2 formats: > > https://github.com/stipub/stixfonts > > Only the TTF files are variable fonts. > > Only the OTF fonts are distributed via CTAN since none of the TeX engines > can use the

Re: [XeTeX] Uppercase in Armenian

deněk Wagner > http://ttsm.icpf.cas.cz/team/wagner.shtml > > > ne 1. 5. 2022 v 0:53 odesílatel David Carlisle > napsal: > >> Something like this, I think. >> >> [image: image.png] >> >> \documentclass{article} >> \usepackage{polyglossi

Re: [XeTeX] Uppercase in Armenian

Something like this, I think. [image: image.png] \documentclass{article} \usepackage{polyglossia} \setdefaultlanguage{armenian} \setmainfont{DejaVu Sans} \ExplSyntaxOn \let\tuppercase\text_uppercase:n \ExplSyntaxOff \pagestyle{empty} \begin{document} Երևան $\rightarrow$ \uppercase{Երևան} Երևան

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

On Sat, 21 Aug 2021, 13:46 Janusz S. Bień, wrote: > On Sat, Aug 21 2021 at 10:48 +02, Ulrike Fischer wrote: > > Am Fri, 20 Aug 2021 19:45:37 -0600 (MDT) schrieb Doug McKenna: > > > >> Using XeTeX, I want to typeset a LaTeX document into a PDF file. The > LaTeX source code in UTF-8 expressly

[XeTeX] internal error using opentype font on mathaccent

\font\f="TeX Gyre Termes" \textfont0=\f \scriptfont0=\f \scriptscriptfont0=\f $ \mathaccent"0017 c $ \bye This is a plain version of a latex example posted by a user to tex.stackexchange. It shouldn't really do anything sensible (if the font load is adjusted for luatex you get the standard

Re: [XeTeX] \XeTeXpdffile causes over-long line unless wrapped in \hbox

Bruno wrote > David got mislead. Yes sorry too many programming languages in head at once today:-)

Re: [XeTeX] \XeTeXpdffile causes over-long line unless wrapped in \hbox

The command is scanning ahead for keywords such as page 2 in the unhboxed case but in the boxed case the } stops the scan but it seems having decided that test is not a keyword it is inserting a space before it which seems wrong. More surprising is that it eats ! here even though ! isn't part

Re: [XeTeX] Coloured fonts

Sigh, I thought you'd like the challenge:-) with luahbtex: \input luaotfload.sty \font\chess=BabelStoneXiangqiColour.ttf:mode=harf testing {\chess ^^01fa64} \bye On Thu, 18 Mar 2021 at 20:44, Philip Taylor wrote: > David Carlisle wrote: > > Not sure if xetex can do col

Re: [XeTeX] Coloured fonts

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

Re: [XeTeX] latin-1 encoded characters in commented out parts trigger log warnings

On Mon, 22 Feb 2021 at 01:28, Ross Moore wrote: > Hi Jonathan, and others. > > > There’s actually a pretty easy fix, at least for XeLaTeX. > The package contains 2 files only: xstring.sty and xstring.tex . > The .sty is just a 1-liner to load the .tex . > > It could be beefed up with: > >

Re: [XeTeX] latin-1 encoded characters in commented out parts trigger log warnings

On Sun, 21 Feb 2021 at 20:27, Ross Moore wrote: > Hi David, > > Surely the line-end characters are already known, and the bits > have been read up to that point *before* tokenisation. > This is not a pdflatex inputenc style utf-8 error failing to map a stream of tokens. It is at the file

Re: [XeTeX] latin-1 encoded characters in commented out parts trigger log warnings

On Sun, 21 Feb 2021 at 11:47, Ross Moore wrote: > Hi David. > > On 21 Feb 2021, at 10:12 pm, David Carlisle > wrote: > > I think that should be taken up with the xstring maintainers. > > > Is xstring intended for use with XeTeX ? > I suspect not. > B

Re: [XeTeX] latin-1 encoded characters in commented out parts trigger log warnings

I think that should be taken up with the xstring maintainers. I don't think there is any reasonable way to say you can comment out parts of a file in a different encoding. The file encoding specifies the byte stream interpretation before any tex tokenization If the file can not be interpreted as

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

>if that doesn't go anywhere, I will try at latex2e's (their bug tracker is much more active than fontspec's). Please don't do that, it just increases our administrative overload. If it is fixable on our side then all relevant people will already have seen your report here and at fontspec

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

On Mon, 14 Dec 2020 at 16:10, Apostolos Syropoulos via XeTeX wrote: > >Works for me, Ulrike : > > > > > > \font \Jost = "Jost*" > > \Jost Hallo > > > > \end > > > > > >Of course, one has to install the font in the first place. > > The above code works just fine in Solaris. > A.S. > >

Re: [XeTeX] problem with ~ in Mapping=velthuis-sanskrit

>\catcode`\~=12% changing catcodes in an environment looks wrong (the % after the 12 is definitely wrong) if you change catcodes then the definition cannot work in the argument of any command (for the same reasons that \verb does not work in command arguments) . Leave ~ active but make it

Re: [XeTeX] Problem with ifpdf switch

I get no spurious output from this document with xetex \input ifpdf.sty \input eplain xxx \bye However you do not have the current version of ifpdf.sty your text is showing a 2016 date which presumably means you have an old copy somewhere on a local input path that is masking the one you

Re: [XeTeX] Colour specials for XeTeX

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 where you just take off the

Re: [XeTeX] Colour specials for XeTeX

On Sat, 6 Jun 2020 at 13:40, Philip Taylor wrote: > Thank you all for your comments and explanations. One question to > Akira-san, though : > > > If you use -no-pdf option and apply xdvipdfmx to a created > > .xdv file, you can see messages like > > > > xdvipdfmx:warning: xetex-style

Re: [XeTeX] Xetex, Latex3, unicode-math and Math font not found

> \exp_args:Nxx \setmathfont > { \tl_use:N \c__test_MathFont_tl } > { [ \tl_use:N \c__test_MathFontSpec_tl ] } > > Thanks for the explanations but this form does not work the x expansion leaves in the braces so this ends up as \setmainfont{somefontname}{[expansionof \c_...]} but the braces

Re: [XeTeX] macro-problem

On Tue, 12 May 2020 at 16:16, Herman Grootaers wrote: > On 05-05-20 08:34, Herman Grootaers wrote: > > I am flabbergasted with this macro I am setting up. I must miss > > something from reading the documentation. > > > > > > It is a part of a macro that is much longer, only a conditional > >

Re: [XeTeX] macro-problem

I don't have the fonts so couldn't get quite the result you want but you are using \lettrine mid-paragraph, and keeping the paragraph text in a group that ends before the paragraph ends, both of these are likely to have strange effects with macros like \lettrine that rely on setting \parshape The

Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

On Mon, 13 Jan 2020 at 03:41, Doug McKenna wrote: > >| Are there architectural reasons preventing you from having a > >| format file, or is it simply that you hope to make loading quick > >| enough that you do not need it? > > Yes, and yes. JSBox does not depend on an internal array of integers

Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

On Mon, 13 Jan 2020 at 03:41, Doug McKenna wrote: > > David Carlisle wrote: > > >| Note this list is for the xetex extended tex, > >| but the issues you raise are unrelated to xetex > >| but to the latex format initialisation so this > >| is not really the right

Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

e jsbox is being developed. Returning to your original question as to what constitutes a "Unicode" TeX for LaTeX, we have put some data on the requirements for extended TeX features in the draft ltnews31 which will be part of next week's latex-dev release, but you can see the sources now at Primitive Requirements: https://github.com/latex3/latex2e/blob/develop/base/doc/ltnews31.tex#L596 see also Improved load-times for expl3: https://github.com/latex3/latex2e/blob/develop/base/doc/ltnews31.tex#L169 on the additional items preloaded in the format. > > > Doug McKenna > Mathemaesthetics, Inc. David Carlisle for the LaTeX3 Project

Re: [XeTeX] Lowercase Unicode code points in hyphenation patterns

On Sun, 24 Nov 2019 at 19:10, Doug McKenna wrote: > > Is xgreek.sty loaded as part of creating the LaTeX format? No > If not, my understanding is that its corrections wouldn't affect any of the > hyphenation patterns installed from xetex.ini during the format build. > > Perhaps this doesn't

Re: [XeTeX] Lowercase Unicode code points in hyphenation patterns

On Sun, 24 Nov 2019 at 18:41, Apostolos Syropoulos via XeTeX wrote: > Of course these tables are all wrong but this is another problem. Yes there is that. However it seems better to start from a known standardised base shared with basically everyone then fix as needed rather than try to come up

Re: [XeTeX] Lowercase Unicode code points in hyphenation patterns

the lccode tables are set by the macro layer not the engine code, it reads in The Unicode consortium data file tex/generic/unicode-data/UnicodeData.txt and sets the lccode values and catcode values according to the data there. see tex/generic/unicode-data/load-unicode-data.tex which is loaded

Re: [XeTeX] Use of BOM in XeTeX and TeXworks

On Sat, 13 Jul 2019 at 21:21, Zdenek Wagner wrote: > Hi all, > > I received files from other users with BOM in UTF-8 ans UTF-16 and > XeTeX correctly recognized them. Tested on Linux and Mac. > > Yes sure, when I said an encoding comment was more readable I meant "more readable for humans to

Re: [XeTeX] Use of BOM in XeTeX and TeXworks

more readable than a BOM you can use an encoding comment as far as I can see for your use case eg as listed here https://www.texdev.net/2011/03/24/texworks-magic-comments/ On Wed, 10 Jul 2019 at 12:07, Taylor, P wrote: > Two related questions, the second dependent on the answer to the first.

Re: [XeTeX] setting math parameters via fontdimens (or other means)

I wrote \ifx\Umathchar\undefined \usepackage{lmodern} \else \usepackage{unicode-math} \fi .. Khaled kindly corrected me off list. This test file is faulty, prior to 2013 \Umathchar wasn't defined (just \XeTeX...) so the test file takes the classic tfm font route on old installations, which

[XeTeX] setting math parameters via fontdimens (or other means)

This document \documentclass{article} \ifx\Umathchar\undefined \usepackage{lmodern} \else \usepackage{unicode-math} \fi \begin{document} \sbox0{$x$} \typeout{\expandafter\meaning\the\textfont2} \fontdimen16\textfont2=20pt $a_b$ \end{document} If processed with pdflatex has an

Re: [XeTeX] semantic nest size

well yes \text makes the thing be set four times as many times as \mbox so does stress the semantic nest a bit but not as much as that usually, but without a reproducible test hard to say exactly what is wrong. On 12 April 2018 at 19:14, Apostolos Syropoulos wrote: >>I

Re: [XeTeX] semantic nest size

I don't have those fonts and couldn't reproduce the error when I tried switching to other fonts so I can't trace the exact cause of the error, but the error is not entirely surprising, unicode-math does document that it must be called after amsmath I get no error from the file below (using random

Re: [XeTeX] Xetex equiv to luatex's \directlua{}

The format is described in the TeXBook but in short .\hbox(7.71974+2.25569)x360.0, is a box of height 7.71974pt, depth 2.25569 and width 360.0pt nested one level inside some other box \hbox(0.0+0.0)x17.0 is a box of height and depth 0 and width 17pt (it will be the indentation box) that

Re: [XeTeX] Xetex equiv to luatex's \directlua{}

there are several ways to get the box output in classic tex (or xetex) although perhaps the easiest (and safest in terms of not accidentally affecting the typeset positions) is to use \showoutput so all boxes are (somewhat verbosely) logged in the log file, and then parse that with perl or python

Re: [XeTeX] "typeset by bidi" message

On 28 January 2018 at 01:25, wrote: > > ... > I think there is a human issue here that will not be solved by a purely > technical fix. > > Exactly. in this case, I asked that the package flip its default to off so it only adds the text if requested and Vafa kindly

Re: [XeTeX] "typeset by bidi" message

Getting the timing right with passing this option to bidi via polyglossia is a bit tricky see https://tex.stackexchange.com/questions/411907/suppress-bidis-logo-when-using-polyglossia the bidi author gives some justification for this here https://github.com/tex-xet/bidi/issues/60 but to be

Re: [XeTeX] Conflict among XeLaTeX, LaTeX.mk, and pdfpages

(apparently) you need to run extractbb testa.pdf after processing testa.tex and before testb.tex not sure if pdfpages should not require this but in any case the issue seems to be at the macro layer not in the xetex or xdvipdfmx binaries. David On 1 January 2018 at 23:22,

Re: [XeTeX] Problem involving \includegraphics after texlive update on Debian Tesing

\Gin@log is defined in the core graphics.sty so it would seem that you have updated xetex.def but not graphics itself, or perhaps have an old copy in your path David On 7 July 2017 at 13:09, Joseph Wright wrote: > On 07/07/2017 12:54, Johann Spies wrote: >>

Re: [XeTeX] ".ttf" automatically added to font names

> So the only question remaining is: Will the xetex compiler developers keep it like this Note that mostly this is not a xetex question as you are using the syntax of the fontspec macro package rather than the xetex primitive font loading syntax (although of course these are not unrelated) it

Re: [XeTeX] Marathi Booklet for Polyglossia

I think you could put it on ctan, they take documentation uploads as well as tex code eg this entry for tex-by-topic https://www.ctan.org/pkg/texbytopic David On 3 May 2017 at 18:20, RD Holkar wrote: > Hello! > > I have been working on a booklet explaining how to use

Re: [XeTeX] are the intercharclasses mentioned in interchar.pdf correct?

On 27 March 2017 at 19:37, jfbu wrote: > .. ah, I don't think I'd noticed xetex was using _quite_ so many digits in its version number:-) as you say the test is a bit suspect but it works in the one case it needs to work so D guess it's OK! David

Re: [XeTeX] are the intercharclasses mentioned in interchar.pdf correct?

On 27 March 2017 at 17:18, Mike "Pomax" Kamermans wrote: > Are the predefined classes from > http://mirror.utexas.edu/ctan/macros/xetex/latex/interchar/interchar.pdf > still correct? are classes 255 (for boundary) and 256 (for unused) still the > right ones, are those

Re: [XeTeX] emdash and endash

On 18 February 2017 at 09:45, Zdenek Wagner wrote: > No, -- and --- are handled by tfm in traditional TeX, in XeTeX it is handled > by the teckit mapping. The keywords are either Mapping=tex-text or > Ligatures=TeX. I have not examined the packages in depth but it may be

Re: [XeTeX] emdash and endash

You could try updating (tuenc is 2017/01/24 v2.0c in the current release) but I don't think it's likely to be a macro issue --- ligatures are handled by tfm metrics or the tex-text mapping depending on the font type. Others on this list would be better able to suggest ways of debugging a failure

Re: [XeTeX] emdash and endash

It should work \documentclass{article} \listfiles \usepackage{fontspec} \begin{document} a---b \end{document} makes an emdash for me with current texlive. If you have an example that fails can you show log from such a test (\listfiles makes a list of package versions at the end of the log)

[XeTeX] misaligned math if \smash used in subscripts

The following first reported at the unicode-math github https://github.com/wspr/unicode-math/issues/383 but the problem can be seem with plain tex. In the tex below there are six repeated instances of a subscripted bracket they should all be the same but the first one is misaligned. It appears

Re: [XeTeX] unicode-math and ucharcat

ucharcat.sty isn't needed for xetex as it's already a primitive but if you have texlive 2016 you should have ucharcat.sty (or tlmgr install ucharcat should install it if for some reason it isn't installed already). That said unicode-matth could move the luatex-specific part, but really there's no

Re: [XeTeX] why does Latin Modern Mono have some stretch and shrink with XeTeX ?

> Using XeTeX without fontspec is a relatively unusual case and it's > unsurprising there hasn't been a lot of time spent on testing that. The > engine and package go together. It may become slightly less unusual after this week's latex release as now latex defaults to TU (Unicode) encoding with

Re: [XeTeX] why does Latin Modern Mono have some stretch and shrink with XeTeX ?

For latex at least I think the thing to do is amend tulmtt.fd in base so that it has \DeclareFontFamily{TU}{lmtt}{% \hyphenchar \font\m@ne \fontdimen3\font\z@%<< \fontdimen4\font\z@%<< } with the two extra lines ensuring that these two font dimens are set to 0. (If you try this with a latex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

On 15 January 2017 at 09:20, Philip Taylor wrote: > > > But all of this is besides the point : surely > > o XeTeX --output-directory=../dynamic-content foo (or foo.tex) > > should compile foo.tex, not ../dynamic-content/foo.tex > > ** Phil. > No I think not, if

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Phil, > E:\TeX\Projects\WBH\Welcome>xetex foo --output-directory=../dynamic- content > (./foo.tex This is the intended foo.tex ) isn't that just because the flags after the filename are ignored? Personally I'd just add it to the end of the list of reasons never to use --output-directory,

Re: [XeTeX] Are the new etex changes reflected in XeTeX? (was XeTeX bugs in bidirectional typesetting)

On 21 November 2016 at 12:28, Vafa Khalighi wrote: > Hi David > > > Sure \textdir works in vertical mode in luatex but luatex's behavior is > buggy. For instance, consider the following minimal example > > > > {\textdir TRT This} is just a test. > > > \bye > > > As you can

Re: [XeTeX] Are the new etex changes reflected in XeTeX? (was XeTeX bugs in bidirectional typesetting)

On 20 November 2016 at 23:28, Arthur Reutenauer wrote: >> If you do find time to look at this... the other main issue besides \specials >> where the current model causes problems is the inability to specify direction >> while in vertical mode. The restriction to

Re: [XeTeX] Are the new etex changes reflected in XeTeX? (was XeTeX bugs in bidirectional typesetting)

On 20 November 2016 at 18:19, Jonathan Kew wrote: > This is very interesting, I didn't know Peter had done that. I think this is > the right way forward (for an etex-based engine such as xetex), and had been > hoping to find the time to work on essentially the same idea in

Re: [XeTeX] XeTeX bugs in bidirectional typesetting

gt; fixed. The only issue was that the original TeX-XeT model adds \beginL > ... \endL and that would cause some problem in math typesetting > (sorry, I can not remember what exactly it was about but I remember it > was reported by David Carlisle). For this problem, one can look at > TeX-

Re: [XeTeX] Random number primitives

On 14 November 2016 at 09:22, Apostolos Syropoulos wrote: >> >> Changing the source isn't the issue, are you offering also to help >> with user support to manage the change >> and explain to people why it's not possible to re-create documents >> that they created before

Re: [XeTeX] Random number primitives

On 13 November 2016 at 16:50, Apostolos Syropoulos wrote: > > OK please let me know how the pdftex thing is implemented and I will do the > thing with drand48. Then people can check the implementation, etc. > > A.S. > People using a fixed seed to get reproducible results

Re: [XeTeX] Random number primitives

On 13 November 2016 at 16:47, Apostolos Syropoulos wrote: >> >> That's true except that as pdftex and luatex have this already and have had >> for years, in this particular instance it's playing catchup that is >> being suggested. >> Not promoting novel functionality. >> >

Re: [XeTeX] Random number primitives

On 13 November 2016 at 15:46, Apostolos Syropoulos wrote: > Let me say that I find this point of view far too conservative. OK METAFONT > lives in the previous century but luatex and xetex are products of this > century so they must utilize what is better. Also, the point

Re: [XeTeX] Random number primitives

On 13 November 2016 at 13:58, Apostolos Syropoulos wrote: > > > Thank you very much for your prompt response. I would say that > this feature makes the typesetting engine more independent and > this is definitely a good thing. Also, I think it should be > implemented using

[XeTeX] atopwithdelims

I've been looking to see if I can make \atopwithdelims and related commands a little more consistent between the tex engines (specifically in relation to the amsmath \genfrac usage) Short version: would it be possible to make \atopwithdelims scale \Udelimiter specified delimiters to a size

Re: [XeTeX] Devanagari, xelatex, and \footnote

If you base it on catcode changes it will never work in the argument of another command, not just footnotes. There is no need to switch catcodes. leave ~ as active always and when you want it locally to be a normal ~ do \edef~{\string~} so the active ~ just expands to a non-active one. David

Re: [XeTeX] How to reduce terminal output from xelatex?

> xelatex "\def\istwocol{1} \input{./tmpmyfile.tex} -max-print-line=2048 > -c-style-errors -interaction=batchmode" You are applying the options too late so they are ignored. xelatex -max-print-line=2048 -c-style-errors -interaction=batchmode "\def\istwocol{1} \input{./tmpmyfile.tex}"

Re: [XeTeX] [tex-live] Seemingly inexplicable shift in page origin between TL 2014 and TL 2016

but if you have an up to date system it is in the documented code (texdoc color.pdf) I should probably update grfguide at some point. David On 15 July 2016 at 09:24, David Carlisle <d.p.carli...@gmail.com> wrote: > On 15 July 2016 at 09:17, Philip Taylor <p.tay...@rhul.ac.uk>

Re: [XeTeX] [tex-live] Seemingly inexplicable shift in page origin between TL 2014 and TL 2016

On 15 July 2016 at 09:17, Philip Taylor <p.tay...@rhul.ac.uk> wrote: > P.S. Option "nosetpagesize" does not seem to appear in the PDF output of > "TeXdoc color", for the version of 2016/05/22. well no, it wouldnt. 2016-06-02 David Carlisle <latex-b...@lat

Re: [XeTeX] [tex-live] Seemingly inexplicable shift in page origin between TL 2014 and TL 2016

Phil, > And why does : > >\input miniltx > \input color > /not/ change my page size ? as stated earlier, if used under latex the specified page size is known and set in the latex allocated registers \paperheight/paperwidth, but if used under plain these are not set and that section of

Re: [XeTeX] [tex-live] Seemingly inexplicable shift in page origin between TL 2014 and TL 2016

On 15 July 2016 at 00:19, Ross Moore <ross.mo...@mq.edu.au> wrote: > Hi David, > > On Jul 15, 2016, at 8:49 AM, David Carlisle <d.p.carli...@gmail.com> > wrote: > > > well that'll be the page size special change as mentioned earlier I assume. > >

Re: [XeTeX] [tex-live] Seemingly inexplicable shift in page origin between TL 2014 and TL 2016

On 14 July 2016 at 23:40, Philip Taylor wrote: > It transpires that it is /not/ the PDF/X-1A \specials that are the root cause > of the problem. It is the use of > > \input eplain > \beginpackages > \usepackage {color} > \endpackages > > If I replace this with what I

Re: [XeTeX] [tex-live] Seemingly inexplicable shift in page origin between TL 2014 and TL 2016

On 12 July 2016 at 16:17, Philip Taylor wrote: > \advance \voffset by 1 true in % REQUIRED ONLY FOR TL 2016 If it's really a difference in texlive check that you specified the same default driver page size (presumably A4) in both installations, not A4 in one and letter

Re: [XeTeX] Grey fonts with XeTeX

On 29 June 2016 at 13:35, Philip Taylor <p.tay...@rhul.ac.uk> wrote: > > > David Carlisle wrote: > > see the color package documentation > > I tried this again today, David, and came up with a new problem which I do > not understand. Are you able to explain why the

Re: [XeTeX] xelatex, hyperref, and new TeXLive

On 16 June 2016 at 00:25, Ross Moore wrote: > Hi Mike, David, Herb, > > I’m seeing the same behaviour, but for me the packages are as follows: > > (/usr/local/texlive/2016/texmf-dist/tex/latex/latexconfig/hyperref.cfg) > >

Re: [XeTeX] xelatex, hyperref, and new TeXLive

On 16 June 2016 at 00:08, Herb Schulz wrote: > Howdy, > > Again, sorry for the top post. > > Does > > kpsewhich hyperref.cfg > > really return a file in the .../doc/... branch? > Oh of course! well spotted. So that is the error. The file is correctly installed in the

Re: [XeTeX] xelatex, hyperref, and new TeXLive

On 15 June 2016 at 23:46, maxwell <maxw...@umiacs.umd.edu> wrote: > With the help of David Carlisle and Herbert Schulz, I've found part of the > problem. For some reason, in the (our?) 2016 version, kpsewhich points to > this hyperref.cfg file: >...texlive/2016/texmf-dist/

Re: [XeTeX] xelatex, hyperref, and new TeXLive

I get the same error with texlive 2015 so I don't think there is any recent change (since support for hyperref moved to github) that has changed this, with texlive 2015: (/usr/local/texlive/2015/texmf-dist/tex/latex/hyperref/pd1enc.def)

Re: [XeTeX] xelatex, hyperref, and new TeXLive

On 15 June 2016 at 21:56, maxwell wrote: > We've downloaded and installed the new 2016 TeXLive distribution. I was all > set to be happy...but. There seems to be an incompatibility between the new > xelatex and the new hyperref package. No matter what I do, I get the

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On 13 March 2016 at 10:14, Philip Taylor <p.tay...@rhul.ac.uk> wrote: > > > David Carlisle wrote: > >> Philip Taylor <p.tay...@rhul.ac.uk> wrote: > >>> Also please consider the following text from Wikipædia : >> (Well from Wikipedia actually) >&

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On 13 March 2016 at 09:43, Philip Taylor wrote: > Also please consider the following text from Wikipædia : (Well from Wikipedia actually) Yes the relevant part is > On many systems, the higher the value, the more severe the > cause of the error. so the status code should

Re: [XeTeX] Handling of combining and variant selector characters in math

nt? > > David > Note I was using Khaled's xits-math variant not the original stix version, xits-math has many improvements to the opentype internals. The VS1 combinations in xits-math work for example in firefox. David > > On 2/9/2016 8:54 AM, David Carlisle wrote: > > Sending th

Re: [XeTeX] Copyright page with \pagestyle{empty} clears all styles

That seems to be a general latex question rather than anything xetex related, but to affect just one page use \thispagestyle not \pagestyle David On 6 February 2016 at 11:26, Shakthi Kannan wrote: > Hi, > > I have released the Tamil-English XeTeX customized book template

Re: [XeTeX] not enough \XeTeXcharclass registers

Thanks for the test sources, It all seems to work for me (texlive 2015/cygwin 64 build), but.. I do wonder if this change is going in the right direction. The main problem with the char classes is not the overall number, in fact since the important thing as far as specifying code is the

Re: [XeTeX] not enough \XeTeXcharclass registers

On 1 February 2016 at 10:53, Jonathan Kew <jfkth...@gmail.com> wrote: > On 1/2/16 10:25, David Carlisle wrote: > >> y. >> > > You're right, of course; this is a limitation of the concept as currently > implemented. > > In practice, I suppose I don't ex

Re: [XeTeX] misplaced accents in printout only?

On 20 January 2016 at 23:42, Zdenek Wagner wrote: > As far as I know nowadays with HarfBuzz it does nothing, HarfBuzz handles > normalization in its own way. > > Zdeněk Wagner > http://ttsm.icpf.cas.cz/team/wagner.shtml > http://icebearsoft.euweb.cz > > 2016-01-21 0:35

Re: [XeTeX] [6933] luatex output encoding

In experiments with using the inputencoding for latex https://github.com/wspr/xetex-inputenc/blob/master/xetex-inputenc.dtx deal with that problem by writing \XeTeXinputencoding "utf8" at the top of the auxiliary file so that it is read back in utf8 even if the main document is using a legacy

Re: [XeTeX] not enough \XeTeXcharclass registers

On 13 December 2015 at 07:04, Werner LEMBERG wrote: > > [XeTeX 3.14159265-2.6-0.2 (TeX Live 2015)] > > > Folks, > > > I'm updating the `ucharclasses.sty' to completely cover Unicode. This > style file maps Unicode character blocks to character classes, and > I've hit the 256

Re: [XeTeX] Problem with bidi + longtable + caption packages

On 21 October 2015 at 02:34, Herbert Schulz wrote: >> On Oct 20, 2015, at 7:55 PM, maxwell wrote: >> > The longtable environment is like a tabular environment, not the same as a > floating environment like the teble environment. It's floats that

Re: [XeTeX] Problem with bidi + longtable + caption packages

On 21 October 2015 at 01:55, maxwell wrote: > (Apologies if this isn't the right mailing list--the documentation I have > says I should send this to persian-...@tug.org, but I don't see that mailing > list on the list of TUG mailing lists, nor am I subscribed to it... and

Re: [XeTeX] Problem with bidi + longtable + caption packages

The caption wasn't really centred (hard to tell as the text was short) it is a justified paragraph (set in a centred box) the problem is that bidi doesn't "patch" the caption code to add \beginR it redefines the standard one, so over-writing the caption package changes. The following simply

Re: [XeTeX] Discretionary hyphens don't work in paragraphed footnotes

On 8 October 2015 at 09:25, Philip Taylor wrote: > > > Zdenek Wagner wrote: > >> I have no time to look deep into it but does anybody know what is the >> definition of \- if these packages is used? Isn't is possible that it is >> a fragile macro? I remember one thing from

Re: [XeTeX] Discretionary hyphens don't work in paragraphed footnotes

On 8 October 2015 at 09:50, Philip Taylor wrote: > Hmmm, completely stymied : not even this works ... It wouldn't be expected to really, this was asked on stackexchange initially and it looks almost certainly due to the interface between tex's hyphenation and the font

Re: [XeTeX] Discretionary hyphens don't work in paragraphed footnotes

> Yes, it's very possible this is an engine bug. What would be most useful > here, I think, would be a reduced (non-LaTeX!) > testcase demonstrating the > underlying incorrect behavior at the (Xe)TeX primitive level. Any takers? I'll see what I can do David

Re: [XeTeX] Discretionary hyphens don't work in paragraphed footnotes

Here is a plain tex example, not quite as minimal as I'd like but out of time for now. This hyphenates with pdftex but not xetex \nopagenumbers \catcode`\@=11 \ifx\Umathchar\@undefined \font\x=cmr12 \else \font\x="[lmroman12-regular]:mapping=tex-text" \fi \x \newbox\FN@tempboxa

Re: [XeTeX] Discretionary hyphens don't work in paragraphed footnotes

On 8 October 2015 at 17:53, Dominik Wujastyk wrote: > The original questioner said he was doing a critical edition. If he's using > EDMAC or LEDMAC then perhaps I can note that EDMAC does some work to avoid > setting footnote text in "restricted horizontal mode". Restricted

Re: [XeTeX] Does there exist the equivalent of testfont.tex/fonttable.tex for XeTeX?

On 12 June 2015 at 16:05, roger ro...@herz-fischler.ca wrote: As François Charette states on page 4 of his ««ArabXeTeX Manual»» there is a great advantage to being able to input a language via code rather than typing the glyph. This is particularly true if the language is not one that you

[XeTeX] (not) understanding XeTeXinterchartoks

The following plain xetex document loops forever on \show\tmpb the \show don't cause the looping, if they are replaced by \def\zzzb{} xetex just hangs in a tight loop. The fact that it loops isn't necessarily a bug. \def\zzz{\zzz}\zzz does the same, but are there any words that could be added

  1   2   >