New Member

Typography Variables - Bind Variable to Case (All caps, title case etc)

19 replies
2315 views

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case.

We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps).

Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1).
We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route.

Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use case.

Show previous replies

Jim_Knox

Active Member

I wish the team would acknowledge this, im running into the same issue, we have 17 brands, some title case some full caps (for headings). Designers will have to look at best practices for each brand (And I will have to make that documentation). Even if implimented in a crappy way would help, also need line heights as % .

Courtney Deer

New Member

I started using a text string variable typed in the appropriate casing for each theme as a workaround.

Lea_Gucciardi

New Member

+1 here as this means we cannot use the Library for multiple brands

Joel_K

New Participant

+1

GwenFred

New Member

+1 it’s an easy enough concept to use a string variable to assign a type casing. We are running in the same issues with our multi-brand. 1 brand likes all caps for their metadata but another brand prefers title casing to give a more casual vibe for a lower-tier feel. I would hope since extended collections is rolled out and json can support type casing (via code) why not figma support it so we have a better ecosystem between code and what the designers are creating.

Jbarber

New Member

Everyone needs this feature. @figma is this difficult to implement? Curious why this hasn’t been dealt with yet

Tuguldur_Baatar

New Member

Desperately need this functionality. We are paying $30k for Org account, and yet our designers are having to spend additional time/money manually adjusting text case for a multi-brand application.