Assistance With Label Using Code 128
Hello, I was asked to design the following label with specific requirements and I'm having a hard time figuring out how to fix a few things.
The version I'm using is 9.2 SR2.
This is how the label has to look:
[attachment=973:2014-06-10 12.59.06.jpg]
The first issue is with using CODE 128 B for Weight. For some reason when I add the (320) code for weight and 50lbs for weight, the label adds leading zeros. I can't seem to figure out how to get rid of them and the label bar code has to read as 3200500 instead it reads as 3200000500.
[attachment=974:Screen Shot 2014-06-10 at 1.00.44 PM.png]
I would appreciate if someone could point me on the right direction.
Second issue would be the X-Dimension stated at 6.06 cpi but BarTender shows mils instead of cpi. Should I follow the number that says density and use that as my cpi number?
Third issue would be the date:
- The label has to display the Maximum Durability Date as (17)05092007 and I can't seem to find a way to make it 4 digit year instead of 2.
I downloaded the trial version of Bartender 10 to see if that helps solve my problem. If anyone could help me out I would be ok with moving forward and updating to a full version of 10 if required.
-
Hello Msada,
1. Could you please clarify if you wish to use a plane Code 128 barcode or if you wish to apply the GS1 standard to it? If the latter, the (320x) Application identifier (AI) is limited to having 6 digits, nothing more and nothing less. That's a GS1 specification and cannot be changed.
*You could instead "hide" the extra characters only in the human readable using a "Character Template" (only available on v10.1), but those leading zeros will always be encoded.
2. Barcodes in BarTender are not measured in cpi (characters per inch) but using the X Dimension and/or their density (which is closely related to the X dimension).
When talking about barcodes, the X dimension refers to the width of the narrowest unit in a bar code. Wider elements in the bar code (typically, bars or spaces in the bar code) are then measured as multiples of the X dimension. Therefore, the X dimension correlates directly with the overall width of the bar code.The available values for X dimension rely on the resolution and type of printer that is being used. The options available for a 300 dpi (dots per inch) printer will differ from those of a 2400 dpi printer, due to the size of dots that are printed. The higher the dpi value is, the smaller the narrowest unit in a barcode will be, and you’ll be able to change the total width of the barcode in smaller “steps”.The X dimension is used to determine the density of a bar code, which defines how many characters can be encoded per inch of bar code. When you decrease a bar code's X dimension, you increase its density; furthermore, if you increase the X dimension, you effectively decrease its density.One factor controlling the density of a barcode is its symbology. Different symbologies require different numbers of bars and spaces to represent the same information.3. Regarding the (17) AI I've used the GS1 Application identifier wizard to design it and by default I get a two digit year value. Note that on v10.1 it's easier to specify the date format of a data source than in older version, but you should still be able to do so.Did you use the wizard to design the barcode?For more information on the GS1 Application identifier wizard please read the below white papers,.Regards0 -
Fernando thank you for your reply and very well detailed info.
I have version 9.2 and will need to stick with it for now, but I can't seem to make it work for (17) GSI Application Identifier and 4 digit year. All I get is 2 digit year.
Is it possible to run a script to allow 4 digits?
I tried both using the wizard and doing it manually, but can't seem to make it work.
Any suggestions?
0 -
Hello msada,
You should certainly be able to force the format of that precise Application Identifier (AI), but that would break the GS1 standard.
In any case, you should be able to access the date data source and change the format of the date. On version 10.0 and later you can manually enter the appropriate format (though a custom one).
On earlier version you might want to enter the "More Options..." dialog and add an "OnProcessData" script to adapt the script to your requirements.
Regards.
0
Please sign in to leave a comment.
Comments
3 comments