We'd need fonts for the following languages: This combination's total size is 6.17 MB while wqy-zenhei alone would consume 12.6 MB.Ī screenshot of wesnoth 1.9.13 running in Japanese with Droid fonts: They are both from Google Android's Droid font family and licensed under Apache License 2.0 which is fully GPL compatible. They provide italic characters, and can offer Japanese characters instead of Chinese ones if you give Droid Sans Japanese priority. Meanwhile, I figured out that Droid Sans Japanese combined with Droid Sans Fallback Full could be an acceptable solution for CJK. Whether Takao can be distributed with Wesnoth is still unclear, and I have emailed ivanovic for a clearfication. ![]() If you say takao's license is not fully compatible with the GPL,you can choice sazanami.At least sazanami does bot show garble. ![]() If Russian designer make a font for the entire alphabet,Īnd you use poor Latin alphabet while Russian alphabet is perfect.It's a situation like that. when using CJK characters in an western locale, or trying to display Japanese on a Chinese system, sometimes the locale settings are not even taken into account), so a Chinese font will provide Chinese characters in priority - and they are subtlely wrong when representing Japanese.Īnd i didn't think about Hanja problem because i don't use Hanja translating wesnoth. when using CJK characters in an western locale, or trying to display Japanese on a Chinese system, sometimes the locale settings are not even taken into account), so a Chinese font will provide Chinese characters in priority - and they are subtlely wrong when representing Japanese.ĬloudiDust wrote:Actually there's much similarity between Chinese Hanzi, Japanese Kanji and Korean Hanja (though Hanja is not frequently used in Korea now), which makes "han unification" possible and said unification is the reason why Japanese characters appear strange when rendered in Chinese fonts - many Kanji's and their Hanzi / Kanja counterparts (that have a common root and similar meanings, but are somewhat different visually, like "Hanzi", "Kanji" and "Hanja" themselves) are mapped to the same codepoints in Unicode (in order to reduce the size of the spec), and the Asian fonts may not have all the different glyphs for CJK or have no way to figure out whether they are supposed to represent a Chinese or Japanese or Korean character (eg. ![]() English and other Latin alphabets have a similarity but CJK have no similarity.Īctually there's much similarity between Chinese Hanzi, Japanese Kanji and Korean Hanja (though Hanja is not frequently used in Korea now), which makes "han unification" possible and said unification is the reason why Japanese characters appear strange when rendered in Chinese fonts - many Kanji's and their Hanzi / Kanja counterparts (that have a common root and similar meanings, but are somewhat different visually, like "Hanzi", "Kanji" and "Hanja" themselves) are mapped to the same codepoints in Unicode (in order to reduce the size of the spec), and the Asian fonts may not have all the different glyphs for CJK or have no way to figure out whether they are supposed to represent a Chinese or Japanese or Korean character (eg.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |