Missing Font OCRB Barcode Error

[Row13]

Any help would be much appreciated. I finally got my barcode on my back cover but not I cannot get rid of the Error: 

 

 

I am getting this error (Missing Font OCRB) because the font on the barcode I purchased is not listed in the Font Manager:

 

 

My barcode has the Font OCR-B:

 

Does anybody know how I can clear this Missing Font error? Thanks in advance

 

 

[lacerto]

9 hours ago, Row13 said:

Does anybody know how I can clear this Missing Font error? Thanks in advance

If the placed file is an EPS, you can open it and render the embedded font as curves.

If the placed file is a PDF, place it for "Passthrough" (= default) so that the embedded font is used when you export. If you place a PDF as interpreted file, you need to have the embedded font installed.

Certain apps like Adobe Acrobat Pro and macOS Preview, can also flatten the fonts and convert an embedded font to outlines.

[Row13]

Thank you very much. It is saved as PDF. Could I ask you how to place it as “Passthrough”? 

[Row13]

12 hours ago, lacerto said:

If the placed file is an EPS, you can open it and render the embedded font as curves.

If the placed file is a PDF, place it for "Passthrough" (= default) so that the embedded font is used when you export. If you place a PDF as interpreted file, you need to have the embedded font installed.

Certain apps like Adobe Acrobat Pro and macOS Preview, can also flatten the fonts and convert an embedded font to outlines.

Any thoughts on how to convert the barcode to curves when the option is grayed out? When I go into Layer the only option is to Convert to Picture Frame. I cannot select the Convert to Curves option. 

[Row13]

This is the message I get and when I click "fix" it give me the missing font message. 

 

[Alfred]

21 hours ago, Row13 said:

I am getting this error (Missing Font OCRB) because the font on the barcode I purchased is not listed in the Font Manager:

How did you install the font? Does it work correctly with other software?

[Komatös]

Maybe I'm wrong, but as long as I've been using Windows, OCR-A and OCR-B have always been installed with Windows. OK, I've been dragging the font folder along since Windows 3.0, maybe the two font families are no longer installed since Windows XP.

[firstdefence]

The barcode_OCRB is for the 50999 number but can be set to pretty much any font, I could generate one with the text set to say Arial for you.

[firstdefence]

9798218148423;9.99.zip

 

[kenmcd]

OCRB came with Office XP and Office 2000 (v1.01) and some others.
Now the only place OCRB is available (AFAIK) is in the O365 Cloud Fonts (v1.56).
And there are other versions out there from BT and Monotype, etc.

The Microsoft version has always been named OCRB, not OCR-B (AFAIK).
There are some OCR-B versions floating around out there.
Perhaps that is the problem.

OCR A Extended v1.80 comes with MS Office for quite awhile now (2003-2019).
Previously it came with various MS apps - Win95, Publisher 98, Plus! packs, etc.

@Row13 Can you attach the PDF?
I cannot imagine why Affinity cannot match the OCRB font.

And what version of the OCRB font do you have installed?

Note: also Adobe Font Folio 11 has OCR A Std and OCR B Std

[firstdefence]

The font I have installed is OCR-B 10 BT on my iMac 12.6.3 I also have Office installed and an app called Barcode, this website appears to list and offer download of OCRB and OCR-B 10 BT: https://fontsdata.com/find.php?q=OCRB

[lacerto]

When using embedded fonts, Affinity apps basically behave in three ways:

1) When the font is embedded in a PDF file and the file is placed to be passed through:

• The embedded font will be passed through whether the font is available on the system where export happens or not, unless there is a PDF compatibility issue
• If there is a compatibility issue (e.g. the placed PDF uses PDF version 1.7 and the file is exported using a lower version, like when exporting using PDF/X-based methods),  the conflicting parts will be rasterized and color values reinterpreted and/or the embedded font will be replaced.

2) When the font is embedded in a PDF file and the file is placed as interpreted:

