Comment not present in a target (*.PO) file

 Hello,

 no matter what severity level it has, no comment shows up in translated target file (also *.po, naturally). I don't know if there is anything special about comments the *.po files, e. g. a need to configure saving of comments first. See the attached *.SDLXLIFF file. Thank you in advance for any help, ides, hints etc.

Kind Regards,

Jonáš.CZ-EN.po.zip

Parents
  • Hi Jonáš Pospíchal,

     

    There are lots of issues around comments in general and the safest way I can think of maintaining comments is outside of Studio environment (at least true in the latest version of Studio 2017). 

    PO files might have a special issue of Studio just not maintaining any of them at all. Since PO file type settings do not maintain comments at all in the target, your only option would be to put the comments back after generating the target. I noticed there is no header information in the target from your SDLIXLIFF either. Anyway, please try Beyond Compare if you haven't from here. If you set it up correctly, putting comments back will only take a minute provided you have the original source .po file.

     

    FYI interesting issues with comments in general with the latest version of Studio 2017 are (I am curious if anyone could test it in another version):

    - When the first occurrence of reps are confirmed and all the rest of reps get populated, comments get lost for all the reps (except for the first occurrence) in the SDLXLIFF during translation and the generated target files are missing those comments.

    - Copy source to target and comments disappear for that segment. 

     

    FYI "Comment View Plugin" from AppStore can load comments in your SDLXLIFF file (see screenshot below) and export them to an Excel file. So I see all the comments you are referring to.

    Thank you,

    Naoko

  • Hi Naoko & Paul Filkin,

    Paul: you're right, I've found them in *.sdlxliff and tried to sort them out. Unfortunately, the comments there do not include any useful index or any other identifier, each comment is only accompanied by some sequence of chars and numerals with not apparent pattern that could allow me to pair the comments with the respective segments.

    Naoko: thank you all you suggestions. Beyond Compare proved to be useful in extracting the comments in the case of this project, while the Comment View Plugin you've recommended did not run on SDL Trados 2017. For the future projects, I've chosen a path of smallest resistence, i. e. a conversion of the original *.po file to a *.xlf file. Comments entered this way remained in a target file, which was in turn converted by another tool into a requested *.po. A slightly more complicated, but perhaps the quickest way of solving this.

    Thank you both.

    Jonáš.
Reply
  • Hi Naoko & Paul Filkin,

    Paul: you're right, I've found them in *.sdlxliff and tried to sort them out. Unfortunately, the comments there do not include any useful index or any other identifier, each comment is only accompanied by some sequence of chars and numerals with not apparent pattern that could allow me to pair the comments with the respective segments.

    Naoko: thank you all you suggestions. Beyond Compare proved to be useful in extracting the comments in the case of this project, while the Comment View Plugin you've recommended did not run on SDL Trados 2017. For the future projects, I've chosen a path of smallest resistence, i. e. a conversion of the original *.po file to a *.xlf file. Comments entered this way remained in a target file, which was in turn converted by another tool into a requested *.po. A slightly more complicated, but perhaps the quickest way of solving this.

    Thank you both.

    Jonáš.
Children
No Data