[lac-discuss-en] =? utf-8? q? RES=3A_Estado_de _software_de_la_tradu? = =? utf-8? b? Y2Npw7Un? =

sylvia at internautabrasil.org sylvia at internautabrasil.org
Tue Sep 20 19:38:03 UTC 2011


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

Subject:   =? utf-8? q? RES=3A_Estado_de _software_de_la_tradu? =	=? utf-8? b? Y2Npw7Un? = 
From: sylvia at internautabrasil.org 
 
 Dear Kent 
 If the text below was doing using the new tool, I' terrible m sorry to tell you is. 
 We need to find out to another solution.  
 Regards, 
 Sylvia 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
-----Original Mensagem-----
 Of: lac-discuss-es-bounces at atlarge-lists.icann.org [ mailto:lac-discuss-es-bounces at atlarge-lists.icann.org ] member state nome of kent at icann.org 
 Shipment member state: Tuesday, 20 of September of 2011 16:02 
 For: lac-discuss-es at atlarge-lists.icann.org 
 Cc: Simon raveh; David closson 
 Assunto: State of the software of the translation 
 
 
 
 
 [ [--Translated text (in -> is)--] ] 
 
 
 Subject:State of the software of the translation 
 Of: kent at icann.org 
 
 
  hello everything 
 
 
 
 
  as you know, the interface of Google that we used with a certain success some months ago <of tbNL> was continued.  Google not too much sent a commercial version a long time ago, and I have been working in the incorporation of that in the software of the translation <of tbNL>.  This has been a distribution greater than <of tbNL would have thought>, for several reasons. 
 
 
 
 
  the previous version of software unfortunately used an interface of general aims of the translation that happened to support Google, but that did not make the interface of general aims, last time watched, work with the new commercial API.  > Was so necessary to recodificar the system to use the new API.Esto directly was probably a good thing to do in general principles <of tbNL, only he wasn&amp; #039;as easy t as one wanted.  Nevertheless, I now has east operation. 
 
 
 
 
  nevertheless, another problem emerged in my test: the new API is commercial product of a.  They measure carefully how much text you have translated, and are more final on the amount of text that you can you translate in a single request.  Particularly, the limit of the defect for the request of a now is around 2000 octets, and consume to the significant parts of that in the plate of boiler of the protocol.  On the other hand, the transmitted text is due to codify of a way that can extend the number of sent octets perceivably <of tbNL> (for which they take care of, the interface is an interface of the REST, the text <of tbNL> must URI-be saved, and of the rest of parÃmeters> counts in lÃmite <of tbNL - he is 2K for the whole URL).
 
 
 
 
  we finished previously returning an error when the text that traducirÃhe was too great, but this new lÃmite is so pequeño that it is really necessary to handle to the error of a way mÃattractive s.  I am executing this change at the moment, and hope that it is done today.  If the things go según the predicted thing, convertiré the list to use new cà ³ I say mañana. 
 
 
 
 
  nevertheless, please considers that <of tbNL have been significant internal changes>, so allà can well be editions.  à ‰ ntreme in contact with please 
  (kent at icann.org) with any problem that you can find. 
 
 
 
 
  memories 
  Kent Crispin 
 
 
 
 
 
 
 
 
  ___________________________________________ 
 
 
 
 
 
 
 


[[--Original text (es)
http://mm.icann.org/transbot_archive/305bcd8745.html
--]]




More information about the lac-discuss-en mailing list