MB: the client sent her a memoQ bilingual .rtf
This wasn't clear from the original posting, nor from the posting on the Mac part of this forum. Besides, it isn't clear from Jane's own website that the second RTF project also involved proofing, and I wonder if it does.
And why would you proof a bilingual RTF file in CAT?
workflow to translate a memoQ bilingual file in CafeTran:
copy content of target column in memoQ bilingual rtf
paste into empty .docx
translate this docx in CT
export translation from CafeTran
past back into original memoQ rtf file
note: make sure not to split of join any segments in your CT project, as this will mess up getting it back into the correct rows in the target column
The whole problem, from my very quick read of http://translationswithchemistry.com/2015/10/27/a-smorgasbord-of-cat-tools-trados-memoq-and-now-cafetran/comment-page-1/#comment-1784 is that the client sent her a memoQ bilingual .rtf (like in my screenshot above), meaning: yes, it can be done fine in CT, but would involve a bit of copy/pasting and conversion into .docx.
Look, I'm sick and tired of this nonsense. Tell (not ask) that Igor to add a feature so Jane can import samsung specific RTF files into CT. I mean, that's what it's all about. Features. Very samsung specific. Like with all the tables in RTF (not), notes (not), and whatevers (neither).
What the samsung does is completely irrelevant. Jane was sent an .rtf file, and CT can handle it if converted to .docx or .odt.
I am starting to think I am going crazy here. Hans, memoQ exports its bilingual tables as .rtf files, but it isn't the fact that it is an .rtf file that matters: but the form of the data inside the file. Not the underlying code, but merely the file's contents. How hard is this to understand?
This is an example of a memoQ bilingual file:
They just happen to use RTF, but it's basically the same concept as the bilingual tables that can be exported in CafeTran, SDL Studio, DVX, etc.
Nope. RTF is a standard, a proprietary standard (MS at that). You can't copulate around with it. Not even the samsung of CAT tools.
@woorden: of course we need to see what is in it before we can tell her how to translate it in CT. An .rtf file could contain anything. memoQ stuff, tables, no tables, old Trados stuff, etc. We all know that a simple e.g. Dutch text in an .rtf file poses no problem. Just convert it to .docx and translate it. But that doesn't seem to be the issue here.
MB: ...we need to see the actual file Jane Ellis is talking about
Before speculating more about .RTF (as a format, its history, etc.), we need to see the actual file Jane Ellis is talking about. I posted a question about this on her blog (http://translationswithchemistry.com/2015/10/27/a-smorgasbord-of-cat-tools-trados-memoq-and-now-cafetran/comment-page-1/).
I never had any problems with the conversion from Word files to RTF for DejaVu and back, and I started using it in 1997 (DV2).
Hans CafeTran Wiki: I know what RTF is
But yes, of course.
I'm asking whether it is used as an exchange format.
As I mentioned above, it was used as a project file format by several CAT tools, whereas .doc wasn't. So yes, it is/was used as an exchange format.
Like Igor, I never heard of any issues in this respect.