Katja Heimann-Kiefer

Katja Heimann-Kiefer said:

[After the Studio update my custom Batch Task was gone and I couldn't define it again. I am SERIOUSLY annoyed about this because the default batch tasks offered by Studio are not what I need and now I'm stuck with these useless options!!]

I'd be suspicious of this.  You presumably have the Freelance version and must have created this custom task while it was running in professional mode, perhaps during the trial period?  So you now have a template that refers to something that shouldn't be there and the update removed it... or something like that.

Perhaps...if you tell me what tasks you used before I can send you the information you need to add to your Project Template and then see whether that resolves the problem.  A bit of a long shot but this seems to be related because details of the original customised task will be stored in your sdlproj as well.

Perhaps you can also send me your sdlproj so I have a reference file.

Hi Paul,

thank you so much for looking into this.

I don't think the batch tasks have anything to do with my problem. After all, I only did the update *because* I was having these problems in the first place. Until then everything had been running fine - with my customised workflow. It was the update that deleted my customised task sequence, but the problems were there before the update. The TM problems will be solved eventually but my task sequence is gone for good, that's what makes this particular bit so annoying.

Nevertheless, the update deleting my custom settings is only a side issue. I needed to get rid of those error messages that appeared out of the blue and impeded my working.

I created the project from scratch - same errors.

Then I tried something else: I deleted the TM filters I was using. Now it seems to be working. That would be very nice (except that I do need the filters). I'll do some more work over the next days and will let you know if the problem reappears.

I had already created a sanitised version of the sdlproj file for you, obscuring all names and file names that could have pointed to the client in question (NDAs...). I can send you that if needed for further problems.

Now it would be nice to get the filters back to work, but I'll fiddle around with that some more.

And about those batch tasks: Yes, I use the demo period to create a batch task without project memories and without any kind of pretranslation. I need it available when I add files to an existing project, not only for creating a new project (that's still there). If you can resolve that and give that back to me, that would be fantastic.

But for the moment: Have a good Easter break and stay healthy.

Katja

Katja Heimann-Kiefer

Katja Heimann-Kiefer said:

I don't think the batch tasks have anything to do with my problem. After all, I only did the update *because* I was having these problems in the first place.

ok - that's good then.  CU6 was released yesterday and you said you just started having problems which is why I wondered.

You also said:

Katja Heimann-Kiefer said:

Every time when they send me something to translate, I add the new files to the existing project.

That existing project will have references to these custom batch tasks...hence why I wondered about that.

Katja Heimann-Kiefer said:

And about those batch tasks: Yes, I use the demo period to create a batch task without project memories and without any kind of pretranslation. I need it available when I add files to an existing project, not only for creating a new project (that's still there). If you can resolve that and give that back to me, that would be fantastic.

Try this:

1. Close Studio
   
   
2. Copy your default template to another folder for safe keeping
   
   
3. Open the original (not the copy) in a text editor and look for this (or something like it)
   
      <SubTaskTemplates>
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.Conversion" />
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.Split" />
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.PerfectMatch" />
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.Translate" />
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.Analysis" />
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.ProjectTm" />
      </SubTaskTemplates>
   
   
4. Delete the unwanted lines to leave this:
   
      <SubTaskTemplates>
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.Conversion" />
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.Split" />
        <SubTaskTemplate TaskTemplateId="Sdl.ProjectApi.AutomaticTasks.Analysis" />
      </SubTaskTemplates>
   
   
5. Restart Studio and create a project with your default template

Hi Paul,

thanks a lot. It's really cool to see where those settings are stored.

I did what you suggested and edited several project templates plus the "projects.xml" file. However, when I add new files to my old existing project I still only get the basic default batch tasks offered. What I do: In the language of origin I add new files to my project, right-click on them and select "Add Files > Add Files and Select Batch Task". It's here where I expect my customised batch task to appear. Any ideas?

(I had given it a name when I created it and I still see that name in the text editor, but it's not offered as an option I can select.)

As for the original problem: It appears it started when I edited the filters I had been using for years. As a workaround I did some filtered exports and imports on my TMs and am now using penalties on a TM level. This seems to work so I'm happy with that.

Best regards

Katja

Katja Heimann-Kiefer

Katja Heimann-Kiefer said:

However, when I add new files to my old existing project I still only get the basic default batch tasks offered.

No surprises there.  I mentioned earlier that the existing project will have references to these custom batch tasks.  So you need to edit the tasks in the *.sdlproj as well and then it "might" resolve your problem.

Hi Paul,

(happy Easter!)

Editing the .sdlproj didn't resolve my problem for adding new files to the project. I edited those  <SubTaskTemplates> wherever I found them but was not getting the task combination I need. I then created a new project (losing all sub-folders but some .sdlproj tweaking solved that), and now it works.

So, all problems seem to be solved now. I am genuinely grateful for your support. Still, may I send you some general thoughts?

I don't understand why SDL so stubbornly resists offering users the possibility to configure default settings in Studio: batch tasks (why am I forced to choose between project TMs or pretranslation when I don't want either?), default paths for saving projects, TMs, termbanks or return packages (Like, Trados always thinks I want to save my current project's return package in the previous project's folder - so illogical! And while I have all my work on a separate partition, Trados is again and again suggesting locations in the Windows libraries on C).

Of course it makes sense to offer default settings and workflows for less savvy users, but what's the harm in letting people change them when they just don't suit? We all have our own way of working and organising our projects. A finely tuned software is such an important factor and will save us work, can reliably support our workflow and thus boost productivity. Having to fight against the behaviour of my software again and again is so exhausting.

I'm really glad I now know how to tweak some of these issues but there's still a long way to go until my Trados software becomes a real partner and supports MY work.

Thanks again.

Katja