Recent font update (Apple Symbols) breaks Japanese rendering

sorah
  • 편집된 시간

Reported roughly at https://x.com/sora_h/status/1798647485629616391/photo/1 (also refer to this post for screenshot), The following are details of this issue. Please remove ‘Apple Symbols’ from the --font-primary list in CSS.

Currently Discord font-family puts ‘Apple Symbols’ at the end of primary font family list (--font-primary in CSS), but this breaks Japanese text rendering as unfortunately Apple Symbols has certain Japanese glyphs.

If there's no matching font in a font-family list (OTOH when we remove ‘Apple Symbols’ from the present list), then the browser attempts to find a possible correct font using its font fallback algorithm and this generally works well with CJK text.

Note: generic font family ‘sans-serif' does nothing here for this fallback font selection because html lang attribute is not set to Japanese, so ‘sans-serif’ doesn't resolve into Japanese font.

This issue only occurs when UI is set to a language other than Japanese (OTOH, when HTML lang attribute is not ‘ja’); When UI is set to Japanese it is fine because :root:lang(ja) has --font-primary with several Japanese font faces, however, when the UI is set to other language - such as English. It doesn't work around. Actually, I do primarily use English, so the UI is set to English, but just some communications are in Japanese. Why do I have to change the app language?

Note 2: To let browsers prefer Japanese font faces when resolving fallback font, you need to add Japanese as a second language in the system preference. See also https://github.com/electron/electron/pull/23247

If you want to retain ‘Apple Symbols’, I'd suggest using @font-face with local() and unicode-range to restrict range of symbols.

 

7

댓글

댓글 2개

날짜 투표수
  • zakin alvix
    1. Recent font updates, such as Apple Symbols, have affected various text rendering systems.
    2. Specifically, the update has caused issues with Japanese character display.
    3. The problem arises from changes in font rendering and character support.
    4. This impacts users who rely on accurate Japanese text representation.
    5. Websites and applications using the updated font may exhibit broken or garbled Japanese characters.
    6. Users may experience reduced readability and formatting inconsistencies.
    7. Developers should consider rolling back to previous font versions or applying fixes.
    8. The issue highlights the importance of thorough testing with language-specific characters.
    9. For context, similar issues can arise with other updates, affecting various text elements.
    10. On a different note, the current سعر الفضة في تركيا (silver price in Turkey) remains a topic of interest for many.
    11. Keeping abreast of such updates and their impacts is crucial for maintaining optimal user experiences.
    12. Addressing font issues promptly ensures that users continue to receive accurate and reliable text display.
    -1
  • sorah

    This issue has been remaining for a while and disappointing.

    0

댓글을 남기려면 로그인하세요.