|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer crashes when translating an .slp file
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer crashes when translating an .slp file
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Sisulizer crashes when translating an .slp file - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
interpro Member
|
Dear all, While handling a translation project using Sisulizer Free Edition version 3.0 (build 330), we are experiencing a serious issue that prevents us from completed the translation of one .slp file. Sisulizer crashes during the translation process of this .slp file. Other .slp files have been translated without this problem. I have attached the error message that's displayed when Sisulizer crashes. I tried to find out the origine of the problem without success and I hope that you guys can help me isolate the source of the problem and provide me with a solution. Thank very much ahead of time for your help. Regards, Abdel PS: if you prefer, I can send you the actual .slp file as well. Attachment: ErrMsg.png (Downloaded 30 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
I answered here: http://www.sisulizer.net/forum4/2708.html Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for file. Issue is caused by 2 French translations for _labelTimeFrom and _labelTimeTo components in grid panel of assetcontrolstestassetwindow form (excluded in SLP) in SmartSignal.Client.WPF.csproj source. I'll forward it to our R&D. You can manually remove those French texts from SLP file in third party text or XML editor, but I recommend first create copy of your SLP. You should go in txt/xml editor to in <node class="TXamlFormNode" name="assetcontrolstestassetwindow" filename="..ServiceClientWPFAssetControlsTestAssetWindow.xaml"> node and find following subnodes: <component class="TVisTextBlock" name="_labelTimeTo" state="1" type="System.Windows.Controls.TextBlock"> and <component class="TVisTextBlock" name="_labelTimeTo" state="1" type="System.Windows.Controls.TextBlock"> Next clear text content in <lang> tags. Let me know if you can't do it and you encountered some troubles. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
Can you send me TestAssetWindow.xaml file? Zip the file and click Private Upload to send the file. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
interpro Member
|
Dear Janusz and Ikka, Thank you both for taking the time to look into the issue I submitted. I appreciate it. I will get back to both of you as soon as I can. Kind Regards, Abdel
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
interpro Member
|
Hi Guys, I cleared text context in the tags as Janusz suggested and managed to open the slp succesfully. It looks like no translation has been lost. Before I give back the file to the team to finish the translation, is this all what I needed to do? I am asking the question since Ilkka has requested that we send to him the TestAssetWindow.xaml file and I believe it was sent to him already. Thank you Janusz for your Help I appreciate it a lot. Kind Regards, Abdel
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Abdel, We need the files to improve Sisulizer in a way that this problem does not happen again to you or any other user. We always also try to find a work-around so you do not have to wait for a fix in the software. Seems this work-around worked for you. If we need more info to make the fix we contact you in the forum. Thanks for your report and co-operation Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Abdel,I believe it was sent to him already. Yes, we got this file. Thanks! Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
interpro Member
|
Hi Markus, Thank you for your reply. Thanks to Janusz advise, I managed to open the slp after removing the text he asked me to remove. The same slp is also being translated into Korean and the team did experience the same issue (Sisulizer crashes and the slp can't be reopened). According to my contact, they resolved the problem by splitting the slp file. Do you know if it's possible to split an slp file? Will this work around resolve the problem without any negative impact and how the files thata resulted from th esplit will combined? I am sorry to bother you with so many questions, I just want to avoid having to deal with worse issues while getting close to the due date for this job. Thank you very much for any advise you might have. Kind regards, Abdel
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Abdel,Do you know if it's possible to split an slp file? Will this work around resolve the problem without any negative impact and how the files thata resulted from th esplit will combined? Solution depends on your workflow and how you want split SLP. For example: 1.) If you would like remove some parts from SLP/SLE sent to translators and keep your SLP not changed, you should disable unnecessary parts in Exchange Wizard (e.g. source or selected forms). You can do it in Language and Items step of Export Wizard. Simple double click on unnecessary item in "Items" box. I attached screenshot from your SLP with disabled form caused error (If you don't want share it, I'll remove it). 2.) If you would like split your own SLP, you can do it only on source level. Simple create copy of SLP. From one copy of SLP you remove e.g. first source, from second cope second source, but keep first, etc. In this way you get separated SLP for each source. If you later you would like join all those SLP, simple add removed sources to selected SLP, set up settings and import (with "By context" method) translations from all matched SLP files. Here is short article about this: http://www.the-localization-tool.com/?p=67 Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
interpro Member
|
Hi Janusz, Thank you very once again for your prompt reply and for all the help you provided me with. I really appreciate it a lot. Where should I look for the attached screenshot you mentione din your reply? Kind regards, Abdel
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sorry... I forgot attach it. Here is image: Attachment: screen.png (Downloaded 24 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
interpro Member
|
Thank you very much Janusz for the great support. I appreciate it a lot. Kind regards, Abdel
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator
|
I fixed the bug that caused this problem. The fix will be in the next build (331). It will be released soon. Once you have 331 open your project and rescan it (Project | Scan for Changes) Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
interpro Member
|
Thank you Ilkka. I appreciate it. Kind regards, Abdel
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
interpro Member
|
Hi guys, I am sorry to report that we are experiencing similar issue with the same file that I fixed recently with Janusz help. I will upload a zip file that includes the actual slp file and the screenshot of the error message. Thank you ahead of time for any help you can provide me with. Sincerely, Abdel
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Issue is caused by French translation in ChariotClient.sln -> SmartSignal.HistoricalData.ChartingSmartSignal.HistoricalData.Charting.csproj -> Forms -> historicaldatatagconfigurationcontrol -> Grid[0] -> Grid[2] > Grid[0] -> Grid[0] -> TextBlock[0] -> Content. This is a bit complicated (lot of levels) so I attached screenshot with this structure. Please open your SLP in external TXT/Editor and remove French entry for this item. Janusz Attachment: screen.png (Downloaded 9 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
I recommend you exclude all dangerous/unnecessary items when you generate Exchange package or exclude it permanently in your main project. In this case you needn't disable those items every time when generate Exchange package. Here is article about exclude features: http://www.the-localization-tool.com/?p=454 Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
interpro Member
|
Thank you very much Janusz. I will remove the French entry you highlighted and keep you posted on the result. I will also ask the developpers to exclude all unnecessary items as you suggested. Kind regards,
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
interpro Member
|
The problem has been resolved following your advise Janusz. Thanks a lot for your help. Kind regards, Abdel
|
||||||||||||||||
| |||||||||||||||||
| Current time is 05:02 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer crashes when translating an .slp file | |
Sisulizer software localization tool - Three simple steps to localize
