• State Verified Answer
  • Replies 2 replies
  • Subscribers 432 subscribers
  • Views 1622 views
  • Users 0 members are here
Options
Related

Destination file - incomplete translation

Gaia Celeste

Dear All,

thanks in advance for helping.

The customer has asked me to deliver my work in advance - they have put on hold the project - and the translation is currently at 40%. I have delivered the return package for the document, but the customer also asked for the destination file to be forwarded.

Problem is that the remaining not-translated 60% is copied down as the source text in the destination file. 


Is there any automatic solution to fix this other than manually erase the source text form the destination .xml?

Thank you for helping!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Gaia

    This is normal behaviour od Studio by design. If a target segment is empty, the target document contains the source text. This feature provides advantages, e.g. you don't need to translate citations, numbers etc. that would remain unchanged if translated. Leaving the target segment empty will show the source text and avoids polluting the TM with unnecessary TUs.

    Why is this a problem? What would you expect to see for the untranslated text? If your client does not like it, then send him only the translated part of the document.

    Personally, I would not deliver a party translated document anyway because this is problematic. You may decide to change some sentences you have already translated while doing the rest of the document.

    Walter
  • 0 in reply to Walter Blaser

    Hi Walter,

    thank you for your quick and kind reply.
    I totally agree with you and personally find this feature very useful for the same reasons you've put down.
    I suppose the client would like blanks for the untranslated text.

    We're dealing with an .xml where you have product descriptions that consist of several segments. I've now sent the client an .xml where only the description with all the segments translated appear. To manually clean the descriptions with untranslated segments in them would be time-consuming, and I wouldn't know how to signal them (I guess blanks again?).

    Of course, this meant I cut off a lot of translated material (100%, CM and fuzzy that was dispersed through the document), but it is currently the only solution that makes sense to me.

    Thank you again for helping and providing info, and thank you in advance to anyone who might have come across a similar situation!

    Best

    Gaia
Reply
  • 0 in reply to Walter Blaser

    Hi Walter,

    thank you for your quick and kind reply.
    I totally agree with you and personally find this feature very useful for the same reasons you've put down.
    I suppose the client would like blanks for the untranslated text.

    We're dealing with an .xml where you have product descriptions that consist of several segments. I've now sent the client an .xml where only the description with all the segments translated appear. To manually clean the descriptions with untranslated segments in them would be time-consuming, and I wouldn't know how to signal them (I guess blanks again?).

    Of course, this meant I cut off a lot of translated material (100%, CM and fuzzy that was dispersed through the document), but it is currently the only solution that makes sense to me.

    Thank you again for helping and providing info, and thank you in advance to anyone who might have come across a similar situation!

    Best

    Gaia
Children
No Data