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
Resource strings lost when you scan the same .Net solution after few changes - 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: Fri May 11th, 2018 09:14 am
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

Joined: Fri Sep 18th, 2015
Location:  
Posts: 8
Status: 
Offline
Hi,

we are working on the translation of a new project. We regularly realease a new version every 3-4 weeks, and we manage this process using branches. What we would like to do is to start the translation process from a branch, and then, when we release a new version, to scan the solution of the new branch to find only new or changed strings. Supposing we have the following 2 branches:

- Release 1
- Release 2

what we have done so far is:

- Scanning the solution of Release 1
- Excluding projects, rows and so on.
- Marking some projects and strings as "Do not translate"

At the end, we have 5401 strings.

Then we have copied the Sisulizer project into the folder of Release 2, and we have changed the reference to the solution file (see attachments 002a.png and 002b.png). After scanning for changes, we have have the following problems:

- We have 3717 strings.
- All the strings have been marked as "unused".
- There are no "new" strings, even though Release 2 has more strings than Release 1.
- 2 projects of the solution have been removed, even though there are strings in these projects and we marked them as "Do not translate" (we didn't exclude them).

There is one projects of the solution that has 341 strings in Release 1 and 275 in Release 2, even though there are 6 new strings in Release 2 (that by the way are not marked as new...). And other projects have the same problem.

Is there something we are missing? Is this the correct way to proceed when you want to manage more than one release?

There is also another "issue": when we scan for changes, Sisulizer shows the "Multiple Translations Found" window (see attachment 001.png), and there are 3 "Copy" buttons... Is it normal?

Below my system's information:

Application version: 4.0.370
License: Enterprise Edition
Operating system: Windows 7 (Build 7601)
Operating system patch: Service Pack 1

Thank you very much for your help in advance. I hope I have been clear :)

Best Regards,
Guido Spazzafumo (METEDA s.r.l.)

Last edited on Fri May 11th, 2018 09:39 am by guido.spazzafumo

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 11th, 2018 10:08 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

All strings in the Sisulizer project use paths besides the control names as context. If you move the source the context will not match.

There is an easier way. Open the original project (branch a) with all strings. Now add a new source (branch b) to the same project (Project - Add source). Now Sisulizer will find the duplicates by value and you can re-use them easily. No need to have two Sisulizer projects. And both projects will stay in sync. Sisulizer will ask to change all same strings in all branches.

Hope that helps

Markus



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

 Posted: Fri May 11th, 2018 11:07 am
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

Joined: Fri Sep 18th, 2015
Location:  
Posts: 8
Status: 
Offline
Thanks you very much for your answer.

I understand what you suggested, but by doing so, we are forced to change the properties of the new added sources every time. For example the "Excluded Properties", "Excluded Files", "Excluded types", the "Resources" and so on.
Moreover we must mark again the same .Net projects as "Do not translate", or as "Excluded".
Is it correct?

I have just one more questions: does Sisulizer use the strings excluded by "Original" when it scans the added source? For example, if we remove the string "???" in the original project (branch a), when we add a new source (branch b) and Sisulizer scans it, is the string "???" automatically removed? If yes, I suppose it is better to exclude strings by "Original" than excluding the row in our scenario.

Thanks a lot.

Best,
Guido Spazzafumo

Last edited on Fri May 11th, 2018 11:09 am by guido.spazzafumo

Back To Top PM Private Upload Quote Reply

 Posted: Fri May 11th, 2018 03:58 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3088
Status: 
Offline
Sisulizer uses your sources as a sort of blue print for the output. If you exclude parts from scan Sisulizer has to include them in the build anyway. It will just copy these parts to the output. I prefer Do Not Translate since it has the same effect while I can see these string and have better control.

If you have two branches in one project, it is like having two projects - but with the advantage of easy sharing of translations.

All other things are not synced. So yes, Do not Translate needs to be done for every branch.

Btw: There is also an option to merge projects (Project - Merge) in case you already have working projects for both branches.

Markus



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

Current time is 11:36 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Resource strings lost when you scan the same .Net solution after few changes



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