• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 431 subscribers
  • Views 3545 views
  • Users 0 members are here
Options
Related

What is the best way to work with a package received by the client when we have different steps and different participants to the project?

Marine Tresnie

Hi everyone,

One of our client changed his method and now sends us packages. Since we work with various participants, we are not sure how we can work to be as efficient as possible. I am not used to working with packages.

When we receive the project (WorldServer Project with only file-based TMs), we want to be able to add our own TM and then send the file to our translator. When the translator is done, we have to send the file to the reviser and then when the reviser is done, we need to do a quality check internally. For our client's delivery, we need to deliver a Return package.

We are several project managers and we should be able to open the files on any computers internally (and not only on the computer that first opened the project).

We are used to work with file and thus to extract the file from the Packages we receive and to deliver only the sdlxliff file but now that we have to deliver return packages, everything changes.

Do you have any ideas on how to proceed (in the most efficient way) ?

Thank you very much,

Marine

Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    This is, what I do:
    Receive the package as usual.
    Take the target files into my own project (just add them on the proper screen during project creation). If necessary, add the resources from customer package to my project.
    Translate the files in my project. Do QA on those.
    When done, update my own TM.
    After that copy the files from my projects target folder and paste them into customers package target folder, where the existing files will be overwritten. Run a "Translation wordcount" there, create a return package.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0
    You can do this in 2 ways depicted below (some of the steps are common):

    1.- The PM opens the package by double-clicking.
    2a.- If there are not many people working in-house, this PM can select a project path in your own LAN. This way anybody will be able to access the project (it's a SDLPROJ file). Take into account that here are some drawbacks when several people access the same Multiterm database or open the same Studio project.
    2b.- Alternatively, this PM creates a project in his/her own PC (not accesible to anyone).
    3.- This PM adds your TM (you might consider the free plugin Apply Studio Project Template from the AppStore).
    4a.- Let everybody open and work on the project.
    4b.- Alternatively, the PM creates as many packages as needed and send them to the translators, reviewers, etc.
    5.- When everything is done, the PM creates the return package and sends it to your client.

    Believe me: the best way is working with packages. . For example I always ask for a return package, don't accept XLIFFs. Maybe it's a new thing for you, but the're very good advantages:

    - One reason is that the package contains all the assets needed to work with the documents. Otherwise, you have to add them manually, which is proned to forgetness…

    - Another reason, is that anybody can deliver a XLIFF file which is not final believing it is, I've been a witness of it, and never again! Think of this: It's just a matter of not saving the file in Studio an you un into problems. It happens as well in Word, Excel, so you've got to have an extra check step… On the other hand, working with packages in Studio is a different matter: first you have to save all the unsaved files, otherwise you can't create the package (a nice feature of Studio which prevents sending finished but unsaved XLIFFs).
  • 0 in reply to Jesús Prieto
    Thank you very much for your help. We will try these ways too but we need to get used to packages.
  • 0
    Hi,

    A couple of other alternatives, but it all depends on your setup of course.

    GroupShare:
    Might be an option if you are sharing projects on a regular basis and your company is of a certain size, so that it's worth the investment.

    Poor man's GroupShare:
    1. Pull out the SDLXLIFF's from the client's package. (Tip: Associate the SDLPPX and SDLRPX file extensions with your ZIP application, that way you can just double click packages and they will open in the ZIP application instead of Studio.)
    2. Create a master project on the file server. This could be the package project, but since you would have to go through all settings in it, it is probably easier to create your own project. The master project will only be used for delivery, not working. Keep your TM's on the file server.
    3. Everyone involved in the project either copies the master project from the file server to their C:\, or creates their own project on C:\ with the same files as the master project (use the target files of the package as your source files). Then share the only SDLXLIFF's on the file server as necessary. Anyone who needs the translated/reviewed/checked version of a certain file picks it up from the file server.
    - This way there will be no clashes between people writing to the same SDLPROJ file. But it also demands some communication among you about who does what and when.

    In my opinion packages are nice and handy to send out, but they are not as fun to receive (neither SDLPPX nor SDLRPX), since you have no control of what they contain or how they behave.

    Daniel Fransson | SDL Sweden