David got mislead. The truth is rather stranger: it seems the width of the
image used when placing glyphs of a given hlist on the page is different from
(and larger than) the width of the image used when measuring the total box size.
For instance "!" does not get eaten: it overlaps with the
For those who want a complete working example based on Yiannis' code, here is
one, to be compiled with "xetex -ini -etex test.tex" and in which the arabic
"word" is hyphenated at every letter.
Thank you Yannis and others.
Bruno
On 3/25/21 6:50 PM, Yannis Haralambous wrote:
> Silly of me, when
Check \the\catcode"200D perhaps, it does not seem to be set in your example
document. Note that the LaTeX format might reset that catcode.
The other mystery is why Arabic words seem to only be hyphenated once.
On 3/25/21 5:17 PM, Yannis Haralambous wrote:
> Well it is neither polyglossia nor
>> So what am I missing in my code, Jonathan ? I have added a \hyphenchar,
>> removed the pointless (and dysfunctional) \showhyphens), but still get no
>> hyphenation —
>>
>> % !TeX Program=Ini-XeTeX
>>
>> \catcode `\ = 10
>> \catcode `\ = 10
>> \catcode `\{ = 1
>> \catcode `\} = 2
>>
Could you add the following two lines to the start of your file and check for
"Missing character" messages?
\tracingonline 1
\tracinglostchars 2
On 3/25/21 11:22 AM, Yannis Haralambous wrote:
> When I run the same file with Amiri:
>
> % !TeX Program=Ini-XeTeX
>
> \catcode `\ = 10
> \catcode
Hello Yannis,
On 3/25/21 10:41 AM, Yannis Haralambous wrote:
> This is XeTeX, Version 3.141592653-2.6-0.93 (TeX Live 2021) (preloaded
> format=plain)
> restricted \write18 enabled.
> (./test.tex
> Underfull \hbox (badness 1) in paragraph at lines 6--6
> *[] \tenrm blabla*
> [1] )
> (see
Hi Ross,
On 2/21/21 10:42 PM, Ross Moore wrote:
> Hi Ulrike,
>
>> On 22 Feb 2021, at 7:52 am, Ulrike Fischer wrote:
>>
>> Am Sun, 21 Feb 2021 20:26:04 + schrieb Ross Moore:
>>
>> > Once you have encountered the (correct) comment character,
>> > what follows on the rest of the line is going
On 7/3/20 6:50 PM, Jonathan Kew wrote:
> On 03/07/2020 16:26, Philip Taylor wrote:
>> 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
On 7/3/20 1:46 PM, Philip Taylor wrote:
> It would seem that adding the command-line qualifier "--shell-escape" is
> required in order that \write 18 be permitted, but then we run into the
> problem
> that (with the benefit of hindsight) we should have foreseen at the outset :
> the PDF file is
On 11/3/19 6:57 PM, Taylor, P wrote:
> Taylor, P wrote:
>
>> Many thanks for the warning, Bruno — will amend code accordingly.
>
> The following would seem to suffice for now :
>
>
> % \ifcase \numexpr \strcmp {\the \XeTeXversion \XeTeXrevision} {0.9}
> + 1 \relax
>
> \ifcase
Note that the version test using \ifdim is unsafe because values are
rounded to a certain number of scaled points before being compared.
On 11/3/19 5:27 PM, Taylor, P wrote:
> *\ifdim \XeTeXrevision pt < 0.9pt*
\ifdim 0.8pt < 0.9pt
% expected
\else
\UNEXPECTED
\fi
Perhaps try adding the following early enough in your document (before
any use of U+200B).
\catcode"200B=13 % (active)
\def 200b{\discretionary{}{}{}}
Regards,
Bruno
On 9/30/19 1:05 PM, Roland Kuhn via XeTeX wrote:
> From a programmer’s perspective it is usually much nicer to not have
>
On 5/14/19 08:50, Janusz S. Bień wrote:
> The paper was accepted and several days ago I prepared a final
> version. To my surprise almost all images was scaled down by
> XeLaTeX. The test shows the culprit is the presence of *.bb files. There
> are however some *.bb files which has no such side
{\expandafter\noexpand\Ucharcat `~ 13 }
run the code of the active ~ as if it had been typed directly, then show
its meaning, then do the equivalent of \def\foo{~}.
Bruno
>From ab3698191833315858cb5751af886230ffc2a82d Mon Sep 17 00:00:00 2001
From: Bruno Le Floch <br...@le-floch.fr>
Date
Hello Kamal,
On 01/25/2018 09:10 PM, Kamal Abdali wrote:
> My xelatex-processed document has this message on the title page of the
> document: *"Typeset by the bidi package."*
> **
> I understand that bidi is being called by polyglossia which I am using.
>
> I hadn't
> seen
> such a
Filed https://sourceforge.net/p/xetex/bugs/138/ with a text essentially
identical to my message below explaining the bug's origin and how to fix it.
On 04/16/2017 06:50 AM, Julian Bradfield wrote:
> On 2017-04-16, Zdenek Wagner wrote:
>> 2017-04-16 10:08 GMT+02:00 Julian
Dear all,
The primitive conditional "\ifcat\relax\cr true\else false\fi" gives
"true" in pdfTeX, LuaTeX, (e)(u)pTeX, and XeTeX from some time ago
(could be years), but "false" in XeTeX 0.6
It would be useful for me to know which of \ifcat, \relax, and \cr
changed, to determine whether I
On 11/14/2016 04:47 AM, David Carlisle wrote:
> 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
On 08/01/2016 01:01 PM, Philip Taylor wrote:
>
>
> Zdenek Wagner wrote:
>> Append >/dev/null in unix systems or >null in Windows, it will send
>> all terminal output to a black hole.
> Er, yes, but is that what ShreeDevi meant by "reduce" ? "Reduce" and
> "eliminate" are not the same, IMHO. Is
On 08/01/2016 12:51 PM, Zdenek Wagner wrote:
> Append >/dev/null in unix systems or >null in Windows, it will send
> all terminal output to a black hole.
>
> Zdeněk Wagner
> http://ttsm.icpf.cas.cz/team/wagner.shtml
> http://icebearsoft.euweb.cz
>
>
> 2016-08-01 12:42 GMT+02:00 ShreeDevi Kumar
On 7/12/16, Philip Taylor wrote:
> I have just installed TeX Live 2016 for the first time, using the "small"
> scheme and a couple of additional options, but I find when I try to
> re-generate /The Oral History of Horsmonden/ that the entire page image has
> been displaced
On 2/8/16, Philip Taylor wrote:
> P.S. Experimenting against both versions, I found that what Python 3
> detected as syntax errors in the Version 2 source prevented the test
> from ever being evaluated, but the following three changes allow the
> diagnostic to be issue
On 2/1/16, David Carlisle wrote:
> On 1 February 2016 at 10:53, Jonathan Kew 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
Here's a shorter example which hyphenates with cmr12 (in pdfTeX/XeTeX)
but not with the font copied from David's example: hyphenation is lost
when closing the hbox, as can be seen by adding the appropriate
\tracingonline=1\showboxbreadth=99 and \showlists just before the
closing brace.
I have no
On 10/8/15, David Carlisle wrote:
> 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
Sorry to add yet another a voice to the discussion. I agree with
Apostolos Syropoulos that the adding primitives to XeTeX should be
limited, but I disagree on other points.
On 7/2/15, Apostolos Syropoulos asyropou...@yahoo.com wrote:
So someone will step in and implement this primitive but then
It appears that the Unicode Core Specification (version 7.0.0) defines
in Table 3-14 what a Final Sigma is. A sigma is final if the previous
character is cased and the next is not, ignoring case-ignorable
characters completely. To know which characters are
cased/case-ignorable, see the
On 4/24/15, Khaled Hosny khaledho...@eglug.org wrote:
On Fri, Apr 24, 2015 at 11:55:41AM +0100, Philip Taylor wrote:
Will Robertson wrote:
On 24 Apr 2015, at 1:51 am, Khaled Hosny khaledho...@eglug.org wrote:
Even shorter:
\ifnum\XeTeXcountvariations\font0\fi\bye
:)
Phew! Glad to
On 7/15/14, maxwell maxw...@umiacs.umd.edu wrote:
I'm attaching the minimal file below. The PDF output has a blank line
between the first and second footnotes, which IMO shouldn't be there. I
don't get this result if bidi isn't loaded, and with bidi loaded I only
get this result if the last
Hello all,
On 5/4/14, David Carlisle d.p.carli...@gmail.com wrote:
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.
I think it should not be too hard to use the
Hello,
This is caused by fontspec, I'd say, due to somewhat recent changes in
the expl3 supporting package: \c_keys_code_root_tl was renamed
\c__keys_code_root_tl at some point, to reflect its internal nature,
and fontspec should not be using it. I don't know if this was fixed
in more recent
Hello,
I'm the author of morewrites, which has to perform various hacks to go
around the hard limitation of the number of TeX output streams (see
the thread that you linked: TeX has not changed in this regard). My
guess is that it is probably a bug in morewrites. Please try to make
a reasonably
On 5/14/12, Ross Moore ross.mo...@mq.edu.au wrote:
Hi Ulrike, and Bruno,
On 13/05/2012, at 11:05 PM, Ulrike Fischer wrote:
Am Fri, 11 May 2012 19:44:00 +0200 schrieb Bruno Le Floch:
I'm really no expert, but the siunitx package could include, e.g., µ
as 00b5. This would not make
On 5/14/12, Ulrike Fischer ne...@nililand.de wrote:
Am Mon, 14 May 2012 09:19:18 +1000 schrieb Ross Moore:
But it doesn't solve the problem here as pdftex chokes if it sees
more than two ^^:
... this is not a good example to support this view.
\documentclass{article}
\begin{document}
On 5/11/12, Joseph Wright joseph.wri...@morningstar2.co.uk wrote:
On 11/05/2012 17:36, Tobias Schoel wrote:
Hi,
I have done a few tests with the problematic symbols in siunitx (namely
micro, ohm, angstrom, celsius, degree/arcsecond/arcminute) and different
math fonts. You'll find source and
As Tobias mentions, use a package for loops. I think the code below
should work, but I don't know how to build diacritics on a letter:
isn't the point of combining marks that just putting the two
characters next to each other should do the trick? I didn't test.
\documentclass{article}
I tried runing your code, but I get the following message:
! Missing number, treated as zero.
to be read again
*
l.20 \maketable{c,0}{1,2}
I knew I should've tested that code.
\documentclass{article}
\usepackage{xparse}
\usepackage{array}
\ExplSyntaxOn
I'm having an issue with the .aux file being incomplete in two
different files I am working with.
Did you try deleting the auxiliary files then running TeX again?
Usually, going with a clean slate helps in cases like that.
Regards,
Bruno
--
On 1/1/12, Michael Sharpe msha...@ucsd.edu wrote:
On Jan 1, 2012, at 10:46 AM, Jean-Louis Cordonnier wrote:
In order to write genetics, I need something like $\frac{A}{a}$ but with
a double horizontal bar -- and left( and right)
I tried this, but there is too much white around it.
On the quotes front, one answer, generally inapplicable, is to move away
from Anglo-Saxonia and to use « and », and double quotes within quotations.
Most programs handle that automatically now.
In a XeTeX context, « and » could be made active, and expand to the
relevant language-aware quotes,
It would still be better to have an engine-level solution. Morewrites
is definitely a hack.
Update the l3kernel bundle to the newest version
OK, thanks! I am hoping to complete and deliver a major project this
month, so I don't want to risk a major update to my Texlive system at
this point;
Has there been any progress on getting around the 16 open write file
limit and the associated crash message
No room for a new \write?
This has been causing me problems lately.
\usepackage{morewrites}
If you are using XeLaTeX (or any other *LaTeX). It won't work if
filenames contain
. It's sort of mentionned in the doc of
morewrites (but I really should've added an explicit test in the
package, sorry).
Hope this helps,
--
Bruno Le Floch
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Is it simply a matter of going through the string and replace various
characters by TeX accents (and take care of character order), or does
the result have to be Unicode?
E.g., does it have to be a(a^ → ăâ, or can it be a(a^ → \u{a}\^{a} ?
If the second one is ok, then it shouldn't be too hard to
Bruno Le Floch wrote:
Is it simply a matter of going through the string and replace various
characters by TeX accents (and take care of character order), or does
the result have to be Unicode?
E.g., does it have to be a(a^ → ăâ, or can it be a(a^ → \u{a}\^{a} ?
If the second one is ok
There's hardly big bucks involved here.
If you think you can improve the performance of this package,
while retaining its overall structure, then the nicest way
to do it is to write a small wrapper package that requires
ucharclass and then patches some of its internal macros
to work more
*sigh*
On 10/23/11, Zdenek Wagner zdenek.wag...@gmail.com wrote:
2011/10/23 Philip TAYLOR (Webmaster, Ret'd) p.tay...@rhul.ac.uk:
Tobias Schoel wrote:
Besides, I also wouldn't do, if it was allowed. Who knows, what methods
the author employs in order to enforce the discouragement? ;-)
I
.
Instead, you can create your own package which can be loaded on top of
uchar.sty or you can put your changes at the preamble of your
document.
It turns out not to be possible to fix the problem without fixing
ucharclasses.sty itself.
Regards,
Bruno
On Sun, Oct 23, 2011 at 6:14 AM, Bruno Le
Hello all,
Loading the ucharclasses package with no option is extremely slow (
2min on my installation), because it loads every Unicode block (as
documented).
The performance can be significantly improved by using lower-level
code for the loops. For instance, using the following helper macro
Hello,
I would like to know if it is possible to access the Unicode
properties of a given character from within XeTeX (e.g., Upper case
letter, or Surrogate character).
I am thinking of this in the context of a recent experimental addition
to LaTeX3 of a regular expression engine. Currently, it
50 matches
Mail list logo