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
Strings are 'missing', build 368 - 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: Mon Aug 7th, 2017 01:36 pm
PM Private Upload Quote Reply
meta
Member
 

Joined: Wed Oct 14th, 2009
Location: Sweden
Posts: 112
Status: 
Offline
Hi!
The scans and builds of our projects are performed on a build server. We use Tortoise to copy the project to my local PC where the translations are performed.
Three strings are translated but the translations do not show up in the application and when I check the build server there are some objects missing from the tree view.
How can that be? Needless to say I use the same filters....
When debugging the slp file the strings are there anyway!
The State tag in the component class is set to 0. For other similare parts of the slp the State tag is not showing.
Sorry about the fuzzy description, it is my first day back from vacation.... :whatever: Meta

Last edited on Mon Aug 7th, 2017 01:50 pm by meta

Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 7th, 2017 03:09 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Hmm... I need more info about this. It could have couple reasons, for example:
  • Source files on build server were changed in the meantime and after scan/build there are missed items.
  • Your SLP and SLP on build server have different source properties, for example checked/unchecked different items in "Resources" or "Excluded Types" tabs. But it depends on your source platform type.
  • SLP on build server has excluded some Rows, Originals or Strings. It can be checked via appropriated menu items in the "Project" menu.
Let me know, if you'll find out more.

it is my first day back from vacation.... :whatever: Meta
I understand you. I also back from my vacation a few days ago.

Janusz



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

 Posted: Tue Aug 8th, 2017 09:13 am
PM Private Upload Quote Reply
meta
Member
 

Joined: Wed Oct 14th, 2009
Location: Sweden
Posts: 112
Status: 
Offline
Hi Janusz and thanks for your quick reply.

We use .NET platform.

Let me try to explain...
1. We use Tortoise repository for keeping track on all files and versions.
2. Sisulizer (same version) is installed both locally and on build server
3. Translations are performed locally after updating slp file from build server. When translation is finished for the day, the slp file is committed.
4. All scannings, builds as well as adding or removing sources are performed during the night on the build server. Before scanning, build etc the slp file is updated from the repository, after build it is committed to the repository again.
I was under the impression that the settings of the project (excluded rows etc) is indeed saved IN the project and not in Sisulizer application. The same for the source properties. Anyway, I compared them and they are exactly the same.
The icons in the tree view sometimes look slightly different, why is that? Tick is missing and 100% shown in grey color. Pic will be sent!

KR
Meta

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 8th, 2017 08:43 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3741
Status: 
Offline
Thank you for screenshots, but both images are identical.

meta wrote:

The icons in the tree view sometimes look slightly different, why is that? Tick is missing and 100% shown in grey color.!

It means all items are translated in selected node, but not all translations have Completed status. If you change status of all translations in node to Completed, this node will be indicated by thick symbol and green 100% stat value next to node name. You can find all items without Completed status (and check them) by using Project Tree filters. Here is article about Project Tree filters: https://www.the-localization-tool.com/i-want-to-find-nodes-with-not-translated-items-how-i-can-do-it/
Node items can get lower translation status e.g. Auto translated instead Completed for example by:
  • Manually changing it by user
  • After import, and it depend on "Import translation status" settings in the Import Wizard (Options step)
  • After updating of source, if Sisulizer automatically translate new/changed rows. You can enable/disable this feature in "Tools" menu -> "General" -> "Translations" tab.
Janusz



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

 Posted: Wed Aug 9th, 2017 05:22 am
PM Private Upload Quote Reply
meta
Member
 

Joined: Wed Oct 14th, 2009
Location: Sweden
Posts: 112
Status: 
Offline
OK sorry about the pics, I wasn't sure that you would accept that format.
Thanks for the clarification.
How about the real issue, any ideas there?
:) Meta

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 10:51 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

State="0" means "New" row/node status, so items with this attribute probably were added recently during scan operation of updated source.
If those new items are not localized in the targeted localized version, it could have following reasons:
  • New source code is not fully compatible with localization purposes. Usually it concerns hard-coded strings, but they rather shouldn't be visible in the Sisulizer Sheet.
  • New strings are not translated.
  • New strings are translated but translations have lower status than status set in the "Project" -> "Options" -> "When building use translations that have at least this status".
If SLP files on your computer and build server are identical, but files are displayed differently it could be result of filtering/displaying settings. Sisulizer saves visual and filter settings of project to separated file with SDS extension. You can check this, by replacing your local SDS file with file imported from build server. If you remove SDS file, Sisulizer automatically generate new after saving SLP.

BTW:
Could you upload to us screensots with differences between Project Tree on your local computer and build server?

Janusz



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

Current time is 08:48 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Strings are 'missing', build 368



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