Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

fallback font support seems to be broken, breaking some languages and sites.

  • 2 ŋuɖoɖowo
  • 2 masɔmasɔ sia le wosi
  • 4 views
  • Nuɖoɖo mlɔetɔ rhlp

hello. my name is Andrew. im learning the language toki pona. great language! however, it does not currently have support in Unicode.

as a workaround to use this language online, people have been downloading a font called nasin nanpa, and adding it to firefox's font fallback system in the about:config settings, and using the fonts UCSUR characters, like these 󱥬, 󱥂​󱤴​󱤧​󱤑​󱦐󱤄󱤽󱤧󱤊󱥵󱦑.

[specifically, the font uses codepoints in the Private Use Area because the language's script is not yet in Unicode. ]

the changes are to these settings.

font.name-list.cursive.x-western font.name-list.monospace.x-western font.name-list.sans-serif.x-western font.name-list.serif.x-western

recently, this system has stopped working. this change breaks multiple websites, including many discord community's that used the font to talk online in toki pona!

it also presumably breaks other fallback scenarios. now im guessing that this has not been noticed as most fonts support every commonly used character, making this feature rather obscure. however i really would love this to be fixed, and so would the large toki pona community!

to see what i mean better, please see the below images. the last image shows a website that loads this font on it's own, showing what the others should look like.

hello. my name is Andrew. im learning the language toki pona. great language! however, it does not currently have support in Unicode. as a workaround to use this language online, people have been downloading a font called nasin nanpa, and adding it to firefox's font fallback system in the about:config settings, and using the fonts UCSUR characters, like these 󱥬, 󱥂​󱤴​󱤧​󱤑​󱦐󱤄󱤽󱤧󱤊󱥵󱦑. [specifically, the font uses codepoints in the Private Use Area because the language's script is not yet in Unicode. ] the changes are to these settings. font.name-list.cursive.x-western font.name-list.monospace.x-western font.name-list.sans-serif.x-western font.name-list.serif.x-western recently, this system has stopped working. this change breaks multiple websites, including many discord community's that used the font to talk online in toki pona! it also presumably breaks other fallback scenarios. now im guessing that this has not been noticed as most fonts support every commonly used character, making this feature rather obscure. however i really would love this to be fixed, and so would the large toki pona community! to see what i mean better, please see the below images. the last image shows a website that loads this font on it's own, showing what the others should look like.
Screen ƒe photowo kpe ɖe eŋu

All Replies (2)

Hi Andrew,

Could you please report this on Bugzilla, Mozilla's bug tracker, so that the developers can take a look?

After reporting, you can also share a link to the bug here, so that we can follow along.

Denys said

Hi Andrew, Could you please report this on Bugzilla, Mozilla's bug tracker, so that the developers can take a look? After reporting, you can also share a link to the bug here, so that we can follow along.

gotchya. thank you. https://bugzilla.mozilla.org/show_bug.cgi?id=2014449

Bia biabia

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.