Mojikyō: Comparison
View Latest Version
Please note this is a comparison between Version 1 by Jason Zhu and Version 2 by Jason Zhu.

Conceptualized in 1996, the first version of the CD-ROM was released in July 1997. For a time, the Mojikyō Institute also offered a web subscription, termed "Mojikyō WEB" (文字鏡WEB), which had more up-to-date characters. (As of September 2006), Mojikyō encoded 174,975 characters. Among those, 150,366 characters ([math]\displaystyle{ \approx }[/math]86%) then belonged to the extended Chinese–Japanese–Korean–Vietnamese (CJKV)[note 2] family. Many of Mojikyō's characters are considered obsolete or obscure, and are not encoded by any other character set, including the most widely used international text encoding standard, Unicode. Originally a paid proprietary software product, as of 2015, the Mojikyō Institute began to upload its latest releases to Internet Archive as freeware, as a memorial to honor one of its developers, Tokio Furuya (古家時雄), who died that year. On December 15, 2018, version 4.0 was released. The next day, Ishikawa announced that without Furuya this would be the final release of Mojikyō.

  • 文字鏡web
  • cd-rom
  • unicode

1. Premise

The Mojikyō encoding was created to provide a complete index of Chinese, Korean, and Japanese characters. It also encodes a large number of characters in ancient scripts, such as the oracle bone script, the seal script, and Sanskrit (Siddhaṃ). For many characters, it is the only character encoding to encode them, and its data is often used as a starting point for Unicode proposals.[1][2] However, Mojikyō has much looser standards than Unicode for encoding, which leads Mojikyō to have many encoded glyphs of dubious, or even unintentionally fictional, origin.[3][4] As such, while many non-Unicode Mojikyō characters are suitable for addition to Unicode, not all can become Unicode characters, due to the differing standards of evidence required by each.

2. Composition

The Mojikyō fonts (文字鏡フォント) are TrueType fonts that come in a ZIP file and are each around 2–5 megabytes; the different fonts contain different numbers of characters.[5] Also included is a Windows executable that implements a graphical character map, the "Mojikyō Character Map" (文字鏡MAP), MOCHRMAP.EXE.[6][7] MOCHRMAP.EXE allows users to browse through the Mojikyō fonts, and copy and paste characters in lieu of typing them on the keyboard. As opposed to the regular Windows character map, or for that matter KCharSelect, which both support TrueType fonts, MOCHRMAP.EXE displays the numbered Mojikyō encoding slot of the requested character.[8][9] In order for MOCHRMAP.EXE to work, all Mojikyō fonts must be installed.[10]

3. Encoding

When referring to a character encoded in Mojikyō, the format MJXXXXXX is often used, similar to the U+XXXX format used for Unicode. For example, hentaigana U+1B008 𛀈 has Mojikyō encoding MJ090007 and Unicode encoding U+1B008.[11] A difference, however, is that Mojikyō encodings displayed this way are decimal, while Unicode's U+ encoding is hexadecimal.

From the earliest days of Unicode, Mojikyō has both influenced—and been influenced by—the standard. Glyphs originating from Mojikyō first appear in a proposal to the Ideographic Rapporteur Group (IRG),[12] which is responsible for maintaining all CJK blocks in Unicode,[13][14] on 18 April 2002.[15] In May 2007, Mojikyō played a minor role in an eventually successful series of proposals to encode the Tangut script in Unicode;[16][17] Mojikyō already had within its encoding 6,000 Tangut characters by October 2002.[18]

The Unicode Standard's Unihan Database refers to Mojikyō as the "Japanese KOKUJI Collection" (日本国字集), abbreviated "JK".[19] For example, U+2B679 𫙹 ,[20] an ideograph read in Japanese as burizādo (ブリザード, lit. blizzard), has a J-Source[21] equal to JK-66038. All Unicode characters with a JK-prefixed J-Source originate from Mojikyō.[22][23] According to Ken Lunde, a subject matter expert in character encodings and East Asian languages, as of Unicode 13.0, 782 ideographs in Unicode originate from Mojikyō, split somewhat evenly between two blocks: CJK Unified Ideographs Extension C, with 367, and CJK Unified Ideographs Extension E, with 415.[24][25] Not all Unicode characters with Mojikyō origins (JK-prefixed J-Sources) have the same representative glyph in the code chart as in the Mojikyō font;[26] some characters had their shapes changed before final encoding, as investigation showed the shapes assigned by the Mojikyō Institute were wrong.[4][27]

3.1. Blocks

(As of September 2006) it encoded 174,975 characters.[18] Among those, 150,366 characters then belonged to the extended CJKV[28] family.[29] Many of the encoded characters are considered obsolete or otherwise obscure, and are not encoded by any other character set, including the international standard, Unicode. Each Mojikyō character has a unique number, and the characters are organized into blocks.

Mojikyō puts CJKV characters in different blocks according to their traditional Kangxi radical. Common radicals containing an especially high number of characters, such as Radicals 9 (人) and 162 (⻌), are split further by stroke order.[30]

