Yes, this is a known mistake. It is based on font and printer. Another user claimed that switching to Arial fixes the problem . His problem was the Calibri font , and mine was the Tahoma font .
My experience was that it also depended on the printer, as my client received this error with one printer, but not with another, using the same computer.
Switching to Arial font worked for both of us. With the exception of the tests already mentioned here, there is no list in which I can find which fonts are errors and which ones work.
source
share