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
The translation of Javascript files is deleted after build - 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: Tue Feb 7th, 2017 12:09 pm
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

Joined: Fri Sep 18th, 2015
Location:  
Posts: 6
Status: 
Offline
Hello,

I have a Sisulizer project with different sources. One of them is a folder containing .js files.

I have just updated my Sisulizer version from 4.0.364 to 4.0.365. After I select "Build in selected language" by doing right click on the source, the software builds without any problem but suddenly the translation of the .js files disappears and all the strings are "Not Translated".

If I revert back to 4.0.364, the problem disappears.

What can I do? Some of our translators are using the latest version, so we would like to update our version as well.

Thanks a lot in advance.

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

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 7th, 2017 12:21 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

Can you please check if you have unused translations (blue dots). It sounds like the context did change and Sisulizer found all the strings as new ones (while the old ones should be there as unused). Did you perhaps install the new build to a different path. In Sisulizer projects the path to files is part of the context. Please check if that can be the reason.

If this does not help please zip your SLP plus the .js files and use Private Upload (Button right above this post) so we can check that.

Markus



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

 Posted: Tue Feb 7th, 2017 02:08 pm
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

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

thank you very much for your response.

Consider that the source has more than 500 strings. After installing again version 4.0.365 and building the source, there are only 4 "translated" and "unused" strings. More than 500 are "not translated" and "in use".

I installed the new build on the same path of the previous one, choosing the option "Update" (I have always installed new versions in this way).

I don't know if I can upload the project, because there are 5 more sources in addition to the js one, and we manage 6 languages. Is there another way we can proceed?

Thanks a lot.

Best,
Guido.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 7th, 2017 02:53 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2839
Status: 
Offline
Can you then please upload the .slp before and after. Perhaps that helps to see where your translations go. The build process at first scans your sources to make sure it as current as possible. Perhaps you can do a Project - Scan for Changes with the new version and check the output section for info.

Markus



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

 Posted: Tue Feb 7th, 2017 03:06 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1918
Status: 
Offline
No need to upload. There was a new bug introduced in build 365. I fixed it in 366. Now source code scanning works as it used to.

Please use 364 until 366 comes out.

Ilkka



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

 Posted: Tue Feb 7th, 2017 03:09 pm
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

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

thank you very much for your help! We will keep using 364 then.

May I ask you another question related to the "Node not found" message we sometimes receive when we import a translation, or do I have to start a separate thread?

Thanks a lot.

Best,
Guido

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 7th, 2017 03:30 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3679
Status: 
Offline
You get "Node not found" message during import, when you use "By context" or "By context first then by value" import method, and imported SLP contains nodes not available in targeted SLP. For example, you sent a SLP to your translator, but in the meantime you changed source files (removed/added some items). This Sisulizer dialog allows you select correct node (for example when you moved or renamed it in the source file), or discard import.
If you do not use import method based on context (By value), this dialog is not displayed.

Janusz



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

 Posted: Tue Feb 7th, 2017 04:11 pm
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

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

thank you for your answer. I understand you explanation and indeed we use "By context first then by value" method. But the problem is that we get this message even though we do not modify the source in the meanwhile. This is our typical scenario:

- We scan the sources for changes and we do the necessary changes (lock some rows, add notes, removing unused rows, etc.).
- We exchange the translation using the wizard, usually one package per language.
- We "freeze" the source file until we receive the slp file from the translator. We do not apply any change to the source file.
- We import the translation using the exchange wizard.

At this point, we receive the message. What is strange is that the message says there are some nodes that are not found in the destination project, but:

- Actually the nodes are present in the destination project
- The software suggests me to select a target node in case the name of the node has changed. But in the combobox there is always only one node.

Could it depend on the path where we save the files? Condider that:

- The source file is located in "C:projectstranslationMyProject_Source.slp"
- We save the exchanged .sle file in "C:projectstranslationexchangedsentMyProject_ToTranslator.sle"
- We save the received .slp file in "C:projectstranslationexchangedreceivedMyProject_ToTranslator.slp"

I have attached an image to show you what I mean: the message says it cannot find the path "..\src\MeTeDa.UI\App_GlobalResources\*.resx.LTHomeGR.resx" but as you can see the path is present in the tree. And in the combobox there is only one node.

Thanks,
Guido

Attachment: Sisulizer_NodeNotFound.png (Downloaded 10 times)

Last edited on Tue Feb 7th, 2017 04:18 pm by guido.spazzafumo

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 7th, 2017 06:59 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3679
Status: 
Offline
Hi Guido,

Sisulizer uses relative paths, so I think it shouldn't cause this issue. Anyway, could check if you have enabled "Use partial context in the addition of full context" option in the Import Wizard (Options step)? If no, please try check this option and repeat import.

You use localization of directories with multiple resx file. Maybe issue is related somehow to structure of your SLP. Could you send to us MyProject_Source.slp and MyProject_ToTranslator.slp via Private Upload form? I'd like check this.
re is article about our upload system: http://www.the-localization-tool.com/tech-support-and-using-our-upload-form/

Best regrads,
Janusz



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

 Posted: Wed Feb 8th, 2017 08:05 am
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

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

I have just repeated the import enabling the option "Use partial context in the addition of full context", but the message still appear.

I have uploaded the file via Private Upload Form.

Thanks a lot for your help.

Best,
Guido.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 8th, 2017 09:41 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Thank you for files. You are right. We'll investigate it and let you know about results.

Janusz



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

 Posted: Wed Feb 8th, 2017 04:14 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Sorry for delay, but I was out of office...
Please try following trick: Open MyProject_Source.slp file, go to "File" menu, select "Save As..." and replace existing file. Next, close, reopen SLP and use Import Wizard for importing translations from MyProject_ToTranslator.slp. It solved your issue on my machine. Sometimes (for example, after moving SLP to other location), Sisulizer needs to refresh its location for correct using of relative paths.

Best regards,
Janusz



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

 Posted: Fri Feb 10th, 2017 09:44 am
PM Private Upload Quote Reply
guido.spazzafumo
Member
 

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

thank you very much for your help and sorry for the late in replying. Following your suggestion it seems to work. I have tried with a couple of projects and did some tests, and now the message doesn't display anymore.

Thanks again.

Best,
Guido.

Back To Top PM Private Upload Quote Reply

Current time is 12:21 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > The translation of Javascript files is deleted after build



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