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
Expand (remove?) maximum string length in translation memory. - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Tue Jan 17th, 2012 08:53 pm
PM Private Upload Quote Reply
Doug Schmidt
Member
 

Joined: Wed May 18th, 2011
Location: Vancouver, British Columbia Canada
Posts: 16
Status: 
Offline
Is there a reason why the TranslationMemory string limit even exists? Or if it must exist why it is so small?

For example, the MySQL limit of 250 chars is odd. Especially since for MySQL 5.0.3+ (from 6 years ago), the VARCHAR(max) limit is a 65KB string.

It would be great if a value of 0 or -1 was interpreted to mean "use the maximum length allowed by the DB".

Our translators use the TM search feature extensively, to help check for consistency in translations. Many strings from our HTML pages and HTML help manual exceed the 250 char limit and are excluded from the TM.

I know they'd gladly give up a little more DB disk space and a slower index just to get everything into the TM.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jan 18th, 2012 07:58 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3322
Status: 
Offline
Hi Doug,

It is limited by the maximum index lenght of the field. We know how to overcome the limit and we know that it means a lot of work and testing. The good news: It is already on our road map.

Markus



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

 Posted: Thu Dec 19th, 2019 07:32 am
PM Private Upload Quote Reply
njo
Banned
 

Joined: Mon Oct 14th, 2019
Location: Germany
Posts: 4
Status: 
Offline
Hi Markus,
now, we're writing the year 2019, nearly 2020.
What about the "road map" (which is now nearly 8 years(!) old) regarding the string limit?
When will it be possible to use a MySQL translation memory with strings which are longer than 250 bytes?
And, by the way: Why is exporting a firebird translation memory not finished at 100% but at 144%? :eek:

Thank you very much in advance for your answers. Kind regardsNils

Last edited on Thu Dec 19th, 2019 08:29 am by njo

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jan 22nd, 2020 06:08 am
PM Private Upload Quote Reply
njo
Banned
 

Joined: Mon Oct 14th, 2019
Location: Germany
Posts: 4
Status: 
Offline
Hello Markus.Kreisel,
no answer until now to my question from 19th Dec. 2019?!
Thanks a lot in advanced for a short and soon answer on my question about the original request from Doug.
Kind regards
Nils

Back To Top PM Private Upload Quote Reply

Current time is 07:13 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Expand (remove?) maximum string length in 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