Re: [XeTeX] XeSyriac: Syriac typesetting for XeLaTeX: alaph-test version
* Gareth Hughes (garzoh...@gmail.com) wrote: |> Tentatively, I offer the alaph-test version of XeSyriac, a package for |> Syriac typesetting with XeLaTeX. I've set up a web page for the package |> from which all or parts of it may be downloaded: |> http://www.garzo.co.uk/xesyriac |> A great many thanks for your work. I just installed it and look forward to using it. -- Gildas Hamel -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] XeSyriac: Syriac typesetting for XeLaTeX: alaph-test version
Tentatively, I offer the alaph-test version of XeSyriac, a package for Syriac typesetting with XeLaTeX. I've set up a web page for the package from which all or parts of it may be downloaded: http://www.garzo.co.uk/xesyriac There is still quite a lot of work that I intend to do on the package, and that is clear from the documentation. However, I realised it would help me to bring the monster out into the open and seek advice on its development. I am not technically minded, and have developed this package as an a regular end user. With this in mind, I would like some feedback from 1. The handful of Syriacists who now use XeLaTeX, to ascertain if this is what we want/need, and if there are any end-user requests. 2. Those who know what packages should look like and how to code them, to correct my errors and over-exuberances. I am already grateful to those who have suggested snippets of code here and there that have gone into the package. I have tried to recognise each of you, and will continue to do so for all who offer further guidance. With the fear and trepidation of a new parent, Gareth. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Footnotes in longtable wihth column spec 'p'
On Feb 7 AD 2011, at 7:07 PM, Andy Black wrote:
Hello.
I'm using XeLaTeX with the longtable package, version 4.11. The
documentation says that longtable takes special precautions, so
that footnotes may also be used in 'p' columns. I'm having
problems, though, with this scenario. While the footnote number in
the table has the correct number, the footnote number in the
footnote text at the bottom of the page uses a zero.
A small sample that causes this is below.
What am I doing wrong?
I don't use longtable ... but all I did was remove the bracketed
numbers you have after the \footnote commands and the numbers came
out fine. See your modified example below.
\documentclass[12pt,twoside]{article}
\usepackage{xltxtra}
\usepackage{longtable}
\setmainfont{Times New Roman}
\font\MainFont="Times New Roman" at 12pt
\begin{document}
\begin{MainFont}
\vspace*{1in}
{\centering{\LARGE{\textbf{Footnotes in tables with longtable and
XeLaTex\\
\thispagestyle{plain}
\vspace*{1in}
\indent Here's a footnote in regular text.\footnote{{\leftskip0pt
\parindent1em
Text in first footnote.}}\par{}
\begin{longtable}[t]{@{}lp{.975in}@{}}
blah&blue\footnote{{\leftskip0pt\parindent1em
This is the second footnote, but its number is a zero! Its column
spec uses a 'p'.}}\\
green\footnote{\leftskip0pt\parindent1em Here is another footnote
in a table, but it's column spec does not use a 'p'.}&chartreuse\\
\end{longtable}
\end{MainFont}
\end{document}
HTH.
United in adoration of Jesus,
fr. michael gilmary, mma
Most Holy Trinity Monastery
67 Dugway Road
Petersham, MA 01366
www.MaroniteMonks.org
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
[XeTeX] Footnotes in longtable wihth column spec 'p'
Hello.
I'm using XeLaTeX with the longtable package, version 4.11. The
documentation says that longtable takes special precautions, so that
footnotes may also be used in 'p' columns. I'm having problems, though,
with this scenario. While the footnote number in the table has the
correct number, the footnote number in the footnote text at the bottom
of the page uses a zero.
A small sample that causes this is below.
What am I doing wrong?
The log file has this for the version of XeTeX:
This is XeTeX, Version 3.1415926-2.2-0.9997.4 (Web2C 2010)
(format=xelatex 2010.11.15)
I'm running on Windows XP, although it also happens on a Mac OS X Snow
Leopard.
Thanks,
--Andy
\documentclass[12pt,twoside]{article}
\usepackage{xltxtra}
\usepackage{longtable}
\setmainfont{Times New Roman}
\font\MainFont="Times New Roman" at 12pt
\begin{document}
\begin{MainFont}
\vspace*{1in}
{\centering{\LARGE{\textbf{Footnotes in tables with longtable and
XeLaTex\\
\thispagestyle{plain}
\vspace*{1in}
\indent Here's a footnote in regular
text.\footnote[1]{{\leftskip0pt\parindent1em
Text in first footnote.}}\par{}
\begin{longtable}[t]{@{}lp{.975in}@{}}
blah&blue\footnote[2]{{\leftskip0pt\parindent1em
This is the second footnote, but its number is a zero! Its column spec
uses a 'p'.}}\\
green\footnote[3]{\leftskip0pt\parindent1em Here is another footnote in
a table, but it's column spec does not use a 'p'.}&chartreuse\\
\end{longtable}
\end{MainFont}
\end{document}
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] \XeTeXglyphbounds question
Hi Jonathan, Thanks for your comments. On 2011-02-07 22:34:05 +1030, Jonathan Kew said: So while I think I agree that it would be good for \XeTeXcharglyph to respect the font's selected OT features, it's important to recognize the limitations inherent in *any* API that tries to get glyph information at the level of individual characters. I worry that people will start assuming that they can identify which characters are affected by a given feature on the basis of an API like this, which is a fundamentally flawed approach. Ah, I see. That makes a lot of sense. I agree with you that it's a flawed approach in general, but it's an okay approach for a certain class of features. I guess I'm mostly just thinking of the problems I've had in the past with +sups existing in a font but either through design or font bug, some "obvious" glyphs were not being superscripted. Being able to check simple substitutions would allow better fall-back behaviour in such cases... but as always "get a better font" is always good advice :) Off the top of my head I can't think of any other times that I've wanted to check such things. But I seem to remember I've thought about it on a couple of different occassions. (How about, say, faking a small caps $ if one doesn't exist in the font?) Cheers, Will -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
Am 07.02.2011 um 20:38 schrieb Khaled Hosny: I found it is more fun to keep living in my mom's basement and play with bytes and bits, Then you're presumingly much younger than I thought of... and it turned out that some crazy people want to pay me for that. Sounds you're luckier than me... -- Greetings Pete Almost anything is easier to get into than out of. – Allen's Law -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
Am 07.02.2011 um 19:48 schrieb Paul Isambert: Le 07/02/2011 19:10, Peter Dyballa a écrit : Am 07.02.2011 um 18:16 schrieb Khaled Hosny: I'm rather jobless Sounds Egyptian... Are you trying to make some geopolitical statement or just wielding disparaging remarks, Peter? How did you find reasons to assume the latter? For the case of the want-be Mubaraks, for example here in Europe, EU, it's true. And for the geopolitical statement: yes, I think Khaled is proud of his people. I could not think of another reason for his changed signature. At this moment! -- Greetings Pete The human brain operates at only 10% of its capacity. The rest is overhead for the operating system. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
On Mon, Feb 07, 2011 at 07:10:11PM +0100, Peter Dyballa wrote: > > Am 07.02.2011 um 18:16 schrieb Khaled Hosny: > > >I'm rather jobless > > Sounds Egyptian... I've been trained as a physician but I found it is more fun to keep living in my mom's basement and play with bytes and bits, and it turned out that some crazy people want to pay me for that. -- Khaled Hosny Egyptian -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] wrong page labels in slides with hyperref
On Mon, Feb 07, 2011 at 04:56:49PM +0100, Pablo Rodríguez wrote:
> I've just updated hyperref and it works fine. Thanks again.
>
> There is a small detail that doesn't work. Specifying
> "plainpage=true" in hyperref's options, gives the following warning:
>
> ./a.tex:7: Extra \else.
> \@hyper@@anchor ...g {Ignoring empty anchor}\else
Thanks, will be fixed in 6.82b.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
Le 07/02/2011 19:10, Peter Dyballa a écrit : Am 07.02.2011 um 18:16 schrieb Khaled Hosny: I'm rather jobless Sounds Egyptian... Are you trying to make some geopolitical statement or just wielding disparaging remarks, Peter? Paul -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] Kerning flaw with MinionPro & XeTex
To Adam & Khaled: thank you very much for your hint but I can handle it myself. I know enough of FontForge to be able to change class kerning into a flat one. To Peter: hey, however strongly you may feel about these issues, this is not the place for discussing politics! And moreover, you also sound quite offensive! Please watch your language! Greetings -- Alessandro Ceschini -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
Am 07.02.2011 um 18:16 schrieb Khaled Hosny: I'm rather jobless Sounds Egyptian... -- Greetings Pete Rain is saved up in cloud banks. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
On Mon, Feb 07, 2011 at 06:03:39PM +0100, Peter Dyballa wrote: > > Am 07.02.2011 um 17:50 schrieb Khaled Hosny: > > >Huh? > > > Formerly you outroduced yourself as "Arabic localiser", now you seem > to have a different job... I'm rather jobless, so I've plenty of time for playing with signatures. -- Khaled Hosny Egyptian -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] polyglossia + russian + texttt + Courier New error
Thanks a lot, Alexey!
Your reply was the most informative. I found that similar errors are issued
for many OTF fonts which contain Cyrillic glyphs. Hence, most radical
solution would be for the polyglossia to issue a warning rather that an
error as suggested in
http://www.tug.org/pipermail/xetex/2009-March/012365.html
I guess that I could correct the problem by editing the polyglossia myself
but I don't want to do that since the polyglossia is often modified by its
developers.
I experimented with \newfontfamily trying to define the \cyrillicfont
command as you proposed but did not succeed. Can anybody help me?
Regards,
Igor
From: Alexey Kryukov
To: Unicode-based TeX for Mac OS X and other platforms
Date: Sun, 6 Feb 2011 15:34:57 +0300
Subject: Re: [XeTeX] polyglossia + russian + texttt + Courier New error
On Sun, 6 Feb 2011 13:30:01 +0600
Igor Kotelnikov wrote:
> ! Package polyglossia Error:
> The current roman font does not contain the Cyrillic script!
> Please define \cyrillicfont with \newfontfamily.
This problem has been discussed once: see for example
http://www.tug.org/pipermail/xetex/2009-March/012365.html
If I understand correctly, the workaround is to explicitly
define \newfontfamily\cyrillicfont{Courier New} .
--
Regards,
Alexey Kryukov
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
Am 07.02.2011 um 17:50 schrieb Khaled Hosny: Huh? Formerly you outroduced yourself as "Arabic localiser", now you seem to have a different job... -- Greetings Pete The problem with the French is that they don't have a word for « entrepreneur ». – Georges W. Bush -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
On Mon, Feb 07, 2011 at 05:09:54PM +0100, Peter Dyballa wrote: > > Am 07.02.2011 um 16:17 schrieb Khaled Hosny: > > >-- Khaled Hosny > >Egyptian > > > Uhhh... What do you want us to – pity you, send you congratulations, > welcome you in the small so-called democratic world, which knows how > to handle the whip as well, with hundreds or thousands of want-be > Mubaraks? > > Are you still living under (now probably more theoretical) martial law? Huh? -- Khaled Hosny Egyptian -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
Am 07.02.2011 um 16:17 schrieb Khaled Hosny: -- Khaled Hosny Egyptian Uhhh... What do you want us to – pity you, send you congratulations, welcome you in the small so-called democratic world, which knows how to handle the whip as well, with hundreds or thousands of want-be Mubaraks? Are you still living under (now probably more theoretical) martial law? -- Greetings Pete One person with a belief is a social power equal to ninety-nine who have only interests. – John Stuart Mill -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] wrong page labels in slides with hyperref
On 02/06/2011 03:42 AM, Heiko Oberdiek wrote:
It was not supported by hyperref, because class `slides'
doesn't use \thepage but a complicate combination of counters
slide, note, overlay and page. In 2011/02/05 v6.82a I have now
implemented some support for class `slides' for options
`pdfpagelabels' and `pageanchor'.
Hi Heiko,
I've just updated hyperref and it works fine. Thanks again.
There is a small detail that doesn't work. Specifying "plainpage=true"
in hyperref's options, gives the following warning:
./a.tex:7: Extra \else.
\@hyper@@anchor ...g {Ignoring empty anchor}\else
\def \anchor@spot
{#2#3}\l...
l.7 \end{slide}
I don't know whether this is a bug or not.
Just in case it might help.
Thanks again,
Pablo
--
http://www.ousia.tk
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
On Mon, Feb 07, 2011 at 03:34:32PM +0100, Adam Twardoch (List) wrote: > On 11-02-07 12:31, Jonathan Kew wrote: > > A couple of possible workarounds: either modify the font file to avoid the > > issue (Adam's analysis makes it clear how this could be done) -- provided > > this is compatible with your license, of course -- or use a different > > typeface that doesn't exhibit the problem. > Adobe is one of the few major font vendors that do permit modification > of their fonts for personal use. > > The solution to the problem would be to open the font in a font editor > such as FontLab Studio or FontForge, then expanding class-based kerning > and removing kerning classes, and then generating a new font with > kerning written in this new way (i.e. as a flat list, not class-based). > > I might be able to write a Python script that does this (convert class > into flat kerning) in a non-invasive manner (I actually have started > this some time ago). I have a script for FontForge, though written for RTL kerning but it is trivial to adapt it to LTR kerning, If there is interest I can try isolating it (it is rather embedded in a larger script right now). Regards, Khaled -- Khaled Hosny Egyptian -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
On 11-02-07 12:31, Jonathan Kew wrote: > A couple of possible workarounds: either modify the font file to avoid the > issue (Adam's analysis makes it clear how this could be done) -- provided > this is compatible with your license, of course -- or use a different > typeface that doesn't exhibit the problem. Adobe is one of the few major font vendors that do permit modification of their fonts for personal use. The solution to the problem would be to open the font in a font editor such as FontLab Studio or FontForge, then expanding class-based kerning and removing kerning classes, and then generating a new font with kerning written in this new way (i.e. as a flat list, not class-based). I might be able to write a Python script that does this (convert class into flat kerning) in a non-invasive manner (I actually have started this some time ago). Best, Adam -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] \XeTeXglyphbounds question
On 7 Feb 2011, at 11:42, Will Robertson wrote: > On 2011-02-04 23:57:38 +1030, Jonathan Kew 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 since the font uses contextual alternates, I may end up >>> having any alternate "f" there, depending on the contents of \sampletext >>> So: how do I find out which glyph ID is the first (or 2nd, or last, for >>> that matter) in my box? >> Unfortunately, I don't think there's currently any way to do that. > > > This reminds me that it would also be very useful to be able to differentiate > glyphs when OT features are applied; e.g., if \XeTeXcharglyph expanded to > different values according to the currently enabled font features (and > contrarywise allow you to detect when a feature doesn't affect a certain > glyph). > > Is this a fundamental limitation with the means by which XeTeX handles > \XeTeXcharglyph? Well, not exactly, but it's true that \XeTeXcharglyph currently looks *only* at the character-to-glyph mapping of the font, it does not consider OpenType features. > In a way, it's surprising that > > \font\1="[texgyrepagella-regular.otf]" at 12pt > \font\2="[texgyrepagella-regular.otf]:+smcp" at 12pt > > \1 a: \the\XeTeXcharglyph`\a / > \2 a: \the\XeTeXcharglyph`\a > > would result in the same glyph slot. Yes, I know; this has come up previously, IIRC. One issue to keep in mind is that \XeTeXcharglyph would still not necessarily tell you which glyph will end up being used for any particular instance of "a" in your text, as they may be modified by *contextual* substitutions. And for the same reason, it would not be a reliable way to determine whether "a feature does[n't] affect a certain glyph", because the feature might affect the glyph in question only in certain contexts, not in isolation. So while I think I agree that it would be good for \XeTeXcharglyph to respect the font's selected OT features, it's important to recognize the limitations inherent in *any* API that tries to get glyph information at the level of individual characters. I worry that people will start assuming that they can identify which characters are affected by a given feature on the basis of an API like this, which is a fundamentally flawed approach. JK -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] \XeTeXglyphbounds question
On 2011-02-04 23:57:38 +1030, Jonathan Kew 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 since the font uses contextual alternates, I may end up having any alternate "f" there, depending on the contents of \sampletext So: how do I find out which glyph ID is the first (or 2nd, or last, for that matter) in my box? Unfortunately, I don't think there's currently any way to do that. This reminds me that it would also be very useful to be able to differentiate glyphs when OT features are applied; e.g., if \XeTeXcharglyph expanded to different values according to the currently enabled font features (and contrarywise allow you to detect when a feature doesn't affect a certain glyph). Is this a fundamental limitation with the means by which XeTeX handles \XeTeXcharglyph? In a way, it's surprising that \font\1="[texgyrepagella-regular.otf]" at 12pt \font\2="[texgyrepagella-regular.otf]:+smcp" at 12pt \1 a: \the\XeTeXcharglyph`\a / \2 a: \the\XeTeXcharglyph`\a would result in the same glyph slot. Or have I fundamentally misunderstood the concept of "glyph slots"? (I *thought* they were a unique index to each glyph in a font, but now I'm considering they could still be affected by substitution features. And in fact that would make quite a bit of sense.) Best, Will -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
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 code. > I beg > you to provide me a workaround that doesn't force me to undergo the epic > effort of manually kerning the book. A couple of possible workarounds: either modify the font file to avoid the issue (Adam's analysis makes it clear how this could be done) -- provided this is compatible with your license, of course -- or use a different typeface that doesn't exhibit the problem. JK -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] Kerning flaw with MinionPro & XeTex
To Adam: Yeah, that was exactly the point I made two days ago, when I told you XeTeX was apparently unable to read correctly the GPOS. Me too I've the 2.068 version dated 2004. Now, gentlemen, since it's obvious a patch won't be released soon, I beg you to provide me a workaround that doesn't force me to undergo the epic effort of manually kerning the book. Best wishes -- Alessandro Ceschini -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
On 11-02-07 09:53, Jonathan Kew wrote:
> Adam,
>
> Thanks for the detailed analysis and testcase.
>
> It looks like this is an instance of
> http://bugs.icu-project.org/trac/ticket/7753.
Yes, seems like it. I've posted my testcase files there as well.
Best,
Adam
> JK
>
> On 7 Feb 2011, at 01:31, Adam Twardoch (List) wrote:
>
>> I have identified this issue as a serious bug in XeTeX.
>>
>> In MinionPro-Regular.otf (version 2.068 is the one I have, but it's
>> likely that it applies to all versions), the relevant kerning definition
>> excerpt looks like the following:
>>
>> feature kern {
>> lookup kern1 {
>> pos uni0423 uni0431.ital -53;
>>subtable;
>> pos [uni040E uni0423 uni0474] [uni0435 uni043E uni0441
>> uni0444 uni0451 uni0454 uni0473 uni0431.ital] -118;
>> } kern1;
>> } kern;
>>
>> This means that there is an individual kern value between uni0423
>> uni0431.ital with the value of -53, then a subtable break, then a
>> class-based value for the same pair of -118.
>>
>> Adobe InDesign CS5 correctly identifies the pair in the first subtable
>> (-53) as the one that it should apply, and ignores the second value. So
>> the kern comes out as -53.
>>
>> It very much looks like XeTeX *incorrectly* parses *both* subtables, and
>> applies a sum of both the individual and the class value (-53-118 =
>> -171), which results in a very deep kern, and therefore an overlap.
>>
>> This seems to be a serious, systematic bug in the way XeTeX (or its
>> underlying ICU Layout library) processes the GPOS table.
>>
>> I've made an isolated test case that confirmes it.
>>
>> I've created a test OpenType font. It defines a kerning pair A B -300, a
>> subtable break, and again the same pair. InDesign correctly applies only
>> the first value (-300), which is shown in the
>> SubtableKernTest-InDesign.pdf file. XeTeX applies both values
>> consecutively, which is shown in SubtableKernTest-XeTeX.pdf
>>
>> All the test files (.ttf, .fea feature definitions, .tex 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, and List information, etc.:
>> http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Kerning flaw with MinionPro & XeTex
Adam,
Thanks for the detailed analysis and testcase.
It looks like this is an instance of
http://bugs.icu-project.org/trac/ticket/7753.
JK
On 7 Feb 2011, at 01:31, Adam Twardoch (List) wrote:
> I have identified this issue as a serious bug in XeTeX.
>
> In MinionPro-Regular.otf (version 2.068 is the one I have, but it's
> likely that it applies to all versions), the relevant kerning definition
> excerpt looks like the following:
>
> feature kern {
> lookup kern1 {
> pos uni0423 uni0431.ital -53;
>subtable;
> pos [uni040E uni0423 uni0474] [uni0435 uni043E uni0441
> uni0444 uni0451 uni0454 uni0473 uni0431.ital] -118;
> } kern1;
> } kern;
>
> This means that there is an individual kern value between uni0423
> uni0431.ital with the value of -53, then a subtable break, then a
> class-based value for the same pair of -118.
>
> Adobe InDesign CS5 correctly identifies the pair in the first subtable
> (-53) as the one that it should apply, and ignores the second value. So
> the kern comes out as -53.
>
> It very much looks like XeTeX *incorrectly* parses *both* subtables, and
> applies a sum of both the individual and the class value (-53-118 =
> -171), which results in a very deep kern, and therefore an overlap.
>
> This seems to be a serious, systematic bug in the way XeTeX (or its
> underlying ICU Layout library) processes the GPOS table.
>
> I've made an isolated test case that confirmes it.
>
> I've created a test OpenType font. It defines a kerning pair A B -300, a
> subtable break, and again the same pair. InDesign correctly applies only
> the first value (-300), which is shown in the
> SubtableKernTest-InDesign.pdf file. XeTeX applies both values
> consecutively, which is shown in SubtableKernTest-XeTeX.pdf
>
> All the test files (.ttf, .fea feature definitions, .tex 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, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
