Characters likely to cause offence
Dear Yoneya-san, I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature. I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples. It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm. As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
I guess both of 卍and 卐 (swastika, स्वस्तिक) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi. What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first. -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA 发送时间: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主题: Re: [ChineseGP] Characters likely to cause offence Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm. As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Agree with Wangwei. Edmon
-----Original Message----- From: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] On Behalf Of ?? Sent: Tuesday, May 12, 2015 10:35 AM To: 'Yoshiro YONEYA'; 'Dillon, Chris' Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: [ChineseGP] 答复: Characters likely to cause offence
I guess both of 卍and 卐 (swastika, स्वस्तिक) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 Yoshiro YONEYA 发送时间: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主题: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
I agree that GPs had better not try to touch on this kind of cross-cultural issues. I agree to leave this issue to IP, but I suspect IP can solve that. If this kind of judgement (i.e., not a script/language-based judgement, but a judgement considering other cultures) is needed, it is likely beyond the ability of RootLGR project. Even IP cannot solve such issues, I believe. In my understanding, such kind of judgement should be done in the evaluation phase of a TLD application with possible objection mechanism. We should not try to make RootLGR solve all the potential issues we can imagine. Hiro On Tue, 12 May 2015 10:40:21 +0800 "Edmon Chung" <edmon@registry.asia> wrote:
Agree with Wangwei. Edmon
-----Original Message----- From: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] On Behalf Of ?? Sent: Tuesday, May 12, 2015 10:35 AM To: 'Yoshiro YONEYA'; 'Dillon, Chris' Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear Sarmad, This issue may depend on the scope of the RootLGR project mandate. If I may, I'd like to ask the following question to ICANN. Question here : Providing, a character in Han script means 'lucky' and is sometimes used in strings in CJK area. The character has visual similarity to a symbol that could be abused by people outside CJK area. In this case, should such character be removed from CJK repertoire? Who will decide the removal of the character, and how? Is such removal decision within the scope of RootLGR project? (not within the scope of gTLD application evaluation panels along with public objection appeals?) Regards, Hiro On Tue, 12 May 2015 12:19:11 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
I agree that GPs had better not try to touch on this kind of cross-cultural issues.
I agree to leave this issue to IP, but I suspect IP can solve that.
If this kind of judgement (i.e., not a script/language-based judgement, but a judgement considering other cultures) is needed, it is likely beyond the ability of RootLGR project. Even IP cannot solve such issues, I believe.
In my understanding, such kind of judgement should be done in the evaluation phase of a TLD application with possible objection mechanism. We should not try to make RootLGR solve all the potential issues we can imagine.
Hiro
On Tue, 12 May 2015 10:40:21 +0800 "Edmon Chung" <edmon@registry.asia> wrote:
Agree with Wangwei. Edmon
-----Original Message----- From: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] On Behalf Of ?? Sent: Tuesday, May 12, 2015 10:35 AM To: 'Yoshiro YONEYA'; 'Dillon, Chris' Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear Hotta-san, Thank you for raising the question to ICANN. I will have to check internally from multiple quarters and will get back to you as soon as I have synthesized the information. If you have a timeline which needs to be followed to get the response, please do advise me. Regards, Sarmad -----Original Message----- From: hotta@jprs.co.jp [mailto:hotta@jprs.co.jp] Sent: Wednesday, May 13, 2015 6:16 PM To: Sarmad Hussain Cc: Edmon Chung; ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [ChineseGP] 答?: Characters likely to cause offence Dear Sarmad, This issue may depend on the scope of the RootLGR project mandate. If I may, I'd like to ask the following question to ICANN. Question here : Providing, a character in Han script means 'lucky' and is sometimes used in strings in CJK area. The character has visual similarity to a symbol that could be abused by people outside CJK area. In this case, should such character be removed from CJK repertoire? Who will decide the removal of the character, and how? Is such removal decision within the scope of RootLGR project? (not within the scope of gTLD application evaluation panels along with public objection appeals?) Regards, Hiro On Tue, 12 May 2015 12:19:11 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
I agree that GPs had better not try to touch on this kind of cross-cultural issues.
I agree to leave this issue to IP, but I suspect IP can solve that.
If this kind of judgement (i.e., not a script/language-based judgement, but a judgement considering other cultures) is needed, it is likely beyond the ability of RootLGR project. Even IP cannot solve such issues, I believe.
In my understanding, such kind of judgement should be done in the evaluation phase of a TLD application with possible objection mechanism. We should not try to make RootLGR solve all the potential issues we can imagine.
Hiro
On Tue, 12 May 2015 10:40:21 +0800 "Edmon Chung" <edmon@registry.asia> wrote:
Agree with Wangwei. Edmon
-----Original Message----- From: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] On Behalf Of ?? Sent: Tuesday, May 12, 2015 10:35 AM To: 'Yoshiro YONEYA'; 'Dillon, Chris' Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear Sarmad. Thank you for your quick response. If the response comes by this Friday, it's very helpful because we can share the situation in the meeting and discuss about how we should deal with it. Next timing may be well before Buenos Aires, albeit sooner is better. Thanks in advance. Regards, Hiro On Wed, 13 May 2015 14:20:54 +0000 Sarmad Hussain <sarmad.hussain@icann.org> wrote:
Dear Hotta-san,
Thank you for raising the question to ICANN. I will have to check internally from multiple quarters and will get back to you as soon as I have synthesized the information. If you have a timeline which needs to be followed to get the response, please do advise me.
Regards, Sarmad
-----Original Message----- From: hotta@jprs.co.jp [mailto:hotta@jprs.co.jp] Sent: Wednesday, May 13, 2015 6:16 PM To: Sarmad Hussain Cc: Edmon Chung; ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [ChineseGP] 答?: Characters likely to cause offence
Dear Sarmad,
This issue may depend on the scope of the RootLGR project mandate. If I may, I'd like to ask the following question to ICANN.
Question here : Providing, a character in Han script means 'lucky' and is sometimes used in strings in CJK area. The character has visual similarity to a symbol that could be abused by people outside CJK area. In this case, should such character be removed from CJK repertoire? Who will decide the removal of the character, and how? Is such removal decision within the scope of RootLGR project? (not within the scope of gTLD application evaluation panels along with public objection appeals?)
Regards, Hiro
On Tue, 12 May 2015 12:19:11 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
I agree that GPs had better not try to touch on this kind of cross-cultural issues.
I agree to leave this issue to IP, but I suspect IP can solve that.
If this kind of judgement (i.e., not a script/language-based judgement, but a judgement considering other cultures) is needed, it is likely beyond the ability of RootLGR project. Even IP cannot solve such issues, I believe.
In my understanding, such kind of judgement should be done in the evaluation phase of a TLD application with possible objection mechanism. We should not try to make RootLGR solve all the potential issues we can imagine.
Hiro
On Tue, 12 May 2015 10:40:21 +0800 "Edmon Chung" <edmon@registry.asia> wrote:
Agree with Wangwei. Edmon
-----Original Message----- From: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] On Behalf Of ?? Sent: Tuesday, May 12, 2015 10:35 AM To: 'Yoshiro YONEYA'; 'Dillon, Chris' Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear Hotta-san, Thank you for the query. Based on internal discussions, kindly find the response below: As per the "Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels" <http://www.icann.org/en/resources/idn/variant-tlds/draft-lgr-procedure-20ma r13-en.pdf>, the decision of which Unicode code points to include from the MSR in their respective proposals for the Root Zone LGR is up to the Chinese, Japanese and Korean Generation Panels. They may decide not to include a character which “has visual similarity to a symbol that could be abused by people outside CJK area”. However, when a code point that has such potential issues is included in an LGR proposal, ICANN recommends that the relevant Generation Panel(s) point this out in their proposal, as it is released for public comment. The relevant Generation Panel(s) will decide whether to finally include such a code point based on the review of the public comments received. Regards, Sarmad -----Original Message----- From: hotta@jprs.co.jp [mailto:hotta@jprs.co.jp] Sent: Wednesday, May 13, 2015 2:16 PM To: Sarmad Hussain <sarmad.hussain@icann.org> Cc: Edmon Chung <edmon@registry.asia>; ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [ChineseGP] 答?: Characters likely to cause offence Dear Sarmad, This issue may depend on the scope of the RootLGR project mandate. If I may, I'd like to ask the following question to ICANN. Question here : Providing, a character in Han script means 'lucky' and is sometimes used in strings in CJK area. The character has visual similarity to a symbol that could be abused by people outside CJK area. In this case, should such character be removed from CJK repertoire? Who will decide the removal of the character, and how? Is such removal decision within the scope of RootLGR project? (not within the scope of gTLD application evaluation panels along with public objection appeals?) Regards, Hiro On Tue, 12 May 2015 12:19:11 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
I agree that GPs had better not try to touch on this kind of cross-cultural issues.
I agree to leave this issue to IP, but I suspect IP can solve that.
If this kind of judgement (i.e., not a script/language-based judgement, but a judgement considering other cultures) is needed, it is likely beyond the ability of RootLGR project. Even IP cannot solve such issues, I believe.
In my understanding, such kind of judgement should be done in the evaluation phase of a TLD application with possible objection mechanism. We should not try to make RootLGR solve all the potential issues we can imagine.
Hiro
On Tue, 12 May 2015 10:40:21 +0800 "Edmon Chung" <edmon@registry.asia> wrote:
Agree with Wangwei. Edmon
-----Original Message----- From: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] On Behalf Of ?? Sent: Tuesday, May 12, 2015 10:35 AM To: 'Yoshiro YONEYA'; 'Dillon, Chris' Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Thank you for your response, Sarmad. I think I understand. Hiro On Sun, 18 Oct 2015 07:57:43 +0000 Sarmad Hussain <sarmad.hussain@icann.org> wrote:
Dear Hotta-san,
Thank you for the query. Based on internal discussions, kindly find the response below:
As per the "Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels" <http://www.icann.org/en/resources/idn/variant-tlds/draft-lgr-procedure-20ma r13-en.pdf>, the decision of which Unicode code points to include from the MSR in their respective proposals for the Root Zone LGR is up to the Chinese, Japanese and Korean Generation Panels. They may decide not to include a character which “has visual similarity to a symbol that could be abused by people outside CJK area”. However, when a code point that has such potential issues is included in an LGR proposal, ICANN recommends that the relevant Generation Panel(s) point this out in their proposal, as it is released for public comment. The relevant Generation Panel(s) will decide whether to finally include such a code point based on the review of the public comments received.
Regards, Sarmad
-----Original Message----- From: hotta@jprs.co.jp [mailto:hotta@jprs.co.jp] Sent: Wednesday, May 13, 2015 2:16 PM To: Sarmad Hussain <sarmad.hussain@icann.org> Cc: Edmon Chung <edmon@registry.asia>; ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [ChineseGP] 答?: Characters likely to cause offence
Dear Sarmad,
This issue may depend on the scope of the RootLGR project mandate. If I may, I'd like to ask the following question to ICANN.
Question here : Providing, a character in Han script means 'lucky' and is sometimes used in strings in CJK area. The character has visual similarity to a symbol that could be abused by people outside CJK area. In this case, should such character be removed from CJK repertoire? Who will decide the removal of the character, and how? Is such removal decision within the scope of RootLGR project? (not within the scope of gTLD application evaluation panels along with public objection appeals?)
Regards, Hiro
On Tue, 12 May 2015 12:19:11 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
I agree that GPs had better not try to touch on this kind of cross-cultural issues.
I agree to leave this issue to IP, but I suspect IP can solve that.
If this kind of judgement (i.e., not a script/language-based judgement, but a judgement considering other cultures) is needed, it is likely beyond the ability of RootLGR project. Even IP cannot solve such issues, I believe.
In my understanding, such kind of judgement should be done in the evaluation phase of a TLD application with possible objection mechanism. We should not try to make RootLGR solve all the potential issues we can imagine.
Hiro
On Tue, 12 May 2015 10:40:21 +0800 "Edmon Chung" <edmon@registry.asia> wrote:
Agree with Wangwei. Edmon
-----Original Message----- From: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] On Behalf Of ?? Sent: Tuesday, May 12, 2015 10:35 AM To: 'Yoshiro YONEYA'; 'Dillon, Chris' Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Besides卍and 卐, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards, Zhang -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王伟 发送时间: 2015年5月12日 10:35 收件人: 'Yoshiro YONEYA'; 'Dillon, Chris' 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 答复: Characters likely to cause offence I guess both of 卍and 卐 (swastika, स्वस्तिक) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi. What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first. -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA 发送时间: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主题: Re: [ChineseGP] Characters likely to cause offence Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm. As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Hello All, the discussion on 卍 and 卐 must abide by some wider principle. In this case, the principle of historic precedence should be respected: the Sanskrit svastika, which can be traced back at least to the Neolithic, is unquestionably more ancient than any more recent use of this script, or its tragic misuse by the Nazi régime in the first half of the 20th century. I would therefore urge that we keep the historic Sanskrit script present in the list, insofar as it has been adopted in Chinese, Japanese or Korean usage, for instance in religious or other texts. To be perfectly clear, by taking this position of respecting the original Sanskrit script, I am in no way condoning the despicable Nazi régime that later employed this as its trademark. Best regards, Jean-Jacques. ----- Mail original ----- De: "Joe Zhang" <joezhang43@hotmail.com> À: "王伟" <wangwei@cnic.cn>, "Yoshiro YONEYA" <yoshiro.yoneya@jprs.co.jp>, "Chris' 'Dillon" <c.dillon@ucl.ac.uk> Cc: ChineseGP@icann.org, KoreanGP@icann.org, JapaneseGP@icann.org Envoyé: Mercredi 13 Mai 2015 14:18:33 Objet: [ChineseGP] 答复: 答复: Characters likely to cause offence Besides卍and 卐, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards, Zhang -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王伟 发送时间: 2015年5月12日 10:35 收件人: 'Yoshiro YONEYA'; 'Dillon, Chris' 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 答复: Characters likely to cause offence I guess both of 卍and 卐 (swastika, स्वस्तिक) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi. What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first. -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA 发送时间: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主题: Re: [ChineseGP] Characters likely to cause offence Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm. As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
I may agree to that in principle. But here I just want to say who should think about that and who is responsible for that? If it's within GP's mandate, GP cannot afford that. If it's within IP's mandate, further question may be 'who can decide some specific characters should not listed in MSR' ? Hiro On Thu, 14 May 2015 11:19:40 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello All,
the discussion on 卍 and ? must abide by some wider principle. In this case, the principle of historic precedence should be respected: the Sanskrit svastika, which can be traced back at least to the Neolithic, is unquestionably more ancient than any more recent use of this script, or its tragic misuse by the Nazi regime in the first half of the 20th century.
I would therefore urge that we keep the historic Sanskrit script present in the list, insofar as it has been adopted in Chinese, Japanese or Korean usage, for instance in religious or other texts.
To be perfectly clear, by taking this position of respecting the original Sanskrit script, I am in no way condoning the despicable Nazi regime that later employed this as its trademark.
Best regards, Jean-Jacques.
----- Mail original ----- De: "Joe Zhang" <joezhang43@hotmail.com> A: "王?" <wangwei@cnic.cn>, "Yoshiro YONEYA" <yoshiro.yoneya@jprs.co.jp>, "Chris' 'Dillon" <c.dillon@ucl.ac.uk> Cc: ChineseGP@icann.org, KoreanGP@icann.org, JapaneseGP@icann.org Envoye: Mercredi 13 Mai 2015 14:18:33 Objet: [ChineseGP] 答?: 答?: Characters likely to cause offence
Besides卍and ?, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards,
Zhang
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王? ?送??: 2015年5月12日 10:35 收件人: 'Yoshiro YONEYA'; 'Dillon, Chris' 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主?: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Hello Hiro-san, thank you for your response. It might be worth considering an alternative: include such scripts, unless there is a documented opposition, based on historical, linguistic or technical factors. In practical terms, it may be useful to draw up a list of characters which present similar problems. This list would be sent out to our membership lists (all C, J, K) for comment within a one-month period. Those characters meeting no opposition could then be included; those presenting a problem would then be either submitted to further examination, or rejected, and the rationale for either decision would be documented. Also, it may be useful to provide a mechanism for periodic review. Best regards, Jean-Jacques. ----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> À: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, "王?" <wangwei@cnic.cn>, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoyé: Jeudi 14 Mai 2015 18:38:31 Objet: Re: [Japanesegp] [ChineseGP] 答?: 答?: Characters likely to cause offence I may agree to that in principle. But here I just want to say who should think about that and who is responsible for that? If it's within GP's mandate, GP cannot afford that. If it's within IP's mandate, further question may be 'who can decide some specific characters should not listed in MSR' ? Hiro On Thu, 14 May 2015 11:19:40 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello All,
the discussion on 卍 and ? must abide by some wider principle. In this case, the principle of historic precedence should be respected: the Sanskrit svastika, which can be traced back at least to the Neolithic, is unquestionably more ancient than any more recent use of this script, or its tragic misuse by the Nazi regime in the first half of the 20th century.
I would therefore urge that we keep the historic Sanskrit script present in the list, insofar as it has been adopted in Chinese, Japanese or Korean usage, for instance in religious or other texts.
To be perfectly clear, by taking this position of respecting the original Sanskrit script, I am in no way condoning the despicable Nazi regime that later employed this as its trademark.
Best regards, Jean-Jacques.
----- Mail original ----- De: "Joe Zhang" <joezhang43@hotmail.com> A: "王?" <wangwei@cnic.cn>, "Yoshiro YONEYA" <yoshiro.yoneya@jprs.co.jp>, "Chris' 'Dillon" <c.dillon@ucl.ac.uk> Cc: ChineseGP@icann.org, KoreanGP@icann.org, JapaneseGP@icann.org Envoye: Mercredi 13 Mai 2015 14:18:33 Objet: [ChineseGP] 答?: 答?: Characters likely to cause offence
Besides卍and ?, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards,
Zhang
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王? ?送??: 2015年5月12日 10:35 收件人: 'Yoshiro YONEYA'; 'Dillon, Chris' 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主?: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Hello, Jean-Jacques. I personally don't object the removal of characters that are very offensive to some others. I think we can follow the procedure if such procedure is globally established and employed by ICANN. I am asking ICANN whether such removal should be solved by RootLGR project (i.e., each GP or IP) or not. Regards, Hiro On Fri, 15 May 2015 10:27:12 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello Hiro-san,
thank you for your response. It might be worth considering an alternative: include such scripts, unless there is a documented opposition, based on historical, linguistic or technical factors.
In practical terms, it may be useful to draw up a list of characters which present similar problems. This list would be sent out to our membership lists (all C, J, K) for comment within a one-month period. Those characters meeting no opposition could then be included; those presenting a problem would then be either submitted to further examination, or rejected, and the rationale for either decision would be documented. Also, it may be useful to provide a mechanism for periodic review.
Best regards, Jean-Jacques.
----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> A: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, "王?" <wangwei@cnic.cn>, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoye: Jeudi 14 Mai 2015 18:38:31 Objet: Re: [Japanesegp] [ChineseGP] 答?: 答?: Characters likely to cause offence
I may agree to that in principle.
But here I just want to say who should think about that and who is responsible for that?
If it's within GP's mandate, GP cannot afford that. If it's within IP's mandate, further question may be 'who can decide some specific characters should not listed in MSR' ?
Hiro
On Thu, 14 May 2015 11:19:40 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello All,
the discussion on 卍 and ? must abide by some wider principle. In this case, the principle of historic precedence should be respected: the Sanskrit svastika, which can be traced back at least to the Neolithic, is unquestionably more ancient than any more recent use of this script, or its tragic misuse by the Nazi regime in the first half of the 20th century.
I would therefore urge that we keep the historic Sanskrit script present in the list, insofar as it has been adopted in Chinese, Japanese or Korean usage, for instance in religious or other texts.
To be perfectly clear, by taking this position of respecting the original Sanskrit script, I am in no way condoning the despicable Nazi regime that later employed this as its trademark.
Best regards, Jean-Jacques.
----- Mail original ----- De: "Joe Zhang" <joezhang43@hotmail.com> A: "王?" <wangwei@cnic.cn>, "Yoshiro YONEYA" <yoshiro.yoneya@jprs.co.jp>, "Chris' 'Dillon" <c.dillon@ucl.ac.uk> Cc: ChineseGP@icann.org, KoreanGP@icann.org, JapaneseGP@icann.org Envoye: Mercredi 13 Mai 2015 14:18:33 Objet: [ChineseGP] 答?: 答?: Characters likely to cause offence
Besides卍and ?, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards,
Zhang
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王? ?送??: 2015年5月12日 10:35 收件人: 'Yoshiro YONEYA'; 'Dillon, Chris' 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主?: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Hiro-san, there seems to be a misunderstanding: - you are suggesting "removal of characters", - but in fact I made the point that we should keep the 2 characters under discussion, precisely because they have a long documented history, way before they were misused, for about 2 decades, by the Nazi régime. A further reason for keeping these 2 characters is that, in spite of their misuse between roughly 1930 to 1945 in Europe, their use as cultural and religious references has been continuous for more than 2000 years, mainly in Asia. This continues to be true today. Finally, I would like to make clear that my suggestion of a mechanism for removal applies to characters which may be considered offensive TODAY, but in my mind this does not apply to the 2 characters discussed in the thread. Best regards, Jean-Jacques. ----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> À: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, wangwei@cnic.cn, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoyé: Lundi 18 Mai 2015 17:33:44 Objet: Re: [Japanesegp] [ChineseGP] 答?: 答?: Characters likely to cause offence Hello, Jean-Jacques. I personally don't object the removal of characters that are very offensive to some others. I think we can follow the procedure if such procedure is globally established and employed by ICANN. I am asking ICANN whether such removal should be solved by RootLGR project (i.e., each GP or IP) or not. Regards, Hiro On Fri, 15 May 2015 10:27:12 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello Hiro-san,
thank you for your response. It might be worth considering an alternative: include such scripts, unless there is a documented opposition, based on historical, linguistic or technical factors.
In practical terms, it may be useful to draw up a list of characters which present similar problems. This list would be sent out to our membership lists (all C, J, K) for comment within a one-month period. Those characters meeting no opposition could then be included; those presenting a problem would then be either submitted to further examination, or rejected, and the rationale for either decision would be documented. Also, it may be useful to provide a mechanism for periodic review.
Best regards, Jean-Jacques.
----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> A: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, "王?" <wangwei@cnic.cn>, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoye: Jeudi 14 Mai 2015 18:38:31 Objet: Re: [Japanesegp] [ChineseGP] 答?: 答?: Characters likely to cause offence
I may agree to that in principle.
But here I just want to say who should think about that and who is responsible for that?
If it's within GP's mandate, GP cannot afford that. If it's within IP's mandate, further question may be 'who can decide some specific characters should not listed in MSR' ?
Hiro
On Thu, 14 May 2015 11:19:40 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello All,
the discussion on 卍 and ? must abide by some wider principle. In this case, the principle of historic precedence should be respected: the Sanskrit svastika, which can be traced back at least to the Neolithic, is unquestionably more ancient than any more recent use of this script, or its tragic misuse by the Nazi regime in the first half of the 20th century.
I would therefore urge that we keep the historic Sanskrit script present in the list, insofar as it has been adopted in Chinese, Japanese or Korean usage, for instance in religious or other texts.
To be perfectly clear, by taking this position of respecting the original Sanskrit script, I am in no way condoning the despicable Nazi regime that later employed this as its trademark.
Best regards, Jean-Jacques.
----- Mail original ----- De: "Joe Zhang" <joezhang43@hotmail.com> A: "王?" <wangwei@cnic.cn>, "Yoshiro YONEYA" <yoshiro.yoneya@jprs.co.jp>, "Chris' 'Dillon" <c.dillon@ucl.ac.uk> Cc: ChineseGP@icann.org, KoreanGP@icann.org, JapaneseGP@icann.org Envoye: Mercredi 13 Mai 2015 14:18:33 Objet: [ChineseGP] 答?: 答?: Characters likely to cause offence
Besides卍and ?, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards,
Zhang
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王? ?送??: 2015年5月12日 10:35 收件人: 'Yoshiro YONEYA'; 'Dillon, Chris' 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主?: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Thanks for your clear explanation, Jean-Jacques. I agree with your discussion. I think we are not thinking in a different way. I just wanted to say that "if someone can decide, with reasonable reason, what characters should be removed from the repertoire, I will not object that". I believe GPs should not be responsible for such decision. As you explained, those two characters have a deep innocent history and CJK folks will think such characters are important good characters for their lives. However, I think it will not be CGP/JGP/KGP's responsiblility to prove that. Regards, Hiro On Mon, 18 May 2015 18:01:02 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hiro-san,
there seems to be a misunderstanding: - you are suggesting "removal of characters", - but in fact I made the point that we should keep the 2 characters under discussion, precisely because they have a long documented history, way before they were misused, for about 2 decades, by the Nazi regime.
A further reason for keeping these 2 characters is that, in spite of their misuse between roughly 1930 to 1945 in Europe, their use as cultural and religious references has been continuous for more than 2000 years, mainly in Asia. This continues to be true today.
Finally, I would like to make clear that my suggestion of a mechanism for removal applies to characters which may be considered offensive TODAY, but in my mind this does not apply to the 2 characters discussed in the thread.
Best regards, Jean-Jacques.
----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> A: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, wangwei@cnic.cn, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoye: Lundi 18 Mai 2015 17:33:44 Objet: Re: [Japanesegp] [ChineseGP] 答?: 答?: Characters likely to cause offence
Hello, Jean-Jacques.
I personally don't object the removal of characters that are very offensive to some others. I think we can follow the procedure if such procedure is globally established and employed by ICANN.
I am asking ICANN whether such removal should be solved by RootLGR project (i.e., each GP or IP) or not.
Regards, Hiro
On Fri, 15 May 2015 10:27:12 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello Hiro-san,
thank you for your response. It might be worth considering an alternative: include such scripts, unless there is a documented opposition, based on historical, linguistic or technical factors.
In practical terms, it may be useful to draw up a list of characters which present similar problems. This list would be sent out to our membership lists (all C, J, K) for comment within a one-month period. Those characters meeting no opposition could then be included; those presenting a problem would then be either submitted to further examination, or rejected, and the rationale for either decision would be documented. Also, it may be useful to provide a mechanism for periodic review.
Best regards, Jean-Jacques.
----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> A: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, "王?" <wangwei@cnic.cn>, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoye: Jeudi 14 Mai 2015 18:38:31 Objet: Re: [Japanesegp] [ChineseGP] 答?: 答?: Characters likely to cause offence
I may agree to that in principle.
But here I just want to say who should think about that and who is responsible for that?
If it's within GP's mandate, GP cannot afford that. If it's within IP's mandate, further question may be 'who can decide some specific characters should not listed in MSR' ?
Hiro
On Thu, 14 May 2015 11:19:40 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello All,
the discussion on 卍 and ? must abide by some wider principle. In this case, the principle of historic precedence should be respected: the Sanskrit svastika, which can be traced back at least to the Neolithic, is unquestionably more ancient than any more recent use of this script, or its tragic misuse by the Nazi regime in the first half of the 20th century.
I would therefore urge that we keep the historic Sanskrit script present in the list, insofar as it has been adopted in Chinese, Japanese or Korean usage, for instance in religious or other texts.
To be perfectly clear, by taking this position of respecting the original Sanskrit script, I am in no way condoning the despicable Nazi regime that later employed this as its trademark.
Best regards, Jean-Jacques.
----- Mail original ----- De: "Joe Zhang" <joezhang43@hotmail.com> A: "王?" <wangwei@cnic.cn>, "Yoshiro YONEYA" <yoshiro.yoneya@jprs.co.jp>, "Chris' 'Dillon" <c.dillon@ucl.ac.uk> Cc: ChineseGP@icann.org, KoreanGP@icann.org, JapaneseGP@icann.org Envoye: Mercredi 13 Mai 2015 14:18:33 Objet: [ChineseGP] 答?: 答?: Characters likely to cause offence
Besides卍and ?, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards,
Zhang
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王? ?送??: 2015年5月12日 10:35 收件人: 'Yoshiro YONEYA'; 'Dillon, Chris' 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主?: [ChineseGP] 答?: Characters likely to cause offence
I guess both of 卍and ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don’t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?件原件----- ?件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 Yoshiro YONEYA ?送??: 2015年5月12日 9:55 收件人: Dillon, Chris 抄送: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org 主?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear Jacques and Hotta San Thanks for your effort on this issue. I agree with Hotta that CJK should focus on the coordination of a unified variant table and generation rule first. If ICANN will set up an evaluation process to address this issue, CJK would like to join and follow. Anyway, it is out of CJK's current working scope now. Regards Wang wei -----�ʼ�ԭ��----- ������: hotta@jprs.co.jp [mailto:hotta@jprs.co.jp] ����ʱ��: 2015��5��19�� 0:21 �ռ���: Subrenat, Jean-Jacques ����: Joe Zhang; wangwei@cnic.cn; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org ����: Re: [Japanesegp] [ChineseGP] ��?: ��?: Characters likely to cause offence Thanks for your clear explanation, Jean-Jacques. I agree with your discussion. I think we are not thinking in a different way. I just wanted to say that "if someone can decide, with reasonable reason, what characters should be removed from the repertoire, I will not object that". I believe GPs should not be responsible for such decision. As you explained, those two characters have a deep innocent history and CJK folks will think such characters are important good characters for their lives. However, I think it will not be CGP/JGP/KGP's responsiblility to prove that. Regards, Hiro On Mon, 18 May 2015 18:01:02 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hiro-san,
there seems to be a misunderstanding: - you are suggesting "removal of characters", - but in fact I made the point that we should keep the 2 characters under discussion, precisely because they have a long documented history, way before they were misused, for about 2 decades, by the Nazi regime.
A further reason for keeping these 2 characters is that, in spite of their misuse between roughly 1930 to 1945 in Europe, their use as cultural and religious references has been continuous for more than 2000 years, mainly in Asia. This continues to be true today.
Finally, I would like to make clear that my suggestion of a mechanism for removal applies to characters which may be considered offensive TODAY, but in my mind this does not apply to the 2 characters discussed in the thread.
Best regards, Jean-Jacques.
----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> A: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, wangwei@cnic.cn, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoye: Lundi 18 Mai 2015 17:33:44 Objet: Re: [Japanesegp] [ChineseGP] ��?: ��?: Characters likely to cause offence
Hello, Jean-Jacques.
I personally don't object the removal of characters that are very offensive to some others. I think we can follow the procedure if such procedure is globally established and employed by ICANN.
I am asking ICANN whether such removal should be solved by RootLGR project (i.e., each GP or IP) or not.
Regards, Hiro
On Fri, 15 May 2015 10:27:12 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello Hiro-san,
thank you for your response. It might be worth considering an alternative: include such scripts, unless there is a documented opposition, based on historical, linguistic or technical factors.
In practical terms, it may be useful to draw up a list of characters which present similar problems. This list would be sent out to our membership lists (all C, J, K) for comment within a one-month period. Those characters meeting no opposition could then be included; those presenting a problem would then be either submitted to further examination, or rejected, and the rationale for either decision would be documented. Also, it may be useful to provide a mechanism for periodic review.
Best regards, Jean-Jacques.
----- Mail original ----- De: "HiroHOTTA" <hotta@jprs.co.jp> A: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Joe Zhang" <joezhang43@hotmail.com>, "��?" <wangwei@cnic.cn>, KoreanGP@icann.org, ChineseGP@icann.org, JapaneseGP@icann.org Envoye: Jeudi 14 Mai 2015 18:38:31 Objet: Re: [Japanesegp] [ChineseGP] ��?: ��?: Characters likely to cause offence
I may agree to that in principle.
But here I just want to say who should think about that and who is responsible for that?
If it's within GP's mandate, GP cannot afford that. If it's within IP's mandate, further question may be 'who can decide some specific characters should not listed in MSR' ?
Hiro
On Thu, 14 May 2015 11:19:40 +0200 (CEST) "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
Hello All,
the discussion on �d and ? must abide by some wider principle. In this case, the principle of historic precedence should be respected: the Sanskrit svastika, which can be traced back at least to the Neolithic, is unquestionably more ancient than any more recent use of this script, or its tragic misuse by the Nazi regime in the first half of the 20th century.
I would therefore urge that we keep the historic Sanskrit script present in the list, insofar as it has been adopted in Chinese, Japanese or Korean usage, for instance in religious or other texts.
To be perfectly clear, by taking this position of respecting the original Sanskrit script, I am in no way condoning the despicable Nazi regime that later employed this as its trademark.
Best regards, Jean-Jacques.
----- Mail original ----- De: "Joe Zhang" <joezhang43@hotmail.com> A: "��?" <wangwei@cnic.cn>, "Yoshiro YONEYA" <yoshiro.yoneya@jprs.co.jp>, "Chris' 'Dillon" <c.dillon@ucl.ac.uk> Cc: ChineseGP@icann.org, KoreanGP@icann.org, JapaneseGP@icann.org Envoye: Mercredi 13 Mai 2015 14:18:33 Objet: [ChineseGP] ��?: ��?: Characters likely to cause offence
Besides�dand ?, there would be many "sensitive" even "dirty" characters in the repertoire. I agree with Wang Wei, let's leave such issue to IP or next working stage. BTW. Sorry for not being able to attend the important meeting. I believe your guys will come up with good result. The best regards,
Zhang
-----?��ԭ��----- ?����: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] ���� ��? ?��??: 2015��5��12�� 10:35 �ռ���: 'Yoshiro YONEYA'; 'Dillon, Chris' ����: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org ��?: [ChineseGP] ��?: Characters likely to cause offence
I guess both of �dand ? (swastika, ????????) were imported into Chinese characters from ancient India Buddhism hundreds years ago Both of them mean something like luck or fortune in east Asia. Most western people don��t know them until one of them was borrowed by Nazi.
What about leave the problem to IP or policy guys. Let's finish repertoire, variant coordination and generation rules first.
-----?��ԭ��----- ?����: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] ���� Yoshiro YONEYA ?��??: 2015��5��12�� 9:55 �ռ���: Dillon, Chris ����: ChineseGP@icann.org; KoreanGP@icann.org; JapaneseGP@icann.org ��?: Re: [ChineseGP] Characters likely to cause offence
Dear Chris-san,
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
The reason why this character (U+5350) is in J-LGR-2 is that this is defined as variant of U+534D in C-LGR-1. U+534D is in J-LGR-1 repertoire, so it was integrated into J-LGR-2 by proposed integration algorithm.
As you see in J-LGR-2.xlsx, U+5350 is marked as (o) or (b), so it will never appear on Root zone if it is used in applied-for string as Japanese IDN TLD.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 11 May 2015 14:02:14 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature.
I suspect there may be other characters in there that could cause offence, but ? 5350 could be horribly abused. I realize that the character it represents is used innocently in temples.
It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues.
Regards,
Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp _______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
participants (8)
-
Dillon, Chris -
Edmon Chung -
HiroHOTTA -
Joe Zhang -
Sarmad Hussain -
Subrenat, Jean-Jacques -
Yoshiro YONEYA -
王伟