rkoide

You can attach the file by zipping it first then add though this menu:

I think your assumptions are correct:

rkoide said:

we have no control over where the translate="no" attribute ends up in a RoboHelp XLIFF so it's no surprise that Trados cannot properly process RoboHelp XLIFF files with "translate='no'" attributes.

Depending on whether you use XLIFF 1.2 or 2.0 the results could be different so perhaps this will help if you can define the version?  XLIFF 1.2 supports this in the <group>, <trans-unit> and <bin-unit>:

http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#translate

XLIFF 2.0 supports it in <file> <group> <unit>, <mrk> and <sm>:

http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html#translate

So you have a bit more flexibility for XIFF 2.0.

Another solution, if you don't have target content in the prepared files is to prepare the files with a copy of the source in the target, then create a custom monolingual XML filetype to handle the target only.  This way you have virtually infinite ability to get at only the text you need to translate.

rkoide

You can attach the file by zipping it first then add though this menu:

I think your assumptions are correct:

rkoide said:

we have no control over where the translate="no" attribute ends up in a RoboHelp XLIFF so it's no surprise that Trados cannot properly process RoboHelp XLIFF files with "translate='no'" attributes.

Depending on whether you use XLIFF 1.2 or 2.0 the results could be different so perhaps this will help if you can define the version?  XLIFF 1.2 supports this in the <group>, <trans-unit> and <bin-unit>:

http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#translate

XLIFF 2.0 supports it in <file> <group> <unit>, <mrk> and <sm>:

http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html#translate

So you have a bit more flexibility for XIFF 2.0.

Another solution, if you don't have target content in the prepared files is to prepare the files with a copy of the source in the target, then create a custom monolingual XML filetype to handle the target only.  This way you have virtually infinite ability to get at only the text you need to translate.

6305.contents_First_Topic_htm_xlf.zip

Paul-san, thank you for your reply. I have attached my sample file just in case.

Paul said:

Depending on whether you use XLIFF 1.2 or 2.0 the results could be different so perhaps this will help if you can define the version?  XLIFF 1.2 supports this in the <group>, <trans-unit> and <bin-unit>:

Sorry that I tagged my post incorrectly (I'll try to fix it later) and I'm dealing with an XLIFF 1.2 file that RoboHelp creates and RoboHelp has no option so far to create an XLIFF 2.0 file.

And thank you for the information that Trados works according to the XLIFF specifications and it's good to know!

But again, I don't think I can make RoboHelp insert translate="no" attributes to where I want them and I would not want to manually modify XLIFF files.

Paul said:

Another solution, if you don't have target content in the prepared files is to prepare the files with a copy of the source in the target, then create a custom monolingual XML filetype to handle the target only.  This way you have virtually infinite ability to get at only the text you need to translate.

OK, I will try to create a custom XML filetype then. Thank you for the advice.

Best regards,

rkoide

rkoide said:

OK, I will try to create a custom XML filetype then. Thank you for the advice.

Great... let us know how you get on.

Paul-san, thank you for your reply.

Paul said:

Great... let us know how you get on.

I have had to put this thing on hold by the way because the information of this issue has been shared with Adobe and it's still undecided how we should translate the RoboHelp project in question. Thank you.