Framemaker's description says it can handle multiple languages ... Yep. You can write the document in any one language ... and it seems like it can do layering which Framemaker calls conditional expressions that can be turned on of off as needed. Would this work? As it happens, I'm doing sort-of that right now. We need to generate two different versions of the English document depending on destination region. USA gets one. UK gets another. All the US customary units (often mis-named Imperial units) are switched off for the UK ed. But more in line with your problem, certain bits of industry jargon are conditionally tagged, so we can switch between US and UK nomenclature. With "both versions" visible, this causes the document to have a larger flow (repagination issues), and causes some flows (in anchored frames) to flow-under (out of sight) during editing. Also, unless you have FM10, you can't see which text is which, because you can't set visible indicators in the Condition Codes that are easy to switch off (you can use color if you can live with Print All Text as Black when pushing, which we can't). I think FM10 adds a CC feature that might handle this more elegantly. We've also had to settle on just one spelling dictionary (UK), because it's not trivial to switch an entire document from one dict to another, as it's defined in each paragraph format (although a batch switch could be scripted). In any case, we can live with the minor hassles, to avoid maintaining near-twin documents. But I can't imagine interleaving whole sentences or paragraphs of entirely different languages, particularly if the writer doesn't speak them all. Do text as insets? Probably won't work, due to Xrefs. Most publishers probably give the single-language source files to a translator. There are some things you can do to make life easier for translators. It's surprising how seldom they ask. I suspect that in some cases here, they are translating from our PDFs, because I get so few requests to run my pre-translation scripts.
... View more