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, ...

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.

Not logged in - Login | Register

.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.

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

New Topic

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

Author

Post

Posted: Tue Jan 17th, 2012 09:53 pm

Private Upload

Quote

Doug Schmidt
Member

Joined:	Wed May 18th, 2011
Location:	Vancouver, British Columbia Canada
Posts:	11
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.

Private Upload

Quote

Posted: Wed Jan 18th, 2012 08:58 am

Private Upload

Quote

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Monschau, Germany
Posts:	2122
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

Private Upload

Quote

Current time is 10:15 pm
.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.

Sisulizer software localization tool - Three simple steps to localize