Use of special characters (ÄÜÖ) in receipt examples#1184
Open
rottifant wants to merge 1 commit into
Open
Conversation
|
You are adding a issue on that example, |
Owner
|
It's a fair point though that the example shows a way to align data that only works correctly for ASCII. I'll leave this PR open for now - I'm open to including presentation of tabular data in the scope of library, it's a common theme on the bug tracker and it's easy to get it wrong. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Up to now, if special characters such as ÄÜÖ were used in the receipt examples, there were problems with the distance to the margin.
It looked like this:
With function utf8_decode before str_pad so that the margin is calculated "correctly" and utf8_encode after it, it works as it should:
(The printer I use is the Epson TM-T88IV)