Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
microsoft translation engine doesn't work - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Sun Jun 20th, 2021 05:12 pm
PM Private Upload Quote Reply
bulent
Member
 

Joined: Sun Jun 20th, 2021
Location: Turkey
Posts: 2
Status: 
Offline
I have a working Azure Cognitive Services subscription and I tried to add Microsoft engine to the system. Entered the correct API key and when I pressed the "test" button, I'm getting a socket error 10054 error?

Back To Top PM Private Upload Quote Reply

 Posted: Fri Jun 25th, 2021 10:42 pm
PM Private Upload Quote Reply
jaska
Member
 

Joined: Thu Dec 7th, 2017
Location:  
Posts: 16
Status: 
Offline
Microsoft has changed the endpoint to get the access token for MS translator. Sisulizer still uses the old endpoint. In fact the endpoint has been hardcoded into Sisulizer's code. This ends Sisulizer's MS translator support. It won't work any more, ever.

I suggest you change to another localization tool. Soluling
https://www.soluling.com
has all the features of Sisulizer and an easy migration from Sisulizer project file to a Soluling project file.

In addition Soluling has not hardcoded the token endpoint into the code but you can specify it. So MS translator works with Soluling.

https://www.soluling.com/Help/MachineTranslation.htm

Last edited on Fri Jun 25th, 2021 10:44 pm by jaska

Back To Top PM Private Upload Quote Reply

 Posted: Sat Jun 26th, 2021 07:44 am
PM Private Upload Quote Reply
bulent
Member
 

Joined: Sun Jun 20th, 2021
Location: Turkey
Posts: 2
Status: 
Offline
Hi Jaska,

Thank you for the reply. I looked at the tool you mentioned. It is using the same endpoint address Sisulizer uses which is: https://api.cognitive.microsoft.com/sts/v1.0/issueToken

Also it isn't correctly importing the .slp file and gives warning about missing localization files which were already built and there.

I further investigate the problem and it seems a communication protocol problem. When I set a http proxy, Sisulizer works with the MS translation engine correctly. When it worked, unchecking proxy settings doesn't affect it and continues to work properly.

Is the Sisulizer tool ended? Since there isn't any team member here and I see lots of spam messages lately in the forum.

Back To Top PM Private Upload Quote Reply

 Posted: Sat Jun 26th, 2021 06:32 pm
PM Private Upload Quote Reply
jaska
Member
 

Joined: Thu Dec 7th, 2017
Location:  
Posts: 16
Status: 
Offline
> It is using the same endpoint address Sisulizer uses which is: https://api.cognitive.microsoft.com/sts/v1.0/issueToken

The current build still populates the old token endpoint (MS did not change very recently) but you can change it. If you modify and enter the correct one, it works.

Starting from the next build Soluling does not populate the API endpoint but you have to enter the right now.

About .slp import. In some cases Soluling can not locate the localized files. This need to be fixed. If you send your .slp to support_(at)_soluling.com I can fix the converting.

We need to implement proxy mapping to Soluling. Added that to TODO list.

Sisulizer tool has ended. I am pretty sure the won't be any new versions because nobody seems to monitor this forum either.

Back To Top PM Private Upload Quote Reply

 Posted: Sun Jun 27th, 2021 12:26 am
PM Private Upload Quote Reply
jaska
Member
 

Joined: Thu Dec 7th, 2017
Location:  
Posts: 16
Status: 
Offline
Added support for proxy servers. The new feature will be in the next build, 861, that will come out in a day or two.

Back To Top PM Private Upload Quote Reply

Current time is 06:26 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > microsoft translation engine doesn't work



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize