Skip to main content
monrocks12
Inspiring
October 14, 2022
Question

Bullets not displaying correctly when converting to PDF.

  • October 14, 2022
  • 3 replies
  • 445 views

I am using FrameMaker 2020, and when I am working remotely, something is going wrong when I convert Frame files to PDF. I have tried all publishing methods (Save as PDF, Print to PDF, and Publish to PDF). Each time, the PDF displays the bullets as ellipses (three dots). I don't havc this issue when I convert files while working in the office. Any idea what the issue could be?

    This topic has been closed for replies.

    3 replies

    Matt-Tech Comm Tools
    Community Expert
    Community Expert
    October 17, 2022

    Can you share a screenshot of the Numbering pane for your paragraph style in the Paragraph Designer?

    -Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
    Bob_Niland
    Community Expert
    Community Expert
    October 14, 2022

    What version of FM?
    Using default FM Numbering properties for Bulleted lists?


    Historically, FM's AN properties for that used to be:
    \b\t
    but as of FM2019, if not earlier, it appears that it is now
    •\t
    where "•" is
    U+2022 BULLET

     

    It appears that your doc is being rendered as
    U+2026 HORIZONTAL ELLIPSIS […]
    instead, but you'd need to copy the rendered character into a Unicode converter app/site to verify the codepoint.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    October 14, 2022

    Fonts installed on that remote machine?

    monrocks12
    Inspiring
    October 14, 2022

    It's the same machine, a laptop that I take between the office and home.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    October 14, 2022

    Sorry, that wasn't clear. If the software is installed on that machine & the FM files are there too, it shouldn't make any difference where you are located. I suspect there's something else at play here - you probably connect to an office VPN when working remotely? That might be the culprit - is your default Windows printer instance changing from when at home or when in the office?