On Mon, Feb 08, 2016 at 07:37:43AM +, 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 iss
On Sun, Feb 07, 2016 at 10:41:15AM +, Philip Taylor wrote:
>
>
> Khaled Hosny wrote:
>
> > Looks like you are using Python 3.x, but this code was written against
> > Python 2.x, so you will need to use that.
>
> Thank you, Khaled; all now works well (see belo
On Sun, Feb 07, 2016 at 09:48:06AM +, Philip Taylor wrote:
> I downloaded the most recent version available from Github yesterday,
> installed the most recent Python available for Windows, but 'dviasm'
> nonetheless reports :
>
> > $ dviasm hyperlinks.xdv
> > File "D:\(elided)\Oral history\T
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
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
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 wrote:
> >>
> >> Even shorter:
> >> \ifnum\XeTeXcountvariations\font>0\fi\bye
> >
> >
On Fri, Apr 17, 2015 at 03:31:33PM +0100, David Carlisle wrote:
> On 17 April 2015 at 15:26, Philip Taylor 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 approache
On Thu, Apr 16, 2015 at 12:39:47PM +0100, David Carlisle wrote:
> On 16 April 2015 at 12:35, Khaled Hosny 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
> > nece
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
that there is no some blackmagic^W deep
TeX hackery that plays with the this nod
On Wed, Apr 15, 2015 at 09:19:04PM +0100, Philip Taylor 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
On Wed, Apr 15, 2015 at 09:45:32PM +0100, David Carlisle wrote:
> On 15 April 2015 at 21:36, Zdenek Wagner 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 آپ
> > جآم
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 not do any actual reversal but rather outputs special
opcodes in the DVI fi
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 penalizes the unlucky people who need to enable the special
behaviour, I’d rather penalize everyone
On Wed, Apr 15, 2015 at 08:44:12PM +0100, David Carlisle wrote:
> On 15 April 2015 at 20:05, Khaled Hosny 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 int
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 not
going to go way magically, much to my surprise. Peter Breitenlo
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 math list
This is part of the TeX-XeT code actually and not related
On Fri, Apr 03, 2015 at 01:09:21PM +0100, Philip Taylor wrote:
>
>
> Khaled Hosny wrote:
>
> >I’ve no immediate plans for this myself, but patches are welcomed.
>
> Khaled, did you also see my own query, posted on 23rd ult. and replicated
> below ?
>
> ** Phil
On Fri, Apr 03, 2015 at 09:01:13AM +0800, Daniel Greenhoe wrote:
> The new datetime2 package has been released. It supports time stamps
> that include time zones and seconds:
> http://www.ctan.org/pkg/datetime2
>
> However, the package documentation states that this information is not
> availabl
On Sun, Mar 29, 2015 at 02:54:49PM +0100, Philip Taylor wrote:
> Could anyone explain why the continuum that exists from color=00 to
> color=FE, color=FFFEFF and color=FE breaks at color=FF ?
>
> To ensure 100% consistency between the proofing version of a book (which has
> margina
On Tue, Dec 16, 2014 at 09:32:14PM +0900, Simon Cozens wrote:
> On 16/12/2014 20:24, Marek Stepanek wrote:
> > I put together a test file, based on the first example. I replaced the
> > "Linux Libertine O", which is not installed on my computer, with Lucida
> > Grande. This font is displaying these
On Wed, Nov 12, 2014 at 06:21:40PM +0900, Simon Cozens wrote:
> On 12/11/2014 17:07, Khaled Hosny wrote:
> > I'll try to see what is going on here, might be a bug or just XeTeX
> > trying hard to find the font from the incorrect name it is given.
>
> Well, if it was th
On Wed, Nov 12, 2014 at 10:35 AM, Akira Kakuto wrote:
> However,
> \setromanfont{Gentium Book Basic:Ligatures=TeX}
> also works here and Ligature=TeX seems to be effective.
I don’t think it has any effect. The latest fontspec enables it by
default for main and sans fonts, though.
Regards,
Khaled
On Wed, Nov 12, 2014 at 6:58 AM, Simon Cozens wrote:
> OK, this is an odd one. Here's my test document:
>
> \documentclass{book}
> \usepackage{fontspec}
> \setromanfont{Gentium:Ligatures=TeX}
This not the correct syntax; Ligatures=TeX is a fontspec option and
should be passed to it: \setmainfont[
If you have FontForge, you can opeb the PDF file with it, it will present
you with a list of the fonts in the PDF, select the one you want and you
should be able to open it and check its properties. If the font had its
version correctly set, it should be there.
Regards,
Khaled
On Oct 12, 2014 11:
On Thu, Sep 04, 2014 at 01:58:14PM +0900, Akira Kakuto wrote:
> > I'd expect it to be looking at the fsType field in the OS/2 table:
>
> I have found by otfinfo that
> http://www.bpdb.gov.bd/bpdb/images/fonthelp/Nikosh.zip
> has
> fsType = 0x0100 (No subsetting).
I'm yet to check the code, but wh
On Fri, Aug 01, 2014 at 09:52:47AM +0900, Akira Kakuto wrote:
> Hi Khaled,
>
> >>I have found the location where the crash occurs:
> >>
> >>
> >>--- type0.c.origMon Jul 28 19:38:13 2014
> >>+++ type0.cFri Aug 01 09:06:25 2014
> >>@@ -132,7 +132,7 @@
> >> if (font->descriptor)
> >>
On Fri, Aug 01, 2014 at 08:06:36AM +0900, Akira Kakuto wrote:
> Hi Khaled, Jiang,
>
> A japenese user reported that the new dvipdfmx crashed
> in the following example:
>
> %
> % sample.tex
> % (dvipdfmx r34778 crashes)
> % (dvipdfmx r34711 works fine)
> %
> % platex sample
> % dvipdfmx sample
>
On Tue, Jul 29, 2014 at 11:24:52PM +, Karljurgen Feuerherm wrote:
> * Why does this work with luabidi but not bidi? (or even, what¹s a likely
> reason)
It is likely because with current XeTeX nodes are reversed
unconditionally, so some starting \special node is coming after its
ending one, whi
On Tue, Jul 29, 2014 at 03:35:57PM +0100, David Carlisle wrote:
> > \hbox \bgroup $\beginR
>
> but couldn't you just do
>
> \hbox \bgroup \beginR$
That wouldn't work, as math (inline and display) are ensured to always
be LTR. The original assumption was that you never need RTL math, but
this is
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,
> > \beg
On Mon, Jul 28, 2014 at 08:47:44PM +0200, Jiang Jiang wrote:
> On Mon, Jul 28, 2014 at 6:28 PM, Khaled Hosny wrote:
> > On Mon, Jul 28, 2014 at 05:45:38PM +0900, Akira Kakuto wrote:
> >> Hi Khaled,
> >>
> >> >This is a development tree after all, so bugs are
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,
> \beginL, \endR, and \endL are also allowed in math mode. But consider this
> minimal document
>
> \documentclass{article}
> \begin{d
On Mon, Jul 28, 2014 at 05:45:38PM +0900, Akira Kakuto wrote:
> Hi Khaled,
>
> >This is a development tree after all, so bugs are to be expected. Lets
> >debug those issues first then decide what we want to do.
>
> OK, agreed. Thank you very much.
The /rsrc warning seems harmless, but I'm still
On Mon, Jul 28, 2014 at 12:31:51PM +1000, Vafa Khalighi wrote:
> >
> >
> >
> > It should make it to TeX Live 2015 (unless there are any major issues
> > that we can not fix by then, but I hope there will not be any).
> >
>
>
> Thanks. The only problem that I noticed until now is that when you use
On Mon, Jul 28, 2014 at 10:52:09AM +0900, Akira Kakuto wrote:
> Hi Khaled,
>
> >Let hope we have enough time before the next release to make sure it is :)
>
> xdvipdfmx r34745 (after applying the patch by Jiang) sometimes
> crashes at
>
> --- cff.c.origMon Jul 28 08:50:32 2014
> +++ cff.c
On Sun, Jul 27, 2014 at 10:47:40PM +0200, Khaled Hosny wrote:
> I suggest that the new version of bidi check the XeTeX version and only
> load those patches if it is less that 0.3,
I meant less than 0.2 of course.
Regards,
On Sun, Jul 27, 2014 at 06:37:18PM +1000, Vafa Khalighi wrote:
> Thanks for the new version of xetex which fixes some very important bidi
> issues. I have tested the new version and it seems to be working fine. Will
> this make it into TeXLive 2015? or is it experimental?
It should make it to TeX
On Sat, Jul 26, 2014 at 06:57:24PM +0200, Jiang Jiang wrote:
> On Thu, Jul 24, 2014 at 8:28 PM, Khaled Hosny wrote:
> > On Thu, Jul 24, 2014 at 07:18:10PM +0200, Jiang Jiang wrote:
> >> On Thu, Jul 24, 2014 at 6:27 PM, Khaled Hosny
> >> wrote:
> >> > O
On Thu, Jul 24, 2014 at 08:12:56PM +0200, Ulrike Fischer wrote:
> Am Thu, 24 Jul 2014 18:27:39 +0200 schrieb Khaled Hosny:
>
>
> >> OK, sorry about that. So who is the maintainer of dvipdfm-x then?
>
> > I partly do, and it happens that I was in the middle of
On Thu, Jul 24, 2014 at 07:18:10PM +0200, Jiang Jiang wrote:
> On Thu, Jul 24, 2014 at 6:27 PM, Khaled Hosny wrote:
> > On Thu, Jul 24, 2014 at 09:01:32AM +0200, Jiang Jiang wrote:
> >> Hi,
> >>
> >> On Thu, Jul 24, 2014 at 8:07 AM, Peter Breitenlohner
&g
On Thu, Jul 24, 2014 at 09:01:32AM +0200, Jiang Jiang wrote:
> Hi,
>
> On Thu, Jul 24, 2014 at 8:07 AM, Peter Breitenlohner
> wrote:
> > On Wed, 23 Jul 2014, Jiang Jiang wrote:
> >
> >> Since Peter is not responding,
> >
> >
> > Hi Jiang Jiang,
> >
> > that was on purpose because I am not t
On Wed, Jun 18, 2014 at 10:53:40AM +1000, Ross Moore wrote:
> It seems that one cannot break up the processing any more,
> or at least not in the simple-minded way.
> Would one of the developers please explain how to do this
> kind of testing now.
So called “native” fonts (AKA non-TFM fonts) are
On Tue, May 27, 2014 at 01:46:00PM -0400, Bruno Le Floch wrote:
> Hello all,
>
> On 5/4/14, David Carlisle 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
> > typesettin
On Fri, Apr 25, 2014 at 07:18:34PM +0930, Will Robertson wrote:
>
> Khaled, would you be able update the copy in the xetex repo?
Just send me the updated version and I’ll commit it (a git format-patch
would be even better but not necessary).
Regards,
Khaled
---
On Thu, Apr 10, 2014 at 12:58:23PM +0100, Philip Taylor wrote:
>
> Why are these key XeTeX primitives (\XeTeXprotrudechars, \rpcode, etc)
> not documented in /The XƎTEX reference guide/ ? Will, Khaled,
> Jonathan : can you comment on this, and will these (and any other
> currently undocumented p
On Wed, Mar 12, 2014 at 07:46:58PM -0400, maxwell wrote:
> On 2014-03-12 14:47, Joshua and Amy wrote:
> >I'm typesetting with XeLaTeX, using fontspec, and calling a font
> >provided to me by the publisher of a manuscript I'm working on. (Same
> >as my previous post!)
> >
> >The language I work with
On Wed, Mar 12, 2014 at 11:21:10PM -0400, Mike Maxwell wrote:
> On 3/12/2014 10:19 PM, Andrew Cunningham wrote:
> >Although personaly I'd consider such a solution a poor hack compared to a
> >well
> >designed font that is fit for purpose.
>
> I won't disagree. We've been told by the publisher, w
On Wed, Mar 12, 2014 at 02:24:02PM -0400, Joshua and Amy wrote:
> ** ERROR ** Type2 Charstring Parser: Subroutine nested too deeply.
This suggests that either the font is broken or there is a bug in
xdvipdfmx. To rule out (or verify) the first, you will need to run the
font against some sort of va
On Mon, Mar 10, 2014 at 11:11:27PM -0400, Mike Maxwell wrote:
> On 3/10/2014 8:04 PM, Khaled Hosny wrote:
> >That being said, there are some bugs in the HarfBuzz version used in
> >TeX Live 2013 release, but this should be fixed when with 2014 upgrades
> >to the latest H
On Mon, Mar 10, 2014 at 11:02:02PM +0100, Zdenek Wagner wrote:
> Harfbuzz broke the indic rules
Just to be clear, Pango/ICU had broken and/or incomplete Indic support,
some fonts worked fine because they were specifically tested against
them and adapted to their limitations, but the fonts were bro
- Forwarded message from Frédéric WANG -
From: Frédéric WANG
To: "www-m...@w3.org" , LaTeXML project
Subject: Thank you
Dear all,
Two months ago, I started a fundraising campaign to help MathML developments
in Gecko/WebKit as well as producing some sample EPUB documents for science.
On Wed, Jan 29, 2014 at 11:19:31PM -0700, Bobby de Vos wrote:
> Greetings,
>
> I am having trouble building xetex from source. Today I downloaded the
> source tree from
>
> http://git.code.sf.net/p/xetex/code
>
> and in the source tree I ran the command
>
> ./build.sh
>
> System is Ubuntu Prec
On Mon, Jan 13, 2014 at 10:14:13AM +, Philip Taylor wrote:
> So how is it that \showhyphens does not show these hyphenation points,
That is a known issue with Knuth's \showhyphens in XeTeX's way of
forming "native" word nodes AFAIK, xltxtra package has a modified
\showhyphens from Jonathan tha
On Mon, Jan 13, 2014 at 10:26:13AM +0100, Georg Pfeiffer wrote:
> Am Mo 13 Jan 2014 10:18:40 schrieb Georg Pfeiffer:
> > $ etex -etex -ini de.tex test.tex
>
> OK, xetex, not etex, but same result.
> gp
>
> $ xetex -etex -ini de.tex test.tex
“de.tex” is the name of the document you saved, since
On Fri, Jan 10, 2014 at 05:43:10PM -0500, C. Scott Ananian wrote:
> Now both final lines display as "24) April .(2008". That is, the
> parentheses and period have been reordered, even when I explicitly
> request LTR mode. What's going on here? How do I turn this
> (mis)feature off?
That seems to
On Wed, Jan 01, 2014 at 10:07:54PM +1100, Ross Moore wrote:
> > ToUnicode supports one byte to many bytes, not many bytes
> > to many bytes.
>
> Exactly. This is why /ActualText is the structure to use.
My only issue with /ActualText is that using it to tag whole words
breaks fine text selection
On Mon, Dec 30, 2013 at 06:03:14PM +0100, Zdenek Wagner wrote:
> 2013/12/30 Joe Corneli :
> > Thanks Ross.
> >
> > I think in this case all I really need is to revise \href code to
> > insert /ActualText (because I'm using small caps for hyperlinks in
> > this doc). Pretty much everything else wo
On Sun, Dec 29, 2013 at 09:12:28PM +, Joe Corneli wrote:
> This answer talks about how to turn off litgatures:
> http://tex.stackexchange.com/a/5419/4357
>
> Is there a way to turn off *all* special characters (e.g. small caps)
> and just get ASCII characters in the copy-and-paste level of the
On Fri, Dec 27, 2013 at 11:41:19AM +0100, Zdenek Wagner wrote:
> The moral is that even XeTeX in TeX Live 2013 does not always obey the
> search order configured in fontconfig and it is unpredictable and
> unreproducible.
It is FontConfig that does not, we just ask it for a list of fonts and
take
On Thu, Dec 26, 2013 at 02:36:55PM +, Julian Bradfield wrote:
> My xelatex version is
> This is XeTeX, Version 3.1415926-2.3-0.9997.5 (TeX Live 2011) (format=xelatex
> 20
> 12.11.27)
There was a problem with old versions of XeTeX (probably < 0.9998) where
having two different versions of the
On Tue, Dec 10, 2013 at 04:11:43PM -0800, Gildas Hamel wrote:
> * Skriv a reas msk...@ansuz.sooke.bc.ca (msk...@ansuz.sooke.bc.ca):
> |>
> |> What version of XeTeX are you using? Are the fonts involved freely
> |> available?
> |>
> I'm using XeTeX, Version 3.1415926-2.5-0..3 (TeX
On Wed, Dec 11, 2013 at 08:36:53AM +1100, Andrew Cunningham wrote:
> More to the point which libraries is XeTeX using for Bidi support me how
> up-to-date are they?
The issue is not the libraries (we use ICU which implemented the latest
BiDi algorithm changes in its last release), but the fact tha
On Wed, Dec 11, 2013 at 04:36:31AM +0200, Khaled Hosny wrote:
> On Tue, Dec 10, 2013 at 11:11:27AM -0500, C. Scott Ananian wrote:
> > On Tue, Dec 10, 2013 at 6:09 AM, Zdenek Wagner
> > wrote:
> > > 2013/12/10 Keith J. Schultz :
> > >> I will repeat I do not k
On Tue, Dec 10, 2013 at 11:11:27AM -0500, C. Scott Ananian wrote:
> On Tue, Dec 10, 2013 at 6:09 AM, Zdenek Wagner
> wrote:
> > 2013/12/10 Keith J. Schultz :
> >> I will repeat I do not know Vietnamese so I can not give you
> [...]
> >> Now, if "sang" is true Vietnamese and not a latinized form s
On Mon, Dec 09, 2013 at 01:40:21PM -0600, msk...@ansuz.sooke.bc.ca wrote:
> On Mon, 9 Dec 2013, C. Scott Ananian wrote:
> > feeding the output to xelatex. That work won't help others who find
> > themselves in a similar situation (or document authors who would
> > prefer not to have to explicitly
On Mon, Dec 09, 2013 at 09:32:05AM -0600, msk...@ansuz.sooke.bc.ca wrote:
> On Mon, 9 Dec 2013, Khaled Hosny wrote:
> > >U+E0001 U+E0065 U+E006E U+0073 U+0061 U+006E U+0067
> >
> > And it is a kind of tagging, so beyond the scope of identifying the
> > language of
On Mon, Dec 09, 2013 at 08:16:03AM -0600, msk...@ansuz.sooke.bc.ca wrote:
> On Mon, 9 Dec 2013, Philip Taylor wrote:
> > Keith -- could you possible supply an example of
> > "a properly encoded utf-8 string" from which it
> > can be unambiguously determined whether the string
> > "sang" is an Engli
o, they are for identify texts of unknown
> origine and possibly of unknown encoding or an encoding that already has not
> identified
> the language.
If the language of the text is already known (i.e. properly tagged
text), we don’t need to identify it.
> Am 09.12.2013 um 10:38 schrieb Kha
tatistical analysis[1]. You can identify scripts using
Unicode properties quite reliably, though.
1. https://en.wikipedia.org/wiki/Language_identification#Statistical_approaches
Regards,
Khaled
> regards
> Keith.
>
> Am 05.12.2013 um 09:46 schrieb Khaled Hosny :
>
> >
On Sat, Dec 07, 2013 at 03:15:53PM +0100, Zdenek Wagner wrote:
> 2013/12/7 Khaled Hosny :
> > Not at all! I even designed a companion Latin font, so that readers of
> > Latin script can enjoy the same quality and polishes of FreeSerif that
> > Arabic script reade
On Sat, Dec 07, 2013 at 05:40:57PM +0400, Alexey Kryukov wrote:
> On Sat, 7 Dec 2013 15:20:04 +0200
> Khaled Hosny wrote:
>
> > I can not reproduce this here, please attach the PDF output and
> > specify the version of the font you are using.
>
> Thank you for your a
On Sat, Dec 07, 2013 at 11:01:02AM +0400, Alexey Kryukov wrote:
> Dear All,
>
> I am preparing a book with small fragments of Hebrew and Arabic embedded
> into a Russian text. In the process of this work I have upgraded from
> XeTeX, Version 3.1415926-2.2-0.9997.4 I used previously to XeTeX,
> Ve
,
Khaled
On Sat, Dec 07, 2013 at 01:28:31AM +0100, Dominik Wujastyk wrote:
> I'm sensing, I think, that you don't like that font, Khaled?
>
> Dominik :-)
>
>
> 2013/12/5 Khaled Hosny :
> >
>
>
> > >> > Please, please, please, never eve
On Fri, Dec 06, 2013 at 07:55:07PM +0900, Simon Cozens wrote:
> Hello XeTeXers,
>
> Sorry for a not-entirely-XeTeX-related request but I think there may be some
> merit in it for XeTeX in the future.
>
> I have recently been toying around implementing my own layout engine, and
> have started to c
On Thu, Dec 05, 2013 at 12:29:40PM +0100, Zdenek Wagner wrote:
> 2013/12/5 Khaled Hosny :
> > On Wed, Dec 04, 2013 at 12:31:58AM -0500, C. Scott Ananian wrote:
> >> On Tue, Dec 3, 2013 at 5:33 PM, Khaled Hosny wrote:
> >> > On Tue, Dec 03, 2013 at 01:42:21PM
On Thu, Dec 05, 2013 at 09:41:04AM +0100, Keith J. Schultz wrote:
> Hi Scott,
>
> We are talking Unicode here right! What is there to guess?
And how do you, using Unicode, tell in what language is this line
written?
Regards,
Khaled
--
Subscripti
On Wed, Dec 04, 2013 at 11:50:05PM +0100, Zdenek Wagner wrote:
> 2013/12/4 C. Scott Ananian :
> > 3) Arabic comma instead of English comma in citation [23]. (in both
> > web and XeLaTeX output)
> >
> The engine cannot recognize the context if the language is not tagged,
> the comma will always be d
On Wed, Dec 04, 2013 at 12:31:58AM -0500, C. Scott Ananian wrote:
> On Tue, Dec 3, 2013 at 5:33 PM, Khaled Hosny wrote:
> > On Tue, Dec 03, 2013 at 01:42:21PM -0500, C. Scott Ananian wrote:
> >> Does XeLaTeX implement the Unicode BiDi algorithm?
> >
> > Short answ
On Tue, Dec 03, 2013 at 05:27:21PM -0500, maxwell wrote:
> On 2013-12-03 16:43, Khaled Hosny wrote:
> >http://tug.org/pipermail/xetex/2013-March/024118.html
>
> Is there an explanation of xetex's version numbering somewhere? The copy
> I'm running gives the ff. ver
On Tue, Dec 03, 2013 at 01:42:21PM -0500, C. Scott Ananian wrote:
> Does XeLaTeX implement the Unicode BiDi algorithm?
Short answer: no.
Long answer: XeTeX, more or less, breaks words at spaces or other
non-character material (spaces in TeX are converted to the so called
glue, so are not handled
http://tug.org/pipermail/xetex/2013-March/024118.html
On Tue, Dec 03, 2013 at 08:23:02PM +0100, Youcef Mohammed wrote:
> i do...
>
>
> 2013/12/3, Khaled Hosny :
> > May be if you actually read what is posted on the list :)
> >
> > On Tue, Dec 03, 2013 at 07:29:13A
May be if you actually read what is posted on the list :)
On Tue, Dec 03, 2013 at 07:29:13AM +0100, Youcef Mohammed wrote:
> any news???
>
> 2012/6/29, Jonathan Kew :
> > On 28/6/12 20:52, Adam Twardoch (List) wrote:
> >> Youcef is right:
> >> AFIR, XeTeX supports three layout engines:
> >> * ICU
On Wed, Nov 27, 2013 at 09:10:02PM +0900, Simon Cozens wrote:
> This is possibly a daft question, but...
>
> In traditional TeX, character tokens are processed and put into boxes
> individually, with fairly primitive ligature tables. Obviously XeTeX doesn't
> do this, using Harfbuzz (or ICU or wha
On Mon, Nov 25, 2013 at 07:54:00AM +0200, Khaled Hosny wrote:
> On Mon, Nov 25, 2013 at 10:56:25AM +0530, S. venkataraman wrote:
> > This is XeTeX, Version 3.1415926-2.5-0..3 (TeX Live 2013)
> > (format=xelatex 2013.6.27)
>
> This is latest released version indeed,
On Mon, Nov 25, 2013 at 10:56:25AM +0530, S. venkataraman wrote:
> This is XeTeX, Version 3.1415926-2.5-0..3 (TeX Live 2013)
> (format=xelatex 2013.6.27)
This is latest released version indeed, please attach the PDF output you
get.
--
Subscript
On Sun, Nov 24, 2013 at 06:48:56PM +0100, NMPOST7 wrote:
> On 24/11/2013 18:23, Khaled Hosny wrote:
> > What version of XeTeX are you using? You don't seem to be using the
> > latest version.
>
> I am using the latest version from MacTeX (TexLive 2013) but I do not have
On Sun, Nov 24, 2013 at 06:18:56PM +0100, hanne...@staff.uni-marburg.de wrote:
> One year ago
What version of XeTeX was that?
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Sun, Nov 24, 2013 at 08:13:04PM +0530, S. venkataraman wrote:
> I was looking for some free, unicode compliant,
> devanagari font family that has regular, italic and bold variants. I found
> that aksharyogini, CDAC-GISTYogesh, FreeSans and FreeSerif
> fit the bill. But, there are different pro
On Sun, Nov 24, 2013 at 06:02:06PM +0100, Peter Dyballa wrote:
>
> Am 24.11.2013 um 17:27 schrieb Khaled Hosny:
>
> > Huh?
>
> There were a few times problems with Indian scripts reported on this
> list and I have not yet realised a new version
On Sun, Nov 24, 2013 at 05:23:41PM +0100, Peter Dyballa wrote:
> Note that XeTeX is not perfect yet in shaping Indian scripts.
Huh?
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Sat, Oct 12, 2013 at 07:32:54PM +0100, Philip Taylor wrote:
> To provide a starting point for a new project, I have just saved
>
> MS-1214-V15.tex
>
> from a sub-directory called
>
> Lambeth-Palace-Library
>
> in a parallel directory called
>
> Horsmonden-Armistice-Day
>
a specific
> rendering technology is chosen? (Specifically selecting the renderer worked
> great in solving my small-caps problem.)
>
> Richard
>
> On Mon, Oct 7, 2013 at 12:48 PM, Khaled Hosny wrote:
>
> > On Sat, Oct 05, 2013 at 04:25:52PM -0400, Lammert, Richard wrote:
On Sat, Oct 05, 2013 at 04:25:52PM -0400, Lammert, Richard wrote:
> (Sorry about that empty message with one attachment--clicked the wrong
> button.)
>
> The following example attempts to use language-specific glyphs from
> Scheherazade, but does not work with Scheherazade 2.0 or 2.01. The example
On Sun, Sep 22, 2013 at 07:46:17PM +0200, Mojca Miklavec wrote:
> One thing I don't know is whether ICU only breaks between words or
> also between syllables. (If it only breaks between words you would
> still need hyphenation patterns. If it breaks between syllables as
> well, you don't need anyth
Known xdvipdfmx issue http://sourceforge.net/p/xetex/bugs/25/
Regards,
Khaled
On Fri, Sep 20, 2013 at 06:23:58PM +0100, Philip Taylor wrote:
> In a forthcoming PDF catalogue of Greek MSS, a number of "thumbnail"
> images of folia, bindings, etc., will appear, many if not all of
> which will be ex
On Thu, Sep 12, 2013 at 09:17:57PM +0100, Philip Taylor wrote:
> Just to follow up on a thread started on the "TeX-Hyphen" list,
> where does one learn exactly what \XeTeXlinebreaklocale does ?
> TeXdoc XeTeX tells me :
>
> > \XeTeXlinebreaklocale ‹Locale ID›
> > Defines how to break lines for mul
On Thu, Sep 12, 2013 at 07:20:30PM -0400, Mike Maxwell wrote:
> In general, word breaking in scripts that don't indicate word
> boundaries is a partly unsolved research problem in computational
> linguistics--and from what I've heard, native speakers often
> disagree. (If you think that's odd, you
On Wed, Sep 11, 2013 at 05:47:34PM +0200, Javier Bezos wrote:
>
> >Last time I heard from him on this, it was something in the lines of “I
> >wish I didn’t implement \addfontfeatures”, say I maintain my position
> >that people should avoid it whenever possible, it is just a hack.
>
> And the alte
On Wed, Sep 11, 2013 at 05:01:58PM +0200, Ulrike Fischer wrote:
> Did you try to contact Will? The whole "add features to fonts" needs
> imho a bit polishing
Last time I heard from him on this, it was something in the lines of “I
wish I didn’t implement \addfontfeatures”, say I maintain my positio
It was a bug in XeTeX 0. and it have been fixed in master branch:
http://sourceforge.net/p/xetex/code/ci/b9f323a377b2d76e2b69d27c8a5cdbc8f485efdb/
Regards,
Khaled
On Sun, Jun 30, 2013 at 12:04:43PM +0200, Ulrike Fischer wrote:
> Miktex users which updated to the newest xetex engine (version
>
I have no immediate plans for this (or supporting any of of the other
emerging color font formats), but patches are welcomed. Anyway I don’t
think there much we need to do on the layout side, this should be
handled by the viewer (we will need to support subsetting those tables,
of course, for PDF
1 - 100 of 544 matches
Mail list logo
