Re: [XeTeX] XeTeX OpenType Features bug?

[Lorna Evans]

I downloaded Hoefler Text from here: 
https://fontsgeek.com/fonts/Hoefler-Text-Regular#google_vignette


My minimal example:


%!TEX TS-program = xelatex

\documentclass[12pt]{memoir}

\usepackage{fontspec}


\setmainfont[Renderer=OpenType]{Hoefler Text}


\begin{document}

Now is the time for all good men to come to the aid of their country. 
The quick brown fox jumped over the lazy black dog.



\fontspec{Hoefler Text}[

Renderer=OpenType,

RawFeature={+smcp}]

Now is the time for all good men to come to the aid of their country. 
The quick brown fox jumped over the lazy black dog.




\end{document}




This produced

I don't know if the screenshot will come through on this list. But it 
seems to work. I'm on Windows though.


Lorna


On 10/23/2023 8:40 PM, David Barts via XeTeX wrote:


Posted this on the /r/tex subreddit and it was recommended I post it here:

When I run XeLaTeX from TeX Live 2023 on my Mac, it does not allow me 
to access the small caps (smcp feature) in the Baskerville or Hoefler 
Text fonts. I know these fonts contain small caps, because I can 
access the smcp feature in them when using Libre Office. I know Libre 
Office isn’t simply faking it and using a smaller point size to get 
small caps because a) that’s not how the text appears (the small caps 
sure look like proper small caps to me), b) it doesn’t do this for all 
fonts.


It’s not all Open Type fonts that XeTeX has problems with, either. It 
can use the small caps in Shinntype’s Scotch Modern just fine.


I’ve done some web searches about this and so far came up dry. Was 
wondering if anyone else had noticed it or has a workaround.


--
David Barts /n5...@me.com
He who has nothing to die for has nothing to live for.
  -- Moroccan proverb

Re: [XeTeX] xelatex not connecting letters in awami nastaliq font

[Lorna Evans]

Awami Nastaliq is a Graphite font. In XeTeX you would need to say "Awami
Nastaliq/GR". I'm not sure if that syntax would work in XeLaTeX, but
somehow you have to indicate Graphite.

On Sat, Feb 20, 2021, 6:24 PM Kamal Abdali  wrote:

> XeLaTeX (in combination with Polyglossia) is not rendering the Awami
> Nastaliq font properly. The letters in this font are being displayed
> without being connected together. I haven't encountered this problem with
> any other nastaleeq font. Nor have I seen this problem when using Awami in
> word processors.
>
> %demo.tex
> \documentclass[letterpaper]{article}
> \usepackage{polyglossia}
> \setmainlanguage{urdu}
> \newfontfamily\urdufont[Script=Arabic]{Awami Nastaliq}
> \newfontfamily\altnast[Script=Arabic]{Jameel Noori Nastaleeq} % or any
> other nastaliq font
> \setlength\parindent{0pt}
> \begin{document}
> عوامی نستعلیق\\
> \altnast{جمیل نوری نستعلیق}
> \end{document}
>
> demo.pdf attached.
>
> Kamal Abdali
>

Re: [XeTeX] asterisk in font name - font error

[Lorna Evans]

It may be a font installation issue if you are on Windows. Windows made 
a change awhile back where the default place to install is to a user 
folder.


On my system it is: C:\Users\username\AppData\Local\Microsoft\Windows\Fonts

If the fonts are in there, delete them.

Then reinstall the fonts "for all users" and it will go into 
C:\Windows\Fonts. This has taken care of my issues with fonts in XeTeX.


Lorna

On 12/14/2020 9:42 AM, Ulrike Fischer wrote:

Am Sun, 13 Dec 2020 17:01:16 +0100 schrieb Carlos Franke:



This would be a neat workaround. However it doesn't compile on my
system either. Running "xelatex temp2.tex" (temp2.tex being Apostolos'
code, only with Minion Pro replaced with another font as I don't have
Minion Pro installed) I get a similar error as before:

[...]

