HarfBuzz 13.0.0 released with new experimental features: `hb-vector` for vector output of glyph outlines to SVG and `hb-raster` for rasterizing glyphs to A8 / BGRA32 images, among other features.

[isurandil@mastodon.online]

@behdad "Claude & Codex"? It's not yet April 1, is it?

[barubary@infosec.exchange]

@behdad Thanks for the warning.

[iorsh@kishkush.net]

@mcc @dysfun @behdad
That's an interesting approach. I admit I'm a bit cynical here, as I myself just started to use it quite extensively after a long period of scepticism. But at least forking is somehow practical.

[a1ba@suya.place]

@behdad
maybe that's good that I don't need harfbuzz rendering with languages I know.

[jlink@det.social]

@mcc @iorsh @dysfun @behdad Maybe we should agree on a common naming scheme and strategy for forking non-ai branches of projects. This way it would be easy to check if there’s a related non-ai project. In addition there should be a „nonai“ TLD so that domain-based package names are obvious as well.

[valpackett@social.treehouse.systems]

@behdad maybe you should've renamed it to SlopBuzz first

[david_chisnall@infosec.exchange]

@dysfun @behdad

Does HarfBuzz parse things like the hinting tables in fonts? That’s traditionally been a source of a lot of security vulnerabilities and I wouldn’t be surprised if 90% of the things in the training set have vulnerabilities.

[ariadne@social.treehouse.systems]

@behdad are those contributions actually legal?

[ivy_pigeon95@mastodon.social]

@jlink @mcc @iorsh @dysfun @behdad AI bros would start falsely labelling their slop with it as soon as it caught on, because a lot of them are motivated by spite.

[soc@chaos.social]

@behdad 🤮

[mcc@mastodon.social]

@jlink @iorsh @dysfun One problem with this approach is it normalizes randomly generated code as the ordinary thing, and code written by humans as the exception. Wouldn't it make more sense to have big mandatory warning labels on anything created by the planet-boiling plagiarism machine?

I do agree there should be some kind of organized process for creating forks, though.

[ianbicking@hachyderm.io]

@behdad it’s disappointing people are meeting your honesty about useful contributions with all this negative energy, but I hope you can put it aside as the dysfunctions of social media and not take it on as a judgement of the good faith work you are doing

[p@raru.re]

Congratulations, your license is now invalid
@behdad

[jlink@det.social]

@mcc @iorsh @dysfun What can we control? I cannot force anyone to make warning labels, but I can choose the namespace I attach to something I fork.

[tjk@oldbytes.space]

@behdad That's incredibly disappointing to hear.

[alerque@mastodon.social]

@a1ba @behdad You need a shaper for any language, even ones you know. Odds are in my favor that you composed that toot in something that shapes English with Harbuzz.

[mcc@mastodon.social]

@jlink @iorsh @dysfun That's a good point, and don't let my comments dissuade you from doing a thing you think would be helpful.

I think the place to start is clear messages in contributor rules or DCOs banning agent contributions. I've got language for this in my own repos, but I don't think there's a standard/best practices text people could cut and paste. Of course, this isn't a quickly findable sign of quality, which is what you're seeking (contributor guidelines are in inconsistent places)

[a1ba@suya.place]

@alerque @behdad maybe, I wouldn't argue here.

But rendering English, Kazakh or Russian text is pretty much possible without HarfBuzz. And that's what, in fact, what I do in my own projects.

Sure, it doesn't do stuff like ligatures and maps UTF-8 text to Unicode code points in a very stupid way. But for my own cases for the languages I know, it's just enough.

[hexaheximal@mstdn.social]

@behdad I'm disappointed.

[khaled@typo.social]

@iorsh You approved FontForge PRs co-authored by Claude Code, are you going to fork FontForge as well?

@mcc @dysfun @behdad