ᠮᠤᠩᠭᠤᠯ ᠪᠢᠴᠢᠭ ᠤᠨ ᠰᠢᠨᠡ ᠪᠠᠷ ᠺᠤᠳᠠᠯᠠᠬᠤ 8 ᠲᠦᠰᠦᠯ
The Usgiin Solutions, consolidated by Z team pg. 1 Doc Type: Working Group Document Title: Preliminary proposal for encoding the Mongolian Usgiin Solution in the SMP of the UCS File No: File-2 Source: Z Code, M Code, J Code, C Code, S Code, A Code Status: Private entity contribution Action: For consideration by JTC1/SC2/WG2 and UTC Date: 2020-02-14 Contact: Chuck Namujila The report is consolidated by Chuck Namujila and vetted by Tiffany Namujila 1. Problem Statement The major issues in Mongolian Phonetic script were discussed in the previous file “Preliminary proposal for encoding the Mongolian Usgiin Solution in the SMP of the UCS” submitted to Unicode on 25th Jan 2020 and revised on 30th Jan 2020. In summary, the phonetic solution violated Unicode Standard Chapter 2.2 by: Being unreadable in historic writing systems and breaking the “Universality” principle Creating Code Duplication and breaking the “Unification” principle Using FVS/MVS/Grammar logics and breaking the “Plain Text” principle Being unstable between versions and violating the “Stability” principle As a result, popular websites like qinggis.net, Bainu, Holvoo are not using U1800 Phonetic Unicode Standard. 2. Objective This document consolidated multiple proposals for the new codings (in new Unicode Block) for Mongolian Hudum and Todo scripts. Manchu script proposal is in progress and will be submitted in the next few weeks. Sincerely hope the Unicode Experts and Technical Committee to review, comment, and further improve any of the following proposals. Mongolian user community believes in Unicode expert’s unbiased judgment, and we are entrusting the future of our beloved script at your good hands. 3. Writing Direction Historically, the Mongolian script is a child system of Sogdian and Syriac systems, which are written from right to left. If the new coding follows the Syriac/Aramaic and Arabic methods, the new coding could leverage on the sophisticated Arabic software. Arabic world has huge populations and abundant with capital investments, so many vendors are developing software for the Arabic world. If the Mongolian script manages to leverage on Arabic systems, it could bring down the future development cost and software maintenance cost. We would like to leave this important choice (writing direction: right to left or left to right) to Mr. Roozbeh Pournader to decide since he is the Unicode expert in Arabic scripts. 4. Financials The development of new script might need certain investment capitals and financial support. If the Unicode membership fees and other financials are required, please feel free to let us know. We will raise enough capital for the future of our valuable scripts. 5. Database - Word Bank We already built a database with 3 million Hudum Mongolian words/sentences and willing to provide to UTC. The Usgiin Solutions, consolidated by Z team pg. 2 Part 1 Hudum Mongol Proposals Hudum Mongol Option 1: Z-56 Z-56 solution uses the smallest components of Hudum Mongolian script and strictly followed the Unicode Standard chapter 2.2 Design Principles. The curve-joint part is decomposed into smaller components and does not require Opentype. Without Opentype support, these characters could correctly show the Hudum characters. With Opentype support, these characters could be much more beautiful. Two characters Ga (ᡂ) and Ng (ᡉ) were un-split to keep the Mongolian tradition. We could remove these two characters if required. Sample text using the Phonetic IME (Input method editor): The Usgiin Solutions, consolidated by Z team pg. 3 Hudum Mongol Option 2: FSZ-74 FSZ-74 is the medium option between Z-56 and Z-137. It combined the Curve-Joint characters. This is the refined version from the Sainbilig code, which was created by Mr. Sainbilig in 2012. Millions of internet writings were created using Saibilig code until the Phonetic code finally receive the USP10.dll package from an unknown (security risk) third party vendor in 2005. This code chart also picked up some essential elements from FangZheng 6.0, which was created by Mr. QiDeHua in 1990. Fang Zheng 6.0 was widely used in Publishing houses for many years. Mongolians are extremely familiar with Saibilig code and FangZheng 6.0 Early samples of FangZheng 6.0 The Usgiin Solutions, consolidated by Z team pg. 4 Hudum Mongol Option 3: Z-137 Z-137 is the matric combination of Z-56, without creating any code duplication. This code chart is designed by Z-team Mr. Surgalt (ᡗᠪᡷᡂᠡᡒᡩᠮ) and considered most of the possible combinations of Mongolian structured characters. The fonts are carefully built based on different combinations of Curve (ᠯᠪᡌᠮ) and Tail (ᠠᠪᡩᠪᠨᡗᠡᡅᠫᡖ); as a result, the OpenType feature is no longer required. It also created a small box at Medium form to avoid code duplication. The Usgiin Solutions, consolidated by Z team pg. 5 Hudum Mongol Option 4: J-74 Code J-74 Code is designed by Mr. JiranNaima (ᠧᠧᡷᠡᠡᠲᠡᠧᡌᠣ) from the Ordos region. This solution requires OpenType support. Without OpenType, the curved combination will show the separate characters. The designer would like to highlight that: The first group of 26 characters will create the initial forms of Mongolian script. The second group of 26 characters will create medium forms. And the rest of the characters composite the final forms. The grouping of 26 Mongolian characters is following the same pattern of English/Latin 26 characters. The OpenType feature is used in Curve-Joint characters only. Demonstration as below: The final 7 characters will be used for textbook teaching purposes. The beautiful punctuation marks even covered the 5-Line (first in below chart), which is used in the primary school teaching purpose. Pupils will like this 5-Line symbol/character. The designer strongly suggest to have his code direction from right to left, following the Arabic approach, if this code gets selected. The Usgiin Solutions, consolidated by Z team pg. 6 Hudum Mongol Option 5: C-235 Code C-235 Code is designed by Mr. Cideltu from Beijing city. Mr. Cideltu was the leading Technical expert for the FangZheng 6.0 and experienced in Publishing House techniques, Font designing, and IME input method creation. The below chart has three layers: Layer 1: These are the decomposition characters similar to Z-56. Layer 2: These are the combined characters similar to FSZ-74. Layer 3: These are the small components needed for textbook education purpose. The Usgiin Solutions, consolidated by Z team pg. 7 Hudum Mongol Option 6: A-59 Code A-59 Code is designed by Mr. AltanUul. The designer is a well-known Font designer in Inner Mongolia since year 2000. This code does not require OpenType support. Need an IME (Input method editor) and that’s all. More information on the next page The Usgiin Solutions, consolidated by Z team pg. 8 The designer provided a sample list, shown below. The Usgiin Solutions, consolidated by Z team pg. 9 Part 2 Todo Mongol Proposals Todo Mongol Option 1: S-115 Code The S code is designed by Mr.Sainbilig from the Dzungar region (Xinjiang). Mr. Sainbilig is a talented Mongolian font creator and Input method creator, and his IME was most popular among Mongolian users from early 2003 to 2012. This code chart does not require OpenType. With Mr. Sainbilig’s sophisticated IME input method, the below code could be loved by the user community. The Usgiin Solutions, consolidated by Z team pg. 10 The designer provided a sample list shown below. The Usgiin Solutions, consolidated by Z team pg. 11 Todo Option 2: M-149 Code M Code is designed by Mr. Minzai from Dzungar region (Xinjiang). Below is Mr. Minzai’s short article (Translation in the next page) 解决托忒文国际编码的唯一出路就是自立门户单独申请托忒文国际编码 作者: 明再 (一) 蒙古文国际编码与托忒文编码蒙古文国际编码是个没有文字字体支持虚拟编码所以无法使用。 蒙古文国际编码是一个通过 FVS MVS 变形的虚拟假像组成的虚像编码。蒙古文是个音标文字这是事 实,但是每个字符都有词首、词中、词末、独体变形字体。蒙古文国际编码根本就没有字符的词首、 词中、词末、独体等实像和字体支持,所以蒙古文国际编码是个虚拟假像组成的虚像编码。形成了无 法使用现象。 (二)托忒文字文字排序错误,蒙古文国际编码只考虑胡杜木文字排序问题,没有考虑托忒文字排序。 (三)搜索问题:现有的蒙古文国际编码是多种文字混合体,是混合编码(胡杜木文字、托忒文字、 满族文字、文锡箔文字聚在一起),所以无法确认是那一种文字字符,搜索托忒文字出来的是胡都木 文字或者满文,我个人建议不能公用一个字符和一个编码,公用一个字符和一个编码给搜索带来不可 挽回的麻烦…… (四)蒙古文国际编码的托忒文古代文字和现代古代无法解决,各方面考虑现在的蒙古文国际编码的 确无 法 使用也 无 法接受。根据托忒文字用户是否接受使用现有的蒙古文国际编码结果还是等于零。 新疆日报蒙文网址: http://mongol.xjdaily.com/ 新疆蒙古语广播网: http://www.xjmglr.com/ 新疆日报蒙文出版和各个出版部门用的是方正、蒙科立、赛音等其它托忒编码。这些网根本没有使用 蒙古文国际编码,对于托忒文用户来说它的存在毫无 意义! (五)现代托忒文、古代托忒文、嘎立格等托忒文必须的问题无法解决。根据以上情况,托忒文必须 自立门户单独申请托忒文国际编码,托忒文字不应该和胡杜木文字、满族文字、文锡箔文字等文字混 在一起,文字搜索,单词排序等问题无法实现,特别是现代托忒文、古代托忒文、嘎立格等托忒文必 须的问题无法解决。所以请国际编领导小组解决托忒文字编码问题为盼。 The Usgiin Solutions, consolidated by Z team pg. 12 The only way to survive is to apply Unicode block independently for Todo Mongolian Script Written by MinZai Translated by Chuck Namujila Firstly, the U1800 Phonetic solution is lack of characters and using virtual artifact control-format characters (FVS MVS), so it is difficult to be widely used. The Mongolian script is indeed Phonetic based, but each phonetic character has its Initial, Medium, Final, and Isolate characters. The Phonetic solution did not cover all Mongolian characters and used artificial virtual features. Thus, the Phonetic solution is challenging to adopt. Secondly, the sorting for Todo Script is wrong. The U1800 Phonetic solution only considered sorting for Hudum Mongolian script and did not cover the sorting feature for the Todo Mongolian script. Thirdly, the current Phonetic Unicode solution mixed many different scripts, including Hudum script, Todo script, Manchu Script, and Xibo scripts. So it is difficult to identify which character belongs to which script. The search result for Todo script always shows either Hudum or Manchu script and rarely shows Todo script. I personly suggest we should split each script into different Unicode blocks and avoid unnecessary confusion. Fourthly, the Phonetic Unicode solution did not fix the problems in Ancient Todo and Modern Todo scripts. In all respects, the current Mongolian international code is indeed unusable and unacceptable. Usage of the Phonetic Unicode Standard by the Todo User community is almost Zero. Xinjiang Daily News Mongolian web: http://mongol.xjdaily.com/ Xinjiang Mongolian Broadcasting web: http://www.xjmglr.com/ The Xinjiang Daily news and all Xinjiang publishing houses are using either FangZheng, MengkhGal, or SainBilig codes for Todo scripts. None of these websites are using the Phonetic Unicode Standard, and the Phonetic Unicode Standard is meaningless for the Todo user community. Lastly, the problems in Modern Todo, ancient Todo, Galig, must be fixed. We concluded that the only way to survive is to apply Unicode block independently for Todo Mongolian Script, and separate our code from Hudum, Manchu, and Xibo scripts. The sorting for Todo must be fixed too. We sincerely hope that the Unicode experts could help fix the problems in the Todo Mongolian script. Thank you. The Usgiin Solutions, consolidated by Z team pg. 13 The below chart fixed the sorting problem and covered all characters of Todo scripts. The Usgiin Solutions, consolidated by Z team pg. 14 Part 3 Manchu Proposals Manchu Proposal in progress. - Pending Unicode to revert back on other proposals.