> Might be overkill too, I guess. I AM an overkill kinda guy...
> but you knever know- EAN128 could be just around the corner... ;]
Actually EAN-128 is an improper name for GS1-128 which is a standard within
the "Code 128" standard which like 3 of 9 allows the full ASCII character
set to be encod
On 1/24/07, James Smith <[EMAIL PROTECTED]> wrote:
> EAN-8 is easy using 2 functions I wrote...
Holy crap! What's code doing on this list? LOL.
(I've read some of the archives... community changes, neh? :)
Thanks for posting the functions, James. Made it super
clear.
H
> Am piqued as to how you've used CF to do it tho- surely not
> using HTML?
EAN-8 is easy using 2 functions I wrote...
if (len(trim(barcode)) GT 7) {
return "Error: To many digits";
On 1/23/07, James Smith <[EMAIL PROTECTED]> wrote:
> > I thought only code 39 was "fontable". Don't you need
> > special SW to do the checksums and such for the others?
>
> EAN-8, EAN-13 and UPC are all "fontable", you do need to calculate
>
> I thought only code 39 was "fontable". Don't you need
> special SW to do the checksums and such for the others?
EAN-8, EAN-13 and UPC are all "fontable", you do need to calculate
checksums, and even then the digits to the left and right of the centre use
at lea
On 1/22/07, James Smith <[EMAIL PROTECTED]> wrote:
>
> I have been using a truetype font to produce EAN-13 barcodes for some time
[...]
I thought only code 39 was "fontable". Don't you need special SW
to do the checksums and such for the others?
I have been using a truetype font to produce EAN-13 barcodes for some time
now with great success, I now have a need to produce some EAN-8 barcodes and
unfortunately even though the characters are the same my EAN-13 font won't
work due to my EAN-13 font encoding the left hand guide bars a
