esc2html output error

[zarafati]

Hi,
I'm trying to convert an ESCPOS binary file to HTML document.
when I run this command: php esc2html.php ascii.bin >output.html
I get errors:

this is the file ascii.bin
ascii.txt

[mike42]

Can you tell me a bit more about how this file was captured, and what type of printer it is for?

Since our expected output is basically "whatever a real printer would do", I sent your file to a real Epson TM-T20II (USB) to see what it looks like:

cat 2019-10-ascii.txt > /dev/usb/lp0

And this was the output:

This approximately corresponds with what esc2text does (the difference in the garbled text appears to be due to the fact that your input uses ESC t, which has no effect in these tools yet, see #61)

$ php esc2text.php examples/2019-10-ascii.txt 
WARNING: Unknown command DLE NUL
WARNING: Unknown command DLE �
WARNING: Unknown command DLE �
WARNING: Unknown command DLE �
WARNING: Unknown command DLE �
WARNING: Unknown command DLE !
WARNING: Unknown command DLE NUL
WARNING: Unknown command DLE A
WARNING: Unknown command DLE @
WARNING: Unknown command DLE !
WARNING: Unknown command DLE NUL
WARNING: Unknown command DLE A
WARNING: Unknown command DLE @
WARNING: Unknown command DLE !
WARNING: Unknown command DLE NUL
WARNING: Unknown command DLE !
WARNING: Unknown command DLE D
WARNING: Unknown command DLE @
WARNING: Unknown command DLE !
WARNING: Unknown command DLE NUL
WARNING: Unknown command DLE !
WARNING: Unknown command DLE D
WARNING: Unknown command DLE @
WARNING: Unknown command DLE 
WARNING: Unknown command DLE NUL
WARNING: Unknown command DLE �
WARNING: Unknown command DLE �


@┬Ç├╝@?├╛C┬Å├Ç├░?├╝?├ú├░bD@üüDA┬êÇä2├ÇD ├üD DD┬ÇD DB DDD AB@$DD┬îl├â├Ç7├░├á D@$Dpp├╝┬É┬Ç┬Ç ┬ÇD @ ┬ÇD @ ┬Ç┬Ç┬Ç┬Ç

Your input file is not understood by a real ESC/POS printer, so I think that the output is as good as can be expected.

I did find some problems with how we handle errors in esc2html - it crashes due to a malformed image command instead of presenting the same text in a HTML page. That's certainly a bug, but I've raised a separate issue for it (#66), because it's sort of incidental to your problems here.

[mike42]

I'm also assuming that this is a follow-up to #62, so I've closed that off.

I don't know how you're capturing your files, but if a real printer can't understand them, then these tools won't do any better.