|
QSA ToolWorks Public Feedback Forum forum home | register | profile | members |search | faq homepage | lost password? | chat room |
| QSA ToolWorks Public Feedback Forum > General Helix Talk > Helix Bar Code Sequencer? | You are not logged in. Login or Register. |
| Pages: 1 |
| Author: | Topic: Helix Bar Code Sequencer? | |||
| JeffNY Posts: 67 Registered: 2003-05-23 |
Hi, I bought the MacBarFont font package from Worth Data (barcodehq.com)...by the way, if you want it for OS 6 to OS 9 (NOT OS X) you better buy it soon, I'm told they are almost out and may dead end the product because they are having trouble moving the Fonts to OS X....Apple says Fonts should be compatible, but they are having problems. You'd think moving PostScript or TrueType fonts would be easy, but...... ![]() Anyway, to use most of these fonts (like Interleaved 2 of 5 or Code 128) you need to sequence the characters for your string of data. MacBarFont actually comes with an OS 9 sequencer....but it just shows the character string to use....not the "formula" it used to arrive at the sequence. ![]() Does anyone have an Interleaved 2 of 5 or Code 128 (or other format) bar code sequencer Helix abacas? Or info on same? Thanks, Jeff - Edited by JeffNY on: Jul 22, 2003 7:36:05 am - Edited by JeffNY on: Jul 22, 2003 7:36:58 am
|
|||
| Dana Barnard Posts: 2 Registered: 2003-07-22 |
Not exactly sure what you mean by a sequencer but, I will pass on my limited experience with CODE 39 barcode fonts. We use Code 39 fonts to generate shippers for several clients in the auto industry. We have to transform our normal shipper info in to Code 39. For example PO#, Quantity, Job#, Weight, etc. Once installed, it is no problem selecting the different bar code fonts but, you might have to experiment with different font sizes to see what the bar code reader can successfully read. In the case of Code 39, we quickly found out that each filed of info needs a character stuck on the front and back to tell the reader to start and stop reading. In the case of Code 39 it is the asterix character "*" Thus each field needed to be run through an abacus that concantenated them. For example: Quantity = 567. 567 converted to Code 39 would not work because it is missing the leading and following asterix. The desired output is "*567*. Therefore for each field I created and abacus that consisted of two "followed by" tiles (and a text tile to convert the quanity to text). I suggest building the abacuses and then testing the output with normal eye readable fonts, then switch to barcode and test with a barcode reader. Hope this helps Dana(' ')- Edited by Dana Barnard on: Jul 23, 2003 2:56:22 pm
|
|||
| JeffNY Posts: 67 Registered: 2003-05-23 |
For everyones information http://idautomation.com/ has a nice Code39 bar code font. The font set includes a variety of sizes (heights) so you can even use them on listing forms where each record on your list may only be a 1/2" or so high (the bar codes I'm printing are about 1/4" high inside a 5/8" high record)....I even have three horizontally per record. You can also vary the point size to reduce their width. Some bar code readers will read these down to 4 point. Think I'm using 9 or 10 point. idautomation has a downloadable demo of this font you can try too....same as the retail font set, but just missing some characters. Just remember to lead and end your string with a "*" They also have a Code128 font set that offers better "compression" but you need to encode your text..... Jeff ![]()
|
| Pages: 1 |
| Lost Password? Powered by UPB Version : 1.8 A script by PHP Outburst |