3.2. No Uunification

Unlike Unicode, Mojikyō purposely avoids Han unification; no attempt at compactness of the encoding is made, nor is there an attempt to keep all common characters below U+FFFF as there is in Unicode.

Unicode, on the other hand, sorts its CJK into blocks based on how common they are: the most common are generally put into the Basic Multilingual Plane,[27] while those that are rare or obscure are put into the Astral Planes.

For example, Radical 9 has two characters where Unicode has one: MJ054435 (令), and MJ059031 (令), both represented in Unicode as U+4EE4 令 .

4. License

Mojikyō is proprietary software under a restrictive license. Originally, the Mojikyō Institute tried to prevent its character data from being used, and threatened those who published conversion tables to and from its character set. In July 2010, the Mojikyō Institute abandoned its legal efforts to stop at least one Japanese user from publishing conversion tables or converting characters encoded in Mojikyō to Unicode or other character sets.[31] Mere data, sometimes including the shapes of letters, are considered in many jurisdictions to be common property as they do not meet the threshold of originality.[32]

Due to this legacy, however, GlyphWiki (ja) disallowed Mojikyō data as of 2020.[33]

5. Collected Writing Systems

5.1. Living

  • Chinese — Hanzi
  • Japanese — Kanji, Kana (including Hentaigana)
  • Korean — Hanja
  • Latin alphabet with diacritics
  • Cyrillic script with diacritics

5.2. Dead or obsolete

  • Ancient Chinese
    • Oracle bone script
    • Seal script
  • Taiwanese kana
  • Vietnamese — Chữ Nôm
  • Sanskrit — Siddhaṃ
  • Tangut script
  • Sui script

