KanjiVG – SVGs of Kanji character strokes including order, shape and direction
kanjivg.tagaini.net
kanjivg.tagaini.net
I also built a little tool that would expand out the Kanji character into its constituent radicals and Heisig primitives so I could at them to my study code.
At that time, I was reading NHK Web News Easy on a regular basis and wanted to study those characters with Heisig's visual approach.
Resulted in some pretty gnarly code using kanjivg, pygame and ankiconnect: https://github.com/eshrh/anki-kunren
Simplified Chinese is a whole different beast of corruption that is a fork of Traditional Chinese but otherwise not similar to either.
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 Chinese 圓. In Chinese it was separately simplified twice to its current form 元. So when you see prices in 円 in Japan and 元 in China it's actually the same original character simplified differently.
Interestingly, traditional Chinese 國 was simplified by reusing an old character and is now 国 both in Japanese and simplified Chinese but not in traditional Chinese.
Why not.
I think the fork analogy still holds, no one says forks can't have convergent evolution or cross pollination
働 "work" 峠 "mountain pass"
峠 has a mandarin pronunciation apparently: https://baike.baidu.com/item/%E5%B3%A0/4336929
Incidentially, the backstory behind that kanji is hilarious.
The kanji is composed of the kanjis for "mountain" on the left side, and "up" and "down" on the upper right and lower right sides respectively.
You know what a mountain pass does? Go up and down a mountain.
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 News has lang="en", so it'll use a user setting to decide. For example, in Firefox' about:config, there's a setting called cjk_pref_fallback_order. If e.g. ja comes first, the little square inside the top square in 骨 is rendered on the right side, if any zh thing comes first, it's rendered on the left side.
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.
For instance traditional chinese in china will be left 過. Most computer systems will type this one
But in Taiwan they do right side. That said, i dont entirely understand how it works. You cant even copy\paste the right hand version into this comment box for instance- but you can see it on wiki. Maybe theyre separate fonts? Really not sure. Maybe somebody knows better
And simplified is entirely different 过
Well "kanji" literally means "Han character".
https://kanjivg.tagaini.net/viewer.html
Credit for the project is at the bottom of the page.
For example, enter 田 into both the original website (https://kanjivg.tagaini.net/viewer.html?kanji=%E7%94%B0) and hanzi5 (http://www.hanzi5.com/bishun/7530.html), and you'll see that the stroke order differs.
There are also several chinese characters which are not present in that japanese viewer, for example 厅
One thing that IMO is missing is the audio playback option for readings. This would've greatly facilitated remembering readings. AWS Polly is very easy to integrate with and it costs next to nothing. /nudge /nudge.
Another resource: https://github.com/CaptainDario/DaKanji-Single-Kanji-Recogni... someone made an interesting kanji recognition lib that hasn’t gotten attention
I have serious doubts whether this kind of data is even copyrightable, as long as you're not redistributing it verbatim.
A specific selection of words with pitch data (e.g. the NKH pitch dictionary) might be copyrightable as there was creative expression involved in picking which exact words to put into the dictionary and in what order. But the data itself? A 猫 is always going to have a HLL pitch accent (in the standard accent). That's a fact. And facts itself are not copyrightable.
You can't copyright a phone book[1]. Quoting from the case:
> "Notwithstanding a valid copyright, a subsequent compiler remains free to use the facts contained in another's publication to aid in preparing a competing work, so long as the competing work does not feature the same selection and arrangement"
Sounds exactly like the pitch accent data dump that's been floating around which a lot of people use. (Not the verbatim NHK one; the other one.) They probably used the data from NHK's pitch dictionary to compile it along with a few other dictionaries. But does it feature the same selection and arrangement? Nope.
[1] - https://en.wikipedia.org/wiki/Feist_Publications%2C_Inc.%2C_....
Edit: Found https://mizoru.github.io/blog/2021/12/25/Japanese-pitch.html
The correct data already exists, so I'm not sure what the point is besides having a less accurate but freer option
https://research.ibm.com/publications/accent-sandhi-estimati...
Piracy is rampant. Whether lifting and reusing/redistributing copyrighted dictionaries or other stud materials, or pirating ebook/cdrom type content. That’s nice, but as a legit service provider it’s less accessible without just giving users their own ability to side load in materials
Having owned a couple of books that had the stroke orders wrong while I was learning Japanese, I always check for mistakes in the stroke orders of kanji like 右 (right) and 左 (left) to make sure they're correct. KanjiVG gets it right.
On a tangentially related note, I recently purchased an iOS Japanese dictionary app called "Nihongo" (https://apps.apple.com/us/app/nihongo-japanese-dictionary/id...) for my daughter because she wanted to study Japanese. I was just expecting a basic course, but it is probably the best vocabulary/kanji studying app I've ever used. It's a little pricey, but well worth it if you're trying to build a strong Japanese vocabulary or learning to read kanji. I have no affiliation with the people who make the app. I'm just an impressed buyer.
https://web.archive.org/web/20040925183635/http://kanjicafe....
Sorry but I don’t know much about these kinds of characters.
For example, think about writing a capital A. It’ll look different if you draw the middle bar first or if you draw the outer two lines first. F will also look different depending on whether you draw the vertical line or one of the horizontal lines first. Try a Q with the little bottom dash before drawing the circle. It’s not only weird but more difficult.
The difference in these characters is subtle, but you can notice it with your own writing. Now instead of 3 strokes to write a character, imagine those with 15 or even 28 strokes. The odd balance and proportions have cascading effects.
1) Chinese characters are traditionally/historically written with a brush, not a modern pen or pencil. Because brushes don't create uniform lines, there is a connection between the specific series of movements and the final appearance of the character (sort of like calligraphy pens). Basically, inconsistent movements tend to produce inconsistent-looking characters, so an agreed-upon standard aids in legibility.
2) Various components (most notably the "radicals") reoccur across many characters. Having a (mostly) consistent set of rules for how each component is written and in which order aids memorization because you're not learning every new character "from scratch".
3) Stroke order affects how mechanically efficient it is to write the character, which can be a pretty big deal when some of the more complex characters are upwards of a dozen strokes.
If, for example, you are taking handwritten notes on an ipad, and want software to convert the notes into text... well, knowing the order of strokes and having an agreed upon order helps considerably over just trying to match shapes.
Digital dictionaries also usually have a "handwritten input" mode to look up a character, and that mode will also recognize characters much more accurately when input with correct stroke order.
You can normally tell when someone uses the incorrect stroke order because things will be the wrong size. For example, when writing 因 you're supposed to write the outer ㄇ first, then the inner 大 and then the bottom horizontal stroke of the 口. If you start with the 大 then it's harder to write the outer 口 the right size.
Again, this is all from a beginner, so take it with a good amount of salt.