Zint Barcode Generator / Tickets / #72 PDF 417 command line and UTF 8 encoding

Robin Stuart - 2017-10-05

Hi,

I'm afraid I have been unable to duplicate this problem. From your data Zint will automatically select ECI 4 (corresponding to ISO 8859-2). If you want to force the symbol to use UTF-8, which is slightly less efficient, you can set --eci=26. Either way the bigger problem is likely to be that most scanners don't process ECI codes. I suspect some experimentation may be required to get the data into a format your scanner will accept.

Robin.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Siniša Sudec - 2017-10-05
  
  Thanks,
  
  Which parameters are specified to get the same barcode as the GUI, because the barcode is printed over the GUI (default parameters,nothing special), the scanners read.
  and over the CLI can not
  
  Command line:
  zint -b55 -o "c:\artsoft\barcode.png" -i "c:\artsoft\barcode.txt"
  
  Can you specify line in CLI looks like a barcode print as in a GUI, input file is pure ANSI without UTF special codes.
  Thanks in advance
  
  Siniša
  
  From: Robin Stuart
  Sent: Thursday, October 05, 2017 7:46 AM
  To: [zint:tickets]
  Subject: [zint:tickets] #72 PDF 417 command line and UTF 8 encoding
  
  Hi,
  
  I'm afraid I have been unable to duplicate this problem. From your data Zint will automatically select ECI 4 (corresponding to ISO 8859-2). If you want to force the symbol to use UTF-8, which is slightly less efficient, you can set --eci=26. Either way the bigger problem is likely to be that most scanners don't process ECI codes. I suspect some experimentation may be required to get the data into a format your scanner will accept.
  
  Robin.
  
  [tickets:#72] PDF 417 command line and UTF 8 encoding
  
  Status: open
  Milestone: 1.0
  Created: Tue Oct 03, 2017 07:32 PM UTC by Siniša Sudec
  Last Updated: Tue Oct 03, 2017 07:32 PM UTC
  Owner: Robin Stuart
  Attachments:
  
  a.. barcode.txt (204 Bytes; text/plain)
  The difference in encoding UTF 8 between the ZINT command line and the ZINT GUI, the same input file BARCODE.TXT, different results. How to get the ZINT command line the same result as through ZINT GUI. Which parameter --eci= ??? to put...?
  Thanks in advance...
  
  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/zint/tickets/72/
  
  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
  
  alternate
  
  barcode.txt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robin Stuart - 2017-10-06

Hi Siniša,

Thanks for your further explanation - I see what is happening now. Your input data file is Windows formatted i.e. it has CR/LF line endings. When picked up by the GUI this is being converted to UNIX style line endings. I will have a look at changing the GUI to preserve the formatting of the input data. In the meantime I suggest you continue to use the CLI.

Thanks,

Robin.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robin Stuart - 2017-10-22

Hi Siniša,

I have now added code which detects and preserves CR/LF line endings (and a few other control characters) in the GUI. With the latest version of the code you should find that the GUI and CLI give you identical results, in both cases preserving your data in the original format.

If you could get back to me and confirm this is working as expected when you get a chance to run the amended code it would be appreciated.

Thanks,

Robin.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Siniša Sudec - 2017-10-22
  
  OK thanks.
  I use CLI mode.
  It helped me when you said that the fields should be separated by LF rather than CR / LF, and since I did so, the scanners now read the code without any problems.
  
  Thank you again for help,...
  
  Bye,
  
  Siniša
  
  From: Robin Stuart
  Sent: Sunday, October 22, 2017 12:02 PM
  To: [zint:tickets]
  Subject: [zint:tickets] #72 PDF 417 command line and UTF 8 encoding
  
  Hi Siniša,
  
  I have now added code which detects and preserves CR/LF line endings (and a few other control characters) in the GUI. With the latest version of the code you should find that the GUI and CLI give you identical results, in both cases preserving your data in the original format.
  
  If you could get back to me and confirm this is working as expected when you get a chance to run the amended code it would be appreciated.
  
  Thanks,
  
  Robin.
  
  [tickets:#72] PDF 417 command line and UTF 8 encoding
  
  Status: open
  Milestone: 1.0
  Created: Tue Oct 03, 2017 07:32 PM UTC by Siniša Sudec
  Last Updated: Fri Oct 06, 2017 05:17 PM UTC
  Owner: Robin Stuart
  Attachments:
  
  a.. barcode.txt (204 Bytes; text/plain)
  The difference in encoding UTF 8 between the ZINT command line and the ZINT GUI, the same input file BARCODE.TXT, different results. How to get the ZINT command line the same result as through ZINT GUI. Which parameter --eci= ??? to put...?
  Thanks in advance...
  
  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/zint/tickets/72/
  
  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robin Stuart - 2018-06-21

status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

PDF 417 command line and UTF 8 encoding

A barcode encoding library supporting over 50 symbologies.

Milestone

Searches

Help

#72 PDF 417 command line and UTF 8 encoding

Discussion