Hi Stephan,

Can you try other docx files and do they work via the API?  If other DOCX work OK,  SDL will need to look more closely at “SecondSample” again and see if the "tw4winMark" style therein is potentially causing the issue.  BTW, In the Studio UI this is can be governed by a setting in Tools – Options – File Types – Word 2007-2010 – Common – Process files with w4winMark style.

Let us know how you get on?

Regards, Ian

Hey Ian,

thanks for the fast reply. I don't know exactly what you mean, so here is a screenshot:

I tried with another *.docx but it didn't work.

Regards,

-Stephan-

Stephan,

Ian probably meant this (Studio 2011 exclusiv, not available in 2009):

Cheers,

*Stefan.

Hey Stefan, Ian

this setting wasn't activated, so I did it in my template and created a new project from it. But still the AutomaticTask

                            AutomaticTask convertTask = project.RunAutomaticTask(currentFileId,
                                    AutomaticTaskTemplateIds.ConvertToTranslatableFormat);

doesn't convert docx to sdlxliff. doc instead works just fine.

Any other idea?

Best regards,

-Stephan Tandel-

Hey Stefan et al,

I have flagged this one to SDL develoeprment for further investigation.  This issue has not been reported before, so I'll be sure to report back once we have some more conclusions.

Regards, Ian

Feedback from the SDL development is, in their test application the conversion of DOCX files works without issue.  We also suggest you find out if any errors were generated when trying to convert the file by using the overload of the RunAutomaticTask method. This will create a list of MessageEventArgs containing the error information. This might determine why this file cannot be converted.  If any errors are present we could use this information to help determine the problem.

//Set up lists to store messages from automatic task

List<TaskStatusEventArgs> taskStatusEventArgsList = new List<TaskStatusEventArgs>();

List<MessageEventArgs> messageEventArgsList = new List<MessageEventArgs>();

//Call RunAutomaticTask method and collect any error information

AutomaticTask task = createdProject.RunAutomaticTask(

currentFileId,

AutomaticTaskTemplateIds.ConvertToTranslatableFormat,

(sender, taskStatusArgs) =>{ taskStatusEventArgsList.Add(taskStatusArgs); },

(sender, messageArgs) =>{ messageEventArgsList.Add(messageArgs); }

);

//Display error messages

foreach (MessageEventArgs errorMsg in messageEventArgsList)

{

Console.WriteLine(errorMsg.Message);

}

Additional points;

1/ A copy of the files you are trying to convert would be useful.

2/ What version of MSWord do you have installed on the machine where they are running the task?

Feedback from the SDL development is, in their test application the conversion of DOCX files works without issue.  We also suggest you find out if any errors were generated when trying to convert the file by using the overload of the RunAutomaticTask method. This will create a list of MessageEventArgs containing the error information. This might determine why this file cannot be converted.  If any errors are present we could use this information to help determine the problem.

//Set up lists to store messages from automatic task

List<TaskStatusEventArgs> taskStatusEventArgsList = new List<TaskStatusEventArgs>();

List<MessageEventArgs> messageEventArgsList = new List<MessageEventArgs>();

//Call RunAutomaticTask method and collect any error information

AutomaticTask task = createdProject.RunAutomaticTask(

currentFileId,

AutomaticTaskTemplateIds.ConvertToTranslatableFormat,

(sender, taskStatusArgs) =>{ taskStatusEventArgsList.Add(taskStatusArgs); },

(sender, messageArgs) =>{ messageEventArgsList.Add(messageArgs); }

);

//Display error messages

foreach (MessageEventArgs errorMsg in messageEventArgsList)

{

Console.WriteLine(errorMsg.Message);

}

Additional points;

1/ A copy of the files you are trying to convert would be useful.

2/ What version of MSWord do you have installed on the machine where they are running the task?

Hello Ian,

thank you for further investigating that problem. I will try to do what you wrote and will tell you what happens. In the mean time, I've found out, that xlsx is no problem. It just seems to be docx.

Thank you!

Hello Ian,

now it works, YAY.

The problem was Spring.Core.DLL. We send all tasks to our connector using JMS. And there for I added a different version of that DLL. I had a warning in Visual Studio but ignored it. Now I replaced the new Spring.Core.dll with the default one from Studio and it works now. And messaging works as well.

Thank you, best regards and a beautiful weekend,

-Stephan-