Unsuccessful application of font adaptation

Hello,

I'm giving font adaptation another swing but once again having no luck with finding the right combination to get the desired results. For now, what I just want is for Studio to display a target language in the font of my choice. Eventually, I'd like that font to also be used in the generated target file, but I've been told only the default font settings in the native file will determine the font output. But one thing at a time.

I have a test xlsx file written with text in MS P Gothic in Japanese to be translated into American English. Actually, I have a bunch of screenshots explaining my process so please see the powerpoint. And please try yourself using the attached excel file. 

Thank you in advance.

6406.Fontmapping.pptx

4353.MS Gothic as default test.xlsx

  • Unknown said:
    Partially what throws me off even now is the preview function at the bottom of the font mapping screen. Since font mapping is for selecting the font of the target in the target file, then how can that be previewed?

    This is not related to the font mapping part of the settings, but to the File Type in general. It allows you to preview how the parsed bilingual file will look like when the source file is parsed using the current settings.

    It was introduced in Studio 2017 to simplify setting and tuning the file type options.
    In earlier versions, when you configure and/or finetune file type settings, you have to go through tedious process of making the change(s), then inserting source file, letting Studio parse it and 'copy to target languages' and only then you can open the bilingual file in Editor to see the result... mostly to only find out that it's still not what you wanted, so you have to delete the source file, change the settings and go through all that hassle again and again and again, until the setting is satisfactory.
    With the preview one can see the changes using a single click...
    (Still, I believe that the preview does not respect the segmentation settings in a particular TM... it probably uses some default language rules)

  • Yes! It was the "formatting display style" rule that was the culprit. As you said, changing it to "show all tags but do not show formatting" did the trick. In all the texts I've read, (and I just read the help files from each window) I've never read that this setting would affect font adaptation. That vital information felt somewhat hidden. Time to share the good news with my coworkers.
    Also, may be worth adding to a description somewhere that after setting a font, it won't take effect until the project is reopened. It was quick to figure out, but still left me scratching my head for a second when this happened:

  • It doesn’t affect font adaptation at all. It just affects the display.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub