- ChineseGP - lists.icann.org

[lgr] IDN Root Zone LGR Workshop @ ICANN 58
by Sarmad Hussain March 7, 2017

March 7, 2017

IDN Root Zone LGR Workshop 1. Introduction 2. Root Zone Label Generation Rules v2 (LGR-2) - Integration Panel - 20 mins 3. Community Updates a. Chinese GP Update - 7 mins b. Japanese GP Update - 7 mins c. Korean GP Update - 7 mins d. Thai GP Update - 7 mins 4. Q/A Session details: https://schedule.icann.org/event/9nqJ/icann-gdd-idn-root-zone-lgr-workshop Wednesday March 15, 2017 9:00am - 10:15am Hall B3<https://schedule.icann.org/venue/Hall+B3> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] IDN Program Update @ ICANN 58
by Sarmad Hussain March 7, 2017

March 7, 2017

IDN Program Update 1. IDN Program - Overview and Progress - 15 mins 2. Update by Integration Panel - 10 mins 3. Update on IDN Implementation Guideline - 7 mins 4. Community Updates a. Cyrillic GP Update - 7 mins b. Ethiopic GP Update - 7 mins c. Greek GP Update - 7 mins d. Latin GP Update - 7 mins 5. Q/A Session details: https://schedule.icann.org/event/9nqW/idn-program-update Wednesday March 15, 2017 3:15pm - 4:45pm (local time in Copenhagen) Hall B4.1<https://schedule.icann.org/venue/Hall+B4.1> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

CGP variant mappings updates
by 王伟 March 6, 2017

March 6, 2017

