Skip to main content
Participant
November 3, 2023
Question

Font no longer supported in FrameMaker

  • November 3, 2023
  • 4 replies
  • 638 views

I have been using Swiss Greek for many years in FrameMaker. However, since Swiss Greek is no longer supported, when I open my files, I get corrupted fonts and therefore unreadable content. This, can be solved (temporarily) if I install Swiss Greek again on my pc, which makes the content in the file readable (although underlined with red lines). The problem is that I can not replace that font with another legit, supported font. Replacing the font through the Paragraph Designer > Font, does not work. The font becomes corrupted again. Any idea of how replacing an unsupported font is done, would be highly appreciated. Thank you!

    This topic has been closed for replies.

    4 replies

    Community Expert
    November 5, 2023

    If one does a bit of googling there seems to be a fair amount of Swiss Greek fonts available for free download. Windows no longer supports Type 1 to its full extent. While you still can install a pfb file, results can be unpredictable. (in my experience, that is). "Swiss Greek" does sound like it is a copy of Helvetica made years ago and if you are lucky, I think you may be able to merely replace the font with a similar ttf font from a free download. Might be worth giving it a shot, at least.

    Bjørn Smalbro - FrameMaker.dk
    Community Expert
    November 5, 2023

    Hi, @FrameMaker-dk ,

    "Windows no longer supports Type 1 to its full extent."

    what version of windows are you talking about?

    And what problem(s) do you encounter?

     

    I am using Win10 22H2 (latest) and I have no problems with installing or using Type1 fonts.

    "Problems" occur with specific software like latest Adobe CC versions (and someday in the future FM versions will stop supporting Type1 fonts), but with the older ones I can use Type1 fonts until now without any glitches.

    In the long run, yes, Type1 fonts must be replaced with TTF/OTF versions.

    Regards

    Stephan

    Community Expert
    November 5, 2023

    Yeah well... I am talking about Windows 10 and I have had problems involving proper rendering of Type 1 fonts too.

    My advice was meant as a practical advice. If the thing does not work, perhaps it is better to exchange it with something that does work.

    Bjørn Smalbro - FrameMaker.dk
    Community Expert
    November 4, 2023

    Hi, @StefaniaKx ,

    you already know what to do as you wrote "This, can be solved (temporarily) if I install Swiss Greek again on my pc, which makes the content in the file readable (although underlined with red lines)."

    So install the SwissGreek font.

    FrameMaker does support Type1 fonts (FM 11 anyway).

    Or explain exactly what your problem with this font is.

     

    "The font becomes corrupted again. "

    How do you know?

     

    Regards

    Stephan

    Community Expert
    November 3, 2023

    Sounds like Swiss Greek fonts are Type 1. Is that right?

    Bjørn Smalbro - FrameMaker.dk
    Jeff_Coatsworth
    Community Expert
    Community Expert
    November 3, 2023

    What version of FM are you running - always start with that info.

    I haven't heard of any font that isn't "supported" anymore by FM - maybe you need to give some more details about the exact font name and type. And what do you mean that when you replace it with another, that the font is corrupted again? Never heard of that happening either. Corrupted how?

    Participant
    November 3, 2023

    Hello, I am running FM11. Swiss Greek is a Type 1 font and Type 1 characters do no longer display in FM 11. This is how the content is displayed:

    If I try to replace this with another font that is not Type 1, nothing changes. I hope this helps a bit.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    November 3, 2023

    What's the font that you're replacing it with? Does that font support the characters that you're trying to use in the doc? That might be the issue. However, this is out of my area of expertise (I don't use multiple fonts or languages), but @Bob_Niland might have more to offer.