"When enabled the font engine will train a weighting model to provide estimates for string sizes.

[foone@digipres.club]

"When enabled the font engine will train a weighting model to provide estimates for string sizes. Once the model is sufficiently trained it will perform string wrapping without calling ctx.measureText once. This leads to massive performance gains at the cost of accuracy."

excuse me, what?

[foone@digipres.club]

text sizes are too slow! lets instead train a model to estimate text size, inaccurately

[greg@icosahedron.website]

@foone feels like an oversight in font rendering toolkits that you can't just ask for an approximate width, as it would probably know best

[foone@digipres.club]

yeah it does a thing where it measures the width of characters up until you've rendered 20,000 (or 500,000?) characters and then if so, it relies on a small hashmap of character->info that it estimates from instead of using the real measureText

[foone@digipres.club]

that is slightly wacky and I'm not sure I want to use it

[halcy@icosahedron.website]

@greg @foone is there any way to like, general case do that with modern fonts with ligatures and what have you that is meaningfully faster than just rendering and checking how many pixels you end up with?

edit: I didn’t the word „approximate“ in there oops. But yeah