TextMesh Pro Chinese Traditional, Simplified and English text looks blurred

Take a look at this post which describes the strategy for splitting all these characters into a Primary Font Asset with a few fallbacks thus allowing you to have small atlas textures and higher sampling point size.

For CJK characters, try to aim for about 32 to 48 sampling point size with padding value of about 10% of sampling point size. Ie. if the sampling is 40 then padding of 4.

In terms of the blurriness, make sure the softness value is set to zero in the Face section of the material inspector.

The blurriness could also be cause be incorrect scaling / non uniform scale on the text object. For testing scale should be (1, 1, 1).

If you are using a CanvasScaler with Canvas in Screen Space - Camera or World Space that you do have a camera assigned to it.

Rest assured the text should be clean and sharp so we just need to figure what is causing this in this case.

 

You select the same font in the Font Asset Creator and create one primary font asset that will contain all the known / used Chinese characters in the project. Then you create additional font assets (from the same selected) font file and include the rest of the Chinese characters from the Table of General Standard Chinese characters. Basically, you are splitting the characters from the same font file between several font assets.

These fallbacks can be assigned to the primary font asset or to the general fallback list in the TMP Settings. Since these fallbacks are all created from the same font file, it makes sense to assign them to the primary font asset. By contrast if you want to be able to access icons and symbols with any font asset, it makes sense to assign that one to the TMP Settings so that all font asset can use it.

Any reason you are using bitmap font instead of Signed Distance Field?

I didn't pick up on the fact you were using bitmap. In order for bitmap text to render correctly, the glyphs need to be displayed at 1:1. So if the sampling point size is 19 then in order to render correctly, it has to be displayed at 19 points. Otherwise, scaling happens which will make it look fuzzy or harsher depending on whether you are below or above the sampling.

When a font is set to dynamic, each glyph is rendered and added into the atlas texture for each of the point sizes used.

Here is an example of this font sampled at 24 points and displayed at 24 points for the bitmap versions and then one that is SDF. The image shows the text at 5x and 1:1 zoom so you can compare them all.



BTW: One of the benefits of using SDF is that we only need to sample the glyph once for any point size and resolution. This allows us to save texture space but also provide all the benefits of being able to add outline / shadows, etc. still we great performance.

I would have assumed that Google's fonts designated for CJK would include all the relevant glyphs.

Having said that, one of the nice things about the fallback system is that you can find some other font that has those glyphs and create a small fallback font asset that only contains those glyphs and then assign it as a fallback to the primary that is missing those glyph. Provided the alternative font file has similar glyph design it should work nicely.

 

Using an external font view like BMFonts or High-Logic Font Creator, you can see the font file is missing many characters in the 2B0-2FF range. Same is true for the other ranges. The red arrows show the 2B0 - 2FF range.



The file is saved at "Assets/TextMesh Pro/Glyph Report.txt" and deleted when the Font Asset Creator is closed.