How to prepare Frame files for English to Korean translation

[Bill Swallow]

You know, I work for a translation company these days and prior have
worked on highly localized projects, and I've not encountered this.

If you sent them FM files, then you should get FM files back using
whatever font is necessary to properly display the characters. If YOU
need to buy the font to support the files internally (should you be
publishing and not them) that's one thing, but they should have
localized the FM files (variable definitions, master pages, reference
pages, and even font usage in styles).

You should get them on the phone to talk you through what they meant,
as I can only wager guesses (and guessing is bad practice).

Let me know if I can help answer any other questions. I'm happy to help.

Bill

On Thu, Jun 21, 2012 at 10:34 AM, Kelly Lawetz <klawetz at genetec.com> wrote:
> Hi Bill,
>
> I’ve followed most of  the best practices for translation. My confusion
> stems from the following:
>
> Here is the email from my translator:
>
> " I'm including 2 versions of the file :
>
> - the file that doesn't display the fonts properly, and
>
> - the file after running it through the Trados FontMapper utility which is a
> hack to fix the display of fonts (by doing something to the mif file. It
> also requires an English file with Korean fonts as part of the input to
> apply the fix).
>
> The problem doesn't occur in the first place if Korean fonts are used in the
> original English file."
>
> And my confusion is with the last phrase – how do I use Korean fonts in the
> original English file? And is that necessary? What are the steps in Frame to
> do this?
>
> Thanks,
>
> Still have so much to learn!
>
> Kelly Lawetz
>
> Team Leader of Technical Documentation
>
> P: +1-514-332-4000 x6329

-- 
Bill Swallow
Content Solutions Manager
GlobalScript, a division of LinguaLinx
http://globalscript.com
http://lingualinx.com