I'm trying to update the bm package to work with xetex (and luatex,
but concentrating on xetex for now) and in particular to work with
unicode-math package.
bm needs to look at each token (after expansion) and if it is a
character look up the mathcode and construct a suitable bold
replacement.
On 7 January 2013 17:39, Khaled Hosny khaledho...@eglug.org wrote:
This is already fixed in the development version, it now returns:
the letter number 1D6FC
ooh, OK thanks:-)
since I need to decode this in macros could you say when it switches fro
the letter x
(in which case I need to use `x
(in which case the number is just there explicitly)
is it just a function of the Unicode range?
When x = 0x1 (i.e. outside BMP).
Guessed as much, thanks. Although thinking about it a bit more it
doesn't really help knowing that as I need to parse out past number
before I know what the
In a similar thread ,\meaning or \show on a mathchardef'ed character
such as \sumop
in xetex gives
\sumop=\XeTeXmathchar202211
in luatex
\sumop=\Umathchar12211.
the luatex version looks distinctly odd but is legal input.
With the xetex version if you input it
! Bad math class
On 9 January 2013 14:28, Khaled Hosny khaledho...@eglug.org wrote:
It does now.
Thanks
David
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On 12 January 2013 15:58, Nathan Camillo Sidoli sid...@waseda.jp wrote:
Is there anyway to change the math mode digits for only certain parts of a
text?
I have some math in Arabic text in a largely English document. I would like
to change the math mode digits in this parts to use Eastern
On 18 April 2013 05:17, Wilfred van Rooijen wvanrooi...@yahoo.com wrote:
Avoid file names with an unusual number of dots (unusual is
everything not equal to 0).
I would say everything not equal to 1. In fact, I am surprised that
graphicx processes the file name with two dots correctly.
I'm sorry I can not read the script and am not that familiar with the
footnote package that you are using, but footnotes should work in
longtable. If I join your two tables together as one longtable so the file
ends with
نظري أو كشفي\فمب ٣٩\\
\footnote{في المتن: كشفى.}
\hspace{2cm}
This came up on Stackexchange here:
http://tex.stackexchange.com/a/149526/1090
If I include an image using \XeTeXpicfile and then follow it with a box
in the same hlist then the box seems to be oddly offset, and overprints the
following text. If I put the \XeTeXpicfile into its own hbox, the
Phil wrote
Not as good as Knuth's, as it typesets the output rather than
If you wanted something that worked like \showhyphens you could do this
It produces the following with xetex
Underfull \hbox (badness 1) in paragraph at lines 1--1
[] \tenrm good-bye hy-phen-ation
Underfull \hbox
XeTeX My-file
..
XeTeX LaTeX My-LaTeX-file
Philip that's not been true for so long I'm surprised you can remember
that far back:-) all the web2c engines load formats based on their
name, there is no intrinsic difference between say pdflatex with a
preloaded latex and pdftex with a pre loaded
Would it be possible (ever:-) to add a \Uchar primitive like that in luatex?
So like \char but is expandable and returns a character token rather than a
typesetting primitive.
This would be useful in lots of situations, in particular for lowercase
constructs and encoding mapping. In classic TeX
On 29 July 2014 10:55, Khaled Hosny khaledho...@eglug.org wrote:
On Mon, Jul 28, 2014 at 07:25:39PM +0200, Khaled Hosny wrote:
On Mon, Jul 28, 2014 at 10:24:39PM +1000, Vafa Khalighi wrote:
Thanks, fixed.
Thanks. I will try that. I know that in the new algorithm, \beginR,
On 29 July 2014 12:55, Vafa Khalighi texpers...@gmail.com wrote:
If you are looking at extending xetex's RTL support is there any
chance of addressing RTL tables (as affects for example longtable in
the other thread)?
as the nodes can only go in hmode there is no good place to put them
to
\hbox \bgroup $\beginR
but couldn't you just do
\hbox \bgroup \beginR$
to get the same, but working with older engines?
I will look at longtable and see if the same kind of thing can be done there.
I don't have it here but can you put \beginR at the start of $$ and
still have a display
On 29 July 2014 16:27, Khaled Hosny khaledho...@eglug.org wrote:
\hbox \bgroup \beginR$
That wouldn't work, as math (inline and display) are ensured to always
be LTR.
oh yes, I knew that really:-) sorry Vafa, I shouldn't have queried you:-)
David
On 8 December 2014 at 04:18, Mike Maxwell maxw...@umiacs.umd.edu wrote:
On 12/7/2014 7:14 PM, David Carlisle wrote:
If adding markup rather than a general setting is acceptable you can use
\mbox{-}abcd
I see that this works--I had not expected it to, so I didn't even try. What
I did try
I can confirm that \string does convert character tokens
to two tokens giving the UTF-16 representation.
With the attached file luatex produces
90,33
34,33
233,33
233,33
65530,33
65537,33
65537,33
which is in each case the unicode value of the character followed by that
of !
xetex produces
On 25 April 2015 at 18:31, Khaled Hosny khaledho...@eglug.org wrote:
Due to lack of time, skills and motivation, I’ll be no longer able to
work on XeTeX, so I’m stepping down as a maintainer.
Regards,
Khaled
Khaled,
thanks for all your work on this.
I have a horrible feeling that my
On 24 April 2015 at 18:35, Karljurgen Feuerherm kfeuerh...@wlu.ca wrote:
I tried all kinds of variations (including \texthebrew{} in the button
labels), but not this!
I guess the \textenglish{} wrappers keep things tidy, somehow?
Thanks so much.
K
Yes the problem is that the
This runs without error and I think gives the intended layout, although I
can not read the text, sorry.
\documentclass{article}
\usepackage{libertine,media9,polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguage[]{hebrew}
\begin{document}
\marginpar{\includemedia[
Last year I asked about the possibility of adding \Uchar copied from luatex.
http://tug.org/pipermail/xetex/2014-May/025260.html
Bruno suggested a possible implementation, and I finally got round to
trying that
adjusted for the sources as in the texlive 2015 pretest tree (diff attached)
This
On 27 April 2015 at 01:05, Douglas McKenna d...@mathemaesthetics.com
wrote:
Joseph Wright wrote:
\def\{0}\expandafter\def\csname^00022\endcsname{1}
\ifnum\=0 \message{tex82}\else\message{newstuff}\fi
When I implemented a Unicode escape sequence extension using double-caret
notation
On 27 April 2015 at 23:41, Douglas McKenna d...@mathemaesthetics.com
wrote:
Ross Moore wrote -
On 27/04/2015, at 10:05 AM, Douglas McKenna wrote:
Given that the number of TeX input files using ^^u is likely miniscule,
and the number of those that follow the ^^u or ^^U with four or six
On 7 May 2015 at 02:07, Ross Moore ross.mo...@mq.edu.au wrote:
Hi David,
..
No disagreement to this.
OK:-)
In the current versions d835dc00 is two characters in luatex
and one character in xetex
as the implementation detail that xetex's underlying storage is mostly
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
On 6 May 2015 at 23:04, Arthur Reutenauer
arthur.reutena...@normalesup.org wrote:
While working on these bugs, we also discussed how surrogate
characters were handled in XeTeX. Surrogate characters are the 2048
code points that are used in UTF-16 to encode characters with code
points above
The character itself, as bytes that is, is not wrong and users should be able
to create these.
But preferably through macros that ensure that they come correctly paired.
placing two character tokens representing a surrogate pair should not
though magically turn itself
into a single character.
On 6 May 2015 at 20:15, Philip Taylor p.tay...@rhul.ac.uk wrote:
Apostolos Syropoulos wrote:
It seems to me that most people have no idea what Unicode is and what is
really
involved.
OK, so if we restrict the Universe of Discourse to the set of native
Hellenic speakers who know what
On 4 May 2015 at 16:27, Jonathan Kew jfkth...@gmail.com wrote:
...
A fix for this bug, so that \string generates single Unicode characters
even for values above U+, is currently on the utf16-issues branch in
the XeTeX repository on sourceforge.[1]
A bug with characters above U+
On 8 May 2015 at 13:44, Jonathan Kew jfkth...@gmail.com wrote:
If what you want to do here doesn't involve inserting text,
yes, well what I wanted to do here was understand \XeTeXcharclass, so it doesn't
necessarily involve inserting text:-)
\XeTeXcharclass is a slightly strange beast as it
On 8 May 2015 at 11:45, Adam Twardoch (List) list.a...@twardoch.com wrote:
In modern text processing (Unicode+OpenType), a text run is a series of
characters with the same formatting (font, size, color etc.), directionality
(ltr, rtl) and script (writing system such as Latin, Greek, Arabic or
As noted in the release notes direction support now works in math
which is a good thing but a side effect seems to be that beginL endL
nodes are added to every math list
\tracingoutput1
\tracingonline1
$a$
\bye
generates
..\hbox(4.30554+0.0)x469.75499, glue set 444.4691fil
Is there no other way that the issues you have could be addressed
without introducing TeX-XeT?
The more we look at this the more it seems a very unfortunate step,
introducing several incompatibilities
with pdftex and luatex.
Especially if there is a possibility of moving in the end to an
On 15 April 2015 at 21:18, Khaled Hosny khaledho...@eglug.org wrote:
On Wed, Apr 15, 2015 at 09:07:05PM +0100, David Carlisle wrote:
Let me go and read some of those issues, thanks for the pointer,
Just in case it is not clear why reviving the long dead TeX-XeT is a fix
here; TeX-XeT does
On 15 April 2015 at 21:36, Zdenek Wagner zdenek.wag...@gmail.com wrote:
Hi all,
I do not want to vote but I feel that TeX behaviour was really wrong. When I
type an English paragraph quoting in a middle of a sentence an Urdu text آپ
جآمع مسجد کی مینار پر جا کستِ ہِں without special LTR/RTL
On 15 April 2015 at 21:19, Philip Taylor p.tay...@rhul.ac.uk wrote:
Khaled Hosny wrote:
On Wed, Apr 15, 2015 at 08:52:38PM +0100, Philip Taylor wrote:
Might it not be possible to resolve this by making the new behaviour
optional, using a new primitive for the purpose ?
So this just
On 15 April 2015 at 20:05, Khaled Hosny khaledho...@eglug.org wrote:
On Wed, Apr 15, 2015 at 04:29:47PM +0100, David Carlisle wrote:
Is there no other way that the issues you have could be addressed
without introducing TeX-XeT?
I first reported this issue in 2008, 7 years ago, so it seems
It is either that or live with dysfunctional right-to-left support in
XeTeX, it is obvious which one I’m going to chose, sorry.
Yes sure, sometimes you just have to make choices and live with them,
I understand that.
Let me go and read some of those issues, thanks for the pointer,
David
On 16 April 2015 at 01:21, Vafa Khalighi glkv...@gmail.com wrote:
I also support Khaled's changes to xetex; I only tested it few months ago
and if the issues I reported are fixed now, then it is good. And since when
LaTeX has a package/ or test files that uses \beginL \endL? All I remember
is
On 16 April 2015 at 12:35, Khaled Hosny dr.khaled.ho...@gmail.com wrote:
I’m testing a change that removes the direction node from around inline math
and instead (ab)uses the presence of \math(on|off) node to output the
necessary dvi opcode, and it seems to fix this issue as well. Lets hope
On 16 April 2015 at 11:54, Vafa Khalighi glkv...@gmail.com wrote:
I have not got TeXLive 2015 but that is just bad. Does the new xetex effect
any other of math typesetting that used to work fine with Knuth TeX?
yes see the example I posted in the second message I posted to this thread
in Knuth
To see a non contrived example where the change breaks existing
documents, take this example
(using a math expression from the breqn package documentation)
\documentclass[]{article}
\usepackage{breqn}
\begin{document}
aaa
\begin{dmath*}
g = 0 + 1 - 1
\end{dmath*}
\font\x=Arial at 12pt
\x
two verses:\beginR ק את אשפן וכ' ופסוק ואת הארנבת\endR; f.≈89r:
\bye
On 15 April 2015 at 21:54, Philip Taylor p.tay...@rhul.ac.uk wrote:
David Carlisle wrote:
Khaled will correct me if I'm wrong, but I don't think the change
affects this case, (internally
On 16 April 2015 at 20:51, Khaled Hosny khaledho...@eglug.org wrote:
On Thu, Apr 16, 2015 at 12:39:47PM +0100, David Carlisle wrote:
On 16 April 2015 at 12:35, Khaled Hosny dr.khaled.ho...@gmail.com wrote:
I’m testing a change that removes the direction node from around inline
math
On 17 April 2015 at 13:07, Julian Bradfield jcb+xe...@jcbradfield.org wrote:
On 2015-04-16, David Carlisle d.p.carli...@gmail.com wrote:
On 16 April 2015 at 20:51, Khaled Hosny khaledho...@eglug.org wrote:
That was very naive and did not work when inline math is broken over
multiple lines, so
On 17 April 2015 at 15:26, Philip Taylor p.tay...@rhul.ac.uk wrote:
David Carlisle wrote:
possibly but in the interests of keeping divergence of tex-related
engines to a minimum
as a first approach (if different approaches were being considered)
I'd look to what luatex
is doing, where
On 14 April 2015 at 17:47, David Carlisle d.p.carli...@gmail.com wrote:
As noted in the release notes direction support now works in math
which is a good thing but a side effect seems to be that beginL endL
nodes are added to every math list
The change introduces an incompatibility between
On 14 April 2015 at 21:14, Khaled Hosny khaledho...@eglug.org wrote:
On Tue, Apr 14, 2015 at 05:47:29PM +0100, David Carlisle wrote:
As noted in the release notes direction support now works in math
which is a good thing but a side effect seems to be that beginL endL
nodes are added to every
have used the xetex variant,
sorry, I meant to write
have used the etex variant,
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On 17 April 2015 at 21:43, Ross Moore ross.mo...@mq.edu.au wrote:
B.
I'm currently writing a paper describing a method to attach tooltips to
mathematical symbols and expressions. After setting the chunks in boxes for
measuring, this ultimately puts
\pdfannot
into the
Is there a good tool or TeXnique that lets one see the contents of a
math-stream, after all macros are processed, and during the internal
page-construction stage?
I'd like something a bit better than just examining box contents after
using \tracingall .
$x+y\showlists$
might be what you
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
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
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
> 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
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
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
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
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
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
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
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
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)
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
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/
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)
>
>
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
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
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
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
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
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
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
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)
>&
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
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
> 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}"
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
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
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>
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.
>
>
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
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
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
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
> 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
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
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
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
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
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
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
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
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.
>>
>
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
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-
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
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
1 - 100 of 151 matches
Mail list logo