(./temp2.aux) (/usr/share/texlive/texmf-
dist/tex/latex/base/ts1cmr.fd)kpathsea:make_tex: Invalid filename
`[Jost-500-Medium.otf]/OT', contains '['


! Package fontspec Error: The font "Jost-500-Medium" cannot be
found.


I am likely making some very basic mistake. I would be grateful for any
hint.

I wouldn't use xltxtra, and the Mapping is unneeded too, but beside
this it should work.

\documentclass{article}
\usepackage{fontspec}
\setsansfont{Jost-500-Medium.otf}[
  BoldFont = Jost-700-Bold.otf ,
  ItalicFont = Jost-500-MediumItalic.otf,
  BoldItalicFont = Jost-700-BoldItalic.otf]

\begin{document}
\LARGE
\sffamily this is an example \textit{italics}, \textbf{bold},
and \textbf{\textit{bold italics}}.

\end{document}

If you get an error with this the fonts are perhaps not correctly
installed. Where did you put them? Did you really installed the otf?
(the repo seems to provide also ttf.)

Try also to compile with lualatex, it is normally less picky
regarding fonts (and one can inspect the names.lua).


Be that as it may, I am wondering: Should xelatex ideally work with the
font name "Jost*" like it does with "Minion Pro" and others?

Exotic names can always be problematic. And * has the meaning of a
wildcard in various places. I prefer to stick to file names.

Re: [XeTeX] Devanagari ASCII to Unicode mapping

[Lorna Evans]

I think this is a TECkit converter for the Preeti font:

https://github.com/silnrsi/wsresources/tree/master/scripts/Deva/legacy/sag-preeti/mappings

Lorna


 Original Message 
Subject: Re: [XeTeX] Devanagari ASCII to Unicode mapping
From: ShreeDevi Kumar 
To: XeTeX (Unicode-based TeX) discussion. 
Date: 2/17/2018 11:11 AM

Please see

view-source:http://hindi-fonts.com/tools/Preeti-to-Unicode-Converter

There is no direct mapping, butarray_one has the ASCII codes for 
Preeti, while array_two has the corresponding unicode.


ShreeDevi

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com

On Sat, Feb 17, 2018 at 10:32 PM, ShreeDevi Kumar 
> wrote:


> What I think I am looking for is something that would map a document
typeset using something like the Devanagari Preeti font
(https://fonts2u.com/preeti.font
), which seems to have the Devanagari
glyphs encoded in the range 0x00-0x7F, to something like the
Devanagari unicode font Mukta
(https://ektype.in/scripts/devanagari/mukta.html
) in the range
0x0900-0x097F.

Please try http://www.ashesh.com.np/preeti-unicode/


Also see

https://github.com/Shuvayatra/preeti


ShreeDevi

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com

On Sat, Feb 17, 2018 at 10:27 PM, Mike Maxwell
> wrote:

On 2/17/2018 11:08 AM, Daniel Greenhoe wrote:

Does anyone know where I can find an ASCII to Unicode
mapping for Devanagari?

For example, it seems that the Devanagari glyph "ब" is
encoded as
0x61 (hex) in ASCII (lower case 'a' for the Latin
alphabet), but is
0x092C in the Unicode standard:
http://www.unicode.org/charts/PDF/U0900.pdf


So what I am asking for is a map (or table) that maps
0x00-0x7F in
Devanagari ASCII to 0x0900-0x097F in Unicode.


In addition to the ASCII-to-Devanagari transcription system
that Philip Taylor mentioned, you may be interested in the
ISCII encoding for Brahmi-derived writing systems, including
Devanagari:


https://en.wikipedia.org/wiki/Indian_Script_Code_for_Information_Interchange



This is _not_ an ASCII-to-Devanagari encoding, rather it
leaves the ASCII range intact, and encodes Devanagari (etc.)
in the range 128 (actually, 161)-255.  It was afaik never
widely used, but there were (and probably still are) fonts for
it.  I don't imagine those fonts would be terribly high
quality by today's standards, e.g. I'd be surprised if they
handled conjunct characters.

FWIW, there was a similar encoding called TSCII for Tamil.

iconv can be used to map TSCII to other encodings, but for
some reason it doesn't seem to have ISCII in its reportoire
(it does include VISCII, but that's a legacy Vietnamese encoding).
-- 
   Mike Maxwell

   "My definition of an interesting universe is
   one that has the capacity to study itself."
         --Stephen Eastmond



--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex







--
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] fontspec and Graphite features

[Lorna Evans]

I don't know how to access the Graphite user selectable features. What is
the syntax?

On Nov 4, 2017 12:00 PM, "Ulrike Fischer" <ne...@nililand.de> wrote:

> Am Thu, 2 Nov 2017 14:33:19 -0500 schrieb Lorna Evans:
>
> > I was trying to figure out how to use Graphite font features in XeLaTeX
> > with fontspec. I read the most recent fontspec manual on CTAN and it
> > says that AAT and Graphite features are not yet supported. Is there any
> > hope of this changing? It would be great to be able to use Graphite
> > features since not all fonts use OpenType.
>
> What do you mean by not supported? The newest fontspec documentation
> only says that the command `\IfFontFeatureActiveTF` is not supported
> for these fonts but beside this what doesn't work for you?
>
>
>
> --
> Ulrike Fischer
> http://www.troubleshooting-tex.de/
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] fontspec and Graphite features

[Lorna Evans]

I was trying to figure out how to use Graphite font features in XeLaTeX 
with fontspec. I read the most recent fontspec manual on CTAN and it 
says that AAT and Graphite features are not yet supported. Is there any 
hope of this changing? It would be great to be able to use Graphite 
features since not all fonts use OpenType.


I hope this is not too far off topic.

Lorna





--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] graphite-info.tex

[Lorna Evans]

 Original Message 
Subject: Re: [XeTeX] graphite-info.tex
From: Jonathan Kew <jfkth...@gmail.com>
To: XeTeX (Unicode-based TeX) discussion. <xetex@tug.org>
Date: 6/16/2016 4:12 PM

On 16/6/16 21:58, Lorna Evans wrote:

Thanks for your help.

I'm using XeTeX .6 from TeX Live 2016/W32TeX.

I'm using version 3.0 of the font.

This command fires the feature properly:

\test{Padauk/GR:1970040686=1}

And none of these work:

\test{Padauk:+ulon}

\test{Padauk/GR:+ulon}


Curious I would have thought this should work. I wonder if there's 
a endian-ness bug at some level.


Just out of curiosity, does

  \test{Padauk/GR:+nolu}

work, by any chance? (I.e. reversing the feature tag!)

No, it didn't! Too bad.
Lorna






\test{Padauk/GR:+ulon=1}

\test{Padauk/GR:+ulon=True}

\test{Padauk/GR:script=mymr:+ulon}

\test{Padauk/GR:script=mymr:+ulon=1}

\test{Padauk/GR:script=mymr:+ulon=True}


Anyway, I have a workaround.

Lorna





--
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] graphite-info.tex

[Lorna Evans]

Thanks for your help.

I'm using XeTeX .6 from TeX Live 2016/W32TeX.

I'm using version 3.0 of the font.

This command fires the feature properly:

\test{Padauk/GR:1970040686=1}

And none of these work:

\test{Padauk:+ulon}

\test{Padauk/GR:+ulon}

\test{Padauk/GR:+ulon=1}

\test{Padauk/GR:+ulon=True}

\test{Padauk/GR:script=mymr:+ulon}

\test{Padauk/GR:script=mymr:+ulon=1}

\test{Padauk/GR:script=mymr:+ulon=True}


Anyway, I have a workaround.

Lorna



 Original Message 
Subject: Re: [XeTeX] graphite-info.tex
From: Jonathan Kew <jfkth...@gmail.com>
To: XeTeX (Unicode-based TeX) discussion. <xetex@tug.org>
Date: 6/15/2016 6:32 PM

On 15/6/16 20:38, Lorna Evans wrote:

Is there a graphite-info.tex to find out what the feature names are in a
Graphite font?

I've haven't been able to find it and it would be useful. Or, is there
some other way to display all the Graphite features in a font.


If I remember aright, the graphite feature support in xetex shares the 
same commands as the AAT feature support, so you should be able to run 
the AAT-info.tex file and just change the font names appropriately. 
(You'll need to change the Mac-specific fonts it uses to annotate the 
output, as well as the name of the actual target font.)




My actual problem is that I have a font where the feature name is "Long
U with Yayit, long UU with Hato". I'm able to access all other features
in the font except this one. I wonder if XeTeX thinks it's too long or
if it doesn't like the comma in the feature name. Would it concatenate
the feature name in that case?



I'm pretty sure the comma is the problem; the "micro-syntax" xetex 
parses in the font name string will treat comma as separating two 
successive values for the same feature name. That is, it's intended to 
let you say things like:


  \font\x = "MyFont:Ligatures=Common,Rare,Historical"

as a shorthand for:

  \font\x = "MyFont:Ligatures=Common;Ligatures=Rare;Ligatures=Historical"

To work around this, I _think_ it also lets you specify features by ID 
(like for OpenType fonts), so you should be able to do


  \font\x = "Padauk:+ulon"

as suggested by Andrew in the reply I just saw arrive. :)

JK



--
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] graphite-info.tex

[Lorna Evans]

Thank you both. I learned something today!
On Jun 15, 2016 6:34 PM, "Jonathan Kew" <jfkth...@gmail.com> wrote:

> On 15/6/16 20:38, Lorna Evans wrote:
>
>> Is there a graphite-info.tex to find out what the feature names are in a
>> Graphite font?
>>
>> I've haven't been able to find it and it would be useful. Or, is there
>> some other way to display all the Graphite features in a font.
>>
>
> If I remember aright, the graphite feature support in xetex shares the
> same commands as the AAT feature support, so you should be able to run the
> AAT-info.tex file and just change the font names appropriately. (You'll
> need to change the Mac-specific fonts it uses to annotate the output, as
> well as the name of the actual target font.)
>
>
>> My actual problem is that I have a font where the feature name is "Long
>> U with Yayit, long UU with Hato". I'm able to access all other features
>> in the font except this one. I wonder if XeTeX thinks it's too long or
>> if it doesn't like the comma in the feature name. Would it concatenate
>> the feature name in that case?
>>
>>
> I'm pretty sure the comma is the problem; the "micro-syntax" xetex parses
> in the font name string will treat comma as separating two successive
> values for the same feature name. That is, it's intended to let you say
> things like:
>
>   \font\x = "MyFont:Ligatures=Common,Rare,Historical"
>
> as a shorthand for:
>
>   \font\x = "MyFont:Ligatures=Common;Ligatures=Rare;Ligatures=Historical"
>
> To work around this, I _think_ it also lets you specify features by ID
> (like for OpenType fonts), so you should be able to do
>
>   \font\x = "Padauk:+ulon"
>
> as suggested by Andrew in the reply I just saw arrive. :)
>
> JK
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] graphite-info.tex

[Lorna Evans]

Is there a graphite-info.tex to find out what the feature names are in a 
Graphite font?


I've haven't been able to find it and it would be useful. Or, is there 
some other way to display all the Graphite features in a font.


My actual problem is that I have a font where the feature name is "Long 
U with Yayit, long UU with Hato". I'm able to access all other features 
in the font except this one. I wonder if XeTeX thinks it's too long or 
if it doesn't like the comma in the feature name. Would it concatenate 
the feature name in that case?


Lorna



--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

[XeTeX] XeTeX with new Graphite engine?

[Lorna Evans]

I was thinking I had seen a message that Jonathan had updated XeTeX to 
use the newest Graphite engine and that someone else had built a Windows 
binary. I can't find that anywhere. Did I imagine this or can someone 
tell me where to find it?


Thanks,

Lorna




--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] font license

[Lorna Evans]

The font properties say Installable embedding allowed so I'm not sure 
why it won't embed.

The license field has a bunch of CJK that I can't read and then this:

Nikosh font developed by The Election Commission of Bangladesh. Latin 
glyphs Incorporated are from modified DejaVu font project's DejaVu Serif.

Bangla Glyps design by: Jowad Kazi
Core Developers: Jowad Kazi, Omi Azad, Mozammel Sarker

NikoshBangla font is being Released under Creative Common License (CCL).
http://creativecommons.org/licenses/by-nc-nd/3.0/NikoshRegularJowadKazi,OmiAzad: 
NikoshLight: 2008NikoshVersion 001.000NikoshJowad Kazi, Omi AzadJowad 
Hamid Kazi. Bangladesh Election Commission Secretariat.This Font 
Software is licensed under the Creative License, Version 3.0. This 
license is http://creativecommons.org/licenses/by-nc-nd/3.0/


---
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 
LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN 
ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 
INFORMATION ON AN AS-IS BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 
REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR 
DAMAGES RESULTING FROM ITS USE.

License
THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS 
CREATIVE COMMONS PUBLIC LICENSE (CCPL OR LICENSE). THE WORK IS 
PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE 
WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS 
PROHIBITED.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND 
AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS 
LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU 
THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH 
TERMS AND CONDITIONS.

1. Definitions
a.Adaptation means a work based upon the Work, or upon the Work 
and other pre-existing works, such as a translation, adaptation, 
derivative work, arrangement of music or other alterations of a 
literary or artistic work, or phonogram or performance and includes 
cinematographic adaptations or any other form in which the Work may be 
recast, transformed, or adapted including in any form recognizably 
derived from the original, except that a work that constitutes a 
Collection will not be considered an Adaptation for the purpose of 
this License. For the avoidance of doubt, where the Work is a musical 
work, performance or phonogram, the synchronization of the Work in 
timed-relation with a moving image (synching) will be considered an 
Adaptation for the purpose of this License.
b.Collection means a collection of literary or artistic works, 
such as encyclopedias and anthologies, or performances, phonograms or 
broadcasts, or other works or subject matter other than works listed 
in Section 1(f) below, which, by reason of the selection and 
arrangement of their contents, constitute intellectual creations, in 
which the Work is included in its entirety in unmodified form along 
with one or more other contributions, each constituting separate and 
independent works in themselves, which together are assembled into a 
collective whole. A work that constitutes a Collection will not be 
considered an Adaptation (as defined above) for the purposes of this 
License.
c.Distribute means to make available to the public the original 
and copies of the Work through sale or other transfer of ownership.

d.Licensor means the in



...it quits at this point. The Description is more complete and says:
This Font Software is licensed under the Creative License, Version 
3.0. This license is http://creativecommons.org/licenses/by-nc-nd/3.0/


---
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 
LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN 
ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 
INFORMATION ON AN AS-IS BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 
REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR 
DAMAGES RESULTING FROM ITS USE.

License
THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS 
CREATIVE COMMONS PUBLIC LICENSE (CCPL OR LICENSE). THE WORK IS 
PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE 
WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS 
PROHIBITED.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND 
AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS 
LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU 
THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH 
TERMS AND CONDITIONS.

1. Definitions
a.Adaptation means a work based upon the Work, or upon the Work 
and other pre-existing works, such as a translation, adaptation, 
derivative work, arrangement of music or other alterations of a 
literary or artistic work, or phonogram or performance 

Re: [XeTeX] font license

[Lorna Evans]

It came from the Nikosh.ttf file. I have Microsoft Font Properties
Extension installed and with that installed I can right click on a .ttf and
select Properties and it gives me a whole range of tabs full of info that
were not available without the extension. I don't know how you would find
this info on other Operating Systems.
Lorna



On Wed, Sep 3, 2014 at 2:57 PM, maxwell maxw...@umiacs.umd.edu wrote:

 On 2014-09-03 15:42, Lorna Evans wrote:

 The font properties say Installable embedding allowed so I'm not
 sure why it won't embed.
 The license field has a bunch of CJK that I can't read and then this:

  Nikosh font developed by The Election Commission of Bangladesh. Latin
 glyphs
 ...


 That's certainly the sort of thing I was looking for.  How did you extract
 that? (and from what file?)

Mike Maxwell



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] bold small caps, but no regular small caps

[Lorna Evans]

On 2013-08-02 06:40, Georg Duffner wrote:

I tried to reproduce the above behaviour by deleting and adding
different versions – without success.


In my case (I'm the OP), the problem indeed turned out to be with my 
font files--I had two versions of the CharisSIL font files, with 
slightly different names.  Apparently it (Cygwin, and therefore 
XeLaTeX) was picking up the older ones, which were known to have 
issues with small caps.  I imagine this problem could occur in other 
OSs, since the font file naming issue would affect those systems too.
Most OSes use installed fonts so they wouldn't have this problem. This 
is because XeTeX (and XeLaTeX) give the facility to point at a 
particular physical font that may not even be installed. In this case 
it apparently just chose the first one it found.


Lorna



--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] difficulty with ancient greek diacriticals in XeTeX with Gentium Plus

[Lorna Evans]

Thanks for figuring out this problem in Gentium Plus. If there are other 
Greek characters recomposing wrong I'd appreciate hearing about them so 
we can work on getting them right for the next release.

Lorna
SIL International

 Original Message 
Subject: Re: [XeTeX] difficulty with ancient greek diacriticals in XeTeX 
with Gentium Plus

From: Georg Duffner
To: XeTeX (Unicode-based TeX) discussion.
Date: 7/18/2013 4:53 PM

The problem seems to be incomplete recomposition in the font.
Canonically, your precomposed ἆ decomposes to alpha + uni0313 + 
uni0342 where uni0313 is combining comma above and uni0342 greek 
perispomeni. This is also, what should result from decomposed input. 
Gentium Plus however seems to expect uni1FBF greek psili instead of 
uni0313. The sequence uni1FBF+uni0342 is replaced with uni1FCF greek 
psili and perispomeni by opentype feature ccmp in that font, which 
gets positioned correctly and looks identical to the precomposed glyph.


uni1FBF and uni1FCF shouldn’t be used as combining characters but it 
happens nevertheless, it might be worth reporting a bug to SIL.




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex