Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Barcode font Code 128 not printed from PDF

1,299 views
Skip to first unread message

D.J.W. van Kooten

unread,
Feb 25, 2015, 6:45:05 AM2/25/15
to
It's not a cavo problem but maybe someone recognizes it.

A client receives a PDF which shows letters instead of a barcode. This
means the maker didn't embed the barcode font. We installed Code 128
in \Windows\Fonts on the server but Adobe Reader's document properties
say: Code 128 - actual font Adobe Sans MM. And still shows letters.

We then installed PDF XChange VIewer, as this showed the barcode on my
and their system correctly. But the next problem was that their
Kyocera Laser printer leaves the barcode area empty (while my printer
printed it correctly). I remember from years back that fonts had to be
uploaded to the printer or something but that can't be the case
nowadays I guess ? Also note that other PDF's with the same Code 128
font (which also showed correctly in Adobe Reader) print correctly
too.

We can solve it by printing everything as graphics but that shouldn't
be necessary and slows printing down.

Does this ring a bell for somebody?

Dick

Gerhard Bunzel

unread,
Feb 25, 2015, 10:47:43 AM2/25/15
to
Dick,

in the past, I had also that problem with not installed fonts for different
barcodes.
Now I draw the bars for the different barcodes by myself - no font is
needed - no graphics.
All woks fine with different printers and PDF-Files.

What printing system with VO do you use?


Regards

Gerhard Bunzel


"D.J.W. van Kooten" <vank...@removethis.ic2.com> schrieb im Newsbeitrag
news:82drea9jnshr18959...@4ax.com...

D.J.W. van Kooten

unread,
Feb 25, 2015, 3:14:00 PM2/25/15
to
On Wed, 25 Feb 2015 16:50:53 +0100, "Gerhard Bunzel"
<g.bu...@domonet.de> wrote:

Hello Gerhard,
>
>in the past, I had also that problem with not installed fonts for different
>barcodes.
>Now I draw the bars for the different barcodes by myself - no font is
>needed - no graphics.
>All woks fine with different printers and PDF-Files.
>
>What printing system with VO do you use?
>

It's not a VO problem. It's our client but the problem they encounter
is with PDF's with a barcode they get from others and print from Adobe
Reader or PDFXChange viewer.

I do realize the sender of that PDF is the problem (other PDF's from
other senders with the same barcode font print fine) but apparently
they are unwilling or unable to solve it so I wonder why I can view
but not print the barcode on their printer (while I can with the same
PDF on my printer).


Dick

paul...@gmail.com

unread,
Mar 31, 2015, 3:50:28 PM3/31/15
to
Op woensdag 25 februari 2015 12:45:05 UTC+1 schreef D. J. W. van Kooten:
Hi Dick,

In the past a had somewhat the same problems with Code-39. The trick was there, that de code needed a * on front and end of the number of the bar code (like *928495*).
So, could it be that the maker of your document didn't make the right code?
You could test it by making a document in Word, using the code-128-font.
But, you have to use the starting and ending symbols for Code-128. You find these on the Internet, like at http://www.barcodeisland.com/code128.phtml
Then use the code-128-font without these starting and ending symbols.
Make the PDF and try reading/printing.
Readers/printer can be more picky and not just accept the right font.

Paul

D.J.W. van Kooten

unread,
Mar 31, 2015, 5:26:45 PM3/31/15
to
On Tue, 31 Mar 2015 12:50:27 -0700 (PDT), paul...@gmail.com wrote:

Hello Paul,

>In the past a had somewhat the same problems with Code-39.
>The trick was there, that de code needed a * on front and end of the number of the bar code (like *928495*).
>So, could it be that the maker of your document didn't make the right code?


I am convinced that is the basic problem, because other PDF's show
correctly. However, it is a PDF they receive, not one they make.

The background info you provide me with is very interesting.

For the moment we 'solved' it by letting the printer print fonts
graphically. As the client doesn't complain anymore, also not about
speed issues (which I expected) the problem has moved to the
background. If it emerges again I will certainly look into your
information, thanks for it!

Dick
0 new messages