|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Google translate problem - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Juffowup Member
|
Hey there, I'm having a problem with the google translate machine translation. I've got it working, but it will only translate up to 51 lines and then give a very strange error. Atttached is a screencap of it. I'll also upload my SLP file for reference in the successive post. Any ideas of what this might be? Attachment: GoogleTranslateError.jpg (Downloaded 36 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Juffowup Member
|
Here's the slp file for reference. Cheers! Last edited on Tue May 19th, 2009 06:32 pm by |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Juffowup Member
|
P.S. This is the best tool we've found so far, if we can get this issue solved, we'll buy it. And the reason we need it now is the following. - We've got a very creative game writer who is localizing the game for us, but he doesn't speak English. Therefore, we're looking to get the best fits for him to work with so this feature is pretty important.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
I fixed this in build 284. The reason is that one of the string in your project was too long for Google translate and Sisulizer stopped for that error. Now Sisulizer just skips that string and continues for the next one. The new build will come out in few days. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Workaround: Find row visible on below screenshot (context item: localization.hexwarz.talk..20.talk.=text) and temporarily lock translation of this row e.g. via context menu of row or via icon on sheet toolbar (indicated by arrow on below screenshot) and next run Google translation engine. You should to get translation for all strings apart this locked row. Next you can unlock locked row in your Sisulizer project. BTW: For security reason of your sensitive data, I’ve removed your Sisulizer project from your post. Best regards, Janusz Attachment: screen.png (Downloaded 30 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Juffowup Member
|
Wow, what service! Thanks a bunch - think we're going to buy this  .Didn't know google translate had this problem though. I've translated many more characters than that on a single translate via their web interface. Not that it matters, but why would it be limited in an auto-translation request from Sisulizer and not in a manual web-translation?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
There reason was not Google but HTTP. We passed the whole string in one HTTP. I changed the code such way that if it longer than HTTP limit Sisulizer splits the sentance if it contains segmentation parts such as periods. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Juffowup Member
|
Thanks, you guys are truly awesome. You've got a sale :D. Also, just FYI. I was at a bit of a loss as to what the problem was. It would be excellent for users if you were able to put a bit more verbosity into your error reports. As a product manager myself, I know such details are numerous and tedious to deal with - but I think it would improve the quality of the product. Thanks again - Cheers.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Juffowup Member
|
Figured it was the HTTP. Thanks for explaining to me the internal details of the problem though.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Juffowup wrote: It would be excellent for users if you were able to put a bit more verbosity into your error reports. We are working on this. The current build indeed reports too complicated error message. The next build (284) contain only call history in the exception dump. Anyway we are converting thse dumps to more meaningfull error messages. About the translation length issues. We switched from GET to POST method when communicating with Google. This is why there is not length restriction any more. This feature will be in 284. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:45 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Google translate problem | |
Sisulizer software localization tool - Three simple steps to localize