Dear ALL In the CGP, KGP and CDNC joint meeting 22nd to 24th March, both parties reviewed and confirmed the 148 variant groups (which are unacceptable to K) splitting solution. Thus, C and K reached total consensus on repertoire and variant mappings. CGP variant mappings got updated as attached file. Consequently, the allocatable simplified char(s) and traditional char(s) settings of related code points are supposed to be changed. Here I propose new settings for these affected code points as the following table: code char simp trad All variant mappings (201609) code char simp trad All Variant Mappings (201703) 4E81 亁干(5E72) 亁(4E81) 乾(4E7E)亁(4E81)干(5E72)幹(5E79)榦(69A6)漧(6F27) >> 4E81 亁亁(4E81) 亁(4E81) 乾(4E7E)亁(4E81)漧(6F27) 4FDB 俛俯(4FEF) 俛(4FDB) 俛(4FDB)俯(4FEF)頫(982B) 4FDB 俛俛(4FDB) 俛(4FDB) 俛(4FDB)頫(982B) 52F2 勲勋(52CB) 勲(52F2) 勋(52CB)勛(52DB)勲(52F2)勳(52F3) >> 52F2 勲勲(52F2) 勲(52F2) 勲(52F2)勳(52F3) 5C05 尅克(514B) 尅(5C05) 克(514B)剋(524B)尅(5C05) 5C05 尅尅(5C05) 尅(5C05) 剋(524B)尅(5C05) 5CAD 岭岭(5CAD) 岭(5CAD)嶺(5DBA) 岭(5CAD)岺(5CBA)嶺(5DBA) >> 5CAD 岭岭(5CAD) 岭(5CAD) 岭(5CAD)岺(5CBA) 5DBA 嶺岭(5CAD) 嶺(5DBA) 岭(5CAD)岺(5CBA)嶺(5DBA) 5DBA 嶺嶺(5DBA) 嶺(5DBA) 嶺(5DBA) 5E72 干干(5E72) 干(5E72)幹(5E79) 乾(4E7E)亁(4E81)干(5E72)幹(5E79)榦(69A6)漧(6F27) >> 5E72 干干(5E72) 干(5E72) 干(5E72) 5E79 幹干(5E72) 幹(5E79) 乾(4E7E)亁(4E81)干(5E72)幹(5E79)榦(69A6)漧(6F27) 5E79 幹幹(5E79) 幹(5E79) 幹(5E79)榦(69A6) 5FB4 徴征(5F81) 徴(5FB4) 征(5F81)徴(5FB4)徵(5FB5) >> 5FB4 徴徴(5FB4) 徴(5FB4) 徴(5FB4)徵(5FB5) 60E3 惣总(603B) 總(7E3D) 总(603B)惣(60E3)捴(6374)搃(6403)摠(6460)総(7DCF)縂(7E02)總(7E3D) 60E3 惣搃(6403) 摠(6460) 惣(60E3)捴(6374)搃(6403)摠(6460) 62D1 拑钳(94B3) 拑(62D1) 拑(62D1)箝(7B9D)鉗(9257)钳(94B3) >> 62D1 拑拑(62D1) 拑(62D1) 拑(62D1)箝(7B9D) 6374 捴总(603B) 總(7E3D) 总(603B)惣(60E3)捴(6374)搃(6403)摠(6460)総(7DCF)縂(7E02)總(7E3D) 6374 捴搃(6403) 摠(6460) 惣(60E3)捴(6374)搃(6403)摠(6460) 6403 搃总(603B) 總(7E3D) 总(603B)惣(60E3)捴(6374)搃(6403)摠(6460)総(7DCF)縂(7E02)總(7E3D) >> 6403 搃搃(6403) 摠(6460) 惣(60E3)捴(6374)搃(6403)摠(6460) 6597 斗斗(6597) 斗(6597)鬥(9B25) 斗(6597)闘(95D8)鬥(9B25)鬦(9B26)鬪(9B2A)鬬(9B2C)鬭(9B2D) 6597 斗斗(6597) 斗(6597) 斗(6597) 66A6 暦历(5386) 暦(66A6) 历(5386)厤(53A4)暦(66A6)曆(66C6)歴(6B74)歷(6B77) >> 66A6 暦暦(66A6) 暦(66A6) 暦(66A6)曆(66C6) 672F 术术(672F) 術(8853) 朮(672E)术(672F)術(8853) 672F 术术(672F) 术(672F) 朮(672E)术(672F) 69A6 榦干(5E72) 榦(69A6) 乾(4E7E)亁(4E81)干(5E72)幹(5E79)榦(69A6)漧(6F27) >> 69A6 榦幹(5E79) 榦(69A6) 幹(5E79)榦(69A6) 7431 琱雕(96D5) 琱(7431) 彫(5F6B)琱(7431)雕(96D5)鵰(9D70) 7431 琱琱(7431) 琱(7431) 彫(5F6B)琱(7431) 769C 皜皓(7693) 皜(769C) 晧(6667)暠(66A0)皓(7693)皜(769C) >> 769C 皜皜(769C) 皜(769C) 暠(66A0)皜(769C) 7D25 紥扎(624E) 紥(7D25) 剳(5273)劄(5284)扎(624E)札(672D)箚(7B9A)紥(7D25)紮(7D2E) 7D25 紥紥(7D25) 紥(7D25) 紥(7D25)紮(7D2E) 7E4B 繋系(7CFB) 繋(7E4B) 係(4FC2)系(7CFB)繋(7E4B)繫(7E6B) >> 7E4B 繋繋(7E4B) 繋(7E4B) 繋(7E4B)繫(7E6B) 8853 術术(672F) 術(8853) 朮(672E)术(672F)術(8853) 8853 術術(8853) 術(8853) 術(8853) 89D4 觔斤(65A4) 觔(89D4) 斤(65A4)筋(7B4B)觔(89D4) >> 89D4 觔筋(7B4B) 觔(89D4) 筋(7B4B)觔(89D4) 8B8E 讎雠(96E0)仇(4EC7) 讎(8B8E) 仇(4EC7)讎(8B8E)讐(8B90)雠(96E0) 8B8E 讎雠(96E0) 讎(8B8E) 讎(8B8E)讐(8B90)雠(96E0) 95D8 闘斗(6597) 鬥(9B25) 斗(6597)闘(95D8)鬥(9B25)鬦(9B26)鬪(9B2A)鬬(9B2C)鬭(9B2D) >> 95D8 闘鬥(9B25) 鬥(9B25) 鬪(9B2A)闘(95D8)鬥(9B25)鬦(9B26)鬬(9B2C)鬭(9B2D) 982B 頫俯(4FEF) 頫(982B) 俛(4FDB)俯(4FEF)頫(982B) 982B 頫俛(4FDB) 頫(982B) 俛(4FDB)頫(982B) 9B25 鬥斗(6597) 鬥(9B25) 斗(6597)闘(95D8)鬥(9B25)鬦(9B26)鬪(9B2A)鬬(9B2C)鬭(9B2D) >> 9B25 鬥鬥(9B25) 鬥(9B25) 鬪(9B2A)闘(95D8)鬥(9B25)鬦(9B26)鬬(9B2C)鬭(9B2D) 9B26 鬦斗(6597) 鬥(9B25) 斗(6597)闘(95D8)鬥(9B25)鬦(9B26)鬪(9B2A)鬬(9B2C)鬭(9B2D) 9B26 鬦鬥(9B25) 鬥(9B25) 鬪(9B2A)闘(95D8)鬥(9B25)鬦(9B26)鬬(9B2C)鬭(9B2D) 9B2C 鬬斗(6597) 鬥(9B25) 斗(6597)闘(95D8)鬥(9B25)鬦(9B26)鬪(9B2A)鬬(9B2C)鬭(9B2D) >> 9B2C 鬬鬥(9B25) 鬥(9B25) 鬪(9B2A)闘(95D8)鬥(9B25)鬦(9B26)鬬(9B2C)鬭(9B2D) 9B2D 鬭斗(6597) 鬥(9B25) 斗(6597)闘(95D8)鬥(9B25)鬦(9B26)鬪(9B2A)鬬(9B2C)鬭(9B2D) 9B2D 鬭鬥(9B25) 鬥(9B25) 鬪(9B2A)闘(95D8)鬥(9B25)鬦(9B26)鬬(9B2C)鬭(9B2D) 9EB9 麹曲(66F2) 曲(66F2) 曲(66F2)麯(9EAF)麴(9EB4)麹(9EB9) >> 9EB9 麹麹(9EB9) 麹(9EB9) 麴(9EB4)麹(9EB9) Please feel free to give your comments. I will also submit the changes to CDNC experts for their suggestions. Best Regards WANG Wei

