Barcode Fonts
Evelina Kealohanui
ConnectCode Free Barcode Fonts is a generous barcode package that offers three robust barcodes commonly used - Code 39 , Industrial 2of5 and Postnet. This package enables the creation of compliant barcodes for mailing labels, products tagging, inventory control and supply chain management.
The versatility of using fonts allows barcode generation to be integrated into any software that supports text input and font selection. Moreover, when a font is printed, it rasters to the resolution of the printer and will not be limited to the DPI (Dots per Inch) of the computer screen. This behavior provides users with barcodes of the highest resolution in a given environment.
The fonts package also includes the following:
- an Encoder for converting raw data into barcodes;
- Visual Basic macros for generating barcodes in Excel/Word/Access; and
- a command line (or console) application for generating barcodes in scripts or third party applications.
- TrueType
- Open Type
- Type 1 Postscript (Windows pfa)
- Type 1 Postscript (Unix pfb)
Barcodes Supported
Code 39 is one of the earliest and most popular barcode. It supports numbers, uppercase characters and several punctuation characters.
Industrial 2of5 is a widely used barcode for encoding numbers. It is called 2of5 because the barcode is always encoded with 2 wide bars and 3 narrow bars (total of 5 bars). Each of the bars is separated by a narrow space.
Postnet is a fixed width/height barcode that is used widely by the U.S. Postal Service. It encodes numeric digits by using 5 bars and 4 spaces. The bars have two different bar heights, short and tall.
Industrial 2of5 Barcode
Code 39 Barcode
Quick Start Videos on creating barcodes
- How to create a Code 39 barcode in Excel?
- How to create a barcode in Word?
Tutorials
- How to create a barcode with Rust using fonts?
My first step when working with fonts is to make sure that it works on the server side first. So, with SSRS (as an example), I log into the SSRS server and browse to the report webpage and verify I can see and print the fonts as expected. Then I try to find a workstation where I am an admin on and test it from there. Being an admin is not a requirement, but it makes troubleshooting easier. Then I repeat on an end user machine.
If I remember right, with one of the more recent windows 10 updates, fonts can be installed at the per-machine level or per-user level. If you or your IT team is installing fonts from their account on the workstation, it is likely installing at the user level with the user being the IT person. Something to try is to pick a specific end user who is having issues and have them navigate to C:\WINDOWS\FONTS and see if they can see the barcode font.
If you run into problems at any of the steps above, I would check C:\windows\fonts to make sure the barcode font exists in that folder for the user having issues. If it doesn't, they will need to get the font installed.
Printing from a web application is something that is done client side, not server side, so for that the font needs to be installed on the workstation for the user attempting to print. Rendering depends on the application and some render using server-side fonts (preferred way as you can change fonts without affecting the user experience) while others render client side.
Thank you very much for the thorough response; not used to getting a lot of help when it comes to SSRS. My understanding was that the barcode was embedded in the report, and that the .PDF export should support that. Users *are* able to view the barcodes when exporting to MS Word, but unfortunately word doesn't import the report formatting for label sheets. We've installed the font on the server and workstation both on a by-user basis with no success, and are currently working with the IT team to get it installed for all users (since Server 2016 doesn't appear to support the 'install for all users' functionality).
Fonts are a PAIN in the behind in my opinion. We have a few reports on SSRS that have barcode font (3-of-9 font barcodes), but we print out a physical sheet from workstations which generally looks identical to what is on screen. This is why I was thinking printing to PDF MAY work better than exporting to PDF.
I need to create labels in Microsoft Word 2010 with numbers encoded as barcodes. The barcode's format (ean, code39, upc, etc) does not matter. I have downloaded a barcode conversion font that I found at this site.
When I type the number that I want and then I format it with my new font, it produces a barcode. I then print it on an OKI laser printer (1200 dpi). The result seems to be fine, at least for common people.
But, when I try to scan it, nothing happens. I tried both with a barcode scanner and a data collector, but neither of them read the barcode. My barcode scanner is working fine, because I can read commercial barcodes printed on products.
To reinforce what others are saying you need to understand the defined format for the type of barcode you are trying to print. For example Code 128 requires a START and STOP character as well as a CHECKSUM. If you have not included these as part of your data string then the barcode scanner will not make any sense of your barcode. Some other things to consider with barcode fonts are -
I recently upgraded the printer to an HP LaserJet Enterprise M608, but it doesn't seem to be recognizing the fonts. When I print my reports, the regular text looks normal, but the barcode fonts are erroneous characters.
If you use the test print function on the printer, does the PCL font test show the barcode fonts? If not then the usb is likely being recognized. Where are you plugging in the usb stick? You may need to get a B5L28A internal usb kit for the printer. Also make sure that if you are plugging into the external ports that you have host usb enabled.
Now I need to add a Code 39 barcode to my documents. A font TTF file was provided to me by the third party that will be reading the barcode. On my local PC, I installed the font and it displays correctly in MS Word. However when I save my document to PDF using Aspose, instead of the barcode font, the text displays in what looks to be Adobe Sans MM font.
Thanks for the quick response. Perhaps I simplified my example a bit too much. The part that's not displaying the barcode font is a mail merge that returns the PDF to the browser as a byte array. I'm using Doc.Save, but as a memory stream so my web service can pass a byte array back to my web page. Everything else in the mail merge works fine, it's just the barcode displays the literal text *SIC1* instead of the barcode.
I'm now trying to tackle the reason why I can't use EmbeddedWholeTTF := false when using barcode fonts.
I already found this topic but the suggested hack to set isSymbolFont to true for that font doesn't work for me.
=6197
*) First one little question. Embedding partial fonts (even fonts that work correctly like 'Segoe Script') are marked as "Embedded" and Encoding "Ansi" in the PDF. When I create this PDF with another creator I get "Embedded Subset" and encoding "Built-in". Could it be that subset embedding and/or encoding 'flag' isn't set correctly?
*) Then the barcode font. When using EmbeddedWholeTTF := true it works perfectly. When using EmbeddedWholeTTF := false I get blocks for Code3de9 and Code128. The KIXBarcode and SegoeScript work correctly. (but as stated below, all are marked as "Embedded" without the word "Subset" and all are encoding "Ansi".
Where can I look to debug this problem. Embedding the barcodes fully doesn't add much to the PDF but for SegoeScript it does. For what fonts is isSymbolFont to be set (what's it used for)? (But as stated, forcing this to true doesn't work for me)
Edit: Looking at pdffonts from xpdf-tools you see that for Ghostscript (Temp0.pdf) the fonts are embedded but also Subsetted and Unicode.
Subsetted codes need to be proceeded by 6 random character followed by a + sign.
The fonts in Temp1.pdf from SynPdf are not marked as subsetted and are also not embedded as unicode.
Maybe it doesn't really matter (it seems to work fine) but I reckon this is not strict according to the rules
Edit: Probably false alarm. Via another stream debugger I see 4 fonts of which the SegoeScript is the largest one.
So Tahoma should not be embedded (and pdftops probably extract the local Windows font into the ps).
You can ignore this post.
I also made en effort to mark embedded subset fonts correctly in a PDF. Subsets need 6 random uppercase character plus a + sign in front of the name according to the official documentation. I'll also post this in a separate topic.
We are using our customer's SAP portal and they have supplied us with an HP printer that has a .PCL barcode file for SAP (Code 39 I think). When printing to our Xerox 5855 machines this barcode doesn't print. I have tried using the font download utility to send the .PCL font file to the 5855 and although the app says the font downloaded successfully the barcode still doesn't print out. Can anyone offer any insight on how to get this to work?
EPSON Code39
- Four Code39 fonts are available, allowing you to enable and disable the automatic insertion of check digits and OCR-B.
- The height of the bar code is automatically adjusted to 15% or more of its total length, in conformance to the Code39 standard. For this reason, it is important to keep at least one space between the bar code and the surrounding text to prevent overlapping.
- Spaces in Code39 bar codes should be input as "_" underbars.
- When printing two or more bar codes on one line, separate the bar codes with a tab, or select a font other than a BarCode Font and input the space. If a space is input while a Code39 font is selected, the bar code will not be correct.