Why do you have no budget?

hhp

Well its just the TTF I'm after, not a software package

Oh, I thought there was a $100 barcode font you couldn't afford.
There must be a font-only solution that's less expensive.

hhp

Well thats what I was thinking, its just a font!!

For single or a few barcodes there are online resources that will generate them — mostly as png or pdf. Wide selection of code-types available.

(There is a reason why barcode-generators consist of more that just the font — verification is guaranteed when you use an app. I am talking about the checksum digit.)

I know about the double checksums on the Code93, I really need this as a font as it'll be used more than a few times,

Thanks,

So you want the checksums pre-calculated inside the font?

No I can do that from within VBA/Foxpro before the string of text is made a barcode

Has no one at all got a source/copy of a decent code93? :-(

Have you tried Morovia's version?

http://www.morovia.com/fonts/code93/

What do you mean by "copy"?

hhp

A working version they could upload somewhere

What if it's a commercial product?

hhp

Chris. A font won't do it, since there are several ways to encode the font en for placing the extra functions for code 93.
And if you can afford a labelprinter like this, then why not pay for good functioning software...

Not sure what your programing skill is, but here is coding to produce it in PostScript:
http://code.google.com/p/postscriptbarcode/wiki/Code93Ext

For someone that can program, there is GNU Barcode; to compile the sources on my mac, I had to comment out the line int streaming; in the file barcode.h and then add the line int streaming; (say just after #include barcode.h) in the files main.c and sample.c as well as the line extern int streaming; in the file pcl.c; then executing ./configure and make gives the binaries.

Here is the output of barcode -h

GNU barcode 0.99 is a tool to convert text strings to printed bars.

barcode: Options:
   -i      input file (strings to encode), default is stdin
   -o      output file, default is stdout
   -b      string to encode (use input file if missing)
   -e      encoding type (default is best fit for first string)
   -u      unit ("mm", "in", ...) used to decode -g, -t, -p
   -g      geometry on the page: [x][++]
   -t      table geometry: x[++]
   -m      internal margin for each item in a table: [,]
   -n           "numeric": avoid printing text along with the bars
   -c           no Checksum character, if the chosen encoding allows it
   -E           print one code as eps file (default: multi-page ps)
   -S           print one code as svg file (default: multi-page ps)
   -P           create PCL output instead of postscript
   -p      page size (refer to the man page)
   -s           streaming mode (refer to the man page)

Known encodings are (synonyms appear on the same line):
	"ean", "ean13", "ean-13", "ean8", "ean-8"
	"upc", "upc-a", "upc-e"
	"isbn"
	"39", "code39"
	"39ext", "code39ext"
	"128c", "code128c"
	"128b", "code128b"
	"128", "code128"
	"128raw"
	"i25", "interleaved 2 of 5"
	"cbr", "codabar"
	"msi"
	"pls", "plessey"
	"code93", "93"
	"code11", "11"
Mail bug reports and suggestions to <bug-barcode@gnu.org>.

I'm afraid it would probably need to be a true type font to work with our kit,

The label printers are second hand from other companies and we already have those so they don't really cost anything,

Do you mean will this be used in a commercial product? No, we don't plan to sell it on! If you mean does someone have it as part of a commercial product that's what I'm trying to locate online! :-)