1 0

3A5C and 58B5 in C-LGR (2017.02.23.) are not in MSR-1??
by KIM Kyongsok March 6, 2017

March 6, 2017

Dear Messrs Wang and Huang: 1) According to my analysis, two chars, 3A5C and 58B5, in C-LGR (2017.02.23., 19746 chars) are NOT in MSR-1 and therefore must be removed from C-LGR. Am I missing something ? 2) They are also included C variant groups: 3 1 [X 3A5C 㩜] (X 3A5C 㩜) (X 63FD 揽) (O 652C 攬) 8 1 [X 58B5 墵] (X 575B 坛) (X 57EE 埮) (X 58B0 墰) (X 58B5 墵) (O 58C7 壇) (X 58DC >壜) (X 7F48 罈) (X 7F4E 罎) Any comments will be appreciated. Thanks in advance. -- 김 경석 KIM, Kyongsok

2 3

Difference between version201607 and version 201701
by 王伟 Feb. 23, 2017

Feb. 23, 2017

Dear Prof Kim The attached files are two versions of CGP repertoire. CGP delete the following chars from the last version 49D1 䧑,8F0C 輌,7C4F 籏,6AAA 檪,6C17 気,6E13 渓,6E7A 湺,5BFE 対,5C02 専,5CC0 峀,4A12 䨒,5D5C 嵜,5E3F 帿,5F10 弐,4CB3 䲳,9197 醗,4D08 䴈,91B8 醸,4E55 乕,9665 陥,974D 靍,7114 焔,713C 焼,7155 煕,72A0 犠,7363 獣,60A9 悩,874B 蝋,877F 蝿,7573 畳,75E9 痩,633F 挿,63BB 掻,7807 砇,783F 砿,5271 剱,663F 昿,5368 卨,66FD 曽,4137 䄷,9C04 鰄,9C76 鱶,576E 坮,8A33 訳,5817 堗,5841 塁,8AAD 読,58CC 壌,9E78 鹸,8B72 譲,7A4F 穏,7A63 穣,7AD7 竗,48B5 䢵,48C5 䣅,48D3 䣓, and add two chars into the current version 3A5C 㩜,58B5 墵, Just for your reference. WANG Wei

