Support forum of the software localization tool Sisulizer


Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... 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
Cannot exclude strings - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...
AuthorPost
 Posted: Mon Sep 15th, 2008 12:26 pm
PM Quote Reply
jonaliz55
Member
 

Joined: Mon Sep 15th, 2008
Location:  
Posts: 10
Status: 
Offline
I defined the string %1$s as a string for exclusion in both the project (under Project, Excluded strings) and general (under Tools, General, Excluded Strings) sections, but when I compile and build a local translation file the excluded string still appears.

A portion of the relevant source file follows below my signature.

Please advise.

Many thanks

Jonny

Source File

provider = Vringo
EnterVringoPassword = Enter your Vringo password:

Share.ShareEmail       = Share via email
Share.ShareSMS         = Share via SMS
Share.ShareSMSText     = %1$s would like to share a Vringo with you. Click below to watch it.  [[url]]
Share.ShareChannnelSMSText = Your friend at %1$s would like to share with you %2$s Video Ringtone: %3$s

Share.aboutVringo      = Vringo is about video ringtones. It is a new way to share video on your mobile phone by choosing what displays on your buddies' handset when you call them.
Share.defaultMessage   = See this great Vringo!
Share.enterEmail       = Enter an email address to share your Vringo
Share.enterPhoneNumber = Enter a phone number to share your Vringo (ex. 1-410555121)
Share.messageSent      = Your message has been sent.
Share.usersVringo      = %1$s's Vringo

 

Back To Top PM Quote Reply

 Posted: Mon Sep 15th, 2008 12:45 pm
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 780
Status: 
Offline
Hi Jonny,

"excluding strings" removes this strings from the list of strings in the translation sheet. It is used if you have strings that better be not localized, like SQL query strings. Your translator will not see them and thus can not translate them in a wrong manner. Btw: If there is no localization Sisulizer will use the original strings.

The structure of the build file has to be the same as the original.

Best

Markus




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

 Posted: Mon Sep 15th, 2008 01:38 pm
PM Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 446
Status: 
Offline
Sisulizer is localization tool and by default Sisulizer do not change structure of localized files, of course Sisulizer can to compile your Delphi or .NET Visual Studio projects to targeted files, but if you want remove or add new strings to your file, you should to do it in your developer tool. This solution protect developers against changes in their files by translators without developers permissions.
Janusz



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

 Posted: Wed Sep 17th, 2008 03:17 pm
PM Quote Reply
jonaliz55
Member
 

Joined: Mon Sep 15th, 2008
Location:  
Posts: 10
Status: 
Offline
I understand that "excluding strings" removes the string from the list of strings in the translation sheet. But I cannot get this feature to work. The "excluded strings" appear in the original when I build and send it to the translator with the "Exchange" option. Is it possible to discuss this by phone?

thanks
Jonny

Back To Top PM Quote Reply

 Posted: Wed Sep 17th, 2008 03:40 pm
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 780
Status: 
Offline
Hi,

while this is a source filter it will work the next time you use "Project - San for Changes". Have you been aware of that?

Our team is split on four countries. The whole team meets its customer only in this forum.

Markus



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

 Posted: Tue Sep 23rd, 2008 11:50 am
PM Quote Reply
jonaliz55
Member
 

Joined: Mon Sep 15th, 2008
Location:  
Posts: 10
Status: 
Offline
Is there a way I can exclude the parameter "%1$s" from a string if the full string is, for example, "%1$s would like to share a Vringo with you."?
In this case I would like the translator to translate the whole string except the sub-string "%1$s".
If this is not possible, is it at least possible to perform a translation validation where if the string "%1$s" exists in the source string, then it appears in the translation string as well?

We are evaluating Sisulizer at the moment and without a solution to this issue we cannot proceed with the evaluation.

Many thanks
Jonny

Back To Top PM Quote Reply

 Posted: Tue Sep 23rd, 2008 12:02 pm
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
%1$s seems like a message placeholder but $ is something I have never seen on any placeholder. What is your orignal file? Windows EXE compiled by VC++ or something else.

The problem is that Sisulizer does not detect %1$s as placeholder. If it could do that validation would also warn if the translation does not have it.

Please send me more informaiton so I can change the detection code to detect this.

