1. ja 関数 cognates with zh-HK 函數.

Wiktionary: 日本語としての関数はもともと「函数」と書く。これは英語 "function" の中国における訳語である函数 (hánshù) をそのまま輸入したものであるが、「函」が漢字制限による常用漢字に含まれなかったため1950年代以降、同音の「関」へと書き換えがすすめられた。

Besides, ‘function’ appears in another part of this project, and that part is correct: https://github.com/dahlia/cjk-compsci-terms/blob/1fcbf1daad0912b78653148a496483dd45e8c412/tables/paradigms.yaml#L146-L155

2. 式 in zh-TW means ‘style’, but is mistakenly written as ‘number’.

承上而誤

Maybe a native speaker can review this but I think 자료 is more like 'material' whereas 정보 is more like 'information'. Both are a sensible translation of 'data'.

For non-English pages, the ToC extension generates its links as <a href="#{contents}">. When users click them, it routes to the English page. This commit will make them as <a href="{lang}#{contents}">.

The current style has the only color scheme with white background. It would be good to have a more color scheme with black background as well for ones who love dark/night mode.

As the existing color scheme already depends on Open Color, choosing a set of colors for the new color scheme would be not that difficult.

See also the prefers-color-scheme CSS media feature.

Although I am totally ignorant about Vietnamese, I would appreciate if someone help me.

One thing to consider is that it would require the repository name and the website domain name to be renamed from cjk-compsi-terms to cjkv-compsi-terms, but I'm going to do all of bits and pieces for it if we finally manage it.

If there are enough resources about North Korean terms we could add a new column for North Korean (ko-KP). This issue tracks the useful resources for that.

• 《C++프로그람개발법》 (How to program in C++)
• 남북한 IT용어 비교 (South–North differences in IT terms)
• DPRK Textbooks from Internet Archive
• 《남북 정보통신기술 용어집》 (Information technology glossary in South and North Korea; ISBN: 9788929411701)

See also my tweet about this research. Please report more resources.

Sometimes, an existing character can be a regional variant of another character due to its coincidental reading in a region. However, often such regional variants cannot convey the intention in other regions.

For example, 才 (talent) is used often instead of 歳/歲 (age) in Japan due to its coincidental reading in Japanese: さい (sai). However, those two characters don't share the same reading in other regions, e.g., 才 is 재 (jae) & 歲 is 세 (se) in Korean.

If such regional variants replaced orthodox characters in a regional standard they should be normalized to orthodox ones in keys to group cognates, whereas their readings from other languages should be read as variant characters which aren't normalized.

For example, since 函 (box) is unlisted in Japanese jōyō kanji (常用漢字), 函 (かん; kan) is replaced by 関/關 (relation) which has the same reading. That's why 函數 (function) is written as 関数/關數 in Japanese. Still, as those two characters are read differently in other regions (e.g., 함 ham vs 관 guan in Korean), such uses need to be marked in the data set and pronunciations in <ruby> should show the proper reading (e.g., 함 instead of 관).

See also: https://github.com/dahlia/cjk-compsci-terms/pull/9.

• [x] Concurrent programming
• [ ] Parallel computing
• [x] Concurrency
• [x] Lock
• [x] Synchronization
• [ ] Asynchronous programming
• [ ] Synchronous programming
• [x] Transactional memory
• [ ] Multi-core

Thanks @item4 & @disjukr for their suggestions.