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 xetex, but
> so far the
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 hmode was probably needed in
>> te
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 see there is no indent a
On 21 November 2016 at 12:42, Vafa Khalighi wrote:
> When TeX is building a LTR paragraph, if there are some overfull \hbox s,
> then they stick out at the right of the offending box (please see the
> example on page 27 of The TeXBook and Knuth explanation).
>
>
> When one is typesetting a right t
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,
althoug
On 14 January 2017 at 17:39, Philip Taylor wrote:
>
>
> David Carlisle wrote:
>
> >> E:\TeX\Projects\WBH\Welcome>xetex foo --output-directory=../dynamic-
> content
> >> (./foo.tex This is the intended foo.tex )
> >
> > isn't that
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 you do not give a full
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 2017
> 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
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 r
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 t
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)
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 fo
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 added
> automaticaly. The
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 now 4095 and 4096? (based on
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
---
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 package polyglossia
> for
> 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 mi
\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:
>> After a recent upgrade of texlive to
graphicx.sty1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR)
keyval.sty1999/03/16 v1.13 key=value parser (DPC)
graphics.sty2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR)
trig.sty1999/03/16 v1.09 sin cos tan (DPC)
graphics.cfg2016/06/04 v1.11 sample graphics configu
(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, wrote:
> I've run
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 hone
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 agreed and has just sent
an upda
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
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 is
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
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 don't have those fonts and
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 excessively
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 acc
This was cross posted to tex.sx and (apparently) resolved there
https://tex.stackexchange.com/questions/483661/book-index-overflows-bottom-margin?noredirect=1#comment1223103_483661
David
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.
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 unde
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 a
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
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 mat
here
shouldn't be seen as a discouragement and anyway gives you more
flexibility with changing names etc while 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
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
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
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
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
> > part
> \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
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 \special{x:
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 top
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 would
>\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 exp
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.
>
>
>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 github
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
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.
> But anyway,
On Sun, 21 Feb 2021 at 20:27, Ross Moore wrote:
> Hi David,
>
> Surely the line-end characters are already known, and the bits&bytes
> 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
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:
>
> \R
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 ^^
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 d
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 o
Bruno wrote
> David got mislead.
Yes sorry too many programming languages in head at once today:-)
\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 mis
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 inclu
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{Երևան}
Երևան
gt; Zdeně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{polyg
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 (variable)
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
>
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 (Helle
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 xete
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⟩ |
You could switch to luatex then append from Lua.
Failing that, more efficient than repeatedly reading and copying in tex
way would be to not append but write a new file each time file-1.x
file-2.x ... then concat them in your operating system concat in a nix
shell, or copy*.x > realfile.txt in
the same error is in classic tex (with the same fixed value)
tex.ch has
The length of |dvi_file| should not exceed |@"7FFF|; we set |cur_s:=-2|
to prevent further \.{DVI} output causing infinite recursion.
@z
@x [32.601] l.11918 - dvi_swap: check dvi file size
begin if dvi_limit=dvi_buf_siz
101 - 166 of 166 matches
Mail list logo
