e and haven't done
anything with it - indeed, I presume I'm not supposed to.)
Best
John
- Original Message -
From: "David J. Perry"
To: "Unicode-based TeX for Mac OS X and other platforms"
Sent: 23 February 2011 15:33
Subject: Re: [XeTeX] Accessing ligature
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
quot;Unicode-based TeX for Mac OS X and other platforms"
Sent: Wednesday, February 23, 2011 7:48 AM
Subject: Re: [XeTeX] Accessing ligatures from FontForge
Dear David
Many thanks. That looks exactly how I would expect it to be - though I am
obviously not quite umderstanding what fontforg
- 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 sam
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
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 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 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
nicode-based TeX for Mac OS X and other platforms"
Sent: 23 February 2011 12:19
Subject: Re: [XeTeX] Accessing ligatures from FontForge
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), bu
: "David Perry"
To: "Unicode-based TeX for Mac OS X and other platforms"
Sent: 23 February 2011 11:43
Subject: Re: [XeTeX] Accessing ligatures from FontForge
John,
I don't know if FontForge uses the same syntax as Adobe's FDK (also used
in FontLab), but I think
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
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
t
John
- Original Message -
From: "Andy Lin"
To: "Unicode-based TeX for Mac OS X and other platforms"
Sent: 23 February 2011 07:11
Subject: Re: [XeTeX] Accessing ligatures from FontForge
I agree, it's not a good solution. I've seen it break small c
I agree, it's not a good solution. I've seen it break small caps (so
\textsc{first} yields fiRST, where RST is small caps, but fi is the
lowercase ligature), and do other strange things. It is, however, a
relatively painless way to enable such ligatures in TrueType fonts or
OpenType fonts that don'
John,
Using the OT feature is definitely the way to go. Standard
ligatures () are on by default in XeTeX and if you set up the
feature right it should just work. Accessing ligatures through the PUA
codepoints is NOT a good idea (the fact that they even have PUA values
is a holdover from th
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
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 are active.
You'll need to run the file through te
17 matches
Mail list logo
