Wondering if Mojang is forgetting about this but since many other languages have migrated, I do hope Mojang would pay attention to this.
Unifont 15.1.03 has been released with my patch. Please sure to tell me your opinion.
Also that’s not Arial and Consolas, that’s some default CJK sans serif like 等线 as Arial Consolas doesn't contain CJK glyphs and thus 等线 was used as fallback.
I have submitted a related patch to Unifont. We will have to wait for the maintainer’s response.
Please reopen this issue as Unifont 15.0.05 has published a new set of Hangul syllables. Examples (note that the example mixes Han characters and Hangul, the first pic is old and last pic is new):
[media][media]Please reopen this issue, Unifont 15.0.02 is released and fixed it. http://unifoundry.com/pub/unifont/unifont-15.0.02/font-builds/
Be sure to use unifont_all-15.0.02.hex and upper. The character “𰻞” could be correctly rendered with the all.hex.
The original font was replaced by Unifont due to copyright issue. That is, the original font is used by a terminal software called HanTerm, but the font is only licensed to be used on the software, not anywhere else. Later on Unifont used a method to generate Hangul syllables through algorithms, see Generating Hangul Syllables (unifoundry.com). I encourage you guys to also contribute Hangul syllables to Unifont as well.
Already reported to Paul Hardy (Unifont maintainer). They are planning to use the punctuations from Wen Quan Yi. Unifont 16.0.0 is going to be out with Uniccode 16.0 which is going to be this September.
Already reported to Paul Hardy (Unifont maintainer). They are planning to use the punctuations from Wen Quan Yi. Unifont 16.0.0 is going to be out with Unicode 16.0 which is going to be this September.
/damage @s 100 thrown
also causes missing messages.
@Brain81505 they use fcitx5; GitHub repository: https://github.com/fcitx/fcitx5
This actually may affect all IMEs (at least on Linux) that supports composing words. As far as I know, there are also English IMEs which is also affected.
This is related to different standards of font making; Corner-justified rule applies for GB (China mainland) and JIS (Japan) standards, while making most of them center-aligned applies for CNS (Taiwan) standard. Since Unifont inherits the CJK part from Unibit, which follows GB standard, I'd support to making it corner-justified, but it would be not as good for CNS standard users (mainly Traditional Chinese users).
To really solve this problem, we will have to include several CJK fonts inside the game (e.g. Noto Sans provides CN/TW/HK/JP/KR, 5 variants iirc), and choose the corresponding one for each language.
I have made a new glyph_sizes.bin to fix the issue. see MC-231056! I hope my patch can be applied soon lol.
k. 😞
Can confirm in 20w18a
Some of these bad translations are hilarious actually, but they caused a lot of problems like I tried to tell others about one thing and they just didn't understand till we opened the game, which is pretty awful.
Some of the users (including me) are preparing a separate Traditional Chinese Unifont version, however the exact details remain to be discussed. Considering that CNS 11643, or let's say a strictly Taiwan MoE-compliant bitmap font does not actually exist (MingLiU's bitmap font actually leaves quite a lot characters not edited to be compliant), I'd say we could create a font based on traditional orthography, like how IBM Plex TC does.