<p dir="ltr">+1</p>
<p dir="ltr">I will do Serbian (Croatian, Bosnian, Montenegrin...) version. </p>
<p dir="ltr">Dusan</p>
<p dir="ltr">Poslato sa mog Sony Xperia™ pametnog telefona</p>
<br><br>---- Tan Tanaka, Dennis je napisao/la ----<br><br>+1<br><br>-----Original Message-----<br>From: <a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a> [mailto:<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>] On Behalf Of Edmon Chung<br>Sent: Thursday, January 28, 2016 6:28 PM<br>To: 'Paul Mitchell (CELA)'; 'Lars Steffen'; 'Don Hollander'<br>Cc: <a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br>Subject: Re: [UA-discuss] Document Translations<br><br>On the topic of translation, I think we should not depend on the "standard"<br>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).<br><br>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.<br><br>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.<br><br>Edmon<br><br><br><br>> -----Original Message-----<br>> From: <a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a> <br>> [mailto:<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>]<br>On<br>> Behalf Of Paul Mitchell (CELA)<br>> Sent: Friday, 29 January 2016 04:15 AM<br>> To: Lars Steffen <<a href="mailto:lars.steffen@eco.de">lars.steffen@eco.de</a>>; Don Hollander<br><<a href="mailto:don.hollander@icann.org">don.hollander@icann.org</a>><br>> Cc: <a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br>> Subject: Re: [UA-discuss] Document Translations<br>> <br>> 6 UN languages not 5 - don't forget French (which is often the <br>> governing<br>language in<br>> UN negotiated outputs)! Portuguese is not one of the UN official<br>languages but one<br>> that ICANN has been supporting interpretation for.<br>> <br>> -----Original Message-----<br>> From: <a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a> <br>> [mailto:<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>]<br>On<br>> Behalf Of Lars Steffen<br>> Sent: Thursday, January 28, 2016 11:41 AM<br>> To: Don Hollander <<a href="mailto:don.hollander@icann.org">don.hollander@icann.org</a>><br>> Cc: <a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br>> Subject: Re: [UA-discuss] Document Translations<br>> <br>> I have 2 colleagues as translators at eco for the German job.<br>> <br>> Lars<br>> <br>> > Am <a href="tel:28.01.2016">28.01.2016</a> um 20:37 schrieb Don Hollander <<a href="mailto:don.hollander@icann.org">don.hollander@icann.org</a>>:<br>> ><br>> > The five UN Languages: English, Russian, Chinese, Arabic & Spanish <br>> > -<br>sometime<br>> Portuguese as well.<br>> ><br>> > And Mark, this doesn't HAVE to be a funded activity - we have <br>> > already<br>had<br>> community engagement in other translations that we've done.<br>> ><br>> > Some of the documents are quite short and straight forward. The<br>Introduction to<br>> UA does not fall into that category.<br>> ><br>> > Don<br>> ><br>> ><br>> ><br>> >> On 29/01/16, 8:16 AM, "Christian Dawson" <<a href="mailto:dawson@i2coalition.com">dawson@i2coalition.com</a>><br>wrote:<br>> >><br>> >> Don,<br>> >><br>> >> What are the 'standard' ICANN translation languages?<br>> >><br>> >> -Christian<br>> >><br>> >>> On Jan 28, 2016, at 1:36 PM, Mark Svancarek <<a href="mailto:marksv@microsoft.com">marksv@microsoft.com</a>><br>wrote:<br>> >>><br>> >>> I had considered that we should translate to Spanish and German <br>> >>> simply<br>> because Luisa could perform this translation or review someone else's<br>translation. It<br>> seemed to be "low-hanging fruit".<br>> >>><br>> >>> That said, UA-Readiness is probably more important to Cyrillic, <br>> >>> Arabic<br>and<br>> various Asian script-users. (I wish there was more interest in South<br>America...)<br>> >>><br>> >>> If money is no obstacle, I vote for Simplified Chinese, Arabic,<br>Russian, Serbian,<br>> Ukrainian, Thai and Persian to start.<br>> >>><br>> >>> I know there is interest in Afghan and Pakistan governments, too.<br>> >>><br>> >>> -----Original Message-----<br>> >>> From: <a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a><br>[mailto:<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>]<br>> On Behalf Of Don Hollander<br>> >>> Sent: Wednesday, January 27, 2016 10:23 PM<br>> >>> To: <a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br>> >>> Subject: [UA-discuss] Document Translations<br>> >>><br>> >>> As we get closer to completing some of our foundation documents, <br>> >>> its<br>now time<br>> to turn to translation.<br>> >>><br>> >>> The documents that we have or will have ready soon include:<br>> >>><br>> >>> A UA Fact Sheet - complete<br>> >>> A quick guide to UA (covers topics and quick recommendations for<br>Acceptance,<br>> Validation, Storage, Processing, Display and Confusable Characters) A<br>Definition of<br>> UA Readiness An Introduction to Universal Acceptance (a very <br>> comprehensive<br>> document)<br>> >>><br>> >>> Our quick message to webmasters whose sites are not UA Ready has <br>> >>> been<br>> translated by the community into 7 lagnuages.<br>> >>><br>> >>> My question is:<br>> >>><br>> >>> 1) Do we need to do translation at this point in time? (It is<br>relatively early in our<br>> efforts and there may be substantial revisions once we put the <br>> documents<br>'out in the<br>> wild')<br>> >>> 2) What languages should we translate to?<br>> >>><br>> >>> Your thoughts, please<br>> >>><br>> >>> Don<br><br>