Counterpunch Font Editor6d ago

Welcome to #FeatureFocusFriday #1, a new series of posts focussing on font editor innovations.

This first clip focusses on in-place component editing and 100% OpenType-compliant bi-directional font rendering; the assurance that your font will always behave the way it looks in the editor, because **it is a real font that you’re seeing**.

This eliminates the tedious edit-compile-test cycle of existing workflows.

Although today not unique to Counterpunch anymore, as with Fontra a second open-source editor also announced the feature in the same week, remarkably, albeit with some differences in user experience and technical implementation.

Show threadBobby de Vos
@counterpunch Even with shaping a real font in the editor (which sounds very nice, I need to try this) there are still differences between different OpenType shaping engines. Granted, some of those differences are small, some can be overcome with restructuring lookups. Other differences that affect real world applications are script itemizers.
Mar 20 at 11:59amWeb
Show threadCounterpunch Font Editor6d ago
@devosb Sure, that’s correct. Counterpunch builds on Harfbuzz here, which is used by most browsers and Adobe apps, and so we view it as the reference implementation. Mileage in other apps may indeed vary. Need to clarify wording here in the future.