Jane (on her blog): I should mention that prior to negotiating terms with the client, the file they sent me for review was a Word document. I had innocently assumed this was the format I would be translating. (I know, never make assumptions!) It was only after reaching agreement on the project price and delivery deadline that the client then informed me about the memoQ server aspect.
After I explained about my memoQ situation, the client (who I have a good relationship with) offered to provide an rtf file instead. She was trying to be helpful, we had done enough negotiating, in short, I said yes.
I think this is all very confusing. Anyway, as I said, RTF is not a problem for CT, and a bilingual RTF is a minor problem that the user should be able to solve easily.
Instead of asking for another file format I would propose to build macros and/or AHK scripts that will create ready-to-import files, or at least to support this process. There are the following steps:
And if this rtf file is pre-populated / pre-translated, the RTF import won'T really help.
See also here.