# Add font fallback capability and use system UI font fallback by default **URL:** \ **Category:** Feature Requests\ **Created:** [September 26, 2023, 9:18am UTC](https://forum.juce.com/t/add-font-fallback-capability-and-use-system-ui-font-fallback-by-default/58038 "2023-09-26T09:18:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![timothyschoen](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/timothyschoen/32/14089_2.png) [@timothyschoen](https://forum.juce.com/u/timothyschoen)\ **Post date:** [September 26, 2023, 11:14am UTC](https://forum.juce.com/t/add-font-fallback-capability-and-use-system-ui-font-fallback-by-default/58038/2 "2023-09-26T11:14:55Z")
I believe that fixing this is one of the big things planned for JUCE 8, though that still might be a while away. This thread is a collection of all the times it has been discussed previously, and it also offers a few solutions: > [@Non-Latin Text Rendering in Various Components](https://forum.juce.com/t/non-latin-text-rendering-in-various-components/57682/2): > > Just for the record, here’s a list of all the threads on this topic that I’ve found, in chronological order: 2011 2014 2015 2016 2020 2021 2022 If you draw fonts with AttributedString on macOS or Windows, it should allow font fallback. If you want a solution where it will also work on Linux, and it will also work with default JUCE components without modifications, you might want to check out the solution I propose here, in the last post: [Unicode text rendering & editing in 2022 - #25 by timothyschoen](https://forum.juce.com/t/unicode-text-rendering-editing-in-2022/50174/25). If you create a font that contains all unicode characters in it, you can reliably draw non-latin text anywhere you want, at the cost of more memory usage and slightly worse startup time. --- _[View the full topic](https://forum.juce.com/t/add-font-fallback-capability-and-use-system-ui-font-fallback-by-default/58038)._