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
Project file becoming corrupted - 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 Jun 5th, 2018 03:20 pm
PM Private Upload Quote Reply
jenny@iqx.co.uk
Member
 

Joined: Tue Oct 18th, 2016
Location: United Kingdom
Posts: 7
Status: 
Offline
Every time the project is opened in Sisulizer and GREEN ARROW is clicked to create a visual extension of what has been translated, all the rows get updated with a red dot and more worryingly, the ORIGINAL column gets moved and contains the translations instead of the original text.

My Sisulizer version is 4 -Build 372.

Attachment: sisulizer.JPG (Downloaded 11 times)

Back To Top PM Private Upload Quote Reply

 Posted: Tue Jun 5th, 2018 07:14 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3835
Status: 
Offline
When you execute "Run localized source" (green arrow), the Sisulizer performs build operation. Build operation require also scan for changes operation. If your source file was changed in the meantime, you could to see new rows (marked by yellow dots), unused rows (marked by blue dots) and changed rows (marked by red dots) in the Sisulizer sheet. Sometimes scan operation can mix up items with Delphi sources, if there is no path to DRC file, because every time when user compile source file, Delphi reindexes all items in a stringtable. In this case we recommend add DRC file path to Sisulizer project. However, you wrote original strings were replaced by translations. Maybe your source file was replaced by its localized version. Could you check your source file and optionally source/output file pathnames in the Sisulizer? Here is article about source and output settings in a Sisulizer project: https://www.the-localization-tool.com/where-i-can-set-up-output-file-names-and-paths/
Best regards,Janusz



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

 Posted: Fri Jul 20th, 2018 03:29 pm
PM Private Upload Quote Reply
jenny@iqx.co.uk
Member
 

Joined: Tue Oct 18th, 2016
Location: United Kingdom
Posts: 7
Status: 
Offline
Hi Janusz,

Thank you for that, unfortunately my translator does not have either of those options available to her on her eith of those menus. Didn't quite believe her so I dialed in and looked definitely not there. She does have a valid licence but it is a translator's licence.

Thanks

Jenny

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 23rd, 2018 05:20 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3835
Status: 
Offline
I think your source file was replaced by localized version, and for this reason after building (green arrow) you see translated items in the Original column. Every build operation requires also source scan operation. Please check, if your source file is original or localized file. If file was replaced by localized version, please ask your owner of developer version for checking output and source settings in SLP source properties (File tab).
Janusz



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

 Posted: Mon Jul 30th, 2018 09:08 pm
PM Private Upload Quote Reply
Fetra Odilson
Member
 

Joined: Mon Jul 30th, 2018
Location:  
Posts: 4
Status: 
Offline
Hello,

I think I have a pretty similar but more terrible case.
My project file went corrupted after I successfully completed 80% of it (translated). Reason = a short power cut.

And I want to post this in a totally new thread but I don't know.

Please help me.

I was told to retake it back to 0%.

Thanks in advance,

Fetra Odilson

Attachment: non valide.png (Downloaded 2 times)

Last edited on Mon Jul 30th, 2018 09:11 pm by Fetra Odilson

Back To Top PM Private Upload Quote Reply

Current time is 12:34 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Project file becoming corrupted



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