-> ligature doesn't seem to work on VS2013 / Windows 7

[ryani]

Repro steps:

Download font from https://github.com/tonsky/FiraCode/releases/download/0.5/FiraCode-Regular.otf
Open Control Panel > Fonts
Drag font from download into font window
Open Visual Studio Express 2013
Tools > Options > Environment > Fonts and Colors
Select Fira Code 9 pt and click OK
The >>= ligature works as do all the other ones I tested, except the -> ligature doesn't work

Any idea what's going on here? Is VS overriding that ligature? Or is the font bugged?

[tonsky]

No idea. IDE might mess up with ligatures rendering, though. E.g. in
LightTable, if color scheme has different colors for # and () in #(),
then #( would not be rendered as a ligature. Essentially tokenization of
text might be an obstacle for some ligatures.

On Sun, Jul 12, 2015 at 1:33 PM Ryan Ingram notifications@github.com
wrote:

Repro steps:

Download font from
https://github.com/tonsky/FiraCode/releases/download/0.5/FiraCode-Regular.otf
Open Control Panel > Fonts
Drag font from download into font window
Open Visual Studio Express 2013
Tools > Options > Environment > Fonts and Colors
Select Fira Code 9 pt and click OK

= ligature works as do all the other ones I tested, except the ->
ligature doesn't work

Any idea what's going on here? Is VS overriding that ligature? Or is the
font bugged?

—
Reply to this email directly or view it on GitHub
#32.

[kxepal]

Confirm the same behaviour for Geany with 0.5 version: -> ligature works for Python syntax, but not for Erlang. Seems like editor tokenization issue indeed. But this is the only rendering issue so far.

[tonsky]

Closing as I can’t do anything about it. Thanks for reporting

[oriSomething]

might related to the way glyphs export fonts. it's known there are some export problems with OT features on windows' engines (GDI+ / DirectWrite).