Thanks to everyone for the advice.
I don't use XeLaTeX so don't employ commands such as \defaultfontfeatures -
this isn't how I access fonts in plain XeTeX.
It's obvious (I think!) that I need to learn how to set up a liga table in
FontForge, and indeed I thought I'd done just that, but it's
John,
I don't know if FontForge uses the same syntax as Adobe's FDK (also used
in FontLab), but I think it might. Here's how I do in FontLab.
(In FL if you don't specify a script and language it applies Latin
script and the default language, which might be different in FontForge.)
feature
On Wed, 23 Feb 2011 06:43:56 -0500
David Perry wrote:
> I don't know if FontForge uses the same syntax as Adobe's FDK (also
> used in FontLab), but I think it might.
FontForge has a graphical interface (similar to one of Volt) to set up
OpenType features, but it can import Adobe feature files as
Dear David
Many thanks. That looks exactly how I would expect it to be - though I am
obviously not quite umderstanding what fontforge want me to do to get liga
to work. I will keep at it and no doubt the penny will drop eventually.
Best wishes
John
- Original Message -
From: "Dav
Dear Alexy
Many thanks - it may be easiest for me to import the feature at this stage
(and then I can have a good look at what has been done so that I can figure
what I've been doing wrong).
Best wishes
John
- Original Message -
From: "Alexey Kryukov"
To: "Unicode-based TeX for
On Wed, 23 Feb 2011, Meho R. wrote:
> 4. The old problem about PDF search unfortunately still remains: only
> basic standard ligatures are recognized. I would be happy if someone
> knows a way to correct this during font creation or correcting existing
> ones.
I think the Adobe Glyph Naming Conven
On 23.02.2011 12:43, David Perry wrote:
> John,
>
> I don't know if FontForge uses the same syntax as Adobe's FDK (also
> used in FontLab), but I think it might. Here's how I do in
> FontLab. (In FL if you don't specify a script and language it applies
> Latin script and the default language, whi
On 23.02.2011 14:17, msk...@ansuz.sooke.bc.ca wrote:
> On Wed, 23 Feb 2011, Meho R. wrote:
>
>> 4. The old problem about PDF search unfortunately still remains: only
>> basic standard ligatures are recognized. I would be happy if someone
>> knows a way to correct this during font creation or cor
On 2/23/11 9:27 AM, Meho R. wrote:
That page provides an algorithm that is supposed to be used to convert
glyph names into sequences of Unicode character points. If your glyphs
are named according to it, and if the PDF software follows it too, then
PDF software is supposed to be able to figure
- Original Message -
From: "Meho R."
To: "Unicode-based TeX for Mac OS X and other platforms"
Sent: Wednesday, February 23, 2011 9:27 AM
Subject: Re: [XeTeX] Accessing ligatures from FontForge
Thanks for the link. However, even Adobe's OTF fonts have same problems
when used with XeL
John,
When you created the f_f_l and so forth in FontForge, did mark them as
ligatures and indicate the correct number of components? (Characters in OT
are classified as simple, ligatures, marks, components and something else I
forget at the moment; ligatures also receive a value of 2, 3, etc
On Wed, 23 Feb 2011 10:33:34 -0500
David J. Perry wrote:
> When you created the f_f_l and so forth in FontForge, did mark them
> as ligatures and indicate the correct number of components?
FontForge usually automatically recognizes glyph as a ligature when
outputting a font, if this glyph has a l
Dear David
Yes - I'd worked that bit out. (But curiously, in Monotype Baskerville Open
Type, which I was looking at for comparison, the ligatures work perfectly
but are not identified by FontForge as ligatures in the look-up table.
However, I have only viewed Baskerville in FontForge and have
13 matches
Mail list logo