• If the embedded font is installed on the system and the font is correctly mapped, the parts using the embedded font will be correctly rendered and exported.
• If the embedded font is not installed or not correctly mapped, a replacing font will be used.

3) When the font is embedded in an EPS file:

• The font will be converted to curves whether the embedded font is installed/available or not.

When generating things like barcodes (where not only the text parts can be rendered with a font that is embedded in the exported file, but also the barcode itself can be created using glyphs of a special font), it is safest to export using EPS format, if available. If possible, the color format should be for print purposes K100 (no C, M or Y). When generating PDF format barcodes, the most compatible format is non-PDF/X-based one that uses lowest possible version number (1.3; as for Affinity apps, 1.4 will also work in all situations) and that is placed to be passed through.

The safest choice, if available, is to specify that all font based elements are converted to curves.

An example of a PDF where the embedded font was not available, but where there were no compatibility issues in context of PDF placement and export:

barcodefonts_missingfont_nocompatibilityproblem.pdf

An example of a PDF whether the embedded font was not available and additionally there was a PDF compatibility issue (placed PDF was v. 1.7 and PDF version used when exporting was 1.4):

barcodefonts_missingfont_compatibilityproblem.pdf 

In both export PDFs the EPS file works without problems.

[Row13]

On 2/2/2023 at 5:52 PM, Alfred said:

How did you install the font? Does it work correctly with other software?

I never installed the font it just came with the barcode. But I changed the barcode font to what was already in the Font Manager and it cleared the error. Thanks for the reply

[Row13]

On 2/2/2023 at 6:30 PM, firstdefence said:

9798218148423;9.99.zip 38.75 kB · 0 downloads

 

Appreciate it!

[Row13]

11 hours ago, lacerto said:

When using embedded fonts, Affinity apps basically behave in three ways:

1) When the font is embedded in a PDF file and the file is placed to be passed through:

• The embedded font will be passed through unless there is a PDF compatibility issue, whether the font is available on the system where export happens or not.
• If there is a compatibility issue (e.g. the placed PDF uses PDF version 1.7 and the file is exported using a lower version, like when exporting using PDF/X-based methods),  the conflicting parts will be rasterized and color values reinterpreted and/or the embedded font will be replaced.

2) When the font is embedded in a PDF file and the file is placed as interpreted:

• If the embedded font is installed on the system and the font is correctly mapped, the parts using the embedded font will be correctly rendered and exported.
• If the embedded font is not installed or not correctly mapped, a replacing font will be used.

3) When the font is embedded in an EPS file:

• The font will be converted to curves whether the embedded font is installed/available or not.

When generating things like barcodes (where not only the text parts can be rendered with a font that is embedded in the exported file, but also the barcode itself can be created using glyphs of a special font), it is safest to export using EPS format, if available. If possible, the color format should be for print purposes K100 (no C, M or Y). When generating PDF format barcodes, the most compatible format is non-PDF/X-based one that uses lowest possible version number (1.3; as for Affinity apps, 1.4 will also work in all situations) and that is placed to be passed through.

The safest choice, if available, is to specify that all font based elements are converted to curves.

An example of a PDF where the embedded font was not available, but where there were no compatibility issues in context of PDF placement and export:

barcodefonts_missingfont_nocompatibilityproblem.pdf 1.35 MB · 0 downloads

An example of a PDF whether the embedded font was not available and additionally there was a PDF compatibility issue (placed PDF was v. 1.7 and PDF version used when exporting was 1.4):

barcodefonts_missingfont_compatibilityproblem.pdf 1.34 MB · 1 download  

In both export PDFs the EPS file works without problems.

thank you much for all the info!

[Alfred]

10 hours ago, Row13 said:

I never installed the font it just came with the barcode. But I changed the barcode font to what was already in the Font Manager and it cleared the error. Thanks for the reply

If you didn’t install the font, it isn’t hugely surprising that the app reported it as missing when trying to use it!