Hi Alessia Nasini

You don't have to do this because Studio automatically adds the source files to your projects.  The only time this doesn't happen is if your source files are larger than the settings you have used for the embedded sdlxliff.  So if you are not getting the source file then try changing the settings for the embedded sdlxliff here.  Move the slider to make it larger... and do this before you create your project:

FYI - We are running SDL Trados Studio 2019 SR1 - 15.1.2.48878

Hi Alessia Nasini

I can see from your package that the source file isn't there.  If I create a new project and use your project as the basis for my own settings I get the source file.  So for me there isn't a problem.... not very helpful I know!

Perhaps you could try clicking on the reset to defaults in the sdlxliff -> general view.  That might trigger a change in case your template is corrupted somehow?

I tried to reset but no changes (and actually id does not work even on other PCs in our organization where that setting is at the default value). What sounds really strange to me is that this does not work on any of the workstations in our organization. Shall I open a ticket then or do you have any further ideas?

Hi Alessia Nasini

Are you sharing settings on a network perhaps?  Did you import an old template from previous versions of Studio?

If you have a support account then you should raise a ticket.  It's strange behaviour and seems to be related to your environment in some way.

We share our network license but the templates we use are file-based. There may be some templates coming from previous 2019 versions (we always create new templates when we upgrade but not necessarily at SRs or CUs) but I've tested the default template which should not depend on previous versions, as far as I know. We have a PSMA so I'll log a ticket. I'll keep you posted in case we manage to find a solution.

Hi Paul, 

we've just had a session with SDL Support and they confirmed that the behaviour I pointed out is the same they get on their PCs.

The expert's recap is as follows:

"Trying to embed the original source file as reference into the package (Step4 of the Create Project Package wizard,: Review Project Package> Add Files...):

- possible for Single file project;
- not possible for Studio project. "

Since you said that it was working on your side, could you please reply to the following:

- Did you try to embed the source Word file from a full project or from a sigle-file project?

- Did you try to embed in the package the original source file used in my project to create the SDLXLIFF file? (i.e. not another file added as a reference to the project, but the original Italian file)

- Can you maybe try and replicate this last operation and capture it with a video so that I can see where our SDL Trados Studio gets lost?

Our ticket is being raised to Level 2 but I think it would be of great help if you could give me your feedback on the above.

Thanks a lot,

Alessia

Hi Paul, 

we've just had a session with SDL Support and they confirmed that the behaviour I pointed out is the same they get on their PCs.

The expert's recap is as follows:

"Trying to embed the original source file as reference into the package (Step4 of the Create Project Package wizard,: Review Project Package> Add Files...):

- possible for Single file project;
- not possible for Studio project. "

Since you said that it was working on your side, could you please reply to the following:

- Did you try to embed the source Word file from a full project or from a sigle-file project?

- Did you try to embed in the package the original source file used in my project to create the SDLXLIFF file? (i.e. not another file added as a reference to the project, but the original Italian file)

- Can you maybe try and replicate this last operation and capture it with a video so that I can see where our SDL Trados Studio gets lost?

Our ticket is being raised to Level 2 but I think it would be of great help if you could give me your feedback on the above.

Thanks a lot,

Alessia

Hi Alessia Nasini

I owe you an apology.  I started to record the video and then realised I was only creating a project and not the package.  I clearly didn't read your post properly and everywhere you said package I saw project.

Apologies for wasting your time with that.  I also dropped an email to the product manager/dev team as I also tested thiis in the latest Beta for the next update and it doesn't work in there either.  I don't think the fix can still be applied in time for the next release though as it's imminent.

Ok, at least it's not me... :-)

Thanks for your effort and your time, I hope this will be fixed soon.