Skip to main content

Font family fallback stack

Qinyi_Yao

Would Figma ever support something like that? Clearly the team is aware of this but nothing has been done about it.

It’s been incredibly frustrating to do multilingual typesetting in Figma. The limitations of the design tool keeps propagating bad typography decisions and generating bad specifications.

Simply falling back to Noto is not usable. Issues like Unihan forces different font fallback stacks for different languages. Plugins can only do so much before encountering severe performance issues and incompatibilities.

  • Support for a stack of font family names to combine fonts.
  • Variables support for changing font family stacks depending on modes (usually defined based languages and operating systems).
  • Support for OpenType generic feature isolation (ss01-99 & cv01-99) when mixing fonts.
This topic has been closed for replies.

2 replies

Justin_Penner

In my case, I have a special use case (typeface specimens on a type foundry website) where a stack of fallback fonts would be incredibly useful, because I need unsupported characters to fall back to a special font that uses .notdef for all Unicode codepoints.

But I concur, a fallback font stack similar to CSS is pretty much essential for multilingual typesetting, too.

Dave_Nelson
1 person likes this
  • Dave_Nelson
    Dave_Nelson
A
  • Anonymous
  • 0 replies
  • January 7, 2024

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings