Font in layout of adobe form is not the one in the print preview

[sharonphilip]

Hello,

In the layout of the adobe form, we have used font MB Corpo S Text Office Light as seen here

And it was reflecting the same while printing the form as well. As in, the font was right.

But recently, we have noticed that the forms are using a completely different font while printing even though the font in the layout of the form is still the same.

The distinction between the fonts are not very clear in the images but it is in the print preview.

Any idea why this occurs now and didn't before?

Regards,
Sharon

[Tomas_Buryanek]

Hello,

please read Adobe Livecycle documentation - Font handling.

You can try "embed" special font/s in Form Properties. Or best suggested is this approach (quote from documentation):

To ensure that a form design looks the same across PDF, PCL, and PostScript output devices, use these fonts, which are resident in most computers:

• Courier
• Arial
• Times New Roman

[sharonphilip]

Thank you for your response.

But the issue is happening only recently.
The second image provided in the initial question shows that the font was correctly being used in the form.

Using fonts like Courier, Arial, or Times New Roman would make sense if the font MB Corpo S Text Office Light never worked in the first place but as seen in the image, this font was correctly displaying in the form before.

Recently, the font seems to have been replaced with another font.
I was wondering why it worked before and suddenly, it doesn't. Any idea why that is?

[Tomas_Buryanek]

sharonphilip Not sure. But there might have been some Windows update, SAP patch, printer update etc.

[Sandra_Rossi]

Which Print Preview?

Could it be related to the language? (as your screenshots show French versus German)

Did you check all the SAP notes about Adobe fonts?

Ask your administrator to check the fonts in the ADS server.

[sharonphilip]

Hello... Thank you so much for this...
You were right... Seems like the font was removed from the ADS server. 
It was resolved by the BASIS team...