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: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Need help on overall workflow - 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: Thu Jul 22nd, 2010 06:47 pm
PM Private Upload Quote Reply
Dave Scofield
Member
 

Joined: Thu Jul 22nd, 2010
Location:  
Posts: 1
Status: 
Offline
We're just getting started with localizing our Delphi app, and I'm looking for somewhere I can read about the overall workflow model of using this tool with a translator. Here is the simplest example that illustrates my questions about workflow:

- 1 developer, 1 translator, 1 language
- The application contains 1 form, with 5 items that need translation.

1. On Monday, I create a package for the translator and send it.
2. On Tuesday, the translator enters translation values for 3 items. Also on Tuesday, I edit the form, and add 3 new items.

How can I update the translator's copy of the project, without the translator losing his work?

Any help on this subject would be greatly appreciated!

Thanks,
Dave



Back To Top PM Private Upload Quote Reply

 Posted: Fri Jul 23rd, 2010 06:56 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

You can import the translations of your translator at any time into your main project. Your translator will prefer to complete the first job you gave him and send the complete project with translations of the initial job.
If you had changes to the original in the meantime (using Project - Scan for Changes to update you main project) then there will be untranslated and changed rows. You can export these in a new echange package for your translator. After the first package is complete.

Translators charge you by the word. They would not like the idea that you change their work load all the time since it make the calculation of the work complicated. They will prefer to complete the chunks you send to them before they get a new chunk. The above workflow respects that.

Hope this helps

Markus



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

Current time is 08:30 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 > Need help on overall workflow



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