1 0

CGP & KGP & CDNC joint meeting - UTC 1am-3am - 23 February 2017
by Sarmad Hussain Feb. 22, 2017

Feb. 22, 2017

Link to Adobe Connect: https://participate.icann.org/idn/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=1064158692&num=1-719-… Participant Passcode: 1064158692 ?

1 0

CGP & KGP & CDNC joint meeting
by 王伟 Feb. 22, 2017

Feb. 22, 2017

Dear all During the IETF meeting in Seoul, November 2016, CGP and KGP reduced the number of disagreed variant groups to 2. And in the last week of 2016, both parties finally fixed the left 2 groups. It means all 258 disagreed variant groups proposed by KGP has been solved. Therefore, CGP and KGP will hold a joint meeting on 9am (UTC+8) 23th Feb, Beijing, to double check the coordination achievement and draw a formal conclusion. Most CDNC members will also present and witness. For those members not in Beijing, please join the meeting remotely. @Sarmad，could you please help provide the adobe connection for us. Best Regards WANG Wei

2 1

答复: CGP Proposal Update
by 王伟 Jan. 17, 2017

Jan. 17, 2017

Thanks QI Chao for generating XML file and correcting errors in appendix H. That attached proposal, repertoire and variant mapping files will be sent to IP for further coordination. 发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2017年1月16日 22:28 收件人: ChineseGP(a)icann.org; hotta(a)jprs.co.jp; 김경석 (gimgs0(a)gmail.com) <gimgs0(a)gmail.com> 抄送: Sarmad Hussain (sarmad.hussain(a)icann.org) <sarmad.hussain(a)icann.org> 主题: CGP Proposal Update Dear All CGP noticed that in the latest feedback document, IP urged CGP to take the following actions: 1. Reduce the size of repertoire based on modern usage analysis of each code point 2. Reduce the number of allocatable labels 3. Explain the inconsistency between CGP and dotAsia IDN Table Correspondingly, CGP made the following updates to the proposal draft: 1. Section 3.3 explains the attempt that CGP made to reduce the repertoire, and the reason why CGP suggested to keep the current size. 2. Section 4.7 introduces the coordination result between C and K, 146 variant mappings in last version are decoupled, reducing the number of allocable labels mildly. CGP acknowledges that it is far from the goal that IP expected, further work still needs to be done. 3. Section 4.5 illustrates the inconsistency between CGP and dotAsia. According to the discussion with Edmon CHUNG, dotAsia would adjust its SLD repertoire and variant mappings to comply with CGP LGR rules once it was finalized. 4. Proofread the translation of通用规范汉字表, from “Normalized Hanzi List for Common Use (NHCU)” to “Table of General Standard Chinese Characters (TGSCC)” For the next step, CGP would carry out the following work: 1. Hold a vote on the issue of repertoire size reduction. CGP members might take different positions on this issue, the members represent IDN registries who already applied CDNC IDN tables and rules might be more inclined to keep the consistency between CDNC table and CGP repertoire. 2. Work together with JGP on the issue of allocatable labels overproduction CGP and JGP have the similar concern on this issue, and proposed a similar conception named “multiple LGR execution” or “complement process of root LGR”. We will keep working closely to find a way which keep <http://cn.bing.com/dict/search?q=keep&FORM=BDVSP6&mkt=zh-cn> allocatable labels at <http://cn.bing.com/dict/search?q=at&FORM=BDVSP6&mkt=zh-cn> a <http://cn.bing.com/dict/search?q=a&FORM=BDVSP6&mkt=zh-cn> reasonable <http://cn.bing.com/dict/search?q=reasonable&FORM=BDVSP6&mkt=zh-cn> number <http://cn.bing.com/dict/search?q=amount&FORM=BDVSP6&mkt=zh-cn> , <http://cn.bing.com/dict/search?q=.&FORM=BDVSP6&mkt=zh-cn> and could be accepted by IP as well. @QI Chao, could you please help transfer the attached appendix H into XML format, thank you. Regards WANG Wei