References

  1. Takada, Tomokazu; Yada, Tsutomu; Saito, Tatsuya (2015-09-18). Proposal for hentaigana. Information Processing Society of Japan. L2/15-239. https://www.unicode.org/L2/L2015/15239-hentaigana.pdf. Retrieved 2020-07-05. 
  2. Hiura, Hideki; Kobayashi, Tatsuo et al. (2003-10-31). Ideograph Variation Selector and Variation Collection Identifier. Open Internationalization Initiative. L2/03-413. https://www.unicode.org/L2/L2003/03413-varsel.html. Retrieved 2020-07-05. 
  3. Takada, Tomokazu [高田智和]; Oda, Tetsuji [織田哲治]; Konishi, Satoshi (2013-08-26). "Error: no |title= specified when using {{Cite web}}" (in ja). p. 2. https://mojikiban.ipa.go.jp/contents/pdf/2013/20130826_3k_g.pdf. "文字鏡研究会の関係者にヒアリングしたところ、オランダから提案されたWG2 N36981には文字鏡のフォントが使用されているが、文字鏡研究会は関与しておらず、提案内容についても疑問があるとのことであった。[According to an interview with a representative of the Mojikyō Institute, a Mojikyō font is used in WG2 N36981 proposed by the Netherlands, but the Mojikyō Institute itself is not involved with the proposal; it furthermore has doubts about some of the content of that proposal.]"
  4. Suzuki, Toshiya [鈴木俊哉] (2009-07-30). (in ja)IPSJ SIG Technical Report (Information Processing Society of Japan) 2009-DD-72 (7): 2. https://web.archive.org/web/20200320094733if_/https://ipsj.ixsq.nii.ac.jp/ej/?action=repository_action_common_download&item_id=62547&item_no=1&attribute_id=1&file_no=1.+"しかし、拡張Cの標準化作業が8年の長期にわたり、また事後的に用例が必須とされたため、正式に公布された拡張C漢字の典拠は当初の典拠とはかなり異なるものとなっている。たとえば日本では当初は文字鏡研究会によって選定された1000文字程度の漢字を申請していた[。] [...] 典拠用例確認は文字鏡とは独立に行なわれたため、字形が文字鏡漢字から変更されたものも多い。[As the standardization effort for CJK Unified Ideographs Extension C has been eight long years in the making and examples of kanji have been requested after their encoding, the officially promulgated Extension C kanji standard is quite different from the original standard. For example, we, the Government of Japan, initially applied for about 1,000 kanji selected by the Mojikyō Institute[.] [...] Since the verification of the kanji was performed independently of the Mojikyō Institute, the character shapes were often changed from Mojikyō's version of that same codepoint.]". 
  5. Download the file MojikyoCmap400ALL49TTF.7z from the official website http://mojikyo.org
  6. English name from the title of the window produced by running the executable; Japanese name from the icon of the executable.
  7. Also called the "Mojikyō Cmap".
  8. Ishikawa, Tadahisa (1999-05-25). "パソコン悠悠漢字術 今昔文字鏡徹底活用". Mojikyō Institute. https://www.est.co.jp/ks/dish/jepax/samples/ykanji/ykanji-sample.html. 
  9. See the screenshots on the official website http://mojikyo.org
  10. Into the system fonts directory C:\Windows\Fonts.
  11. "Error: no |title= specified when using {{Cite web}}". Information Technology Promotion Agency. http://mojikiban.ipa.go.jp/xb164/.
  12. As of 2019, the IRG rebranded as the Ideographic Research Group.
  13. "Unicode Standard Annex #45: U-source Ideographs". The Unicode Standard. Unicode Consortium. https://www.unicode.org/reports/tr45/. 
  14. "Appendix E: Han Unification History". The Unicode Standard. Unicode Consortium. March 2020. https://www.unicode.org/versions/Unicode13.0.0/appE.pdf. 
  15. "CJK Extension C1 From Japan". Ideographic Rapporteur Group. https://appsrv.cse.cuhk.edu.hk/~irg/n0801-0900.html. "N895-Japan_C1" 
  16. Cook, Richard (2007-05-09). Proposal to encode Tangut characters in UCS Plane 1. UC Berkeley Script Encoding Initiative. pp. 4. L2/07-143. http://unicode.org/wg2/docs/n3297.pdf. 
  17. The history of the encoding of the Tangut script is quite complicated, see Template:Format linkr for a full listing of all the related proposals and a timeline.
  18. "Error: no |title= specified when using {{Cite web}}". Kinokuniya KK. http://mojikyo.com/info/about/index.html.
  19. Jenkins, John H.; Cook, Richard; Lunde, Ken, eds. (2020-03-05), "kIRG JSource", Unicode Standard Annex #38, Unicode Consortium, https://www.unicode.org/reports/tr38/index.html#kIRG_JSource 
  20. Ideographic Description Sequence: ⿰魚嵐
  21. This is a column name in the Unihan database; ⟨J⟩ here is short for "Japanese glyph source". The full name of the column is kIRG_JSource. Under Han unification, there are nine such sources. See §3.1 of UAX38}}|UAX#38 for a complete list and more information.
  22. Ken Lunde [@ken_lunde] (2020-07-06). "JK-prefixed J-Source ideographs came from 今昔文字鏡, which are in Extensions C and E (the mention of Extension D was simply that what became Extension E was originally targeted to become Extension D).". https://twitter.com/ken_lunde/status/1280291832593670145. 
  23. Other J-Source prefixes exist, such as J4, meaning the character originates from JIS X 0213:2004.
  24. Ken Lunde [@ken_lunde] (2020-07-06). "In particular, all 782 JK-prefixed ideographs are indeed from 今昔文字鏡 per IRG N862. Most were encoded in #ExtensionC, and the stragglers were encoded in #ExtensionE..". https://twitter.com/ken_lunde/status/1280285758385827842. 
  25. Ken Lunde [@ken_lunde] (2020-07-06). "367 JK-prefixed ideographs are in Extension C, and the remaining 415 are in Extension E..". https://twitter.com/ken_lunde/status/1280314296799424519. 
  26. That is to say, a glyph made up of the same radicals in the same positions.
  27. Errors in large collections of ideographs are, of course, not uncommon. Such errors even accidentally occur in well funded government-produced collections, such as the famous kanji from unknown sources in the Japanese Industrial Standards Committee's JIS X 0208 double-byte character encoding standard. All of these JIS X 0208 error kanji (幽霊漢字; e.g., 彁) have made their way into Unicode despite not being "real" kanji.
  28. For Korean, Hanja are referred to. For Vietnamese, Chữ Nôm.
  29. "Error: no |title= specified when using {{Cite web}}" (in ja). Kinokuniya KK. http://www.mojikyo.com/info/about/index.html.
  30. For proof, see the list in the Mojikyō Character Map, MOCHRMAP.EXE.
  31. "終戦宣言" (in ja). 2010-07-21. https://www.seiwatei.net/info/endwar.htm. 
  32. See also: fictitious entry; trap street.
  33. "データ・記事のライセンス". http://glyphwiki.org/wiki/GlyphWiki:%E3%83%87%E3%83%BC%E3%82%BF%E3%83%BB%E8%A8%98%E4%BA%8B%E3%81%AE%E3%83%A9%E3%82%A4%E3%82%BB%E3%83%B3%E3%82%B9. "今昔文字鏡およびその関連製品、データは、そのライセンス上グリフウィキには用いることができません。文字鏡番号（独自部分）および文字鏡のフォントに収録されているグリフそのもの、およびそれを参照、利用して作成していると判断できる情報は、グリフウィキに登録する際の典拠とすることはできませんので、ご協力をお願いいたします。 [Konjaku Mojikyō and related products and associated data are licensed in such a way that they are incompatible with our above GlyphWiki license. Neither the number of the Mojikyō encoding slot, nor the appearance of the glyph itself in Mojikyō's fonts, nor any information whatsoever that can be judged to have been gathered by referring to a Mojikyō product, can be used when entering data into GlyphWiki. We absolutely cannot accept Mojikyō data. Please cooperate with us.]" 
More
© Text is available under the terms and conditions of the Creative Commons Attribution (CC BY) license (http://creativecommons.org/licenses/by/4.0/)
Video Production Service
Feedback