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
Error messages saving to translation memory - 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: Fri May 31st, 2019 03:31 pm
PM Private Upload Quote Reply
BWNT
Member
 

Joined: Wed Nov 8th, 2017
Location:  
Posts: 7
Status: 
Offline
Hi guys, could you please help explain the errors we got in the attached screenshot saving to translation memory on one of our linguists machines?

Thanks much.

Attachment: Error messages_sisu_ru.JPG (Downloaded 5 times)

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 31st, 2019 03:33 pm
PM Private Upload Quote Reply
BWNT
Member
 

Joined: Wed Nov 8th, 2017
Location:  
Posts: 7
Status: 
Offline
Also, is there really a max string size and thus not potentially a bug/quirk? Then wouldn't be worried and just move along with it. thx again.

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 31st, 2019 03:53 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3301
Status: 
Offline
The string size is limited by the size of the maximal index size of the database. 

The best way to transfer translations to a new project is in a Sisulizer .slp file. It doesn't have a limitation in string size and it also stores a context which can be handy in some situation.
You can try to split your strings to reduce the maximum strings size using segmentation rules. But I would not recomment that in an existing project since one string becomes n short strings and the translations will not match.
Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Fri May 31st, 2019 04:14 pm
PM Private Upload Quote Reply
BWNT
Member
 

Joined: Wed Nov 8th, 2017
Location:  
Posts: 7
Status: 
Offline
Thanks Markus, we'll keep that mind going forward. Have a great WE

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 31st, 2019 05:48 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3301
Status: 
Offline
Same to you
Markus
P.S. Different Database have different limitations... The maximum I know about is 1024



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 02:08 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Error messages saving to translation memory



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