Target PO files do not contain my translations

Hi, I am using Studio 2015 SP3. I received a translation package containing partly translated PO files from a client. The PO files already contained some full matches and fuzzy matches, but also completely untranslated segments with empty target fields. Translation went fine, but after saving the target po files, I found that none of the new translations I had added and saved in the po.sdlxliff files had been saved to the target po files. The respective target fields were still empty, but some line breaks had been added. Only the pre-existing full-match translations (and I think, the edited fuzzy matches, too) showed up in the target file. I have tried applying varying translation statuses to the segments in Trados, but to no avail. Any idea?

Parents Reply
  • Dear Paul,

    Thank you for replying to my query.

    It turns out my client was able to produce the correct target po files from my SDL Trados Studio return package, so my problem is actually solved. Independently, I found out that I can save correct po files with all translations when I do not use my client's package at all, but import the original po source files into my own, self-created project, translate on the basis of the TM, and save to target po.

    So strangely, I can save Word documents from this particular Studio package and I can save the PO files when I use my own project, but the combination of this Studio package and PO files does not allow saving correct target files. I suppose my client has used some funny setting somewhere in the preparation process.

    Best regards,
    Angelika
Children
  • Unknown said:
    So strangely, I can save Word documents from this particular Studio package and I can save the PO files when I use my own project, but the combination of this Studio package and PO files does not allow saving correct target files. I suppose my client has used some funny setting somewhere in the preparation process.

    Hi Angelika,

    Sounds plausible, although any customisation of the default PO filetype should be in the package so you have it to.  I wonder if they have used the plugin I pointed you to earlier?  When you open the project settings for the package. and after installing this plugin, do you see this in the Filetype Options?

    If you do then click it and add the new PO filetype you just installed.  Not important now as you don't have a problem with the files for your client, but might be interesting to see if this resolves your issue.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    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