You are currently working on UAT
I have posted a question asking any workaround about it (to suppress).
But, have been told that is impossible.
I tried to make the same message from my side.
But, have failed.
Do I need some more programs ? or simply missed how to use SDL Trados Studio ?
Thanks
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Ly Tu Trong said:I have just found that "Dependency file not found" could be avoided easily.
If you delete two Elements at sdlxliff, the pop up disappears.
Make sure you put them back afterwards Kelly or your customer might not be so pleased as this is needed when they create their target files.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Ly Tu Trong said:Nobody helps others. I found my own workaround. So, very satisfied with my result. In the above link, SDL engineers said, they will make some way for customers. But, the solution does not delivered to customer yet. And, nobody knows when will it be. I, have made it.
This is utter nonsense Kelly.
Nobody will have said they will solve the problem of people working directly on SDLXLIFF files that don't contain the embedded file... at least no other way other than to send the original source file with the sdlxliff, or use Project Packages.
You have created a workaround for a problem that isn't really there. The message is purely information anyway.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
The bit you think needs fixing Kelly is this, which occurs with WorldServer packages:
|
This may happen when the original source file is too large to be embedded in the SDLXLIFF file. Instead it is linked as a separate dependency file. When creating packages, these files are not automatically added to the package.
|
And you have not fixed this at all. You have merely prevented the informational message from appearing. Seems a waste of time to me.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
>You have created a workaround for a problem that isn't really there. The message is purely information anyway.
I have made a workaround for a real problem that do exist here, your customer. The message is purely annoying, nothing else. What is the point of the message ? For me, it does not have any meaning.
If you want to inform the user, it should be appeared once when the (problematic) project started. That is good enough.
If you need to stop the user, need to prevent the problem project used, do not make annoying pop up. Just block it. Simple.
You have to select one of above. Current procedure is just nonsense at least to me - And I am a regular customer not a strange idiot beginner.
>You have created a workaround for a problem that isn't really there. The message is purely information anyway.
I have made a workaround for a real problem that do exist here, your customer. The message is purely annoying, nothing else. What is the point of the message ? For me, it does not have any meaning.
If you want to inform the user, it should be appeared once when the (problematic) project started. That is good enough.
If you need to stop the user, need to prevent the problem project used, do not make annoying pop up. Just block it. Simple.
You have to select one of above. Current procedure is just nonsense at least to me - And I am a regular customer not a strange idiot beginner.
Ly Tu Trong said:What is the point of the message ? For me, it does not have any meaning.If you want to inform the user, it should be appeared once when the (problematic) project started. That is good enough.
If you need to stop the user, need to prevent the problem project used, do not make annoying pop up. Just block it. Simple.
You have to select one of above. Current procedure is just nonsense at least to me
Just as I said - you are just so clueless...
That message concerns particular SDLXLIFF(s), not project, so it appears when opening the SDLXLIFF, not project.
And no, it's not there to stop user from anything, it's there to inform user about a problem and it offers a way to fix the problem too (did you notice that you can search for the missing dependency file right from the message?!). Once you fix the problem, i.e. find the dependency file (if you have it somewhere, of course) and let Studio embed it into the SDLXLIFF, the message is gone. Otherwise it will of course pop up every time you open the SDLXLIFF... because the problem is still there.
Ly Tu Trong said:And I am a regular customer not a strange idiot beginner.
Really? So why your rhetoric suggests the exactly opposite from the very first time you appeared on this forum as your Kelly Edward identity?
Translate
