Integrate type in the case where it should be displayed neutrally in a third language.

[kmsu3541]

I think about it as follows,

If so, in the later update or future plan, How about setting the Null tag to Kangxi-based font from a third country perspective?

At first, I heard that the Kangxi-based font was used as a default format. but, as time went by standards were established for each country.

Like this.

• Source Han Sans (Null): [Completely_Kangxi_Based]–Type
• Source Han Sans J: Japanese–Type
• Source Han Sans K: Korean–Type
• Source Han Sans CH: SC(Chinese)–Type
• Source Han Sans TW: TC(Taiwan)–Type
• Source Han Sans HK: TC(Hongkong)–Type

I Think this improvement will be the most neutral way for users who view a third language. Therefore, this classification would be ideal.

[Marcus98T]

While this is a good suggestion, unfortunately, this is not going to happen with regards to the scope of this project. There was a similar thread, and basically they could not do it due to technical limitations.

The substantial enhancements to the glyph repertoire of Source Han Sans as discussed in this thread are, unfortunately, beyond the scope of Adobe's current plans and capacity to investigate further. If we are able to revisit this in the future, we will reopen investigation into what would constitute an appropriate set of glyphs.

Even if we do not add any glyphs and make a so-called neutral null tag, there will soon be people demanding that Adobe must make proper Kangxi versions because a few common use glyphs are not available in the JP/KR style. It's a slippery slope.

And even then there are actually multiple variants of the Kangxi forms. Nothing we can standardize on.

So I think it is technically infeasible. I won't say any more.

[kmsu3541]

Oh.. I am sorry to hear that...🥲

It's amazing to see users who have the same opinion as me.

but, so even if the project is completed in the distant future, is there any attempt or possibility of that???

[Marcus98T]

This project can be forked, but creating new glyphs will take a very, very long time. Plus there's a lot of technical hurdles to set up and try to replicate the features of Source Han Sans/Serif, but with custom mapped glyphs and what not. Not to mention the 65,536 glyph limit if CN, TW and HK handwriting forms are to be kept.