Skip to content

Font axes not available for variable component location #2155

Closed

Description

@NightFurySL2001

In CJK usage, due to high stroke density, there is a need to adjust the weight of individual components at bolder weights. An example is the component 凵:
Image

The bold weight works ok in simple characters like 山:
Image

However in cramped space like 鋼, the component original bold weight is not suitable at all:
Image

The (global font) weight axis doesnt show in the right side component location. Other editors allow font axes as well as glyph axes when using smart components.

Note that although transformation scaling might work in this situation, it won't work with other type of components such as 人 with curved strokes.

Activity

  1. justvanrossum commented on May 8, 2025

    @justvanrossum
    Member

    It's a good use case.

    The internal infrastructure already support this, but it needs to be exposed in the UI.

    One idea: next to the "reload location" icon button, there could be a hamburger menu with a menu item that toggles the visibility of the global axes. Or: a menu item per global axis.

    (TBH, I'm afraid I cannot dedicate time to this in the near future)

  2. justvanrossum commented on Jul 23, 2025

    @justvanrossum
    Member

    So, I don't want the global axes to always be visible, but rather opt-in. Either (as suggested above) as a hamburger menu with a single item: "show global axes" / "hide global axes", or perhaps it could be a tiggle button (although I don't immediately see what that should look like).

    Then, it is important that we can distinguish (at least for global axes) between: "this axis is not set" and "this axis has a value". Since "at the default" is also a valid value, we can't use that. So global axes will need a checkbox (at their right) to indicate "this axis participates". In the data structure, a checked checkbox means "component.location contains an entry for the axis".

    This checkbox probably requires some work on ui-form.js.

  3. changed the title [-]Font axes not available when as component[/-] [+]Font axes not available for variable component location[/+] on Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions