MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2014

RE: AFPDS Barcodes and size when printed / converted



fixed

Width specifies the width of the narrow bar or space on a 2 width bar code
or the width of the 1 width on a 4 width bar code such as Code 128.
Each Code 128 character is 11 widths wide, except for the stop which is
13.
.208 at 600 dpi 125 pels
Even if your data is pure numeric , Start+ 5 +Check digit + End
(11+5*11+11+13) = 90 widths At 125 pels = 11250 divide by 600 18.75
inches.
We do have a printer that could print it, but it seems excessively large.



William Scott
Advisor, Solutions Engineering
Canon Solutions America, Inc.
5600 Broken Sound Blvd., Boca Raton, FL 33487
www.csa.canon.com
wscott@xxxxxxxxxxxxx
T 561.997.3256 C 561.703.3135






From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/20/2014 04:02 PM
Subject: RE: AFPDS Barcodes and size when printed / converted
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Brad,

I snipped a couple of lines out of the information center BARCODE DDS
page...

*Specify the width (in inches) of the narrow bar/space. It is specified as
an expression of the form (*WIDTH value). For more information on how to
specify expressions, see the DDS Concepts information. The valid values
for the parameter are 0.007 through 0.208.
*Specify the ratio of the wide bar/space to the narrow bar/space. It is
specified as an expression of the form: (*RATIO value). The valid values
for the parameter are 2.00 through 3.00.

The width value defines the MINIMUM WIDTH between bars of the barcode. You
have the maximum width specified on REPORT2. This would cause the barcode
to "stretch out"..

Another interesting tidbit:
"The width and ratio parameters are ignored for the 4234 and 4224 printer
models". Perhaps they print with one of these printer types, which ignore
the width specification, but when printing to AFPDS for HPT, that width
value gets invoked...

Hth,
-Eric DeLong

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Bradley Stone
Sent: Wednesday, August 20, 2014 12:11 PM
To: Midrange Systems Technical Discussion
Subject: AFPDS Barcodes and size when printed / converted

I have an issue I'm trying to help a customer with.

They have 3rd party software that creates reports with barcodes. They
seem to print fine to their printers, but when the Host Print Transform
API is used to convert them to a TIFF, one works fine, and another the
barcode gets "stretched" out very long, outside of the page in fact.

Here is the DDS for each:

REPORT1:

A 11 BARCODE@16 16A POSITION(6.1 1.1)
A BARCODE(CODE128 9 *HRZ *HRI -
A (*WIDTH 0.045) (*RATIO 3.00))



REPORT2:

A 10 NSERBC 10A POSITION(6.0 1.5)
A BARCODE(CODE128 9 *HRZ *HRI -
A (*WIDTH 0.208) (*RATIO 3.00))


Now, in this case REPORT1 converts fine, and REPORT2 the barcode ends up
stretched so big, it doesn't even fit on the page. When I say stretched,
imagine each line in the barcode is 10x thicker than it should be, as well
as the spacing between each line.

I can provide examples if the description isn't enough.

Reading the docs for the *WIDTH keyword it almost seems like it's possibly
working as it should, at least for HPT and the printer where it prints
fine may be ignoring those specifications?

Any ideas? Thanks!

Brad
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact