On Mon, Apr 5, 2010 at 4:52 PM, Vafa Khalighi vafak...@gmail.com wrote:
This is a very useful primitive that I just found now.
http://tex.loria.fr/moteurs/etex_ref.html#predisplaydirection says:
an internal read/write integer, initialised by e-TeX to indicate the
direction of the last
On 16 Apr 2010, at 08:15, Brian Wilson wrote:
Lao, Thai and Khmer space at the phrasal level and not the word level. I was
not getting any word wrapping in Lao (haven't tried Thai or Khmer yet) until
a friend suggested that I add the following in the preamble
On 30 Apr 2010, at 11:09, José Carlos Santos wrote:
Please consider again this file:
\documentclass[10pt,a4paper]{book}
\usepackage[frenchb]{babel}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
\frontmatter
\tableofcontents
\XeTeXinputencoding
Hi Mojca,
I'm afraid I don't know anything about this; I believe Thanh has been building
(from the microtype branch in the xetex repository) on Linux, but I haven't
tried this myself yet.
I did, however, just succeed in building that branch on a Mac running Snow
Leopard, which I remember
For those who like to live on the cutting (bleeding?) edge, there is a new
version of xetex available in the source repository. Version 0.9996.0 is now
available from the svn repository at:
http://scripts.sil.org/svn-public/xetex/BRANCHES/microtype
This version supports character
On 3 May 2010, at 13:47, Stephen Moye wrote:
I got the microtype version of xetex, and the build process seemed to go well
until the very last few lines. Is this a fatal error?
Well, it prevented the compilation finishing, so you got no binary that
seems fairly fatal! :)
If so, how do
For those experimenting with this: I have just updated the microtype branch
again, to v0.9997.0.
The keywords used to specify \lpcode and \rpcode values for native-font glyphs
have been changed to be more concise, and also more similar to forms used in
other contexts. Unicode character codes
On 19 May 2010, at 19:47, Robert wrote:
On 18.05.10 10:55, Jonathan Kew wrote:
\font\f=MyFont at 10pt \f
\newcount\n
\loop \noindent \number\n : \XeTeXglyph\n\ = \XeTeXglyphname\f\n \par
\advance\n by 1 \ifnum\n\XeTeXcountglyphs\f \repeat
Thanks, this may be helpful (and I've
On 31 May 2010, at 22:13, Pablo Rodríguez wrote:
Hi there,
I have just accidentally discovered that LetterSpace behaves differently if
the whole paragraph is set with this feature or not.
The minimal example:
\documentclass[12pt]{article}
\usepackage{fontspec}
\setmainfont{Theano
On 26 Jun 2010, at 16:46, Khaled Hosny wrote:
On Sat, Jun 26, 2010 at 03:04:05PM -0700, wodzi...@math.berkeley.edu wrote:
My guess is that you have an old version of the font installed somewhere.
Having to different version of the same font installed is known to cause
this kind of issues
On 26 Jun 2010, at 21:26, Khaled Hosny wrote:
I was thinking that xetex should always pass the full path to xdvipdfmx,
instead of relaying on the later finding the fonts on it own. But now I
think this would break xdv2pdf which can not load fonts by file path,
right?
Not only for xdv2pdf;
On 4 Jul 2010, at 07:37, Mike Maxwell wrote:
Ulrike Fischer wrote:
Put \XeTeXtracingfonts=1 in your document and call in on the command
line like this
xelatex --output-driver=xdvipdfmx -vv file.tex
This should give you more informations about the fonts used by xetex
(in the log) and
On 8 Jul 2010, at 07:01, Khaled Hosny wrote:
That being said, the position of kasra relative to shadda is up to the
font designer. For example I prefer the more traditional behaviour in my
fonts, while fonts like Scheherazade make sure that both shaddakasra
and kasrashadda render kasra
On 9 Jul 2010, at 10:29, William Adams wrote:
Here:
http://www.fontmarketplace.com/font/ascender-2010-pack.aspx
Thought some people might want to grab this for testing purposes.
Announcement text:
The Ascender 2010 Font Pack features 14 fonts with enhanced OpenType
features to
On 12 Jul 2010, at 09:21, ulrik.vi...@arcor.de wrote:
I did check with ldd, but I don't have the exact ouput at hand.
AFAIK, the XeTeX-modified ICU library was statically linked.
Only stuff like fontconfig or zlib was dynamically linked.
I am running Ubuntu 10.4 on AMD 64, but I haven't
On 12 Jul 2010, at 09:26, Ron Aaron wrote:
On Monday 12 July 2010 11:16:48 Philip Taylor (Webmaster, Ret'd) wrote:
Fascinating : can you send me an example that does this
using only English text, and ideally does not use fonts
that don't come with TeX Live 2010 (since I can't process
your
I have just checked-in a patch to the xetex and texlive source trees to fix the
xetex segfault that was occurring with \XeTeXdelcode on some systems. This
brings the xetex version number to 0.9997.4.
Anyone who has been experiencing this problem is welcome to build and test the
new version to
On 30 Aug 2010, at 05:56, Wilfred van Rooijen wrote:
The (more dificult) solution could be to make a shell script which will run
the compilation of the xelatex source and detect whether or not the run was
succesfull - if not, change the input file to the other font and retry.
I'm surprised
On 1 Sep 2010, at 20:32, Khaled Hosny wrote:
On Wed, Sep 01, 2010 at 08:03:03PM +0200, Alexander Schultheiß wrote:
Hey David,
This is just not true. The example I sent you works correctly on my
machine; I deliberately included y-macron-acute which does not exist in
precomposed form in
On 11 Oct 2010, at 15:06, Gareth Hughes wrote:
Fr. Michael Gilmary wrote:
Oh, now I see what you're trying to do ... and what you've got here,
Gareth, works for me. You can also use:
\setmainfont[ItalicFont={BergamoStd-Italic},
BoldFont={BergamoStd-Bold},
On 13 Oct 2010, at 14:10, Vadim Radionov wrote:
I finally found the explanation. Mea culpa, it was in the kerning in
the font. All 3 lookup tables contained kerning -50 for small caps
Cyrillic `t' and `a', and the was another one of -60 in kerning
classes, which gave the total of -210.
I'm
On 16 Oct 2010, at 12:42, Mojca Miklavec wrote:
On Sat, Oct 16, 2010 at 11:47, Cyril Niklaus wrote:
Hello all,
I'd never had (or noticed) that problem before, so I don't know if it's a
new thing or something I do that does not comply. The problem is simple,
hyphenation occurs between an
On 21 Oct 2010, at 11:29, Philip Taylor (Webmaster, Ret'd) wrote:
As to why different planes for different languages (or dialects),
there are many reasons, of which (for me) the two most important
are : (1) all characters required for a single language would form
a contiguous cluster within
Well, you are far better informed in these matters
than am I, Jonathan (I am simply a well-meaning
amateur) but I do not regard the number of planes
required as a major stumbling factor : I am not
for one second suggesting that a font encoded
in my suggested encoding should have separate
On 29 Dec 2010, at 12:45, Ulrike Fischer wrote:
In my miktex 2.9. I have two version of asana-math:
J:/MiKTeX2.9/fonts/truetype/public/asana-math/Asana-Math.ttf.ignore
and
J:/MiKTeX2.9/fonts/opentype/public/asana-math/Asana-Math.otf
Now in the following example xetex uses the .ttf.ignore
On 4 Feb 2011, at 05:41, Adam Twardoch (List) wrote:
(Plain XeTeX, not XeLaTeX).
Imagine I use a font which uses contextual alternates such as:
\font\samplefont = Zapfino Extra LT Pro:+calt at 72bp
\samplefont
\def \sampletext{finality}
\XeTeXuseglyphmetrics=1
\setbox1
and two PDFs)
are available at
http://www.twardoch.com/tmp/SubtableKernTest.zip
I've also sent the test files offline to Jonathan Kew.
Many thanks to Alessandro Ceschini for raising the issue.
Regards,
Adam
--
Subscriptions, Archive
On 7 Feb 2011, at 11:17, Alessandro Ceschini wrote:
Now, gentlemen, since it's obvious a patch won't be released soon,
If someone submits a patch that corrects the underlying ICU issue, it could be
released soon, I expect. But it does depend on someone investing time and
effort in writing the
On 7 Feb 2011, at 11:42, Will Robertson wrote:
On 2011-02-04 23:57:38 +1030, Jonathan Kew jfkth...@googlemail.com said:
On 4 Feb 2011, at 05:41, Adam Twardoch (List) wrote:
I could use:
\XeTeXcharglyph`f
but this only gives me the glyph ID of the *default* glyph for the f
character. Yet
On 15 Feb 2011, at 03:49, David J. Perry wrote:
Will,
Thanks for the reply. Having spent the larger part of Sunday testing on some
additional machines, I can report the following. All tests were conducted
using the same exact font file (a PS-flavor OTF). MiKTeX is kept updated.
If
On 16 Feb 2011, at 07:42, John Was wrote:
Hello
I've used multiple \marks in a few jobs where there are several varying
elements that need to go into the running headlines (\marks 1, \marks 2,
etc., instead of plain TeX's single \mark). For some reason I got it into my
head that this
On 19 Feb 2011, at 17:29, Mike Maxwell wrote:
On 2/19/2011 12:13 PM, Ulrike Fischer wrote:
Am Sat, 19 Feb 2011 00:13:03 -0500 schrieb Mike Maxwell:
In a grammar we're writing, the gloss of a word xowunʣāy gets
just a comment, in the line above I meant roman transcription, not gloss.
On 20 Feb 2011, at 18:17, Khaled Hosny wrote:
OK, checking FF code, there is an isFixedPitch entry in 'post' and 'CFF'
tables that should be non-zero in monospaced fonts, so we just need
someone to come with a patch to make use of that :)
Yes, that would be a possibility - though it's worth
On 22 Feb 2011, at 22:55, Andy Lin wrote:
tex-text.map only provides for some punctuation marks. You can add
these lines to your tex-text.map file (or use it as a base and name it
something different, like tex-text-f.map). Semicolons are comment
characters. Below, only fi and fl ligatures
On 3 Mar 2011, at 20:32, Dominik Wujastyk wrote:
Very preliminary tests, using this:
@book{Vāgbhaṭa:1939,
author = {Vāgbhaṭa, and Gode, P. K. (Parshuram Krishna) and Kuṇṭe,
Aṇṇā Moreśvara. and Navare, Kr̥ṣṇaśāstrī. and Parāḍakara,
Hariśāstrī Sadāśiva.},
title=
On 6 Mar 2011, at 16:46, Gerrit wrote:
Hello,
I thought about this following (relatively simple) method for script
detection (and thus font selection) in Polyglossia. This would drastically
reduce the need to explicitely define the language for non-latin scripts.
Check the mailing list
On 27 Mar 2011, at 21:42, msk...@ansuz.sooke.bc.ca wrote:
On Sun, 27 Mar 2011, Paul Isambert wrote:
Both, actually. The font by itself does nothing, it simply indicates what the
rendering engine should do. I suppose (because it's seems the simplest way
here) that this is implemented as a
On 6 May 2011, at 18:03, Mojca Miklavec wrote:
On Thu, Nov 4, 2010 at 14:42, Adam McCollum wrote:
Dear list members,
I've recently drawn up a short document in Ge`ez (classical Ethiopic) using
Polyglossia and I see that the hyphenation is wrong. As some of you know,
languages that use the
On 11 May 2011, at 18:02, Arthur Reutenauer wrote:
And another nasty issue (that might deserve its own thread). We wanted
to have no hyphenchar at all, but using \hyphenchar\font=0 has a nasty
consequence that lines with broken words are not properly justified
(some extra space is squeezed
On 11 May 2011, at 23:46, Arthur Reutenauer wrote:
That doesn't surprise me; I'd expect you to get the font's .notdef glyph
(which might be a blank space, as in this example, or a box, or some other
symbol).
Thanks for the explanation, that makes sense.
What you want is a character
On 5 Jun 2011, at 21:09, Peter Dyballa wrote:
Am 05.06.2011 um 21:54 schrieb Philip TAYLOR (Webmaster, Ret'd):
So why doesn't it ?!
Phil,
it does! It passes all \special{}s without touching them into the output
file. Whether you're using the xetex or the xelatex command plays no
On 6 Jun 2011, at 13:30, Philip TAYLOR (Webmaster, Ret'd) wrote:
Jonathan Kew wrote:
Phil, the issue you're having is that the xetex option to specify
transparency as part of the font colour does not use \special{} commands,
it's an extra font property that is only supported
On 1 Jul 2011, at 17:20, Petr Tomasek wrote:
So, try:
\noindent \beginR \indent Lorem ipsum dolor sit amet, consectetur adipiscing
elit. Mauris luctus accumsan vulputate. Vivamus vel lacus nunc, a dictum
lacus. Duis rutrum, odio blandit dapibus facilisis, ipsum neque vestibulum
ligula,
On 8 Jul 2011, at 23:24, maxwell wrote:
I found \XeTeXinputnormalization in XeTeX documentation, but I'm not
familiar with the other two commands. I guess \tracingonline=1 means to
output errors to stdout (or stderr?), but where is the effect of
\tracinglostchars described?
See The TeXbook,
On 12 Jul 2011, at 15:38, BPJ wrote:
Does \XeTeXinputnormalization=1 normalize to NFC or NFD?
http://lmgtfy.com/?q=XeTeXinputnormalization
(e.g. see the XeTeX Reference Guide)
JK
--
Subscriptions, Archive, and List information, etc.:
On 25 Jul 2011, at 11:52, Florian Grammel wrote:
The combination of XeTex, marginnote and crop doesn't work properly:
\documentclass[a6paper]{scrbook}
\usepackage[frame,center,a4]{crop}
\usepackage{marginnote}
\begin{document}
Quisque \marginnote{mnote}facilisis erat a dui.
On 10 Aug 2011, at 09:03, Nicolás Hatcher wrote:
Hi All (again):
It seems I was guessing too much. Perhaps my problem is not fc-cache.
What happens is that with any new day the first xelatex run is extremely slow.
Could be 5 minutes before pass the line
This is XeTeX, Version ...
I am
On 31 Aug 2011, at 14:30, Peter Dyballa wrote:
In other words, xe(la)tex would be the way to go. For awhile.
And therefore keep old versions of Mac OS X! Leopard and Snow Leopard are OK
(it depends on the hardware it will run on: Mac OS X must be younger than the
hardware or it won't run
On 12 Sep 2011, at 08:59, Mojca Miklavec wrote:
On Mon, Sep 12, 2011 at 09:36, Yves Codet wrote:
Hello.
A question to specialists, Arthur and Mojca maybe :) Is it necessary to have
two sets of hyphenation rules, one in NFC and one in NFD? Or, if hyphenation
patterns are written in NFC,
Phil,
Put the font name in quotes. That will be taken as a hint that it should try
for an installed font by that name *before* asking kpathsearch to try and find
a TFM, rather than vice versa.
JK
On 23 Sep 2011, at 16:48, Philip TAYLOR (Webmaster, Ret'd) wrote:
Dear Colleagues -- I just
On 29 Sep 2011, at 21:01, Michael Joyner wrote:
On Thu, Sep 29, 2011 at 3:17 PM, Arno Trautmann arno.trautm...@gmx.de wrote:
Michael Joyner wrote:
HELP!
I am getting this on a super-large tex file:
** ERROR ** Page number 65536l too large!
I tried googling it, but did not find any
On 29 Sep 2011, at 18:59, Michael Joyner wrote:
HELP!
I am getting this on a super-large tex file:
** ERROR ** Page number 65536l too large!
I tried googling it, but did not find any references to this error. :(
This error is reported by xdvipdfmx (the PDF-generating output driver
Hello François,
Just a quick note (as I also have far too little time for TeX-related projects
these days) of appreciation for the tremendous contributions you have made to
the xe(la)tex world. Polyglossia, in particular, was a great response to a
widely-felt need, and I have no doubt that
On 28 Oct 2011, at 21:20, Philip TAYLOR (Webmaster, Ret'd) wrote:
Omega was remove because it was buggy, unmaintained, but most
important of all: hardly usable. It took a genius to figure out how to
use it, while XeTeX is exactly the contrary. It simplifies everything
in comparison to
On 28 Nov 2011, at 06:59, Heiko Oberdiek wrote:
On Mon, Nov 28, 2011 at 03:07:07PM +1030, Andrew Moschou wrote:
2011/11/28 Zdenek Wagner zdenek.wag...@gmail.com
Put it into an \hbox and measure its width (\wd). If the width is
zero, the glyph does not exist.
If the required glyph
On 27 Nov 2011, at 23:07, msk...@ansuz.sooke.bc.ca wrote:
On Sun, 27 Nov 2011, Aleksandr Andreev wrote:
It appears that XeTeX colors are handled by inserting pdfliteral nodes
around colored items, which breaks the access to GPOS.
Unless there's been some work on this issue since 2007, it
On 1 Dec 2011, at 16:26, Philip TAYLOR wrote:
And it cost me, and fellow members of this list, considerable work
to identify the problem. Multiply that by the number of fellow
sufferers that must have hit this error message and been completely
mystified, as I was, and the overheads of
On 15 Dec 2011, at 14:30, Philip TAYLOR wrote:
I know that a number of excellent typographers inhabit this
list, so I would like to pick their brains if I may ?
In Two wide ‘weaver’s windows’, usually found on the ground floor
(which could equally well be Two wide ‘weavers’ windows’,
On 15 Dec 2011, at 17:18, Tobias Schoel wrote:
Hi List,
On 15.12.2011 17:02, Jonathan Kew wrote:
On 15 Dec 2011, at 14:30, Philip TAYLOR wrote:
I know that a number of excellent typographers inhabit this
list, so I would like to pick their brains if I may ?
In Two wide ‘weaver’s
On 15 Dec 2011, at 19:54, Peter Baker wrote:
On 12/15/11 2:34 PM, Jonathan Kew wrote:
Not particularly relevant. The full stop or period that ends a sentence
is semantically different from the decimal point that punctuates numbers.
That doesn't mean we have separate character codes
On 2 Jan 2012, at 22:56, Zdenek Wagner wrote:
Hi all,
I apologize for an off topic postig but I hope I find here some people
who can help me. I am going to typeset a bilingual book of modern
poetry in Czech and Hindi. Can you suggest me a beautiful OpenType
Devanagari font?
You might like
On 3 Jan 2012, at 15:29, Philip TAYLOR wrote:
Dear XeTeX TeXworks users ...
When typesetting this year's Christmas newsletter, I ran into
real problems with the names of one of my friends, who in
Pinyin requires a third-tone u (ǔ); neither in TeXworks
nor in the final typeset document
On 3 Jan 2012, at 16:25, Khaled Hosny wrote:
I don't get the 'locl' feature to work with Arabic script, the attached
sample should give diagonal dots not rounded ones (it does if processed
with luatex). 'locl' feature works just fine with Latin script in other
fonts.
Is this a XeTeX bug,
On 4 Jan 2012, at 07:20, Shiva Shankar wrote:
Hi,
I am using xelatex to produce the following pdf which I am attaching
with this mail. I am using siddhanta font typeset this verse.
I am also attaching tex file.
Problem is in the word sasankaa.h when we add the
long 'aa' the dot of the
On 15 Feb 2012, at 14:53, Khaled Hosny wrote:
On Wed, Feb 15, 2012 at 12:21:28AM +, Juan Acevedo wrote:
Hello,
The package arabtex has a handy switch to reduce the number of Arabic
ligatures used: you can alternate between the essential ligatures
(\ligsfalse) or having additionally
On 18 Feb 2012, at 15:37, msk...@ansuz.sooke.bc.ca wrote:
I'm sorry I don't have many details because it wasn't my own system on
which the problem appeared, but: I have a PDF file generated with XeTeX
(xdvipdfm), and a Japanese font embedded in the PDF. It looks fine on my
screen (under
On 18 Feb 2012, at 18:12, Juan Acevedo wrote:
Thanks for all the input, everybody.
Now turning back to arabxetex, I would like to use this specific beautiful
Arabic font, Amiri (v.0.101, downloadable here http://www.amirifont.org/,
with thanks to Khaled).
Trying to overrule with
This sounds like http://bugs.icu-project.org/trac/ticket/7753
JK
On 21 Feb 2012, at 11:02, Paul Isambert wrote:
Hello all,
I use XeTeX to do some testing on fonts. If I'm not mistaken, given a
lookup with subtables, the latter are tried one after the other until
one of them identifies a
Hi Khaled,
Very exciting to see that you're fixing/improving things in this area! I'll try
to have a look at your patches soon and let you know if I see any concerns, but
it sounds like what you're doing is great. We should aim to incorporate these
improvements for the TL'12 release, if
On 14 Mar 2012, at 20:17, Peter Dyballa wrote:
Am 14.3.2012 um 17:32 schrieb d fulano:
But this is exactly my question:: how do I determine what are the standard
ligatures in a font?
I presume you mean what ligatures will be used by default when typesetting
with this font -- i.e., they
On 15 Mar 2012, at 12:34, Philip TAYLOR wrote:
Zdenek Wagner wrote:
2012/3/14 Peter Dyballapeter_dyba...@web.de:
Check the code points in the font! The statement
\defaultfontfeatures{Mapping=tex-text}
informs the XeTeX engine to use the standard ligatures, as TeX would do by
On 26/6/12 15:09, Martin Schröder wrote:
2012/6/26 Khaled Hosnykhaledho...@eglug.org:
XeTeX is still using the old (and more fragile) Graphite engine,
LibreOffice switched to the new (and more robust) one AKA graphite2. So
the segmentation fault is likely from the Graphite engine, so you may
On 28/6/12 20:52, Adam Twardoch (List) wrote:
Youcef is right:
AFIR, XeTeX supports three layout engines:
* ICU Layout, cross platform, working with OT Layout tables in SFNT fonts
* Graphite, cross-platform, working with Graphite tables in SFNT fonts
* ATT, Mac OS X only, working with OT Layout
On 1/7/12 19:21, Shriramana Sharma wrote:
On Tue, Jun 26, 2012 at 8:30 PM, Jonathan Kew jfkth...@googlemail.com wrote:
OTOH, the people who wrote Graphite are still there, and if the graphite
engine is crashing, they may be able to help pinpoint the problem and
suggest a fix that could
On 17/7/12 12:58, Lorna Priest wrote:
Can someone give me the proper incantation to access Character variants
(cv01, cv44, etc)? (I'm not using fontspec, just XeTeX) .
Currently, I have:
\def\testSS#1{
\font\x=#1 at 14pt \x
This shows the font “#1”. \SStext\par}
\def\testCV#1{
\font\x=#1
On 31/7/12 10:39, Shriramana Sharma wrote:
On Tue, Jul 31, 2012 at 3:03 PM, Zdenek Wagner zdenek.wag...@gmail.com wrote:
So as you all can see it cuts both ways. I vote is to gradually switch to
Lua(La)TeX. I believe that it can become the
future.
It can if other scripts become supported.
On 31/7/12 13:26, msk...@ansuz.sooke.bc.ca wrote:
There's the rub. Non-Latin scripts are a big part of the constituency of
XeTeX. I routinely have to manually activate Korean-specific OpenType
features that are specified to be default but that XeTeX/fontspec doesn't
activate by default, just
On 31/7/12 14:36, msk...@ansuz.sooke.bc.ca wrote:
On Tue, 31 Jul 2012, Jonathan Kew wrote:
On 31/7/12 13:26, msk...@ansuz.sooke.bc.ca wrote:
There's the rub. Non-Latin scripts are a big part of the constituency of
XeTeX. I routinely have to manually activate Korean-specific OpenType
features
On 31/7/12 15:09, Khaled Hosny wrote:
What is the difference between XeTeXHanLayoutEngine and ICU's
HanOpenTypeLayoutEngine? In other words, would it be enough to just use
ICU's Hangul engine, or there are adjustments needed?
IIRC, XeTeXHanLayoutEngine adds support for user-specified
On 15/8/12 10:48, Philip TAYLOR wrote:
Zdenek Wagner wrote:
You can see demonstration on my page:
http://hroch486.icpf.cas.cz/freefont-devanagari/
What /should/ be seen here, Zdeněk ? As a non-Indologist, I may
be missing something obvious (indeed, I probably am !), but I cannot
see the
On 15/8/12 11:24, Zdenek Wagner wrote:
2012/8/15 Jonathan Kew jfkth...@googlemail.com:
On 15/8/12 10:48, Philip TAYLOR wrote:
Zdenek Wagner wrote:
You can see demonstration on my page:
http://hroch486.icpf.cas.cz/freefont-devanagari/
What /should/ be seen here, Zdeněk ? As a non
On 15/8/12 12:09, Jonathan Kew wrote:
I'm not sure why the language-specific behavior in FreeSerif isn't
working in Firefox; I thought that was supported, but it appears to be
broken. Will try to investigate...
Oh, of course... it only works if you tell Firefox to use the harfbuzz
back-end
On 15/8/12 12:38, Zdenek Wagner wrote:
2012/8/15 Jonathan Kew jfkth...@googlemail.com:
On 15/8/12 12:09, Jonathan Kew wrote:
I'm not sure why the language-specific behavior in FreeSerif isn't
working in Firefox; I thought that was supported, but it appears to be
broken. Will try
On 15/8/12 13:05, Philip TAYLOR wrote:
Jonathan Kew wrote:
If your distro doesn't offer Aurora, you could presumably download it
directly from http://www.mozilla.org/en-US/firefox/channel/#aurora if
you want to try it out.
As you appear to be one of the Mozilla cognoscenti, Jonathan, could
On 25/9/12 09:30, Philip TAYLOR wrote:
Does XeTeX not consistently support the use of the decimal comma ?
No. Within the extended \font microsyntax, comma separates multiple
settings for a feature (something that's only applicable to AAT
features, IIRC). It will not be interpreted as a
On 4/10/12 09:06, Philip TAYLOR wrote:
Could anyone please tell me the XeTeX primitives into which
the Microtype package hooks in order to enable font protrusion ?
The output of TeXdoc XeTeX makes no reference to any such
primitives. I would like to be able to make use of whatever
On 15/10/12 15:19, Peter Baker wrote:
Here's an example file:
%program=xelatex
%encoding=UTF-8 Unicode
\documentclass{book}
\usepackage[silent]{fontspec}
\usepackage{xltxtra}
\setromanfont{Junicode}
\begin{document}
\noindent You can search for these:
\noindent first flat office afflict\\
On 3/12/12 12:31, Dominik Wujastyk wrote:
No, /this/ is a minimal sample:
\documentclass{book}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\setmainfont[Script=Malayalam]{Rachana}
\usepackage[oldlipi]{omal}
\begin{document}
ഇതൊരു സാമ്പിള് ഫയല്. ഇതൊരു
On 5/12/12 11:56, Joseph Wright wrote:
Right, so some more thinking required here. The question is what is
sensible for new content: from what you say about TeX--XeT and bidi,
using pdfTeX/XeTeX is not currently to be recommended for RTL work
IMO, this is an overly general and somewhat
On 13/4/13 21:53, Zdenek Wagner wrote:
That's the very reason why I want to run all the tests myself and
report only what fails. I can immediatelly see what is wrong but I do
not know the Indic OpenType specification and cannot fix the problem.
I feel that cooperation is needed and I do wish to
On 20/7/13 18:01, Richard Cobbe wrote:
To summarize: it looks like there are some problems with Gentium Pro, and
I'll send a list of all of the issues I've noticed to Lorna Evans off-list.
I can either wait for a release of the font that fixes these problems, or I
can switch to using
On 27/11/13 12:46, Khaled Hosny wrote:
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
On 4/12/13 13:24, C. Scott Ananian wrote:
The goal is to match the Unicode bidi algorithm, because that is how the
web page displays and thus how the original author saw the text as they
wrote.
This would be a nice enhancement, but would require a significant amount
of work (or in other
CJK is quite common. Should I be writing gloss-ja etc files to set the
right directionality and font and get the appropriate CJK support
packages loaded?
--scott
On Dec 5, 2013 5:42 AM, Jonathan Kew jfkth...@googlemail.com
mailto:jfkth...@googlemail.com wrote:
On 4/12/13 13:24, C. Scott
On 1/1/14 11:49, Khaled Hosny wrote:
The situation in XeTeX is more complex because the typesetting (where
the original text string is known) is done in XeTeX, while the PDF
generation is done by the PDF driver and the communication channel
between both (XDV files) passes only glyph ids not the
On 13/1/14 10:32, Philip Taylor wrote:
Khaled Hosny wrote:
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 that should work with XeTeX.
Hmm, thank you Khaled. I took one look and
On 27/1/14 09:47, Ulrike Fischer wrote:
Am Mon, 13 Jan 2014 08:24:30 + schrieb Jonathan Kew:
So is it relly true, that XeTeX is not able to apply the TeX hyphenation
mechnanism correctly to some unicode characters like „ß“?
I can't believe it.
That seems unlikely. It's almost certainly
On 15/4/14 11:05, Philip Taylor wrote:
... and are
you also aware of any documentation discussing how hyperlinks
can be embedded using XeTeX, another apparently undocumented feature
that is successfully exploited by hyperref, eplain, etc., yet
for which no primitive-level documentation seems to
On 26/8/14 16:37, François Patte wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
How can I get this ligature: दोऽंश
It seems that the anusvara cannot be put over the avagraha...
It probably depends on the font you're using. Experiment with some
alternatives... and if that
On 27/8/14 22:51, Ross Moore wrote:
Hi Mike,
On 28/08/2014, at 7:27 AM, maxwell wrote:
One of our people is getting a crash in xetex, which I can't reproduce. It's
very odd, since afaik we're both using the same input files, the same instance
of xetex, the same TeXLive 2014 files, and so
1 - 100 of 194 matches
Mail list logo
