> // This may well ruin the RTF file of Jane, since for instance certain info is lost that Word cannot interpret.
As RTF is a text format with only some additional basic formatting, I think that RTF to Ms Word or LibreOffice conversion is lossless. I have never heard of any issues in this regard.
Hans CafeTran Wiki: Is this RTF an exchange format of mQ server?
RTF is rich text format, it's as old as Methuselah, it used to be the project file format for a number of CAT tools, including DV3, and there's no problem converting it to .docx or .odt as Igor described. And like when you convert .doc to .docx, nothing will get lost.
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.
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).
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/).
MB: ...we need to see the actual file Jane Ellis is talking about
@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.
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.
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.
What the samsung does is completely irrelevant. Jane was sent an .rtf file, and CT can handle it if converted to .docx or .odt.