As we get closer to completing some of our foundation documents, its now time to turn to translation. The documents that we have or will have ready soon include: A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document) Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages. My question is: 1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to? Your thoughts, please Don
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit". That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...) If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start. I know there is interest in Afghan and Pakistan governments, too. -----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations As we get closer to completing some of our foundation documents, its now time to turn to translation. The documents that we have or will have ready soon include: A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document) Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages. My question is: 1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to? Your thoughts, please Don
Don, What are the ‘standard’ ICANN translation languages? -Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to?
Your thoughts, please
Don
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well. And Mark, this doesn’t HAVE to be a funded activity - we have already had community engagement in other translations that we’ve done. Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category. Don On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the ‘standard’ ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to?
Your thoughts, please
Don
I have 2 colleagues as translators at eco for the German job. Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org>:
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn’t HAVE to be a funded activity - we have already had community engagement in other translations that we’ve done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the ‘standard’ ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to?
Your thoughts, please
Don
6 UN languages not 5 - don't forget French (which is often the governing language in UN negotiated outputs)! Portuguese is not one of the UN official languages but one that ICANN has been supporting interpretation for. -----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Lars Steffen Sent: Thursday, January 28, 2016 11:41 AM To: Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations I have 2 colleagues as translators at eco for the German job. Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org>:
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn't HAVE to be a funded activity - we have already had community engagement in other translations that we've done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the 'standard' ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents 'out in the wild') 2) What languages should we translate to?
Your thoughts, please
Don
On the topic of translation, I think we should not depend on the "standard" ICANN translation. Perhaps not even the "standard languages" though it is fine to start there. I feel it is an imperative that we find local tech savvy partners to do what is perhaps better called "interpretations" than "translations". Many words/sentences will be better interpreted in local lingo than translated (which would feel foreign). I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to get their input as well. They may be the ones who are most familiar with the relevant local lingo. So we should, like how we started ourselves, work with an alliance of the willing... to help us develop local versions of the core documents together. Edmon
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Paul Mitchell (CELA) Sent: Friday, 29 January 2016 04:15 AM To: Lars Steffen <lars.steffen@eco.de>; Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
6 UN languages not 5 - don't forget French (which is often the governing language in UN negotiated outputs)! Portuguese is not one of the UN official languages but one that ICANN has been supporting interpretation for.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Lars Steffen Sent: Thursday, January 28, 2016 11:41 AM To: Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
I have 2 colleagues as translators at eco for the German job.
Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org>:
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn't HAVE to be a funded activity - we have already had community engagement in other translations that we've done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the 'standard' ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents 'out in the wild') 2) What languages should we translate to?
Your thoughts, please
Don
+1 -----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Edmon Chung Sent: Thursday, January 28, 2016 6:28 PM To: 'Paul Mitchell (CELA)'; 'Lars Steffen'; 'Don Hollander' Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations On the topic of translation, I think we should not depend on the "standard" ICANN translation. Perhaps not even the "standard languages" though it is fine to start there. I feel it is an imperative that we find local tech savvy partners to do what is perhaps better called "interpretations" than "translations". Many words/sentences will be better interpreted in local lingo than translated (which would feel foreign). I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to get their input as well. They may be the ones who are most familiar with the relevant local lingo. So we should, like how we started ourselves, work with an alliance of the willing... to help us develop local versions of the core documents together. Edmon
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Paul Mitchell (CELA) Sent: Friday, 29 January 2016 04:15 AM To: Lars Steffen <lars.steffen@eco.de>; Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
6 UN languages not 5 - don't forget French (which is often the governing language in UN negotiated outputs)! Portuguese is not one of the UN official languages but one that ICANN has been supporting interpretation for.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Lars Steffen Sent: Thursday, January 28, 2016 11:41 AM To: Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
I have 2 colleagues as translators at eco for the German job.
Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org>:
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn't HAVE to be a funded activity - we have already had community engagement in other translations that we've done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the 'standard' ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents 'out in the wild') 2) What languages should we translate to?
Your thoughts, please
Don
+1 I will do Serbian (Croatian, Bosnian, Montenegrin...) version. Dusan Poslato sa mog Sony Xperia™ pametnog telefona ---- Tan Tanaka, Dennis je napisao/la ----
+1
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Edmon Chung Sent: Thursday, January 28, 2016 6:28 PM To: 'Paul Mitchell (CELA)'; 'Lars Steffen'; 'Don Hollander' Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
On the topic of translation, I think we should not depend on the "standard" ICANN translation. Perhaps not even the "standard languages" though it is fine to start there. I feel it is an imperative that we find local tech savvy partners to do what is perhaps better called "interpretations" than "translations". Many words/sentences will be better interpreted in local lingo than translated (which would feel foreign).
I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to get their input as well. They may be the ones who are most familiar with the relevant local lingo.
So we should, like how we started ourselves, work with an alliance of the willing... to help us develop local versions of the core documents together.
Edmon
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Paul Mitchell (CELA) Sent: Friday, 29 January 2016 04:15 AM To: Lars Steffen <lars.steffen@eco.de>; Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
6 UN languages not 5 - don't forget French (which is often the governing language in UN negotiated outputs)! Portuguese is not one of the UN official languages but one that ICANN has been supporting interpretation for.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Lars Steffen Sent: Thursday, January 28, 2016 11:41 AM To: Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
I have 2 colleagues as translators at eco for the German job.
Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org>:
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn't HAVE to be a funded activity - we have already had community engagement in other translations that we've done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the 'standard' ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents 'out in the wild') 2) What languages should we translate to?
Your thoughts, please
Don
+1 -----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Tan Tanaka, Dennis Sent: Thursday, January 28, 2016 3:37 PM To: edmon@registry.asia; Paul Mitchell (CELA); 'Lars Steffen'; 'Don Hollander' Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations +1 -----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Edmon Chung Sent: Thursday, January 28, 2016 6:28 PM To: 'Paul Mitchell (CELA)'; 'Lars Steffen'; 'Don Hollander' Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations On the topic of translation, I think we should not depend on the "standard" ICANN translation. Perhaps not even the "standard languages" though it is fine to start there. I feel it is an imperative that we find local tech savvy partners to do what is perhaps better called "interpretations" than "translations". Many words/sentences will be better interpreted in local lingo than translated (which would feel foreign). I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to get their input as well. They may be the ones who are most familiar with the relevant local lingo. So we should, like how we started ourselves, work with an alliance of the willing... to help us develop local versions of the core documents together. Edmon
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Paul Mitchell (CELA) Sent: Friday, 29 January 2016 04:15 AM To: Lars Steffen <lars.steffen@eco.de>; Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
6 UN languages not 5 - don't forget French (which is often the governing language in UN negotiated outputs)! Portuguese is not one of the UN official languages but one that ICANN has been supporting interpretation for.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Lars Steffen Sent: Thursday, January 28, 2016 11:41 AM To: Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
I have 2 colleagues as translators at eco for the German job.
Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org>:
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn't HAVE to be a funded activity - we have already had community engagement in other translations that we've done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the 'standard' ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents 'out in the wild') 2) What languages should we translate to?
Your thoughts, please
Don
Agreed. -----Original Message----- From: Edmon Chung [mailto:edmon@registry.asia] Sent: Thursday, January 28, 2016 3:28 PM To: Paul Mitchell (CELA) <Paul.Mitchell@microsoft.com>; 'Lars Steffen' <lars.steffen@eco.de>; 'Don Hollander' <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: RE: [UA-discuss] Document Translations On the topic of translation, I think we should not depend on the "standard" ICANN translation. Perhaps not even the "standard languages" though it is fine to start there. I feel it is an imperative that we find local tech savvy partners to do what is perhaps better called "interpretations" than "translations". Many words/sentences will be better interpreted in local lingo than translated (which would feel foreign). I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to get their input as well. They may be the ones who are most familiar with the relevant local lingo. So we should, like how we started ourselves, work with an alliance of the willing... to help us develop local versions of the core documents together. Edmon
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Paul Mitchell (CELA) Sent: Friday, 29 January 2016 04:15 AM To: Lars Steffen <lars.steffen@eco.de>; Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
6 UN languages not 5 - don't forget French (which is often the governing language in UN negotiated outputs)! Portuguese is not one of the UN official languages but one that ICANN has been supporting interpretation for.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Lars Steffen Sent: Thursday, January 28, 2016 11:41 AM To: Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
I have 2 colleagues as translators at eco for the German job.
Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org>:
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn't HAVE to be a funded activity - we have already had community engagement in other translations that we've done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the 'standard' ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents 'out in the wild') 2) What languages should we translate to?
Your thoughts, please
Don
Edmon is right. I would add that, since we have a budget to work from, if translations involve professional tech translators, then this would be a useful destination for some of the available funds. Tony Harris On Thu, Jan 28, 2016 at 3:27 PM, Edmon Chung <edmon@registry.asia> wrote:
On the topic of translation, I think we should not depend on the "standard" ICANN translation. Perhaps not even the "standard languages" though it is fine to start there. I feel it is an imperative that we find local tech savvy partners to do what is perhaps better called "interpretations" than "translations". Many words/sentences will be better interpreted in local lingo than translated (which would feel foreign).
I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to get their input as well. They may be the ones who are most familiar with the relevant local lingo.
So we should, like how we started ourselves, work with an alliance of the willing... to help us develop local versions of the core documents together.
Edmon
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Paul Mitchell (CELA) Sent: Friday, 29 January 2016 04:15 AM To: Lars Steffen <lars.steffen@eco.de>; Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
6 UN languages not 5 - don't forget French (which is often the governing language in UN negotiated outputs)! Portuguese is not one of the UN official languages but one that ICANN has been supporting interpretation for.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Lars Steffen Sent: Thursday, January 28, 2016 11:41 AM To: Don Hollander <don.hollander@icann.org> Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations
I have 2 colleagues as translators at eco for the German job.
Lars
Am 28.01.2016 um 20:37 schrieb Don Hollander <don.hollander@icann.org :
The five UN Languages: English, Russian, Chinese, Arabic & Spanish - sometime Portuguese as well.
And Mark, this doesn't HAVE to be a funded activity - we have already had community engagement in other translations that we've done.
Some of the documents are quite short and straight forward. The Introduction to UA does not fall into that category.
Don
On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> wrote:
Don,
What are the 'standard' ICANN translation languages?
-Christian
On Jan 28, 2016, at 1:36 PM, Mark Svancarek <marksv@microsoft.com> wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents 'out in the wild') 2) What languages should we translate to?
Your thoughts, please
Don
+1 -- Sincerely yours, Maxim Alzoba. Sent from my phone. On 29 January 2016 02:27:31 GMT+03:00, Edmon Chung <edmon@registry.asia> wrote: >On the topic of translation, I think we should not depend on the >"standard" >ICANN translation. Perhaps not even the "standard languages" though it >is >fine to start there. I feel it is an imperative that we find local >tech >savvy partners to do what is perhaps better called "interpretations" >than >"translations". Many words/sentences will be better interpreted in >local >lingo than translated (which would feel foreign). > >I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to >get >their input as well. They may be the ones who are most familiar with >the >relevant local lingo. > >So we should, like how we started ourselves, work with an alliance of >the >willing... to help us develop local versions of the core documents >together. > >Edmon > > > >> -----Original Message----- >> From: ua-discuss-bounces@icann.org >[mailto:ua-discuss-bounces@icann.org] >On >> Behalf Of Paul Mitchell (CELA) >> Sent: Friday, 29 January 2016 04:15 AM >> To: Lars Steffen <lars.steffen@eco.de>; Don Hollander ><don.hollander@icann.org> >> Cc: UA-discuss@icann.org >> Subject: Re: [UA-discuss] Document Translations >> >> 6 UN languages not 5 - don't forget French (which is often the >governing >language in >> UN negotiated outputs)! Portuguese is not one of the UN official >languages but one >> that ICANN has been supporting interpretation for. >> >> -----Original Message----- >> From: ua-discuss-bounces@icann.org >[mailto:ua-discuss-bounces@icann.org] >On >> Behalf Of Lars Steffen >> Sent: Thursday, January 28, 2016 11:41 AM >> To: Don Hollander <don.hollander@icann.org> >> Cc: UA-discuss@icann.org >> Subject: Re: [UA-discuss] Document Translations >> >> I have 2 colleagues as translators at eco for the German job. >> >> Lars >> >> > Am 28.01.2016 um 20:37 schrieb Don Hollander ><don.hollander@icann.org>: >> > >> > The five UN Languages: English, Russian, Chinese, Arabic & Spanish >- >sometime >> Portuguese as well. >> > >> > And Mark, this doesn't HAVE to be a funded activity - we have >already >had >> community engagement in other translations that we've done. >> > >> > Some of the documents are quite short and straight forward. The >Introduction to >> UA does not fall into that category. >> > >> > Don >> > >> > >> > >> >> On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> >wrote: >> >> >> >> Don, >> >> >> >> What are the 'standard' ICANN translation languages? >> >> >> >> -Christian >> >> >> >>> On Jan 28, 2016, at 1:36 PM, Mark Svancarek ><marksv@microsoft.com> >wrote: >> >>> >> >>> I had considered that we should translate to Spanish and German >simply >> because Luisa could perform this translation or review someone else's >translation. It >> seemed to be "low-hanging fruit". >> >>> >> >>> That said, UA-Readiness is probably more important to Cyrillic, >Arabic >and >> various Asian script-users. (I wish there was more interest in South >America...) >> >>> >> >>> If money is no obstacle, I vote for Simplified Chinese, Arabic, >Russian, Serbian, >> Ukrainian, Thai and Persian to start. >> >>> >> >>> I know there is interest in Afghan and Pakistan governments, too. >> >>> >> >>> -----Original Message----- >> >>> From: ua-discuss-bounces@icann.org >[mailto:ua-discuss-bounces@icann.org] >> On Behalf Of Don Hollander >> >>> Sent: Wednesday, January 27, 2016 10:23 PM >> >>> To: UA-discuss@icann.org >> >>> Subject: [UA-discuss] Document Translations >> >>> >> >>> As we get closer to completing some of our foundation documents, >its >now time >> to turn to translation. >> >>> >> >>> The documents that we have or will have ready soon include: >> >>> >> >>> A UA Fact Sheet - complete >> >>> A quick guide to UA (covers topics and quick recommendations for >Acceptance, >> Validation, Storage, Processing, Display and Confusable Characters) A >Definition of >> UA Readiness An Introduction to Universal Acceptance (a very >comprehensive >> document) >> >>> >> >>> Our quick message to webmasters whose sites are not UA Ready has >been >> translated by the community into 7 lagnuages. >> >>> >> >>> My question is: >> >>> >> >>> 1) Do we need to do translation at this point in time? (It is >relatively early in our >> efforts and there may be substantial revisions once we put the >documents >'out in the >> wild') >> >>> 2) What languages should we translate to? >> >>> >> >>> Your thoughts, please >> >>> >> >>> Don
+1 with UN languages as a starting point +1 to Edmon's statement I offer myself again for the spanish translation On Fri, Jan 29, 2016 at 3:34 AM, Maxim Alzoba <m.alzoba@gmail.com> wrote: > +1 > -- > Sincerely yours, > Maxim Alzoba. > Sent from my phone. > > On 29 January 2016 02:27:31 GMT+03:00, Edmon Chung <edmon@registry.asia> > wrote: > >On the topic of translation, I think we should not depend on the > >"standard" > >ICANN translation. Perhaps not even the "standard languages" though it > >is > >fine to start there. I feel it is an imperative that we find local > >tech > >savvy partners to do what is perhaps better called "interpretations" > >than > >"translations". Many words/sentences will be better interpreted in > >local > >lingo than translated (which would feel foreign). > > > >I would suggest we proactively engage relevant local GAC/ALAC/ccNSO to > >get > >their input as well. They may be the ones who are most familiar with > >the > >relevant local lingo. > > > >So we should, like how we started ourselves, work with an alliance of > >the > >willing... to help us develop local versions of the core documents > >together. > > > >Edmon > > > > > > > >> -----Original Message----- > >> From: ua-discuss-bounces@icann.org > >[mailto:ua-discuss-bounces@icann.org] > >On > >> Behalf Of Paul Mitchell (CELA) > >> Sent: Friday, 29 January 2016 04:15 AM > >> To: Lars Steffen <lars.steffen@eco.de>; Don Hollander > ><don.hollander@icann.org> > >> Cc: UA-discuss@icann.org > >> Subject: Re: [UA-discuss] Document Translations > >> > >> 6 UN languages not 5 - don't forget French (which is often the > >governing > >language in > >> UN negotiated outputs)! Portuguese is not one of the UN official > >languages but one > >> that ICANN has been supporting interpretation for. > >> > >> -----Original Message----- > >> From: ua-discuss-bounces@icann.org > >[mailto:ua-discuss-bounces@icann.org] > >On > >> Behalf Of Lars Steffen > >> Sent: Thursday, January 28, 2016 11:41 AM > >> To: Don Hollander <don.hollander@icann.org> > >> Cc: UA-discuss@icann.org > >> Subject: Re: [UA-discuss] Document Translations > >> > >> I have 2 colleagues as translators at eco for the German job. > >> > >> Lars > >> > >> > Am 28.01.2016 um 20:37 schrieb Don Hollander > ><don.hollander@icann.org>: > >> > > >> > The five UN Languages: English, Russian, Chinese, Arabic & Spanish > >- > >sometime > >> Portuguese as well. > >> > > >> > And Mark, this doesn't HAVE to be a funded activity - we have > >already > >had > >> community engagement in other translations that we've done. > >> > > >> > Some of the documents are quite short and straight forward. The > >Introduction to > >> UA does not fall into that category. > >> > > >> > Don > >> > > >> > > >> > > >> >> On 29/01/16, 8:16 AM, "Christian Dawson" <dawson@i2coalition.com> > >wrote: > >> >> > >> >> Don, > >> >> > >> >> What are the 'standard' ICANN translation languages? > >> >> > >> >> -Christian > >> >> > >> >>> On Jan 28, 2016, at 1:36 PM, Mark Svancarek > ><marksv@microsoft.com> > >wrote: > >> >>> > >> >>> I had considered that we should translate to Spanish and German > >simply > >> because Luisa could perform this translation or review someone else's > >translation. It > >> seemed to be "low-hanging fruit". > >> >>> > >> >>> That said, UA-Readiness is probably more important to Cyrillic, > >Arabic > >and > >> various Asian script-users. (I wish there was more interest in South > >America...) > >> >>> > >> >>> If money is no obstacle, I vote for Simplified Chinese, Arabic, > >Russian, Serbian, > >> Ukrainian, Thai and Persian to start. > >> >>> > >> >>> I know there is interest in Afghan and Pakistan governments, too. > >> >>> > >> >>> -----Original Message----- > >> >>> From: ua-discuss-bounces@icann.org > >[mailto:ua-discuss-bounces@icann.org] > >> On Behalf Of Don Hollander > >> >>> Sent: Wednesday, January 27, 2016 10:23 PM > >> >>> To: UA-discuss@icann.org > >> >>> Subject: [UA-discuss] Document Translations > >> >>> > >> >>> As we get closer to completing some of our foundation documents, > >its > >now time > >> to turn to translation. > >> >>> > >> >>> The documents that we have or will have ready soon include: > >> >>> > >> >>> A UA Fact Sheet - complete > >> >>> A quick guide to UA (covers topics and quick recommendations for > >Acceptance, > >> Validation, Storage, Processing, Display and Confusable Characters) A > >Definition of > >> UA Readiness An Introduction to Universal Acceptance (a very > >comprehensive > >> document) > >> >>> > >> >>> Our quick message to webmasters whose sites are not UA Ready has > >been > >> translated by the community into 7 lagnuages. > >> >>> > >> >>> My question is: > >> >>> > >> >>> 1) Do we need to do translation at this point in time? (It is > >relatively early in our > >> efforts and there may be substantial revisions once we put the > >documents > >'out in the > >> wild') > >> >>> 2) What languages should we translate to? > >> >>> > >> >>> Your thoughts, please > >> >>> > >> >>> Don > > -- Nacho Estrada | @acmuzic <http://twitter.com/acmuzic>
Thanks Mark, What about Russian? I'm ready to organize the translation with my friends. --Yuri Thursday, January 28, 2016, 8:36:06 PM, you wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to?
Your thoughts, please
Don
Yes, Russian. -----Original Message----- From: Yuriy Kargapolov [mailto:yvk@uanic.info] Sent: Thursday, January 28, 2016 11:19 AM To: Mark Svancarek; Don Hollander; UA-discuss@icann.org Subject: Re: [UA-discuss] Document Translations Thanks Mark, What about Russian? I'm ready to organize the translation with my friends. --Yuri Thursday, January 28, 2016, 8:36:06 PM, you wrote:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to?
Your thoughts, please
Don
Sounds like a good selection. eco will do the German version anyhow. Support by Luisa is always appreciated. Lars
Am 28.01.2016 um 20:15 schrieb Mark Svancarek <marksv@microsoft.com>:
I had considered that we should translate to Spanish and German simply because Luisa could perform this translation or review someone else's translation. It seemed to be "low-hanging fruit".
That said, UA-Readiness is probably more important to Cyrillic, Arabic and various Asian script-users. (I wish there was more interest in South America...)
If money is no obstacle, I vote for Simplified Chinese, Arabic, Russian, Serbian, Ukrainian, Thai and Persian to start.
I know there is interest in Afghan and Pakistan governments, too.
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, January 27, 2016 10:23 PM To: UA-discuss@icann.org Subject: [UA-discuss] Document Translations
As we get closer to completing some of our foundation documents, its now time to turn to translation.
The documents that we have or will have ready soon include:
A UA Fact Sheet - complete A quick guide to UA (covers topics and quick recommendations for Acceptance, Validation, Storage, Processing, Display and Confusable Characters) A Definition of UA Readiness An Introduction to Universal Acceptance (a very comprehensive document)
Our quick message to webmasters whose sites are not UA Ready has been translated by the community into 7 lagnuages.
My question is:
1) Do we need to do translation at this point in time? (It is relatively early in our efforts and there may be substantial revisions once we put the documents ‘out in the wild’) 2) What languages should we translate to?
Your thoughts, please
Don
My thoughts are that the primary drive for UA for specific languages/script IDNs should come from those language communities. So, I consider, there is a need to get those language communities onboard with this initiative. UA document translations into the IDN languages may well encourage these language communities to become involved and champion the UA cause. The languages/scripts encompassed by the New IDN gTLD applications are:- German/Latin Russian/Cyrillic Arabic/Arabic Chinese Simplified/Hanzi Hindi/Devanagari Thai/Thai Korean/Hangeul Japanese/Katakana,Hiragana Hebrew/Hebrew http://icannwiki.com/index.php/New_gTLD_IDN_Applications Then if one includes the ccTLDs, we also have these additional language/scripts:- Armenian/Armenian Bengali/Bengali Belarusian/Cyrillic Bulgarian/Cyrillic Chinese Traditional/Hanzi Georgian/Georgian Urdu/Urdu Telugu/Telugu Gujarati/Gujarati Punjabi/Gurmukhi Tamil/Tamil Persian/Persian Kazakh/Cyrillic Macedonian/Cyrillic Malay/Arabic Mongolian/Cyrillic Serbian/Cyrillic Sinhala/Sinhala Ukrainian/Cyrillic This combined list is now too long for the short term for target translations. I suggest that the initial set of target translations should include those languages encompassed by the New IDN gTLDs. André Schappo On 28 Jan 2016, at 06:22, Don Hollander wrote:
2) What languages should we translate to?
Your thoughts, please
Don
participants (13)
-
Andre Schappo -
Anthony Harris -
Christian Dawson -
Don Hollander -
Dusan Stojicevic -
Edmon Chung -
Lars Steffen -
Mark Svancarek -
Maxim Alzoba -
Miguel Ignacio Estrada -
Paul Mitchell (CELA) -
Tan Tanaka, Dennis -
Yuriy Kargapolov