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
1.0.176: Excluded string resources are exported - 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: Mon Aug 21st, 2006 04:30 pm
PM Private Upload Quote Reply
Taylor
Member
 

Joined: Tue Jul 25th, 2006
Location:  
Posts: 22
Status: 
Offline
I opened a managed assembly that had multiple string tables.  I excluded the ones I didn't want and they properly greyed out.  Then, I went to export my project, and my exported tables were included as well.  I would have expected them to not be exported. 

The good news is that marking them as "Read Only" prevented them from being exported, and that is an acceptable workaround for now.  Still, it was definitely some buggy behavior that surprised my translating team.

Please let me know if you need more detail.

Last edited on Mon Aug 21st, 2006 04:31 pm by Taylor

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 22nd, 2006 09:19 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
I will fix this

Jaakko



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

 Posted: Tue Aug 22nd, 2006 02:07 pm
PM Private Upload Quote Reply
Taylor
Member
 

Joined: Tue Jul 25th, 2006
Location:  
Posts: 22
Status: 
Offline
Great - thanks Jaakko!

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 23rd, 2006 12:54 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

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

Just to make sure that I got your case correctly I attached a screen shot. It has a .NET application that has several string resources. One of them have been excluded (is grayed and I drawed red ellipse around it).

Is it so that you do not want the translator to get the excluded string resource node?

I agree. It should not be included to the exchange package. I will remove it.

You can also exclude individual rows but they (excluded) are not shown to to the translator.

Best regards,

Jaakko



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

 Posted: Wed Aug 23rd, 2006 12:59 am
PM Private Upload Quote Reply
Taylor
Member
 

Joined: Tue Jul 25th, 2006
Location:  
Posts: 22
Status: 
Offline
This sounds exactly right from the description.  In fact, there are two issues that you bring up.

1: You are correct: I don't want the translator to get strings that are excluded, either on a per-row basis or on a string resource basis.

2: If I export a text file from the UI in my full copy of SIsulizer, I would have expected it not to export the excluded strings either, although this suggestion has much less weight, as I don't expect to be exporting and importing many strings files with my copy.  The translators will be doing that.  I just wanted to point out what I expected the behavior to be...

Many thanks,

Taylor

P.S. I did not see the attached screenshot.  Can you try again just to be sure?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 23rd, 2006 01:19 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
Sorry. I forgot the screen shot.

Jaakko

Attachment: Exclude.PNG (Downloaded 6 times)



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

 Posted: Wed Aug 23rd, 2006 01:22 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
You are right. When creating an exchange package indivisual excluded row are automatically hidden. However when exporting to Text to TMX file they are included. This is a bug. I correct it.

Jaakko



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

 Posted: Wed Aug 23rd, 2006 01:32 am
PM Private Upload Quote Reply
Taylor
Member
 

Joined: Tue Jul 25th, 2006
Location:  
Posts: 22
Status: 
Offline
Yep - we're talking about the exact same thing.  Thanks!

 

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 23rd, 2006 01:39 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
I fixed this.

1) If a node (e.g. resource) is excluded it is not exchanged or exported.

2) If a row is excluded it is not exported but it is exchange (because editor might need it) but it is not show to the translator.

Let me know if there is something else to be fixed.

Jaakko



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

 Posted: Wed Aug 23rd, 2006 04:38 am
PM Private Upload Quote Reply
Taylor
Member
 

Joined: Tue Jul 25th, 2006
Location:  
Posts: 22
Status: 
Offline
That sounds great Jaakko!

Thanks for the quick turnaround.

Back To Top PM Private Upload Quote Reply

Current time is 03:56 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > 1.0.176: Excluded string resources are exported



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