KanjiVG – SVGs of Kanji character strokes including order, shape and direction

Post by Macha » Wed, Feb 22, 2023, 11:44 AM UTC

mytailorisrich wrote: post #40

Dalewyn wrote: post #21

Earlier quoted context omitted.

This. Traditional Chinese and Japanese are two seemingly similar but distinctly different things (the latter is forked from the former). Simplified Chinese is a whole different beast of corruption that is a fork of Traditional Chinese but otherwise not similar to either.

Kanji were also simplified but not necessarily the same way as simplified Chinese. Simplified Chinese also sometimes uses 'old' characters. So sometimes modern Japanese is actually similar to simplified Chinese, sometimes it is similar to traditional Chinese, and sometimes it is unique. There is no simple 'fork'. For instance, 円 (yen) is simplified Japanese and uniquely Japanese. It used to be same as traditional Chi…

Post by bkbullock » Wed, Feb 22, 2023, 12:09 PM UTC

anonfunction wrote: post #29

I looked around and couldn't find any examples or demo of the SVGs on the website. This is the epitome of a project that would benefit from a visual representation.

Post by AnIdiotOnTheNet » Wed, Feb 22, 2023, 1:44 PM UTC

qiqitori wrote: post #34

fenomas wrote: post #22

Earlier quoted context omitted.

Definitely not exactly the same. Kanji and Hanzi are two different character sets - they overlap a lot, but each has common everyday characters that aren't in the other, and sometimes the "same" character is in both sets but written differently in various languages (e.g. 骨).

In case anyone is wondering why different glyphs have the same unicode code point, and how an app is supposed to decide which one to render... Well I don't know the reason for the first question actually, though many people appear to have some choice comments. But as for the second question: for HTML documents, many tags have a lang attribute that decide which version of the glyph to render within that tag. Hacker Ne…

Post by AnIdiotOnTheNet » Wed, Feb 22, 2023, 2:26 PM UTC

kevin_thibedeau wrote: post #56

AnIdiotOnTheNet wrote: post #55

Earlier quoted context omitted.

> In case anyone is wondering why different glyphs have the same unicode code point, and how an app is supposed to decide which one to render... Well I don't know the reason for the first question actually https://en.wikipedia.org/wiki/Han_unification My understanding is that this is basically "white guy says all Asian writing looks the same" in standards form and is largely regarded as a terrible idea.

Unicode had a builtin language tagging system to resolve glyph variants. Han unification was implemented with this in mind. Then the tagging got deprecated in a later version.

Post by ThinkingGuy » Wed, Feb 22, 2023, 2:43 PM UTC

mytailorisrich wrote: post #40

Dalewyn wrote: post #21

Earlier quoted context omitted.

This. Traditional Chinese and Japanese are two seemingly similar but distinctly different things (the latter is forked from the former). Simplified Chinese is a whole different beast of corruption that is a fork of Traditional Chinese but otherwise not similar to either.

Kanji were also simplified but not necessarily the same way as simplified Chinese. Simplified Chinese also sometimes uses 'old' characters. So sometimes modern Japanese is actually similar to simplified Chinese, sometimes it is similar to traditional Chinese, and sometimes it is unique. There is no simple 'fork'. For instance, 円 (yen) is simplified Japanese and uniquely Japanese. It used to be same as traditional Chi…