Crystal Reports EAN13 barcodes using True Type Fonts

[julie_jamieson2]

We are printing EAN13 barcodes using an Azalea font as we are using .net & can't use the printer font.

the printer is a Zebra G420 and is 200dpi.

I can print a code that scans and reads, but not one that will pass GS1 certification.

the customer needs certification & we have spent 3 months on this already.

Someone must have solved this - any one that can give me some tips?

[former_member11696 · Accepted solution]

Hi Julie,

Have you posted this question to Azalea? I think they are the ones who would need to make their font certifiable.

Or if you have then what is the exact issue you are having, details about why it's failing to be certified...

Do they pass if printing from CR Designer?

Don

[julie_jamieson2 · Accepted solution]

Hi Don,

Azalea have passed me to Zebra.

I can print a passable barcode to PDF from the designer, but not to the printer from the designer. Haven't got to testing from the B1 interface yet.

I am trying to get a contact for Zebra from my customer, but their support site says it is trial & error, as does Azalea. We have been doing that for a month and don't seem to be getting any closer & each test is costing our customer.

I was hoping someone might have cracked this & could tell me which font at which size should work, or if I need to change to a different font provider

We have done the obvious such as cleaned the printer etc.

[julie_jamieson2 · Accepted solution]

Hi Don,

I just tested this morning and the font doesn't display at all in the preview through the crystal viewer in SAP B1, even though the font is installed on the server that is rendering the view.

I guess I am now right back to square one, as that is where I need to produce it from

[former_member11696 · Accepted solution]

Hi Julie,

That is new info... I moved your post to the B1 forum.

B1 I believe uses the 64 bit SDK to process the report so make sure you install the 64 bit UFL on the B1 server.

As for Azalea not being able to Certify their font it may be worth while looking into one that is certifiable.

It could be due to the 200 DPI setting as part of the problem.

So to explain why this works when exporting to PDF is the PDF is rendering the barcode as an image of the characters rather than relying on the viewer to render the font using USP10 and the printer driver CR is using in a .NET application which is what B1 is using in the back end....

So this may be an issue with the Viewer but due to issues or limitations in the Viewers printer routines. The Viewer uses .NET Framework to print the report.

Your only work around may be to export to PDF and then print.

B1 R^D team could have a look at this but I don't believe it's anything we can fix.

Don

[julie_jamieson2 · Accepted solution]

Thanks Don,

When I restarted SAP B1 after installing the font, it the did display in the viewer. Azalea say their font does certify (which it does from PDF) but it is a printer issue.

I found a note on the Zebra site that Crystal viewer can't use internal printer fonts, does that still apply to 12.5.0.1191? If so, at what point is that issue resolved?