1 0

CGP Proposal Update
by 王伟 Jan. 16, 2017

Jan. 16, 2017

Dear All CGP noticed that in the latest feedback document, IP urged CGP to take the following actions: 1. Reduce the size of repertoire based on modern usage analysis of each code point 2. Reduce the number of allocatable labels 3. Explain the inconsistency between CGP and dotAsia IDN Table Correspondingly, CGP made the following updates to the proposal draft: 1. Section 3.3 explains the attempt that CGP made to reduce the repertoire, and the reason why CGP suggested to keep the current size. 2. Section 4.7 introduces the coordination result between C and K, 146 variant mappings in last version are decoupled, reducing the number of allocable labels mildly. CGP acknowledges that it is far from the goal that IP expected, further work still needs to be done. 3. Section 4.5 illustrates the inconsistency between CGP and dotAsia. According to the discussion with Edmon CHUNG, dotAsia would adjust its SLD repertoire and variant mappings to comply with CGP LGR rules once it was finalized. 4. Proofread the translation of通用规范汉字表, from “Normalized Hanzi List for Common Use (NHCU)” to “Table of General Standard Chinese Characters (TGSCC)” For the next step, CGP would carry out the following work: 1. Hold a vote on the issue of repertoire size reduction. CGP members might take different positions on this issue, the members represent IDN registries who already applied CDNC IDN tables and rules might be more inclined to keep the consistency between CDNC table and CGP repertoire. 2. Work together with JGP on the issue of allocatable labels overproduction CGP and JGP have the similar concern on this issue, and proposed a similar conception named “multiple LGR execution” or “complement process of root LGR”. We will keep working closely to find a way which keep <http://cn.bing.com/dict/search?q=keep&FORM=BDVSP6&mkt=zh-cn> allocatable labels at <http://cn.bing.com/dict/search?q=at&FORM=BDVSP6&mkt=zh-cn> a <http://cn.bing.com/dict/search?q=a&FORM=BDVSP6&mkt=zh-cn> reasonable <http://cn.bing.com/dict/search?q=reasonable&FORM=BDVSP6&mkt=zh-cn> number <http://cn.bing.com/dict/search?q=amount&FORM=BDVSP6&mkt=zh-cn> , <http://cn.bing.com/dict/search?q=.&FORM=BDVSP6&mkt=zh-cn> and could be accepted by IP as well. @QI Chao, could you please help transfer the attached appendix H into XML format, thank you. Regards WANG Wei

1 0

[lgr] FW: ICANN News Alert -- Proposal for Thai Script Root Zone‬ Label Generation Rules (LGR)
by Sarmad Hussain Dec. 16, 2016

Dec. 16, 2016

Dear All, Proposal for Thai script Root Zone LGR is now released for public comment. See https://www.icann.org/public-comments/thai-lgr-2016-12-15-en. Regards, Sarmad <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DgMFaQ…>[icann.org]News Alerthttps://www.icann.org/news/announcement-2016-12-15-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> _____Proposal for Thai Script Root Zone Label Generation Rules (LGR)15 December 2016Open Date:15 December 2016Close Date:29 January 2017Originating Organization:Global Domains DivisionCategories/Tags:Top-Level DomainsBrief Overview:The Thai script community has formed the Thai script Generation Panel (GP),which in turn has developed a Propo sal for the Thai Script Root Zone LabelGeneration Rules (Proposal[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> and Proposal Documentation[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 1.7 MB]). As per the LGR Procedure[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste… Jms7xcl4 I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=Cs4RjGPvbZ9mjE64rzzRp9dWR-RO9tBZHaFzJryyY8c&s=oD1bmOpM1JZJ1--PbgD1vNq3XYSsq9EfBgXUCXZwtCw&e=> [PDF, 772 KB], this proposal is being posted for public comments toallow those who have not participated in the Thai script GP to make theirviews known to the GP. Based on the feedback, the Thai script GP will finalizethe proposal for submission for integration into the Label Generation Rulesfor the Root Zone.Link:https://www.icann.org/public-comments/thai-lgr-2016-12-15-en[ican…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0