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
non translated but correct entries - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Tue Oct 24th, 2017 01:28 pm
PM Private Upload Quote Reply
kendziorra
Member
 

Joined: Thu Aug 22nd, 2013
Location:  
Posts: 3
Status: 
Offline
Hi,
we have some small changes in our original sources.
So the translation (e.g. for french) changed to "Zur Prüfung" (engl. toCheck?). Some entries we changed by Hand to "Vermutung" (engl.: guess?).
So we sent the document to the translation company.
We get back all entries with state "translated". But some entries were correct before and so not changed. Thus the timestamp "changed" was newer than the timestamp for "translated".

This wouldbe the reason, that this rows are not imported and the state in my document were not changed (stay on "Zur Prüfung" and "Vermutung".
I have to compare the translators document and my whole project by hand - thats not so fine.
What is the correct way to handle this?

Back To Top PM Private Upload Quote Reply

 Posted: Tue Oct 24th, 2017 06:58 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Sisulizer during import compare translation values and if they are identical (even if they have different translation statuses in both files) Sisulizer ignores those items. Anyway, I'll ask our developer about potential implementing import statuses when strings in main and imported SLP files are identical. I think it could be useful feature.

BTW:
When Sisulizer detects changes during scan in context or original text, it marks them as Changed rows (red dot in Flag column). Below are some details about changers in context and original strings:
  • Behavior of this for context depends on source platform. If source platform uses real context, for example Windows binary, DotNet or Delphi, Sisulizer simply marks updated item as Changed. When source platform doesn't use real context e.g. text files, html, etc. Sisulizer sometimes can't find "connections" between items and add string with changed context as New row in sheet. If item has changed context, but original string is not changed, Sisulizer automatically re-translate this string (it depends on options in "Tools" menu -> "General" -> "Translations" tab).
  • When you changed original string is a source file, row also will be marked with red dot. If this row contains translation, Sisulizer marks this translation as "Invalidated". When translation has "Complete" translation status, it will be also changed to "For review" status. I think this is good solution, because it remind developer or translator for checking if existing translation is still correct for changed original string. You can compare old and new version of original string directly in Sisulizer sheet, by adding "Previous Original" column to sheet via "View" menu -> "Sheet Columns" dialog. There is also Sheet Columns button on sheet toolbar.
 You can filter items with specified Translation Status in easy way by using our filters. Here is article about this. https://www.the-localization-tool.com/filter-panel-common-filters-for-translation-sheet/ Next you can select all filtered content by e.g. Ctrl+A and change status of all selected items at once by clicking appropriated icon on sheet toolbar or select it by sheet context menu.

Best regards,
Janusz



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

 Posted: Wed Oct 25th, 2017 07:41 am
PM Private Upload Quote Reply
kendziorra
Member
 

Joined: Thu Aug 22nd, 2013
Location:  
Posts: 3
Status: 
Offline
I think the problem is an other ...

Developer: defines original and an "guess" entry for french. So the developer export it to the translator.

Translator: He checks it, find it is OK and dont change it. But because it is OK he sets the status to "translated" and send it back to the developer.

The developer imports the around 100 translations. All are imported, but not the not changed entry with the new status "translated". Now I dont know - did the translator overlooked it or did he accepted it?

The only possibility I found is that the translator add a space to set a new translation time an change it back.

In my Opinion, changing the the status from an other state to translated HAVE TO SET a new translation time. This would be help.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Oct 25th, 2017 10:01 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3846
Status: 
Offline
This what I wrote at the beginning of my previous post. Currently, Sisulizer does not import strings from imported file, if they are identical with strings in your SLP (developer version). Sisulizer ignores also identical strings with different translation statuses. I've already asked our developer about implementing of this. Let's wait on his answer.

You can use following workaround. Make copy of your main SLP. Clear French translations (e.g. by using Ctrl+A and "Clear translation" button). Next import translations from received file.

JAnusz



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

Current time is 08:24 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > non translated but correct entries



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