You can use localectl to change the locale on Fedora. Here’s what you need to do:

• See if you have Japanese locale installed. Something like ja_JP.UTF-8 should be in the output of localectl list-locales.
• If it’s not, you should install it using the following command: sudo dnf install langpacks-ja (I’m not 100 % sure about this and I don’t have a Fedora system to test it on.)
• Set the locale: sudo localectl set-locale LANG=ja_JP.UTF-8
• Reboot your system. Everything should be in Japanese now.

This will (probably) change everything to Japanese – texts in menus, error messages in the terminal, and also the font rendering. This answer on Stack Overflow suggests to do something with your fonts.conf. This way your UI would be in English (or your preferred language) and kanji would render as the Japanese variants.

A. I don’t know much about CJK fonts. I’m just spitballing. I am also half asleep.

B. It depends where the font is displayed. As you probably know, different Japanese, Korean and Chinese characters, which share history and look similar, share one unicode codepoint, see this Wikipedia article. Which specific glyph is shown is decided by some variable that specifies in what language the text is written:

• If the text is somewhere in the GUI (the title bar, the panel, some menu), it is probably decided by your default language and locale. This can be changed somewhere in settings. Changing this would also probably change everything to Japanese.
• If the text is somewhere on the web, this is decided by the lang parameter of the website. You can’t change this easily.

It’s not Czech. I’d say it’s Croatian.

Yes, it shouldn’t. Unfortunately, the developers of GTK thrived on changes to the API during the GTK3 era. I don’t know why Go devs don’t (and I am indeed very glad that they don’t). Perhaps it’s because of the different structures of the development teams or perhaps because GTK has more hazy goals. 🤷‍♂️

The GTK3 port has been in the making for a very long time. Long before anyone even mentioned GTK4. Porting an application to a different GUI toolkit is a lot of work.

How is Nushell? Is it stable?

That sounds terrible! I am already not very good at managing the charge of my phone.

Genuine question: How do you manage not to lose one of the earbuds?

I know USB-C is more robust than MicroUSB, but that doesn’t feel like it’s good for the connector. I’d much rather have a bit thicker (Apple said they’re getting rid off the jack to make their phones thinner.) or a bit less waterproof phone (not having a massive hole in the phone helps to waterproof it), than to loose the headphone jack.

Same. I can’t imagine having to remember to charge my headphones.

Yes, they do. Part of the OpenType standard are the so called “OpenType features” which (amongst other things) allow for contextual alternates, i.e. different kinds of ligatures, and for stylistic alternates, e.g. a slashed zero, a single-storey ɑ, etc. All of these different glyphs are encoded in the font and can be enabled when typesetting using different selectors. This website shows them off.

Some ligatures, like “ffl”, are a separate character in Unicode. Some were added because they can be considered a different character in languages other than English. Some (like “ffl”) were added because of legacy reasons; “no more will be encoded in any circumstances”.