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: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
"Do not translate" strings are translated - 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: Thu Feb 18th, 2010 03:27 pm
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 184
Status: 
Offline
Dear all,

we succesfully imported our Multilizer project into Sisulizer. With build 296, we also imported the "Do not translate" status into Sisulizer. Everything looked great.

But unfortunately, the "Do not translate" strings are still translated, I checked the localised output DLL.

We are using the following:

* Sisulizer build 291 (for compatibilty reasons concerning our build machine)
* C++, MFC code
* Multilanguage file
* Language Properties: Country = Neutral

Do you have any idea what's causing the problem? We did not observe this before with Dotnet stuff.

Best regards, Christine

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 18th, 2010 08:59 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2115
Status: 
Offline
Hi Christine,

Please check Poject - Edit Source - <your source> - Options - Items that localized... and set it to Translated. It will exclude empty rows.

Btw: The Do Not translate status is sign for your translator not to enter translations. It sets the row to read only. So if there is already a translation in the row setting the status will not remove the translation.

Please check this article for more info about the possibilities:

http://www.the-localization-tool.com/?p=454

Hope this helps

Markus



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

 Posted: Fri Feb 19th, 2010 08:47 am
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 184
Status: 
Offline
Dear Markus,

thanks for your response. Actually, this worries me. We use the "Do not translate" feature for marking strings that must not be translated to avoid malfunctions of the software, for about 2 years now.
First of all, the command is called "Do not translate", which suggests, well, that they are not translated. If this is not the case, "Lock translation" might be a better string.
Even though I do not find a forum entry, I am pretty sure I asked about this feature in the past and I got a different explanation. Also, I doubt we would not have noticed it if this had always been this way. Is it possible that the feature was changed? Or that it works different for Dotnet?

So what can I do about it now? Actually, I really do not like to exclude the strings, because I won't see them anymore in the project. If later on there is an issue (a bad string showing up, for example) I cannot search for it.
Also, we have projects with 3000 strings that must not be translated. Won't there be a performance issue with the Exclude list?

Any suggestions would be greatly appreciated.

Christine

Back To Top PM Private Upload Quote Reply

 Posted: Fri Feb 19th, 2010 09:21 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
Hello Christine,

Also, I doubt we would not have noticed it if this had always been this way. Is it possible that the feature was changed? Or that it works different for Dotnet?
No, this feature wasn't changed and work in this same way for all platform.

So what can I do about it now? Actually, I really do not like to exclude the strings, because I won't see them anymore in the project.
You can always include these strings to project by "Project", but if you don't want exclude it, you can still use "Do not translate" feature, but first you should find and clear existing translations for items with "Do not translate" status. You can use filter feature for this, that is:
- Go to "View" menu -> "Sheet Filters" -> "Edit" -> "Other" tab -> "Do not translate" and set up filter as "True"
- Select whole column's contents by "Project" menu -> "Select column" (or by column context menu)
- Turn off "Do not translate" status for all rows by click on sheet's toolbar icon, via sheet context menu or "Row" menu
- Clear all translations in selected column
- Check again "Do not translate status" for selected contents. It should prevent typing of translations for these strings in future.
- Reset filters.


Best regards,
Janusz

Attachment: screen.png (Downloaded 16 times)



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

 Posted: Fri Feb 19th, 2010 09:27 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
If you will find translations for these items (cleared as described above) in future, it probably means bug in Sisulizer. Of course, we really appreciate all reports about similar cases, because it allows us improve Sisulizer.

Best regards,
Janusz



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

 Posted: Fri Feb 19th, 2010 09:43 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
I forgot about one thing...
You can use this same filter in Exchange Wizard ("Exchange Wizard - Filter" step -> "Other" tab -> "Do not translate") with "False" value. It exclude all items with "Do not translate" status from exchange package send to your translators (these items are unavailable for them), while these items still exist in your main project.

Best regards,
Janusz



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

 Posted: Fri Feb 19th, 2010 10:59 am
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 184
Status: 
Offline
Dear Janusz

thank you, using the filter is a very good suggestion.

I guess I have observed that sometimes translations are imported even for strings in "do not translate" status. If this should happen again, I will let you know.

Best regards, Christine

Back To Top PM Private Upload Quote Reply

Current time is 08:43 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > "Do not translate" strings are translated



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

Sisulizer software localization tool - Three simple steps to localize