Support forum of the software localization tool Sisulizer


Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... 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
How is the translation memory supposed to work? - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...
AuthorPost
 Posted: Thu Nov 22nd, 2007 08:26 am
PM Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 46
Status: 
Offline
Dear all,

I could not find any detailed information on it in the Help, therefore I have several questions.

1.) As far as I understood, there is a single embedded TM for all my projects, or is there one for each project? [I want to make sure to use a consistent language over all my projects.]

2.) When and how exactly are terms from a project saved into the TM? I used the command "File > Save to Translation Memory", but got the result "0 translations saved". When I then opened another project and used the command "Translate using Translation Engine", only terms that I fed into the TM from the Microsoft Glossary were translated, but not from my other project.

3.) If a term that was already in the TM gets a new translation, how is that handled (old overwritten, new not saved, both alternatives saved)?

4.) If the source term is modified, i. e. there is a translation but the source term is not existing anymore, what happens to the translation (simply deleted? tagged as "not in use"?, "old" source string kept?) (I have the problem that there are several cases where the source strings needs to be revised, though I want to use the translation of the original later.)

I am in the moment using the evaluation version and the answers to these questions are crucial for me. Thank you in advance.

Best regards, Christine

Back To Top PM Quote Reply

 Posted: Thu Nov 22nd, 2007 10:12 am
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 831
Status: 
Offline
Hi Christine,

to 1) You can have multiple TM for each project. Or you can have one TM for all your projects. If you use the Enterprise Edition you can even use one TM by multiple user at the very same time. Sisulizer is very flexible with that. The TMs are external database files and are not embedded in the project file. The term embedded means, that it is a TM engine shipped with Sisulizer and not an external one like e.g. Trados. If you click Tools -> Translation Engines -> Left (+) Button you can add more TMs.

to 2) Only rows with the status "Complete" or better are saved to TM. You can change that in Tools -> Translation Engines -> Common Settings -> Add string if the status is greater or equal to.

to 3) You can select that with Tools -> Translation Engines -> Common Settings -> Overwrite current strings.

to 4) The Sisulizer TM keeps all the translations. You will be able to edit it with the upcomming TM editor planned for next year.

If you import glossaries with Tools -> Translation Engines -> Documents -> Right (+) Button you can later delete all entries if you use
Tools -> Translation Engines -> Documents -> Right (X) Button.

Btw: In Sisulizer the best way to re-use translations is simply to use Project -> Scan for Changes. See our movie: http://www.sisulizer.com/swf/sisulizer-scanforchanges.shtml

The trick is to place the newest build of your binaries or sources in the same path where the old build was. Then you simply use Scan for Changes are Sisulizer reuses all existing translations in the project. This will reuse existing translation based on their context. If you resuse translations using a TM they will be assigned using its value only. And while translations can be different in different context it is better to assign strings by its context like Scan for Changes does it.

The TM should be used if you
a) share translations in your team. But your translators has to check every auto-translated item.
b) reuse translations between two independend projects where Scan for Changes can not be used.

Best

Markus



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

 Posted: Thu Nov 22nd, 2007 12:54 pm
PM Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 46
Status: 
Offline
Dear Markus,

thank you very much, your explanations were a really big help.

Could you recommend a best way to connect Sizulizer to Across (I need the software terminology for translating the user manuals in Across). Is the only possibility via export/import the TMS as CSV? Or is there another way via the SQL-Server, for instance?

The other way round, I am thinking about also loc. the Help/Manual in Sizulizer.
Word-XML files are not supported, right? (I tried to load one, but got an Access Violation.

I selected an XML tag for loc., but the attribute still does not show up in Sizulizer. What did I do wrong?

Best regards, Christine

Back To Top PM Quote Reply

 Posted: Thu Nov 22nd, 2007 01:07 pm
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 831
Status: 
Offline
Hi Christine,

>>Could you recommend a best way to connect Sizulizer to Across (I need the software terminology for translating the user manuals in Across). Is the only possibility via export/import the TMS as CSV? Or is there another way via the SQL-Server, for instance?<<


the probalby best way should be to use the TMX format. It was made to exchange translations. CSV can work but you might encounter problems with different charsets and the fact that the structure of CSVs are not defined. TMX format is defined and as XML format it is full UNICODE aware.

>>The other way round, I am thinking about also loc. the Help/Manual in Sizulizer.
Word-XML files are not supported, right? (I tried to load one, but got an Access Violation.<<


No we do not have DocX support now. Basically .DocX files are XMLs packed into a ZIP file.

>>I selected an XML tag for loc., but the attribute still does not show up in Sizulizer. What did I do wrong?<<


You mean a XML tag from DocX-XML? We do not support that yet. Our developers will have to look into that before we can officially support that special XML structure. We support XML but DocX has some specialities. Support for that is defenitly on our road map for 2008.

Best

Markus



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

 Posted: Mon Nov 26th, 2007 12:55 pm
PM Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 46
Status: 
Offline
You mean a XML tag from DocX-XML? We do not support that yet. Our developers will have to look into that before we can officially support that special XML structure. We support XML but DocX has some specialities. Support for that is defenitly on our road map for 2008.



No, I mean an XML tag from a standard XML file, in this case the following:

<MadCap:keyword term="ICC" />ICC Color Management</h2>

I wanted to tag the attribute, that is, "ICC" as editable, but it did not work.

Back To Top PM Quote Reply

 Posted: Mon Nov 26th, 2007 01:22 pm
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 831
Status: 
Offline
Hi Christine,

to localize XML in Sisulizer you need to have one context for each value, e.g:

<?xml version="1.0" encoding="UTF-8" ?>     
<dataitems>         
<dbstring>              
<value id="test1-context">test1-value</value>      
</dbstring>         
<dbstring>              
<value id="test2-context">test2-value</value>      
</dbstring>
 </dataitems>

In the sample above id=test1-context is the context and test1-value is the values of row 1 and so on.

Your sample tag <MadCap:keyword term="ICC" /> does either not have a value or a context.

Best

Markus





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

 Posted: Wed Jan 2nd, 2008 04:15 pm
PM Quote Reply
Sophie Rattier
Member
 

Joined: Wed Jan 2nd, 2008
Location:  
Posts: 4
Status: 
Offline
I also have a question towards automatic translation. I am using the evaluation version. My edited language is french. I did not save anything by "File/Save to translation memory", and directly used the option "Translate Using Translation engine". I tried with the type "Embedded" and then with "WorldLingo". The result is that some strings were translated correctly or almost in french but others were translated in finnish (or something looking like germain?). How does it work exatly? Does all the translation engine type have a default dictionnary?

Back To Top PM Quote Reply

 Posted: Wed Jan 2nd, 2008 04:38 pm
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 831
Status: 
Offline
Hi,

WorldLingo is a third party service. With Sisulizer comes a WordLingo demo account. This automatically translates to give you an idea how it works but the output language is random.
To really use it you need an own accounts from here: http://www.worldlingo.com/en/products/api_pricing.html

Please be adware that machine translation does not even come close to the quality of a human translator.

Best

Markus



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

Current time is 02:42 am  
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > How is the translation memory supposed to work?



WowUltra 1.11 Copyright © 2007 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize