jlkpc1 has joined #foot
jlkpc1 has quit [Quit: WeeChat 3.5]
cabal704 has quit [Quit: WeeChat 3.5]
zdykstra has joined #foot
zdykstra has quit [Changing host]
jlkpc1 has joined #foot
jlkpc1 has quit [Quit: WeeChat 3.5]
hspak6 has joined #foot
zdykstra has quit [Read error: Connection reset by peer]
jlkpc1 has joined #foot
brocellous has quit [Remote host closed the connection]
brocellous has joined #foot
radu242 has quit [Ping timeout: 240 seconds]
jlkpc1 has quit [Ping timeout: 244 seconds]
radu242 has joined #foot
radu242 has quit [Ping timeout: 240 seconds]
<
kraftwerk28>
So if I want to implement ligatures for foot, I should do it in fcft, right?
<
novakane>
IIRC, at least it was the case sometimes ago, the problem was to add text run support in foot for ligature
<
dnkl>
fcft already has font shaping support (i.e ligatures). The problem is how to make use of it in foot, in an efficient way
<
dnkl>
where "efficient" means a) no speed/throughout regressions, b) no, or little, run-time memory usage, and b) without code bloat
<
dnkl>
s/throughout/throughput
radu242 has joined #foot
radu242 has quit [Ping timeout: 240 seconds]
Gilgamew has joined #foot
radu242 has joined #foot
jlkpc1 has joined #foot
radu242 has quit [Ping timeout: 244 seconds]
jlkpc1 has quit [Quit: WeeChat 3.5]
<
sterni>
plus correctness is another concern
Gilgamew has quit [Ping timeout: 252 seconds]
radu242 has joined #foot
zdykstra has joined #foot
noteness_ has joined #foot
noteness has quit [Ping timeout: 268 seconds]
Gilgamew has joined #foot
cabal704 has joined #foot
Gilgamew has quit [Quit: Client closed]
Gilgamew has joined #foot
noteness_ has quit [Remote host closed the connection]
noteness has joined #foot
cabal704 has quit [Quit: WeeChat 3.5]
an3223_ has quit [Ping timeout: 268 seconds]
cabal704 has joined #foot
Gilgamew has quit [Quit: Client closed]
jlkpc1 has joined #foot