amatsumoto wrote:What was translated (into Japanese), was done in FrameMaker years ago. So, what we have is FrameMaker files in Japanese, probably with no translation memory database, and Flare projects in English. Do we create a translation memory database by importing the Japanese FrameMaker files into Flare and then doing an "align"? Do we have to spend time re-formatting the Japanese version too? Or, is it possible to "align" and create a translation memory database, then create a new Flare project using the properly formatted Flare project that is in English, and then apply the new TM database to hopefully get a huge head-start on applying the translation. I guess I'm trying to figure out which is more time-consuming: A) import the Japanese FrameMaker version into Flare and reformat it, then use that project going forward for future translations and output, or B) use the English version and apply a TM database and redo areas as needed for translation, depending on how much help the TM database is, and use THAT as our project going forward.
there are a few questions here.
the short answer is yes. there is a directional translation (English to Japanese, Japanese to English, or Japanese-English-Japanese) option when you are importing/exporting your TM database so that things are imported/exported correctly in future. I'll need to check my facts on this but if i am not wrong yes.
You'll have to weigh the value of the content.
How about option B.
I am betting the English version, since its possibly newer, has more relevant content, and the document styling is presumably more up to date - always considering the value of timeliness of the content.
Since your English project is already being converted to Flare, work is already progressing there. Use that as the baseline.
Import into MadCap Lingo, translate, and export to Japanese Flare project (and all your hard styling work from the English version would have transitioned smoothly over to your fresh, and new translated Japanese project.)
Use the older Japanese Framemaker projects as a guide to your new translation work. Do this as you migrate and sync/align the English-Japanese content together. No need to reformat again after you translate in Lingo. If you've been careful during the translation and retain the right segments of translated information within the XML tags, amatsumoto, you'll be laughing and a jolly new year by the end of the year.