[lac-discuss-es] RES: Estado del software de la traducción

Vanda UOL vanda en uol.com.br
Mie Sep 21 13:18:09 UTC 2011


Still not correct Spanish but at least more understandable! It is a real
difficult obstacle to overpass. Best, see you in Dakar!

Vanda Scartezini
Polo Consultores Associados 
IT Trend
Alameda Santos 1470 – 1407,8
01418-903 São Paulo,SP, Brasil
Tel + 5511 3266.6253
Mob + 55118181.1464


-----Mensagem original-----
De: lac-discuss-es-bounces en atlarge-lists.icann.org
[mailto:lac-discuss-es-bounces en atlarge-lists.icann.org] Em nome de
devtee en gmail.com
Enviada em: terça-feira, 20 de setembro de 2011 18:12
Para: lac-discuss-es en atlarge-lists.icann.org
Cc: lac-discuss-en en atlarge-lists.icann.org; Simon raveh; David closson
Assunto: Re: Estado del software de la traducción


[[--Translated text (en -> es)--]]

Tema:  Re:  Estado del software de la traducción
De: devtee en gmail.com 
 
 las gracias por la actualización comprensiva, Kent y las gracias por  los
esfuerzos significativos usted, David y Simon ha puesto en superar  los
obstáculos significativos en el uso del Google traduce el API. Cuando se
termina el trabajo <del tbNL>, LACRALO podrá mejor colaborar mejor  en
asuntos políticos de ICANN y de LACRALO. 
 
 
 atentamente, 
 
 
 secretaría del revelador Anand Teelucksingh  LACRALO 
 
 
 
 
 
 
 el Tue, el 20 de septiembre de 2011 en el 8:00 P.M., Kent <kent en icann.org>
escribió: 
 > Hello all
>
> As you know, the Google interface we were using with some success a 
> few months ago was discontinued.  Google released a commercial version 
> not too long ago, and I have been working on incorporating that into 
> the translation software.  This has been a bigger deal than I would 
> have thought, for several reasons.
>
> The previous version of the software used a general purpose 
> translation interface that happened to support Google, but 
> unfortunately that general purpose interface did not, last time I 
> looked, work with the new commercial API.  So it was necessary to 
> re-code the system to directly use the new API.  This was probably a 
> good thing to do on general principles, but it wasn't as easy as one 
> would like.  However, I now have this working.
>
> However, a further problem emerged in my testing: the new API is a 
> commercial product.  They carefully meter how much text you have 
> translated, and they are stricter about the amount of text that you 
> can translate in a single request.  In particular, the default limit 
> for a request is now around 2000 bytes, and a significant part of that 
> is consumed in the protocol boilerplate.  Moreover, the transmitted 
> text must be encoded in a way that can significantly expand the number 
> of bytes sent (for those that care, the interface is a REST interface, 
> the text must be URI-escaped, and all the other parameters count in 
> the limit - it is 2K for the entire URL).
>
> Previously we just returned an error when the text to be translated 
> was too large, but this new limit is so small that it really is 
> necessary to handle the error in a more graceful way.  I am 
> implementing this change at the moment, and I expect it to be done 
> today.  If things go as planned, I will convert the list to use the new
code tomorrow.
>
> However, please bear in mind that there have been significant internal 
> changes, so there may well be issues.  Please contact me
> (kent en icann.org) with any problems you may find.
>
> Best Regards
> Kent Crispin
>
>
> _______________________________________________
> lac-discuss-en mailing list
> lac-discuss-en en atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en
>
  
 
 


[[--Original text (en)
http://mm.icann.org/transbot_archive/0fc16c9124.html
--]]






Más información sobre la lista de distribución lac-discuss-es