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
Rows marked DoNotTranslate get translation - 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: Sat May 4th, 2019 12:26 am
PM Private Upload Quote Reply
lauri
Member
 

Joined: Sat Feb 17th, 2018
Location:  
Posts: 22
Status: 
Offline
Hi!
A customer reported that translated version of my product is showing an error message while untranslated version (English) is fine.
Turns out, almost all languages contained values for some of the rows marked with DoNotTranslate flag.
This is not the first time the issue has happened. Last time i cleared all translations in such rows and restored the DNT flag.

If i understand correctly, rows with such flag should not get altered by translation import, duplicate translation, machine translation etc.
But somehow it still happened. I've changed strategy now and excluded all of those rows instead. However i think there is a bug somewhere. I tried to reproduce with various operations but have been unable to. Still i decided it's better you know about the issue -- perhaps something sticks out for your developer even with this much information.



____________________
BR,
Lauri
Back To Top PM Private Upload Quote Reply

 Posted: Sat May 4th, 2019 09:23 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3261
Status: 
Offline
Hi Lauri,
thanks for your feedback. Indeed the DNT flag was meant as some read-only flag for the translation sheet. So the cell is allowed to have data. And if the translator gets a translation package it will also have that same translation and the flag. So even if these rows get imported back the should be the same.
Please keep your eyes open if you find the situation when these calls might become altered. Something that can be reproduced will help.
To me it sounds like your code is different for different languages. Perhaps it is a good idea not to access these resources you don't use anyway in these languages? This way you have the full control about the process.

Right now I fear you need to filter for DNT rows as you do now.
Markus






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

 Posted: Sat May 4th, 2019 12:30 pm
PM Private Upload Quote Reply
lauri
Member
 

Joined: Sat Feb 17th, 2018
Location:  
Posts: 22
Status: 
Offline
Hi Markus!
The code is exactly the same in any language. Sisulizer is making the copy from original and is replacing resources during build process.
The error was because some DNT marked database column properties (which are stored in resources) got changed.
I will let you know when i know for sure what is causing the change. This might take some time.



____________________
BR,
Lauri
Back To Top PM Private Upload Quote Reply

Current time is 11: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 > Rows marked DoNotTranslate get translation



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