You can send the file to

support (at) sisulizer.fi

Jaakko



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

 Posted: Tue Sep 23rd, 2008 12:50 pm
PM Quote Reply
jonaliz55
Member
 

Joined: Mon Sep 15th, 2008
Location:  
Posts: 10
Status: 
Offline
This is Java’s string formatting syntax. For example:

String.format(“Welcome, %1$s. You have %2$d goats.”, name, numGoats);

We have other placeholders as well like [[url]]. Is it possible to customize the placeholder characters so that we can define what our placeholders are?

Back To Top PM Quote Reply

 Posted: Tue Sep 23rd, 2008 01:11 pm
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
It seems that they have two different formatter string formats in Java. Sisulizer currently detects this

https://java.sun.com/j2se/1.5.0/docs/api/java/text/MessageFormat.html

But your files are using this

http://java.sun.com/j2se/1.5.0/docs/api/java/util/Formatter.html#syntax

Stange that same platform has two different formats. Anyway I will implement support for thise second one. I try to get it done for next week's build.

Thank you for pointing this out.

Jaakko



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

 Posted: Tue Sep 23rd, 2008 01:28 pm
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
This another format seemed to be the same as in C/C++. We already have implemented that so I could take it in use and implemented message format string dectection and validation for these kind of Java strings as well. The new feature is in build 272 that will come out early next week.

Jaakko



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

 Posted: Tue Sep 23rd, 2008 01:30 pm
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
jonaliz55 wrote: We have other placeholders as well like [[url]]. Is it possible to customize the placeholder characters so that we can define what our placeholders are?
Is this [[url]] your own format or is it used by some Java class?

Jaakko



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

 Posted: Tue Sep 23rd, 2008 01:58 pm
PM Quote Reply
jonaliz55
Member
 

Joined: Mon Sep 15th, 2008
Location:  
Posts: 10
Status: 
Offline
It is our own format.

Back To Top PM Quote Reply

 Posted: Tue Sep 23rd, 2008 02:08 pm
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
I don't have any quick solution for this.  We might implement a feature where you can define your own message pattern format. I have added this to TODO list. Right now I recommend you to instruct translator to keep [[url]] in the translated text and just move it to the right position.

I hope that thise new Sl feature by detecting %... will help you a bit.

Jaakko



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

 Posted: Wed Sep 24th, 2008 10:06 am
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
jonaliz55 wrote: Share.ShareSMSText     = %1$s would like to share a Vringo with you. Click below to watch it.  [[url]] 

As I wrote yesterday build 272 will have automatic desction of message string placeholders (bold text). A new thing we decided to implement too in 272 is that you can give a list of string that must be in the translations. The above text contains [[url]] that also must be in the translation but it can of cource be on the different postion as last (the grammer of some language may required it). In that case you add [[url]] to the list of required string of that row and Sisulizer will make sure that the translated string contains it. The both checks are performed via validation (Validate | Validate translation). If either message placehoder or required string is missing a validation error is show and translator can easily fix it.

Jaakko



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

 Posted: Thu Sep 25th, 2008 12:16 am
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
Required strings feature is now implemented and will be in the next build (272). Let's me explain how to use it.

1) Open your Sisulizer project
2) Right click the left side of the row that cotains strings that are required (e.g. [[url]]). Note the checking of Java's standard placeholders (e.g. %1$s) is now automatic an not manual editing is required)
3) Choose Row | Required Strings. Enter the required string in the dialog.

See the screenshot.

Now you have edited the information needed for Sisulizer project. In the next reply I will explain how to run validation to check errors.

Jaakko

Attachment: Untitled.png (Downloaded 11 times)



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

 Posted: Thu Sep 25th, 2008 12:19 am
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1533
Status: 
Online
To run validation choose Validation | Validate translation. A dialog box appers. Click OK to start validation process. Sisulizer will add all validation error on Validation Results pane on the bottom side of Sisulizer workspace. If you click an item on the Validation Result pane Sisulizer will select the row where the error is and you can fix it.

Build 272 will come out early next week.

Jaakko

Attachment: Untitled1.png (Downloaded 12 times)



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

Current time is 04:13 pm  
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Cannot exclude strings



WowUltra 1.11 Copyright © 2007 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize