musescore / musescore/MuseScore

MuseScore.com font fallback does not work for many Chinese characters

Open
#27,554 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce
  1. Create a score that contains any of the following characters, which are used in Chinese but not in Japanese or Korean: 热 爱 纯 馏 轻 败 对 让 说 坚 样 这 时 场 态 哟
  2. Set the font to anything other than "Noto Sans SC" or "Noto Serif SC"
  3. Upload it to MuseScore.com. Example score link
  4. The characters will be shown as boxes, even though the image server has fonts that include these characters

While some other characters display, they are randomly from different fallback fonts (some are serif and some are sans serif), and characters like 耀 and 零 are shown wrongly because Japanese versions of the characters are shown instead of Chinese versions (#27555 has more information about that problem).

Supporting files, videos and screenshots

The score image shown on MuseScore.com. I set the font as Arial Unicode MS in MuseScore Studio, but the characters are randomly from different fonts. Many common characters, like 爱 (love) and 时 (time), are not displayed at all.
Image

Character shapes for (zero). The Japanese/Korean version is the one shown in the score image.
Image

What is the latest version of MuseScore Studio where this issue is present?

4.5.1

Regression

No.

Operating system

All

Additional context

Since this problem affects multiple languages, I suggested to the MuseScore.com staff that they should install all of the Noto Serif fonts and/or Arial Unicode MS. However, it seems like there are some other font logic problems that could not be resolved just by installing more fonts.

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.