Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In testing I've found that ZPL printers are very reliable at telling you they are ZPL printers. Since we can reliably detect them and shortcut to ZPL detection, it's more time-consuming to query an EPL printer for ZPL features. I was initially okay with this, but then I ran into my latest problem child printer.
I have a printer here, standard ELP LP2844 with the latest firmware, which prints "ERR01" if you send it a ZPL command. No clue why. Settings appear normal. If you only send it EPL it's happy as a clam.
So, given that ZPL machines can be reliably detected and EPL machines can't, and there's a non-zero number of EPL machines that throw a fit when you try to talk ZPL at them, it makes sense to default to EPL first.
Who wants to bet CPCL throws a fit if you try to talk EPL or ZPL at it and I'm going to have a barrel of fun doing this autodetection in the future?
Bumps RC8.